View source for Manually re-flashing the u-boot
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Manually re-flashing the u-boot.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Manually re-flashing the u-boot.
This page explains how you can manually re-flash the bootloader into your Neo1973. It is basically the manual task of what the Devirginator tries to do automatically (but not always works).
So how can we boot from RAM? We use JTAG / OpenOCD to
> reset halt target halted in ARM state due to debug request, current mode: Supervisor cpsr: 0x400000d3 pc: 0x00000000 MMU: disabled, D-Cache: disabled, I-Cache: disabled
> load_binary /space/misc/gta01/u-boot.git/board/neo1973/gta01/lowlevel_foo.bin 0 downloaded 332 byte in 0s 21899us
> bp 0x33f80000 4 hw breakpoint added at address 0x33f80000
> resume Target 0 resumed > Target 0 halted target halted in ARM state due to breakpoint, current mode: Supervisor cpsr: 0x600000d3 pc: 0x33f80000 MMU: disabled, D-Cache: disabled, I-Cache: enabled
> load_binary /space/misc/gta01/u-boot.git/u-boot.bin 0x33f80000 downloaded 135692 byte in 6s 567264us
> resume Target 0 resumed
At this point, the display backlight gets bright and we see the following familiar prompt on the serial console:
U-Boot 1.1.6 (Jan 13 2007 - 23:44:23) DRAM: 128 MB NAND: 64 MiB *** Warning - bad CRC or NAND, using default environment In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 GTA01Bv2 #
Now you have the full u-boot running from RAM, you can use all its drivers and have various options to transfer data into the Neo, such as a new u-boot image for NAND. You can use
FIXME: I'll finish after lunch