u-boot 1.3.x and qemu-openmoko

andrzej zaborowski balrogg at gmail.com
Wed Jan 16 21:36:36 CET 2008

On 16/01/2008, Werner Almesberger <werner at openmoko.org> wrote:
> andrzej zaborowski wrote:
> > Because you can't issue any commands when you're connected to the
> > serial port only.
> Sure, but you could just switch this through the boot menu, or connect
> via usbtty.
> Are you talking about breaking flashing in general or some specific
> process ? Seems that there's some context missing :-)

I'm talking about devirginizer only, sorry if that wasn't clear.
Devirginizer is a script (or at least was one year ago when I looked
at it) so it has no access to things like menu. AFAIU it loads the
u-boot into memory through JTAG, then instructs the CPU to jump to
u-boot entry point through JTAG and expects u-boot to now wait for
commands on the serial port - qemu flash.sh script does the same. Then
to flash an image to NAND, it loads it into RAM through JTAG and
issues "nand write.jffs2 ..." to u-boot.

Qemu flash.sh could also require the user to go through the menu first
but that's not very pretty.


More information about the openmoko-kernel mailing list