Hi Bodhi Please take a look at https://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/Photo/Top.jpg This board do not have separate network chip(also on back side), it uses "integrated GbE PHY" which is detected as "generic". Also, as it works, it shouldn't worry us too much if it has (or not) some magic Marvell ID as long as there's no known issues/other revisions ofby osa - Debian
I could not find GPL sourcecode for v5 firmare, but older versions are here (https://community.wd.com/t/wd-my-cloud-v3-x-v4-x-and-v2-x-firmware-versions-download-links/148533) I attached kernel from latest WD firmware, maybe you can extract DTB https://1drv.ms/u/c/3db6dd30f94c5b17/EZF674mKxdBJspMflZRSc58BuPMkCSovFsMePFis_sra6Q?e=dK3Dtnby osa - Debian
Hi Here's bootlog from latest OFW. Maybe theres some useful information BootROM - 1.51 Booting from SPI flash General initialization - Version: 1.0.0 High speed PHY - Version: 0.1.1 (COM-PHY-V20) USB2 UTMI PHY initialized succesfully USB2 UTMI PHY initialized succesfully High speed PHY - Ended Successfully DDR3 Training Sequence - Ver 5.7.1 DDR3 Training Sequence - Runby osa - Debian
Hi @bodhi Here's new bootlog BootROM - 1.51 Booting from SPI flash General initialization - Version: 1.0.0 High speed PHY - Version: 0.1.1 (COM-PHY-V20) USB2 UTMI PHY initialized succesfully USB2 UTMI PHY initialized succesfully High speed PHY - Ended Successfully DDR3 Training Sequence - Ver 5.7.1 DDR3 Training Sequence - Run with PBS. DDR3 Training Sequence - Ended Succby osa - Debian
Here's my bootlog BootROM - 1.51 Booting from SPI flash General initialization - Version: 1.0.0 High speed PHY - Version: 0.1.1 (COM-PHY-V20) USB2 UTMI PHY initialized succesfully USB2 UTMI PHY initialized succesfully High speed PHY - Ended Successfully DDR3 Training Sequence - Ver 5.7.1 DDR3 Training Sequence - Run with PBS. DDR3 Training Sequence - Ended Successfullyby osa - Debian
Hi! AFAIR 6.3.8 is the latest kernel i have tested. Should i try newer kernels to find latest "compatible" or just any working bootlog? Or maybe You need bootlog from original firmware?by osa - Debian
Hi Bodhi, any progress with uboot/kwboot on this platform?by osa - Debian
Old (debian 10) kwboot does not work, but kwboot 2024.04-rc3 works just fine with backup. Funny (strange?) thing is that even changing order of kwboot parameters can cause upload errors Here's successful (not interrupted by user and without drive connected) bootlog ./kwboot -t -b backup_wd.bin -B 115200 /dev/ttyUSB0 kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimby osa - Debian
Still no luck or i am doing something wrong ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2024.07-rc3-tld-1.db-88f6720.uart.kwb kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimage v1 with UART boot signature Sending boot message. Please reboot the target.../ Sending boot image header (22016 bytes)... 0 % [..................................................................by osa - Debian
Still does not work for me. ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot -p kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimage v1 with SPI boot signature Patching image boot signature to UART Aligning image header to Xmodem block size Sending boot message. Please reboot the target...| Sending boot image header (33152 bytes)... 0 % [...................................by osa - Debian
Hi, nice to see some progress ;-) kwboot does not work for me. Upload start, but original uboot runs kwboot version 2022.01+dfsg-2ubuntu2.5 Patching image boot signature to UART Aligning image header to Xmodem block size Sending boot message. Please reboot the target...- Waiting 2s and flushing tty Sending boot image header (33152 bytes)... 0 % [.....................................by osa - Debian
Hi I'm probably the only user of bodhi's kernel on this box, but i just want to let you know I just tested linux-6.3.8 kernel and it fits into 5MB limit and boots just fine. I looked at sizes of all 6.x kernels and they should fit tooby osa - Debian
Hi @alexa163 Try this tutorial to get box working http://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/_Unbricking_en.txt More info http://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/by osa - Debian
Bodhi, it looks this problem was for a longer time, but i didn't paid attention. I'll dig deeper to find out if first supported kernels (5.2/5.3?) had this issue or it is related with changing compression to xz. There's no u-boot source code in wd's gpl sources. BootROM - 1.51 Booting from SPI flash General initialization - Version: 1.0.0 High speed PHY - Veby osa - Debian
> like we'll keep it smaller than 5MB easily. Sounds great. Please, make sure all marvel sata + ext3/4 drivers are built into kernel. I found, that initrd is loaded into memory, but is not used - looks like kernel is overwriting some memory regions (on decompression?) and uses drivers from root partition. For that reason default debian 11 kernel/initrd cannot be used to boot on wdby osa - Debian
Hi, Kernel 5.13.17 segfaults with CONFIG_MVPP2_PTP enabled, so for now disabling it would be necessary. I'm not sure if next kernel will fit into 5MB size limit, so this might be the last working kernel for this boxby osa - Debian
Hi It looks that your 5.12 and 5.13 configs have CONFIG_MVPP2_PTP enabled. Kernel 5.13.17 boots fine when CONFIG_MVPP2_PTP is disabled. Need to investigate later if latest changes to drivers/net/ethernet/marvell/mvpp2 will allow to boot with CONFIG_MVPP2_PTP enabled.by osa - Debian
Hi I found that kernels 5.12+ segfaults on this box Marvell>> bootm 0xa00000 0x3000000 ## Booting image at 00a00000 ... ## Booting kernel from Legacy Image at 00a00000 ... Image Name: Linux-5.12.6-mvebu-tld-1 Created: 2021-09-01 21:16:08 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5185220 Bytes = 4.9 MiB Load Address: 00008000by osa - Debian
It's still work in progress https://translate.google.com/translate?sl=pl&tl=en&u=http://osowiecki.net/debian-na-wd-my-cloud-2-gen/ I believe all that stuff can be run as a single script so probably easiest way to install. Now it's time to write recovery manuals ;-) Comments and suggestions are appreciatedby osa - Debian
@faktorqm Yes, just ssh and some chroot magic ;-) Serial will be needed only if something went wrongby osa - Debian
root@debian:~# uname -a Linux debian 5.10.7-mvebu-tld-1 #1.0 SMP PREEMPT Sat Jan 16 19:49:06 PST 2021 armv7l GNU/Linux Kernel fits into 5MB limit and debian can be installed without serial cable and breaking the case Stay tuned! Tutorial is coming soonby osa - Debian
Hi With every little f*** up i learn something new I found new version of u-boot in gpl source code (binary only) and... got simple flash programmer to fix broken flash ;-) I don't know if they differ somehow, but there's no setenv but bootargs trick works. Is it possible to convert u-boot bin to kwb file? Is it possible to change some internal string values and recalculateby osa - Debian
Hi Still no luck. I splitted flash to u-boot and env parts and nothing really changed. fw_printent shows some values even if env partition is empty.. maybe it reads whole mtd to find some headers? AFAIR mtd partitioning can be made in fdt. But this is not the case now I think in autoboot mode nearly all envs are ignored and only bootargs are properly passed. In manual mode envs are pby osa - Debian
Hi I reset/restore nand to factory state. Last 64kB of flash contains only MAC and Serial number at the end uboot has no saveenv so it's not possible to make permanent changes in env. so original printenv is CASset=max MALLOC_len=5 MPmode=SMP autoload=no baudrate=115200 boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr bootargs=root=/dev/ram consoleby osa - Debian
Marvell>> printenv CASset=max MALLOC_len=5 MPmode=SMP autoload=no baudrate=115200 boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf} boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scrby osa - Debian
Hi, i managed to compile 5.10 xz compressed kernel and it fits to 5MB limit and boots nicely. What are downsides of switching to xz compression? Some envs are hardcoded and overwrites envs like bootcmd (even if CRC is correct) Luckily setting bootargs root=/dev/sda2 console=ttyS0,115200 is persistent and it is enough to boot debian kernel from boot partition (sda3) and use sda2 as rootby osa - Debian
Thanks for reply Making non-default load adresses persistent will require ugly hacks on this boxby osa - Debian
Hi I found latest kernels (5.5+ ???) are over 5MB and they do not fit into hardcoded adresses in u-boot Kernel is loaded at 0xa00000 and initrd is loaded at 0xf00000 so maximum kernel size is 5 242 880 bytes (with mkimage headers) Is it possible to fit into that limit by moving some modules to initrd in next releases? When kernel and initrd is loaded by hand into non overlaping adresby osa - Debian