From: Daniel F. <cyb...@cy...> - 2007-09-04 19:55:13
|
For those of you who, like me, has tried an unsuccessful system flash over SSH / ethernet. A small but very important note. You need to pad the rootfs.arm_nofpu.jffs2 to the appropriate size or your filesystem will become corrupt after reboot. Flash space is distributed like this: U-Boot (mtd0) - 256K : 262144 Bytes. Kernel (mtd2) - 1M : 1048576 Bytes. Padding size is FlashTotal - Kernel - U-Boot. Basic / Connex Standard (4MB) : 2883584 Bytes = 0x2C0000 XM Series (16MB Flash) : 15466496 Bytes = 0xEC0000 Verdex XL6P (32MB Flash) : 32243712 Bytes = 0x1EC0000 The padding can be automated by the buildroot build process: make menuconfig Target Options --> [*] Pad Output (0x0) Pad output size (0x0 = to end of EB) [ ] Use sumtool to write summaries to the filesystem Enable "Pad Output" Disable "sumtool" Replace 0x0 "Pad output size" with the hex value, matching your system, from the list above. Finish building the system, and upload according to the Wiki manual. I'm unsure of at what revision you should do this, but I would say > r1482 since that is the one I'm currently working on. Been there, done that, and I learned from my mistakes. /Daniel Frederiksen |