That image may *not* work on your hardware. Like I said, it's tailored to the EB40 environment and expects to run from the top 1/2 of the FLASH. The provided image is for a little endian system, so the 0xEA comes in byte 3. 0x000000 0e 00 00 ea 18 f0 9f e5 18 f0 9f e5 18 f0 9f e5 |...ê.ð.å.ð.å.ð.å| 0x000010 18 f0 9f e5 00 00 00 00 18 f0 9f e5 18 f0 9f e5 |.ð.å.....ð.å.ð.å| On 24-Aug-2001 Simon wrote: > Hi Gary, > Thanks for your reply. But the redboot.bin from e7t package seems not to > work. I have to mention at first that I program the flash via JTAG port, and > download via serial port. I have inspected the redboot.bin and found that > the first word of this binary image is not a "branch" instruction like > 0xEA..... > Any suggestion? Or does anyone know how to solve this problem? > Simon > > ----- Original Message ----- > From: "Gary Thomas" > To: "Simon" > Cc: > Sent: Friday, August 24, 2001 10:23 AM > Subject: RE: [ECOS] How to build RedBoot for S3C4510 > > > > On 24-Aug-2001 Simon wrote: >> Hi all, >> Does anyone know how to build a RedBoot for S3C4510? I wanna this >> redboot image to be programmed into the flash memory and make the whole >> system boot from it. I know the chip is used on ARM's E7T board, and there >> is a package for this board in eCos. But it seems it does not replace the >> original bootloader in this board. >> So...does anyone know how to build a pure redboot which is executed at >> first atfer power on? > > Actually, the RedBoot in that package does replace the original code in > function (i.e. only RedBoot runs from reset). This is an artifact of how > the hardware is wired up on the board - there is a switch to decide how > the FLASH is mapped. > > You should be able to take the at91/eb40 package and modify it to suit > your needs. Everything should be in there. Note however that the released > code is somewhat hardwired to that particular configuration. You may need > to adapt it to your hardware.