Show all posts by user
Discuss all things Debian on your device
Page 1 of 2 Pages: 12
Results 1 — 30 of 47
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 4 months ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 4 months ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 4 months ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 4 months ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 1 year ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 2 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
> 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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
@faktorqm Yes, just ssh and some chroot magic ;-) Serial will be needed only if something went wrongby osa - Debian
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
Thanks for reply Making non-default load adresses persistent will require ugly hacks on this boxby osa - Debian
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 3 years ago
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
Re: My Cloud Gen2 u-boot - 4 years ago
Hi Original software has no fw_setenv or fw_printenv so only overwriting parts of nand is an option to set or reset env. WD's software do not use nand for storing setting - configs are stored on one of drives partitions and can be reset to defaults with reset button pressed for some time. One thing i can do more to confirm this, is to resetenv and check if firmware can set MAC and wriby osa - Debian
Re: My Cloud Gen2 u-boot - 4 years ago
So, i verified reset button and i think i was wrong. It does not clear env when booting with button pressed (maybe sets other boot order?? can't confirm) But resetenv does and fills last 64K of nand with zeros (and clearing checksum) See log below - just after resetenv I use fox-exe kernel and initrd because it fits into 0xa00000/0xf00000 adresses BootROM - 1.51 Booting from SPby osa - Debian
Re: My Cloud Gen2 u-boot - 4 years ago
It seems boot order, commands and adressess are hardcoded in uboot, but uses bootargs env If crc is corrupted default bootargs is used If i set manually root partition with bootargs (using mkenvimage) I can boot debian from HDD!!! Funny thing is that kernel overlaps initrd and it is disabled (like previously posted in other thread) and it allows kernel to boot I can't remember whatby osa - Debian
Re: My Cloud Gen2 u-boot - 4 years ago
Hi CRC is an issue, because when if CRC corruption is detected u-boot uses default values. NAND env is cleared when board is started with button pressed. But i made some progress again ;-) We can use mkenvimage from u-boot to create valid but empty env and then overwrite last sector of NAND and ... now fw_setenv allows us to set env variables! Downside of this is no MAC set (and seriby osa - Debian
My Cloud Gen2 u-boot - 4 years ago
Hi all! We have working new box - WD My Cloud (Gen2) But there's also big issue with u-boot. There's Default CRC is messed and default values are always used, saveenv is not availiable. Maybe i'ts hard coded or maybe just bugged. For example reset button clears env so mac address is cleared causing network not usable. I think there are some ways to fix this without WD'sby osa - Debian
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 4 years ago
5.3.5-mvebu-tld-1 works for me The only issue i see is gigabit led (in the socket) but i can live with this ;-) DTS is from here with phy-mode changed and led triggers set There is another file but looks very similar (not tested) /* * Device Tree file for WD MyCloud based on Marvell Armada 375 * (DB-88F6720) * * Copyright (C) 2014 Marvell * * Gregory CLEMENT <gregory.clby osa - Debian
Re: WD MyCloud Gen2 (Glacier, Armada 375) - 4 years ago
All DTBs are binary identical. 5.2 and 5.3 were not working for me either (i think they returned PHY error 22) I tried 5.5.0-rc7 with no luck, but now ethernet port led is turned off and no status change on cable plug/unplug (maybe this patch? https://github.com/torvalds/linux/commit/f3f2364ea14d1cf6bf966542f31eadcf178f1577#diff-38b28d4e5f70b4f5e7ec9b5e787a0e13) root@wdmc:~# ifdown eth0by osa - Debian
Page 1 of 2 Pages: 12