From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] problem when running the bootm command
Date: Tue, 23 Oct 2007 17:14:41 -0400 [thread overview]
Message-ID: <471E6441.2060501@ge.com> (raw)
In-Reply-To: <7fd1eb680710231357o760cc9efr7c3f1384862198f4@mail.gmail.com>
Erez Koelewyn wrote:
> Hi,
>
> I am using the M5282EVB configuration. I have come across the
> following problem: I load a compressed linux image into address 400000
> (I leave enough
> room for it to be decompressed at address 100000).
> I then run -> bootm 400000
> This works fine (the image is decompressed at address 100000 and runs
> correctly).
>
> Now I reset the board, download the compressed image again (using
> iminfo to very it's header is there and correct) and again I run ->
> bootm 400000
>
> This time I get an exception (this happens consistently until I
> program U-Boot again into FLASH, at which time I can again use bootm
> successfully only once):
>
> -> bootm 400000
> ## Booting image at 00400000 ...
> Image Name:
> Image Type: M68K Linux Standalone Program (gzip compressed)
> Data Size: 1249874 Bytes = 1.2 MB
> Load Address: 00100000
> Entry Point: 00100000
> Verifying Checksum ... OK
> Uncompressing Standalone Application ...
>
> *** Unexpected exception ***
> Vector Number: 3 Format: 04 Fault Status: 4
>
> PC: 00fe5d48 SR: 00002704 SP: 00f9155c
> D0: 00000000 D1: 00000000 D2: 00000000 D3: 0000011a
> D4: 00000000 D5: 00000000 D6: 004000d8 D7: 00fa1f90
> A0: 00000009 A1: 00fac8e0 A2: 00fa28e0 A3: 00f91afe
> A4: 00fa2928 A5: 00ff7600 A6: 00f91ad4
>
> *** Please Reset Board! ***
>
> The problem cannot e related to overwriting critical areas in RAM
> because I don't overwrite U-Boot's region or the region where I store
> the packaged image.
>
> Did anyone come across this problem
>
> Thanks,
> Erez
I'm clueless but that never stopped me from guessing. ;-)
It sounds like your linux image is scribbling in flash, messing up
u-boot (but not fatally). Do you have a flash file system configured in
your linux image? Any other reason your linux image would overwrite
flash? If you dump the end portion of the *flash* u-boot image before
and after the successful linux boot, does it show corruption?
If that isn't the problem the follow up question is: what is the
unexpected exception vector number 3, what is the meaning of the PC
(where the exception occurred), what does the stack tell you when you
dump it?
Good luck,
gvb
next prev parent reply other threads:[~2007-10-23 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 20:57 [U-Boot-Users] problem when running the bootm command Erez Koelewyn
2007-10-23 21:14 ` Jerry Van Baren [this message]
2007-10-24 2:50 ` Erez Koelewyn
2007-10-24 14:34 ` Erez Koelewyn
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=471E6441.2060501@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.de \
/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