Last week i have reactivate my cube. The last nylon image with functioning iptables is 1.0 from October 2005.
Today i find out that Kamikaze support the cube. Now i like to reflashing my cube with the image for this.

Now i have 2 questions about the images:
1. What is the difference between the 128k- und the 64k-image?
2. Can i reflashing my cube from nylon like install-image or i must use the serial cable and tftp?

thanks for answers
tobolff

1. i don't know, i use 128k
2. you need to use tftp with serial attached for controlling yamon

this is how i reflash, using minicom and serial
the device is 1.1, my laptop running atftpd is 1.2
the image called cubeimage and is placed under /tftpboot on my laptop

here the minicom log:
YAMON> setenv start "go 0xbfd00000 root=/dev/mtdblock0"
YAMON> setenv bootserver 192.168.1.2
YAMON> setenv ipaddr 192.168.1.1
YAMON> erase 0xbfd00000 0xf0000
what...
The following area will be erased:
Start address = 0x1fd00000
Size          = 0x00100000
Confirm ? (y/n) y
Erasing...Done
YAMON> erase -s
Erasing...system...
Done
YAMON> setenv
MAC         (R/W)  0
bootfile    (R/W)  vmlinux-mtx.srec
bootprot    (R/W)  tftp
bootserport (R/W)  tty0
bootserver  (R/W)  192.168.1.2
cubeID      (USER) 730
ethaddr     (R/W)  00.0e.56.00.02.da
gateway     (R/W)  0.0.0.0
ipaddr      (R/W)  192.168.1.1
memsize     (RO)   0x04000000
modetty0    (RO)   115200,n,8,1,none
modetty1    (RO)   115200,n,8,1,none
prompt      (R/W)  YAMON
start       (R/W)  go 0xbfd00000 root=/dev/mtdblock0
subnetmask  (R/W)  255.255.255.0

YAMON> ping 192.168.1.2
64 bytes ICMP-ECHO-REPLY user data received from 192.168.1.2
YAMON> load /cubeimage
About to load tftp://192.168.1.2/cubeimage
Press Ctrl-C to break
...............................................................

after that you simply type $start or powercycle

regards ulf

(Last edited by ulf_k on 3 Jun 2007, 20:38)

Cool, big thanks ulf_k

Looks like the standard tftp procedure only with the openwrt-image.

tobolff

(Last edited by tobolff on 3 Jun 2007, 21:53)

right, i only needed to change .../mtdblock/0 of .../mtdblock0

The kamikaze build process generates a number of images:

openwrt-au1000-2.6-jffs2-128k.fs
openwrt-au1000-2.6-jffs2-128k.img
openwrt-au1000-2.6-jffs2-64k.fs
openwrt-au1000-2.6-jffs2-64k.img
openwrt-au1000-2.6-vmlinux.bin

Your description below seems to refer to the filesystem image. Is this correct?
How do you install the kernel image?
The Meshcube-Wiki indicates that the vmlinux image should be in SREC format as well, which openwrt-au1000-2.6-vmlinux.bin is not. Did you convert the kernel image?
How?
Should this be part of the build process?
The Meshcube-Wiki makes a distinction between Flash and RAM kernel images. What kind is the openwrt image?

Thanks in advance
  Joerg