First try: new kernel + old RamDisk -> doesn't boot. I guess the kernel is ok, because it is the same behaviour: try to boot, with the red led and blue blinking, but the it's off.by i5Js - Debian
Ok, understood: first try new kernel + oldramdisk second try all new Let’s seeby i5Js - Debian
I shlould restore all the box first, because it’s completely empty, just an usb with two files :) I’ll try with the VM Should I rename the uInitrd to uRamDrive ?by i5Js - Debian
Ok!! Thanksby i5Js - Debian
Ok! many thanks, !'ll do, Question: can I do it from a Linux VM using crosscompile? PS: Fingers cross!by i5Js - Debian
Yes, the files are in the USB, there are no drives. I've created a folder named boot, and just copy uImage and uRamdisk as follow / # ls /mnt/boot uImage uRamdisk / # ls -l /mnt/boot -rwxr-xr-x 1 root 0 4177681 Nov 3 2022 uImage -rwxr-xr-x 1 root 0 2679866 Nov 3 2022 uRamdisk There files come from here: https://hackers.cx/wdnas/WDMyCloud-Miby i5Js - Debian
It's the first thing I did, to connect the serial cable. But same, nothing is coming :( So, just to understand, no matter I can compile the kernel, an uImage and a uRamDisk, it won't work, right?by i5Js - Debian
Hello, Here you are: dmesg Booting Linux on physical CPU 0x0 Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Initializing cgroup subsys cpuacct Linux version 3.10.70 (root@build64) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #5 SMP Tue Dec 27 22:04:20 +05 2016 CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nby i5Js - Debian
New chapter, I have had lucky and the box has booted up from a USB key. So I guess I would be able to flash an modified uImage and uRamdisk to work with the uBoot from the command line, right? But which one could I use? Thanks,by i5Js - Debian
I'm done. I have rechecked the solders, all has continuity in both sides, but it's clear that something is broken in my board, and I don't have enough skills to figure it out and/or fix it. Now it would be nice if I could boot from usb, or an internal drive to try to unbrick it. I followed the steps below and after that, the box is not booting anymore: ## Usage #by i5Js - Debian
bodhi Wrote: ------------------------------------------------------- > > You can check one end to make sure it is OK (on > the server end, i.e. the rPI). Loop back to RX to > TX on this end, and type something, it should echo > back the character. If you don't see any thing, > then you'd know something wrong with the console > settings (baud rate, data bit,by i5Js - Debian
Thanks for your advice, I’ll do it tomorrow… time to sleep in Ams :)by i5Js - Debian
Quote The connector has the following pin map: 5 o <-- RX Data 4 (No pin) 3 o — N/C (3.3V) 2 o — GND 1 o --> TX Data Indeed this the pin map I’m following. It was really hard to solder the pins. I’ve tried with the cross connections and direct, but it did not work. Sometimes, as I mentioned before, I can see some characters when I move the wires, but I don’t knoby i5Js - Debian
I have some Rasp, and I'm doing some tests.... but nothing works :( sometimes moving the pins in the board I get som characters, but it's strange because with a multi tester the connection between both works... honestly I don't know that else I can do. Do I need to connect any hardrive?by i5Js - Debian
Well, my box is officially dead or bricked. I've tried to follow the tutorials and I flashed the nand and recreated the filesystem, but now it doesn't boot. Blinking blue all the time. I also get another uart interface, but it don't know why it doesn't work. I don't have anything the screen. I'm trying to use my Mac, or a windows machine with puttt, but nothing wby i5Js - Debian
dimes [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.4 (root@build-server) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4)) #14 SMP Wed Dec 20 01:09:34 +05 2017 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.00by i5Js - Debian
root@wdmc:~# cat /etc/fw_env.config /dev/mtd0 0x100000 0x80000 0x20000 4 root@wdmc:~# fw_printenv Cannot read environment, using default Cannot read default environment from fileby i5Js - Debian
ah, one last thing, my mistake, my model is an EX2 Ultra too.by i5Js - Debian
This is from the dmesg, when the WD boots, I don't know if it helps: [ 4.933398] Creating 8 MTD partitions on "pxa3xx_nand-0": [ 4.937518] 0x000000000000-0x000000500000 : "u-boot" [ 4.941648] 0x000000500000-0x000000a00000 : "uImage" [ 4.945666] 0x000000a00000-0x000000f00000 : "uRamdisk" [ 4.949853] 0x000000f00000-0x00000c800000by i5Js - Debian
Hi, I've bought another UART cable and arrives tomorrow, let's see if It works this time, Thanks,by i5Js - Debian
Hey bodhi, Many thanks for your answer. I've changed the file, but it didn't work either :( root@wdmc:~# cat /etc/fw_env.config /dev/mtd0 0x00080000 0x20000 0x20000 root@wdmc:~# fw_printenv Cannot read environment, using default Cannot read default environment from fileby i5Js - Debian
Hello all, Sorry for bumping this topic, but I am run out ideas: I have an EX2 ultra working fine, with the kernel 4.x working and all the old stuff Quick summary: cd /mnt/root wget http://fox-exe.ru/WDMyCloud/WDMyCloud-Ex2-Ultra/Dev/Linux-4.15.0-rc6/libs-4.15.0-rc6.tar.gz wget http://fox-exe.ru/WDMyCloud/WDMyCloud-Ex2-Ultra/Dev/Linux-4.15.0-rc6/uImage wget http://fox-exe.ru/WDMby i5Js - Debian