Re: [ECOS] i386 Memory Size Problem

[Nick Garnett <nickg@ecoscentric.com>]

kevin_lemay@agilent.com writes:

> It appears to not be that easy.....
> 
> The BIOS calls may only be made in real mode. Redboot initializes
> the CPU, makes the required BIOS calls and switches to protected
> mode. Then thru TFTP, GDB, etc, loads an application and executes
> it.
> 
> So I would be able to perform the operations in RedBoot.
>

Good point, I hadn't realized that this is what you wanted to do.


> How do redboot and the loaded application work together? I know that
> portions of redboot continue to run. It appears that redboot owns
> the lower 640K of space and applications are always loaded starting
> at the 1MB boundary. I know that the pcmb_misc.c file is run, at
> least, by the application.
> 
> I do not know where to look for a way to pass data between them, but
> it must already been done for them to share CPU for debugging.

The ususal mechanism is via the virtual vectors. The application can
make calls back into RedBoot to do things like serial IO and fetch
things from the flash.

The virtual vector interface is implemented in the hal/common files:
hal_if.h and hal_if.c. 

> 
> I modified pcmb_misc to poke values at the 1Mb boundaries and read
> it back that appear to work correctly. I am having trouble
> envisioning what the proper solution looks like.
> 

The proper solution is probably to add a new virtual vector entry that
allows an eCos app to call the HAL_MEM_REAL_REGION_TOP() macro in
RedBoot.


-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


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