From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Patrick O'Grady" To: ecos-discuss@sourceware.cygnus.com Subject: Re: [ECOS] i386 rom image Date: Tue, 20 Jun 2000 07:26:00 -0000 Message-id: References: <200006201339.OAA07258@sheesh.cygnus.co.uk> X-SW-Source: 2000-06/msg00205.html Hi, Ranj-- Look and see if the EEPROM can be used to emulate a floppy disk, your system may allow the the prom to be used as a rom-disk. If that's so, then you would only need to write the .bin file into the device. If not, I'm planning on having a bit of time here after next week, so I'm planning on figuring out how to get my FreeBSD development system back up, and since making a ROM image should be really simple, I'll take care of that first. Stay tuned! -patrick On Tue, 20 Jun 2000, Bart Veer wrote: > >>>>> "Ranj" == Talia Sound and Vision P/L 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 >