public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Rycerz Roman-G11565 <roman.rycerz@motorola.com>
To: "'Miguel Josue Vega'" <mserrano@engin.umich.edu>,
	Rycerz Roman-G11565 <roman.rycerz@motorola.com>
Cc: ecos-discuss@sources.redhat.com,
	Eric Gregory Castle <ecastle@engin.umich.edu>
Subject: [ECOS] RE: FLASH initialization failed, AM29LV400BB on CME-555
Date: Thu, 03 Jun 2004 00:25:00 -0000	[thread overview]
Message-ID: <5D454811D0A1D711A12A00065BF36FAD08B9DF03@il06exm11> (raw)

Yes...

Both these files have to change to reflect the mapping on your particular platform..

I would start with a clean build.... That is delete the 3 directories 
This should get you going.

Roman


-----Original Message-----
From: Miguel Josue Vega [mailto:mserrano@engin.umich.edu] 
Sent: Tuesday, June 01, 2004 9:20 PM
To: Rycerz Roman-G11565
Cc: ecos-discuss@sources.redhat.com; Eric Gregory Castle
Subject: RE: FLASH initialization failed, AM29LV400BB on CME-555


Hi Roman and ecos list,

(sorry, in previous e-mail I typed RAM instead of FLASH)

Thanks for your advice. My teammate Eric used GDB to confirm that something bad is indeed occuring at address 0xD978. This address is from _mem_copy. The instruction is lbz r1,0(r4) where the contents of r4 is 8e00000(which we suspected to be out of external FLASH range). We found out that the default redboot build has external FLASH mapped from 0x800000 to 0x87FFFF. I think that this might be incorrect since this default mapping applies to when the CME-555 board has 512K of AM29LV200 type memory. Since our CME-555 board came with AM29LV400BB type FLASH, we have double that amount (1M). Does anyone know what kind of changes I have to make to the configuration to take this into account? I have the idea to manually change the memory mapping in the following:

mlt_powerpc_cme555_rom.ldi
mlt_powerpc_cme555_rom.h

Is this a good approach to take?

Thanks,
Miguel Vega
FEGI Team
University of Michigan


On Tue, 1 Jun 2004, Rycerz Roman-G11565 wrote:

> Hi....
>
>
> You shouldn't get the 1st message you did about the "+FLASH: driver 
> init failed: Driver does not support device..." If you truly have 
> removed the flash support... Rebuild Redboot with a fresh set of 
> directories... I.e. delete them.
>
> The other message is that Redboot is barfing on powerup.. 1 trick I was clued in about, is before you power up the board
> Make sure gdb is open and the connection to target started.  When you hit the power, gdb should connect and tell you where it is unhappy.   What it looks like is that is something bad is at address 0000d978
>
>
> Roman
>
>
> -----Original Message-----
> From: Miguel Josue Vega [mailto:mserrano@engin.umich.edu]
> Sent: Tuesday, June 01, 2004 12:05 PM
> To: Roman Rycerz
> Cc: ecos-discuss@sources.redhat.com
> Subject: FLASH initialization failed, AM29LV400BB on CME-555
>
>
> Hi Roman,
>
> We have gotten RedBoot (ROM-startup) to run on our Axiom CME-555 
> board. The board has AMD AM29LV400BB external flash. When we built a 
> default RedBoot build with no FLASH support we get the following 
> message before the startup banner: "+FLASH: driver init failed: Driver 
> does not support device..."
>
> When we configure redboot for AM29LV400 type flash we do not get a 
> startup banner at all, instead we get the following output: 
> "+$T0b40:0000d978;01:00400f2c;#50".
>
> I do not understand why we get the output since RedBoot was configured 
> for the type of flash on the board. Any suggestions?
>
> Thanks,
> Miguel Vega
> FEGI Team
> University of Michigan
>

-- 
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:[~2004-06-03  0:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  0:25 Rycerz Roman-G11565 [this message]
     [not found] <5D454811D0A1D711A12A00065BF36FAD08B9DEFC@il06exm11>
2004-06-02  1:52 ` Miguel Josue Vega
2004-06-02  2:19 ` Miguel Josue Vega

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=5D454811D0A1D711A12A00065BF36FAD08B9DF03@il06exm11 \
    --to=roman.rycerz@motorola.com \
    --cc=ecastle@engin.umich.edu \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=mserrano@engin.umich.edu \
    /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).