On Wed, Mar 12, 2008 at 06:09:37PM +0800, venice wrote:
> Hi, everyone, my board is something similar to the public board
> AT91SAM7X256. When I joined the packages "FLASH memory support for Atmel
> AT91 EFC." and "Generic FLASH memory support." the redboot get hints
> like that:
>
> +Sorry, FLASH config exceeds available space in FIS directory
>
> AT91_ETH: Initialising @ fffdc000
> AT91_ETH - Warning! ESA unknown
> AT91_ETH: 12:34:56:78:9a:bc
> AT91_ETH: 10Mbyte/s Half Duplex
> Ethernet eth0: MAC address 12:34:56:78:9a:bc
> IP: 192.168.0.230/255.255.255.0, Gateway: 192.168.0.1
> Default server: 0.0.0.0
> .........................
>
> RedBoot> fis list
> Name FLASH addr Mem addr Length Entry point
> RedBoot>
>
>
> But actually the redboot can write the flash well(I have experimented)
> but I can not use fis init to finish the initialization, neither can I do
> the "fc -i" .
>
> So, is there something wrong in the configuration? I have tried many ways
> but I cannot solve this problem!
Are you using combined FIS and CFG in one flash block? The flash
blocks are too small for this.
> BTW:
> The at91sam7x256 has only 64k ram, but my applications are too big to
> download to the ram and I cannot debug them, so any good idea to fix
> that?
My personal opinion is that using Redboot on these devices does not
make sense. The FLASH and RAM is too small. I would simply use an eCos
ROM application which directly boots without using a boot loader. I
would suggest using a JTAG device to program your application into
FLASH. You are going to need a JTAG device to debug your application
anyway since your application is running from ROM so you need to use
hardware breakpoints, which the gdb stub in RedBoot does not support.
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
