Difference between revisions of "Hammer How to Reflash Apex and kernel"
Line 35: | Line 35: | ||
< send apex.bin via xmodem> | < send apex.bin via xmodem> | ||
− | apex> erase nor:0x00+ | + | apex> erase nor:0x00+256k <<<yes this is correct, the 256k is intended to erase the entire block! |
− | apex> copy 0x30008000+ | + | apex> copy 0x30008000+128k nor:0x00 |
131072 bytes transferred | 131072 bytes transferred |
Revision as of 14:06, 4 October 2007
These instructions assume that apex has been configured for a 1024k kernel region
==> Flashing a new kernel:
apex> xr 0x30008000 <=== This is the address that the flash base kernel is copied to by apex on powerup>
< send zImage via xmodem>
apex> erase nor:256k+1024k
apex> copy 0x30008000+1024k nor:256k
1048576 bytes transferred
apex> boot <this will boot the newly flashed kernel with the existing rootfs>
==> Flashing the new rootfs:
apex> xr 0x30800000 <=== This is the address that the flash base rootfs is copied to by apex on powerup>
<send rootfs.arm.ext2.gz via xmodem>
apex> erase nor:1280k+1024k
apex> copy 0x30800000+1024k nor:1280k
1048576 bytes transferred
apex> boot <this will boot the existing kernel with the newly flashed rootfs>
==> Flashing a new apex:
apex> xr 0x30008000
< send apex.bin via xmodem>
apex> erase nor:0x00+256k <<<yes this is correct, the 256k is intended to erase the entire block!
apex> copy 0x30008000+128k nor:0x00
131072 bytes transferred
<then press reset to run the newly flashed apex, do not type boot>