public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: venice <venice.uurg@gmail.com>
Cc: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] AT91SAM7X256--flash can not Initialise?
Date: Wed, 12 Mar 2008 10:24:00 -0000	[thread overview]
Message-ID: <20080312102403.GA30106@lunn.ch> (raw)
In-Reply-To: <28A4FD4E2F85457E9B91E9A99A9D935C@veniceuurg>

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

  reply	other threads:[~2008-03-12 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 10:10 venice
2008-03-12 10:24 ` Andrew Lunn [this message]
     [not found]   ` <6B6125D574D6450EA59CE4808655B339@veniceuurg>
2008-03-12 11:29     ` Andrew Lunn
2008-03-12 11:37       ` Gary Thomas
2008-03-12 11:55         ` Andrew Lunn
2008-03-12 12:07           ` Gary Thomas
2008-03-19  9:38 venice

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080312102403.GA30106@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=venice.uurg@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).