On Sun, Aug 24, 2008 at 5:15 PM, Brian Whitman <brian@...> wrote:
>> I also like to test my new u-boot images by downloading them and
>> executing them from RAM. If they don't execute properly, then I don't
>> burn them into flash. If they do work properly, then I redownload,
>> recompare the crc, and then burn the image.
> Do you know how to do that? Say I'm at the stage where I've transfered
> the u-boot.bin over but haven't unprotected the sector or flashed it
> yet. What GUM> commands can I issue to boot the image?
> In other news, a series of miscommunications is likely my problem --
> I've been thinking (and repeating here) that I have a verdex xm-bt
> board, when in reality I've been working on a connex 400xm-bt. When I
> set up the buildroot I chose a verdex type -- which I understand is a
> whole different architecture.
Yeah burning a verdex u-boot on a connex wouldn't be good.
Generally, it goes something like this:
...send your file...
and then do
I've sometimes had to do slightly different things depending on
whether I'm using a verdex or connex, and which exact version of
u-boot is being run/laoded.
Normally u-boot detects that it's not running at it's "correct"
location, and it will relocate itself to the correct location and run
Vancouver, BC, Canada