[ECOS] workspace_end_init, workspace_end and flash.c

[Ben Wu]

I've been working to integrate the RedBoot 2.04 Intel IXP42x NPE 
ethernet driver to work with the most recent Ecos code and ran into a 
problem where NPE "workspace" buffers were being overwritten causing the 
boot process to hang.

I've tracked down the problem to the flash code where it allocates it's 
own workspace buffers. Specifically :

 >  workspace_end = (unsigned char )(workspace_end_init - fisdir_size);

In the 2.04 intel fork, the line reads

 >  workspace_end = (unsigned char )(workspace_end - fisdir_size);

why the change? It seems that by doing so the flash init assumes it 
always be called first and assumes any code that needs workspace will 
use the workspace_end pointer rather than the workspace_end_init pointer.

It turns out that the NPE init code is being inserted before the flash 
init code with the same RedBoot_INIT_FIRST priority level. Is there 
anyway to fine tune insertion of initialization routines with a the same 
priority order?


-- 
---------------------------
Ben Wu
Design Engineer
email: bwu@changind.com
phone: (909) 596-7888
CHANG Industry, Inc.
1925 McKinley Ave. Suite F
La Verne, CA 91750

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss