This is the mail archive of the ecos-discuss@sourceware.cygnus.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: i386 rom image


>>>>> "Ranj" == Talia Sound and Vision P/L <jtalia@ozemail.com.au> writes:

    Ranj> Our platform is an AMPRO PC-104 Coremodule, which has a
    Ranj> socket for an EPROM. I was thinking of leaving the BIOS to
    Ranj> do the hardware initialization and use the BIOS extension
    Ranj> facility (which is run after initialization) to run a little
    Ranj> bootloader (located at the start of the EPROM) which will
    Ranj> copy the application/eCos code (also in the EPROM) to RAM
    Ranj> and then run it. Will this work?

It sounds like it should work, but I have no experience with this
hardware. You may still need to worry about the state of the processor
and the various devices at the point that the bootloader switches to
the eCos application. Since you control both the bootloader and the
eCos startup code (in fact they could be the same thing), this should
not pose a major problem. The floppy bootstrap code may provide some
useful hints.

    Ranj> What changes are needed in the linker script?

Basically you need to figure out where the code and static data are
going to end up, and set up the memory sections accordingly. Again,
look at some of the existing code plus the linker documentation for
more details.

Bart Veer // eCos net maintainer

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]