> It's just `load kernel' then `boot'. I'm not sure why you're adding `save kernel'.
I guess I figured that the 'save kernel' step would save the kernel that
I had downloaded to the flash so that I could boot without downloading
it again.
> If you aren't seeing bootldr do an erase cycle followed by
> a successful program & verify after you xmodem your kernel image, then there's a
>reasonable chance that there's no image to load.
Hmmm, yes, I don't ever see the those messages ... I just get:
boot> load kernel
ready for xmodem download..
and then when I initiate the download (with minicom) it succeeds. After
this, I see no response from the assabet, unless I hit enter, at which
point I get a 'boot>' prompt. So I guess my question becomes, why is
the assabet not getting my kernel that I am downloading to it? Xmodem
seems to succeed (from the terminal side, at least).
A slight aside (but maybe important), I am using the terminal at 115200
baud, but the baudrate param in bootldr says 57600 ... what does the
baudrate actually define?
Thanks
-Mike
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
