Hi Bodhi, ok, I tried to update the kernel now. What I did: root@debian:/boot# tar -xjf linux-4.2.0-kirkwood-tld-1-bodhi.tar.bz2 root@debian:/boot# dpkg -i linux-image-4.2.0-kirkwood-tld-1_1.0_armel.deb Selecting previously unselected package linux-image-4.2.0-kirkwood-tld-1. (Reading database ... 11637 files and directories currently installed.) Unpacking linux-image-4.2.0-kirkwood-by Reto - uBoot
No luck, it is not doing anyting after reboot... So back to Debian and upgrade there? How do I upgrade the kernel?by Reto - uBoot
I changed it and then I get: root@debian:/tools# fw_printenv Too few good blocks within range Back to 0x20000 and fw_printenv generates a correct output again... But not with 0x4000by Reto - uBoot
There is a difference... root@debian:/tools# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 I posted the fw_printenv in my last post...by Reto - uBoot
My result: root@debian:/tools# ./flash_erase /dev/mtd0 0 32 Erase Total 32 Units Performing Flash Erase of length 16384 at offset 0x7c000 done root@debian:/tools# ./nandwrite /dev/mtd0 uboot.2015.10-tld-1.sheevaplug.mtd0.kwb Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x4000 Writing data to block 2 at offset 0x8000 Writing data to block 3 at offset 0xc000by Reto - uBoot
There is nothing about the erase size block... My flash is empty, so let's give it a try. What would the modified commands be?by Reto - uBoot
Bodhi, flinfo unknown command...by Reto - uBoot
Bodhi, I have no stock OS. This is why I opened this thread... Does this tell us something? Erase Total 4 Units Performing Flash Erase of length 16384 16384 / 4 units = 4096 = 4k ?by Reto - uBoot
I'm sorry, I thought it looked ok... My bad... Note: I changed the file system on my USB device to ext2 linux-k858:/home/aos/kwboot-tool # ./kwboot -t /dev/ttyUSB0 -b uboot.2015.10-tld-1.sheevaplug.mtd0.kwb -p Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 1 % [...............by Reto - uBoot
Bodhi, I am having no luck. Absolutely no output on the serial port... :-( What I did: root@debian:/tools# ./flash_erase /dev/mtd0 0 4 Erase Total 4 Units Performing Flash Erase of length 16384 at offset 0xc000 done root@debian:/tools# ./nandwrite /dev/mtd0 uboot.2015.10-tld-1.sheevaplug.mtd0.kwb Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x4000 Writiby Reto - uBoot
Damn! Of course! Now it is booting from USB!!! :-) Next step would be to try to flash u-boot to NAND by following this guide, right? http://forum.doozan.com/read.php?3,12381 I tried it but unfortunately it is not working. There is no output on the serial console after a cold start... There are some differences to your guide in the mtds though. Could this be the problem? # MTD device nby Reto - uBoot
Ok, I think I got it now. I have 3.16 rootfs booting. I am getting a (initramfs) prompt... is this normal?by Reto - uBoot
Thanks, I am one step further. However I am unable to get the ramdisk. I tried the "dpkg -i linux-image-4.2.0-kirkwood-tld-1_1.0_armel.deb" command but it is not working. I guess this is because I am on an amd64 system here... My environment: Sheevaplug> printenv arcNumber=2097 baudrate=115200 bootcmd=run bootcmd_uenv; run bootcmd_usb; reset bootcmd_uenv=run uenv_load; if tby Reto - uBoot
Ok, I will try to build a roots on an USB drive? And how can I boot it from a u-boot residing in RAM?by Reto - uBoot
But how should I boot a Linux OS if I have not even a working Ethernet connection? ... I now managed to transfer the u-boot file via serial, flashed it to NAND but after reset nothing happens. Is there anything else I have to do after flashing? What I did: mw 0x0800000 0xffff 0x100000 nand erase 0x0 0x100000 loadb 0x0800000 115200 wait for the transfer to complete... nand write 0xby Reto - uBoot
bodhi, my NAND is completely empty. As explained earlier I accidentally erased the WHOLE NAND. There is nothing left, so nothing to lose. Can I transfer the u-boot file via serial connection?by Reto - uBoot
bodhi, I loaded the Sheevaplug u-boot via kwboot. Does this look ok? U-Boot 2015.10-tld-1 (Nov 08 2015 - 21:01:07 -0800) Marvell-Sheevaplug SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB (ECC not enabled) WARNING: Caches not enabled NAND: 32 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 PHY reset timed out 88E1116by Reto - uBoot
Hi bodhi, Thank you for your answer. It is an Iomega ix4-200d. I accidentially erased the whole NAND. vasichkin posted here that he had best results with u-boot-rd88f6281a_400rd_nand.bin: http://forum.doozan.com/read.php?3,12381,15570#msg-15570 I have a serial connection and am able to load an u-boot via kwboot. Thanks for your help, Retoby Reto - uBoot
Hi, I am a complete Linux noob and need an u-boot binary. Is there someone who could compile it for me? I need this one: u-boot-rd88f6281a_400rd_nand.bin As far as I can see this code should generate it? https://github.com/niamster/uboot-marvell-openrd-ultimate Line 148 in https://github.com/niamster/uboot-marvell-openrd-ultimate/blob/master/create_all_images.sh Thanks in advance, Rby Reto - uBoot