Re: question with redboot
From: Jonathan Larmour (jiflnews_at_jifvik.org)
Date: Sat, 26 Jun 2004 22:43:03 +0100
eric <email@example.com> enlightened us with:
>I'm now porting the redboot from a EVM board to my target board. However,
>I've changed the flash and it seems doesn't work with my old redboot
>configuration. I can only see the target board send some rubbish out from
>the serial port. I don't know what to do next. I'm actually loading the
>redboot thru a JTAG. In normal case, how does people solve this problem
>since it is tedious to trace the assembly from my windows based debugger?
I know this post is a few weeks old but I've only just seen it. In case
you didn't work it out, there are two possibilities: redboot stores
baud rate configuration information in the flash. If you can erase the
flash entirely first, then RedBoot will pick up that it isn't initialised
(a checksum failure) and will fall back to its default baud rate, whatever
that is for your board.
The second possibility is that the data you are seeing goes something
like $T02:12345678;fedcba98;656536565654#ab or whatever numbers. That's GDB
remote protocol and means redboot has hit a processor exception for
whatever reason and bombed out. One of the numbers will be the PC
register in hex which you can look up in your redboot image or linker
map, or you can attach with GDB to find out in a more friendly way where
it stopped, assuming you have the source tree still around.
-- --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine