Difference between revisions of "Hammer How to Reflash Apex and kernel"

From eLinux.org
Jump to: navigation, search
(Reformatted to look a bit nicer)
Line 1: Line 1:
 
These instructions assume that apex has been configured for a 1024k kernel region
 
These instructions assume that apex has been configured for a 1024k kernel region
  
==> Flashing a new kernel:
+
=== Flashing a new kernel (zImage) ===
  
apex> xr 0x30008000  <=== This is the address that the flash base kernel is copied to by apex on powerup>
+
You'll find the zImage file in the linux-2.6.22/arch/arn/boot directory.
  
< send zImage via xmodem>
+
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>
  
apex> erase nor:256k+1024k
+
=== Flashing a new rootfs ===
  
apex> copy 0x30008000+1024k nor:256k
+
You'll find the rootfs.arm.ext2.gz file in the buildroot/binaries/Hammer directory.
  
1048576 bytes transferred
+
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>
  
apex> boot  <this will boot the newly flashed kernel with the existing rootfs>
+
=== Flashing a new bootloader (apex) ===
  
==> Flashing the new rootfs:
+
  apex> xr 0x30008000
 
+
< send apex.bin via xmodem>
apex> xr 0x30800000 <=== This is the address that the flash base rootfs is copied to by apex on powerup>
+
apex> erase nor:0x00+256k  <<<yes this is correct, the 256k is intended to erase the entire block!
 
+
apex> copy 0x30008000+128k nor:0x00
<send rootfs.arm.ext2.gz via xmodem>
+
131072 bytes transferred
 
+
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>
+
  
 +
then press reset to run the newly flashed apex, do not type boot
  
 
[[category:TCT-Hammer]]
 
[[category:TCT-Hammer]]
 
[[category:TinCanTools]]
 
[[category:TinCanTools]]

Revision as of 03:16, 31 January 2008

These instructions assume that apex has been configured for a 1024k kernel region

Flashing a new kernel (zImage)

You'll find the zImage file in the linux-2.6.22/arch/arn/boot directory.

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 a new rootfs

You'll find the rootfs.arm.ext2.gz file in the buildroot/binaries/Hammer directory.

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 bootloader (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