bodhi, this looks good as well. : ) ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstone_2014T30p6_bodhi-tld-4-nand-uart.bin -s 0 -q 1 Sending boot message. Please reboot the target...\▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUfw Sending boot image... 0 % [......................................................................] 0by saschadd - Debian
bodhi, i think this looks good. ;) ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstone_2014T30p6_bodhi-tld-4-nand-uart.bin -s 0 -q 1 Sending boot message. Please reboot the target...-▒"▒&T▒▒▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUf\ Sending boot image... 0 % [....................................................................by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > 3. Please try kwboot tld-4 again (using USB rootfs > ), and set the fw_env.config as I described above, > see if we can get fw_printenv working. Still no luck. :( ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstone_2014T30p6_bodhi-tld-4-nand-uart.bin -s 0 -q 1 Sending boot message. Please rebby saschadd - Debian
bodhi, good to read that. after your notes i was a bit worried if i could corrupt something by unplugging power cord.by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > OK let try other things first then. And we come ba > ck to this fw_env. > > 1. Don't turn off power in u-boot. You should boot all the way in, then do a shutdown. Do you mean that i should never turn of power in u-boot? That would mean booting all the time into stock firmware when trying to kwboot.by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Log in to Debian as root, and change the content o > f /etc/fw_env.config > > > # MTD device name Device offset Env. size Flash se > ctor size Number of sectors > /dev/mtd0 0x100000 0x20000 0x20000 > > > And then > > > fw_printenv > unfortunately no change testedby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > I think that probably was! kwboot should not chang > e anything. > > Do you shutdow the box before running kwboot, and > then press power button? or the power is automatic > ally on when you plug the power cord in? when i plugin the power cord the power is automatically on and the box boots up. Haby saschadd - Debian
bodhi, new try ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstone_2014T30p6_bodhi-tld-4-nand-uart.bin -s 0 -q 1 Sending boot message. Please reboot the target.../▒"▒&T▒▒▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUfw Sending boot image... 0 % [......................................................................] 0 % [.......by saschadd - Debian
Okay, can boot to stock again. :) As i do plug power off while trying kwboot i did that all the time and not used the power switch. There has to be an security log at very early stage as i get notes about the power losses (caused by unplugging to kwboot) when i log in mycloud webgui. picocom -b 115200 -d 8 /dev/ttyAMA0 picocom v1.7 port is : /dev/ttyAMA0 flowcontrol : noneby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > 1. Try kwboot earlier version, > > > ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a3 > 8x-Yellowstone_2014T30p6_bodhi-tld-3-nand-uart.bin > -s 0 -q 1 > stops and switches off like tld-4 > > 2. And power off, unplug the cord, wait a few minu > tes, power up with serial console,by saschadd - Debian
Same happens when trying to boot stock firmware. :(by saschadd - Debian
bodhi, i got a problem now. Trying to kwboot now stops at "Set lan 1 WakeOnLan ok" and switches power off. :( ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstone_2014T30p6_bodhi-tld-4-nand-uart.bin -s 0 -q 1 Sending boot message. Please reboot the target...-▒"▒&T▒▒▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUfw Sending boot image... 0by saschadd - Debian
bodhi, just a quick try before i have to go to bed. unfortunaly this boots to stock firmware ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstone_2014T30p6_bodhi-tld-4-nand-uart.bin -s 0 -q 1 Sending boot message. Please reboot the target...|▒"▒&T▒▒▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUf/ Sending boot image... 0 % [.........by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > saschadd, > > Here is the new patched u-boot. Please kwboot it a > s before. But don't run saveenv. I like to see the > bootlog before we try that. bodhi, just tried it. following the bootlog, printenv, dmesg and cat /proc/mtd ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstone_by saschadd - Debian
Sorry guys was on the road with no access to internet or the nas box. I am back now and have to read through your post to find what i should do next.by saschadd - Debian
Okay, another try with setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 earlyprintk=serial mtdparts=armada-nand:5m(u-boot)ro,5m@5m(kernel),5m@10m(uRamdisk),441m@15m(image.cfs),15m@456m(rescue_fw),20m@471m(config),10m@491m(reserve1),10m@501m(reserve2)' pi@raspberrypi:~ $ sudo ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Yellowstone_by saschadd - Debian
Okay, new kwboot from usb with setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 earlyprintk=serial mtdparts=armada-nand-0:5m(u-boot)ro,5m@5m(kernel),5m@10m(uRamdisk),441m@15m(image.cfs),15m@456m(rescue_fw),20m@471m(config),10m@491m(reserve1),10m@501m(reserve2)' pi@raspberrypi:~ $ sudo ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-by saschadd - Debian
> Could you post this serial boot log with this error? I just reinstalled the latest firmware to Version 2.30.165. It is now booting to stock and we are sure we use the same version. Let me try the boot with mtdparts you posted. Will update soon.by saschadd - Debian
bodhi, following complete boot log from kwboot to debian via usb pi@raspberrypi:~ $ sudo ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Ylowstone_2014T30p6_bodhi-tld-3-nand-uart.bin -s 0 -q 1 Sending boot message. Please reboot the target...-▒"3DUfw▒"3DUfw▒"3DUf\▒"3DUfw▒"3DUfw▒"3DUfw Sending boot image... 0 % [..........................by saschadd - Debian
bodhi, just trying to boot to stock but it says it is corrupted. I think it is because of the test=1 env we saved. How can i delete this env or do i have to import the backup? EDIT: i am pretty sure that i am on the latest Firmware Version 2.30.165 because i update regularly. but need to boot to stock to verify.by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Hold on. I think I might have overlooked something > . > > Could you post this after you've booted into Debia > n with tld-3 version. I want to make sure I look a > t the latest boot log and the mtds. > > > dmesg > cat /proc/mtd > Here we go WD My Cloud EX4100 Linuxby saschadd - Debian
bodhi, well, i would try everything where we can go back to current status IOW which is reversible. With only one year linux knowledge my wisdom is far away from fully understanding the whole thing. ;) Therefore i don't really know which way would be better and i would trust your suggestion. I think you know much more of what is possible what we should do and not do at this state.by saschadd - Debian
bodhi, looks good. setting and saving gives Marvell>> setenv test 1 Marvell>> saveenv Saving Environment to NAND... Erasing Nand... Writing to Nand... done Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv load_initrd_addr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_inby saschadd - Debian
No luck again. :( I have the feeling that i am doing something wrong. ;) Or the envs are always one step forward. :D root@debian:~# ./find_uboot_env_location20170622.sh /dev/mtd0 0x1e0000 0x80000 0x20000 stuff found at mtd0 1e0000 Warning: Bad CRC, using default environment bootargs= bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:by saschadd - Debian
bodhi, just tried it with space and tab as separator. unfortunately with no luck. :( root@debian:~# nano /etc/fw_env.config GNU nano 2.2.6 File: /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size $ /dev/mtd0 0x00000 0x00080000 0x20000 root@debian:~# fw_printenv Warning: Bad CRC, using default environment bootargs= bootcmdby saschadd - Debian
bodhi, just tested the tld3 version you posted. following the console output. havent saved any envs yet. pi@raspberrypi:~ $ sudo ./kwboot -f -t -B 115200 /dev/ttyAMA0 -b u-boot-a38x-Ylowstone_2014T30p6_bodhi-tld-3-nand-uart.bin -s 0 -q 1 Sending boot message. Please reboot the target...-▒"▒&T▒▒▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUfw▒"3DUf\ Sendinby saschadd - Debian
bodhi, just grepped all the mtds. following the outputs Linux version 4.9.0-mvebu-tld-12 (root@tldDebianVM) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #2 SMP PREEMPT Wed Feb 1 02:31:29 PST 2017 10:11:24 up 18 min, 1 user, load average: 0.00, 0.00, 0.00 root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00500000 00020000 "U-Boot"by saschadd - Debian
bodhi, thanks for the info. Well i will try to grep through all mtds this evening in round about 5 to 6 hours and post the output.by saschadd - Debian
bodhi, i just dumped the mtd's again from within the usb booted debian. what confuses me a bit is that the nanddump dumps mtd6 and mt7 as well while it gave an error "No such file or directory" at first try when we booted stock os. another side note: see the "OOB size 64" part? i remember that i have read somewhere that wd stock firmware has somewhere something setby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Could you boot into Dedian using USB or HDD rootfs, and double check the content of fw_env.config Booted the usb via kwboot and did one space as separator nano /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size $ /dev/mtd0 0xc0000 0x20000 0x20000 fw_printenvby saschadd - Debian