Re: [ECOS] "Fis init" failed on EB40A

[Andrew Lunn <andrew@lunn.ch>]

On Thu, Jul 28, 2005 at 05:22:32PM +0200, Domenico La Fauci wrote:
> Hi Paul,
>     sorry but I don't understand what you said. Could you please explain me?
> Now I have a new version of Redboot for EB40A that works with all of fis
> commands.
> The problem that I have now is that the RAM version of redboot works
> properly but the ROM or ROMRAM version doesn't start. when the board is
> powered up led D1-D5 are on but no communication the serial line.
> 
> When I tried to load the ROM version in RAM and launch it, this is the
> result:
> 
> RedBoot> fis lis
> Name              FLASH addr  Mem addr    Length      Entry point
> RedBoot           0x01000000  0x01000000  0x00020000  0x00000000
> RedBoot[ROM]      0x01100000  0x01100000  0x00010000  0x02024C00
> FIS directory     0x011F0000  0x011F0000  0x0000F000  0x00000000
> RedBoot config    0x011FF000  0x011FF000  0x00001000  0x00000000
> 
> RedBoot>
> RedBoot> fis load RedBoot[ROM] -b %{FREEMEMLO}
> RedBoot> go

This will not work. eCos is position dependant. The ROM version is
linked so that it runs at the address location the ROM is at. 

Another thing a ROM version might do is setup the RAM controller. With
most processors, setting up the RAM controller when running in RAM
will cause a crash.

So if you want to run the ROM version you need to put it into ROM. I
suggest you have a JTAG flash programmer handy. If your ROM image does
not boot you have a dead board which you can only recover using the
programmer.

        Andrew

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