WD MyCloud Gen2 (Glacier, Armada 375)

doppelgospelhm Wrote:
-------------------------------------------------------
> Could you provide installation steps please? For
> me this didn't work:

1. You're only building the uImage, not the uInitrd
2. You need to ensure that your USB disk is FAT formatted
3. You need to copy uImage and uInitrd to a /boot/ folder on the USB, and rename uInitrd to uRamdisk
4. You may also need to modify your bootargs on the device, this needs to be done on the device itself otherwise it won't find your root partition and you'll get flashing red light (see the last steps under step 4 in osa's tutorial

The additional instructions look like this:

# Before chroot
mkdir /mnt/usb/boot
# Inside chroot
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-6.6.2-mvebu-tld-1 -d initrd.img-6.6.2-mvebu-tld-1 uInitrd
# Exit chroot
cp /mnt/sdb3/boot/uImage /mnt/usb/boot/uImage
cp /mnt/sdb3/boot/uInitrd /mnt/usb/boot/uRamdisk

Then the command to set the boot args is

fw_setenv bootargs 'root=/dev/sda3 console=ttyS0,115200'

but it has to be done on the device as it alters the contents of the flash.

So decompiling u-boot wasn't a complete waste :)
Setting the bootcmd variable doesn't work, but the built-in process is as follows:

### Loading Firmware from USB 2.0 Disk ###
usb reset; fatload usb 0:1 0xa00000 /boot/uImage; fatload usb 0:1 0xf00000 /boot/uRamdisk
### Loading Firmware from Disk ###
ide reset; ext2load ide 0:3 0xa00000 /boot/uImage; ext2load ide 0:3 0xf00000 /boot/uRamdisk
### Loading Rescure Firmware from Disk ###
ext2load ide 0:5 0xa00000 /boot/uImage; ext2load ide 0:5 0xf00000 /boot/uRamdisk
### Start network installation ###
dhcp; tftp 0xa00000 uImage

Knowing this, instead of bootstrapping with a USB, I just created a third partition on the disk, formatted ext2, created /boot folder and put uImage/uRamdisk in there. Could even script it in post-update.d. It's an extra step when upgrading kernel but better than needing a USB to boot from HDD.
I can updated bootargs, but even if I couldn't, I can embed them in the .dts so that would solve that too. Finally a useable board!
Thanks @bodhi for all your work!

megal0maniac Wrote:
-------------------------------------------------------

> Then the command to set the boot args is
>

> fw_setenv bootargs 'root=/dev/sda3
> console=ttyS0,115200'
>

> but it has to be done on the device as it alters
> the contents of the flash.

Thank you! Is set the boot args mandatorily? Because I relied on Franceso's post and there is no bootargs set. Also is it safe to set boot args, like can I bricking my device with this settings? Or I can just format sda3 if something goes wrong and start it again?

megal0maniac Wrote:
-------------------------------------------------------

>
> The additional instructions look like this:
>

> cp /mnt/sdb3/boot/uImage /mnt/usb/boot/uImage
> cp /mnt/sdb3/boot/uInitrd /mnt/usb/boot/uRamdisk
>

why we need to copy uImage and uRamdisk on USB? As I know device boot from sda3, so rootfs, uImage and uRamdisk are supposed to be there.

in my case i use FAT32 USB with boot folder with these files in it https://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/usbrecovery.tar.gz, so device booted from USB correctly with Fox's mini OS, then i connect to device with telnet and do all stuff.

doppelgospelhm Wrote:
-------------------------------------------------------
> why we need to copy uImage and uRamdisk on USB? As
> I know device boot from sda3, so rootfs, uImage
> and uRamdisk are supposed to be there.

Sorry, I think that you and I are trying to do things quite differently so I'm still getting up to speed with the other process. In my case, I don't have the original drive (or firmware), just the bare board with serial port access so I'm fairly free to do whatever - I'm not trying to preserve anything.

Once you have Fox's mini OS installed on a USB, there's no reason to do anything with a USB so the instructions you posted confused me. Are you trying to preserve the original firmware?

The bootargs, as far as I understand, are necessary. At a minimum they tell the kernel where to find the root filesystem. There is a way to embed the bootargs in the dtb file, but that isn't done here so I don't see how the system would boot based on those instructions. Default bootargs points to /dev/ram for rootfs. I'm waiting for @bodhi to jump in and make all of this clear :P

> based on those instructions. Default bootargs
> points to /dev/ram for rootfs. I'm waiting for
> @bodhi to jump in and make all of this clear :P

Actually I don't know how to help. Since we don't have a complete installation instruction here for this box, I need to see all the steps that you guys use for installation.

- Can this u-boot read from USB and/or HDD using ext2load?
- Can you save the envs at u-boot prompt? especially the bootcmd.
- If you can save envs, does the bootcmd got reset by this u-boot each time it powers up?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> - Can this u-boot read from USB and/or HDD using
> ext2load?
It can. It has ext4load and fatload as well.

> - Can you save the envs at u-boot prompt?
> especially the bootcmd.
Nope. I have not found a way to persist any env vars from within u-boot. Once booted, fw_saveenv works if you provide initial variables in a file, then it can write the whole environment. BUT, this overwrites the MAC address and serial at the tail end of the flash (could be corrected by making the environment smaller)

> - If you can save envs, does the bootcmd got reset
> by this u-boot each time it powers up?
Yip. All changes and new variables set by fw_setenv reflect in u-boot EXCEPT for bootcmd which gets defaulted by some boot routine. Even then, it seems to be ignored anyway, so you need to configure storage to satisfy one of the three built in commands.

I also made a backup of mtd0 which I’m happy to share. Flash is only 1MiB.

@megal0maniac,

> Nope. I have not found a way to persist any env
> vars from within u-boot.

> Yip. All changes and new variables set by
> fw_setenv reflect in u-boot EXCEPT for bootcmd
> which gets defaulted by some boot routine. Even
> then, it seems to be ignored anyway, so you need
> to configure storage to satisfy one of the three
> built in commands.
>

OK. Thanks for the refresher. I dealt with too many boards so really hard to keep track things, unless I own the HW or there is an installation guide written here.

Let me build an armada-375 reference board u-boot, hoppefully if it is bootable with kwboot then that's what we will see if it will solve the problem. It might not have everything, but if it is able to set envs and save envs and boot into Debian would make life easier.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Please try kwboot the attached u-boot image.

uboot.2024.07-rc2-tld-1.db-88f6720.kwb

md5:
806ec0f497725b46b9e0d322719b4d5e
sha256:
c595b3a5794ddb9f7a60e27917b8c2e87db9819039e30b4a64fbcb2407f91955

An example of running kwboot (if you have not run it before): https://forum.doozan.com/read.php?3,51739,51919#msg-51919

If it loads and runs OK, interrupt the count down and see if you can bring up the USB and ping the router:

usb start
setenv ipaddr <some valid IP address in the subnet that this box is connected to>
ping <router IP address>

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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 % [......................................................................]
 27 % [......................................................................]
 54 % [......................................................................]
 81 % [.................................................                     ]
Done

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 Successfully 
BootROM: Image checksum verification PASSED

 ** LOADER **


U-Boot 2013.01_v1.03 (Nov 20 2014 - 16:39:45) Marvell version: 2014_T2.0p3

Board: WD_Glacier_DB-88F6720-V2

I flashed nand with your uboot (filled with zeros to match flash size) and it goes into loop

BootROM - 1.51
Booting from SPI flash

BootROM - 1.51
Booting from SPI flash

BootROM - 1.51
Booting from SPI flash

BootROM - 1.51
Booting from SPI flash

BootROM - 1.51
Booting from SPI flash

BootROM - 1.51
Booting from SPI flash

BootROM - 1.51
Booting from SPI flash

Hi Osa,

Good to see you, too :)

Quote

kwboot version 2022.01+dfsg-2ubuntu2.5

This version is a bit old. Please try my latest kwboot build:

https://forum.doozan.com/read.php?3,27280

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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 % [......................................................................]
 27 % [......................................................................]
 54 % [......................................................................]
 81 % [.................................................                     ]
Done

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 Successfully 
BootROM: Image checksum verification PASSED

 ** LOADER **


U-Boot 2013.01_v1.03 (Nov 20 2014 - 16:39:45) Marvell version: 2014_T2.0p3

Osa,

> ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot -p

You forgot the u-boot image uboot.2024.07-rc2-tld-1.db-88f6720.kwb here? or did you rename to uboot?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 06/05/2024 01:21AM by bodhi.

File was renamed

> File was renamed

OK. Might be kwboot problem with this SoC image. Let's try a pure UART booting u-boot then. I'll upload another build.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

The attached u-boot image is for UART booting only (don't flash it).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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 % [......................................................................]
 41 % [......................................................................]
 81 % [................................                                      ]
Done

BootROM - 1.51
Booting from SPI flash

[blablablabla removed some output blablabla]

ERROR: can't get kernel image!
Marvell>> 

xmodem: Connection timed out

I tried to mess with other kwboot parameters and when setting -o (xmodem block timeout) to 0

./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2024.07-rc3-tld-1.db-88f6720.uart.kwb -o 0
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 % [+++++++++++++++EE
xmodem: Bad message

and system diode is red (no blinking) and i can use kwboot without turning off/on power
and then when -o is greater than 0 (ie 1 or 2)

root@debian:~# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2024.07-rc3-tld-1.db-88f6720.uart.kwb -o 1
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 % [+++++++++.++++++++.++++++++.++++++++.+++++.+...................+......]
 18 % [......................................................................]
 58 % [...E
xmodem: Protocol error

But if i turn off board and execute kwboot with -o 1 (or bigger number) output is

./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2024.07-rc3-tld-1.db-88f6720.uart.kwb -o 1
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 % [++++++++++.++++++++.++++++++.++++++++.++++.+.....................+....]
 18 % [......................................................................]
 58 % [......................................................................]
 99 % [..                                                                    ]
Done
BootROM: Invalid header checksum
Booting from SPI flash

The same happends with rc2 uboot

Osa,

You're not doing any thing wrong, and it's not the timing (the header was sent successfully).

It looks like kwboot problem (i.e. MVEBU boot code) has problem with this Armada 375 SoC. I'll take a look at that code when I have a chance.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Osa,

Can you kwboot your mtd0 backup?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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 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 (92032 bytes)...
  0 % [......................................................................]
  9 % [......................................................................]
 19 % [......................................................................]
 29 % [......................................................................]
 39 % [......................................................................]
 48 % [......................................................................]
 58 % [......................................................................]
 68 % [......................................................................]
 78 % [......................................................................]
 87 % [......................................................................]
 97 % [...................                                                   ]
Done


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 Successfully 

Sending boot image data (837116 bytes)...
  0 % [......................................................................]
  1 % [......................................................................]
  2 % [......................................................................]
  3 % [......................................................................]
  4 % [......................................................................]
  5 % [......................................................................]
  6 % [......................................................................]
  7 % [......................................................................]
  8 % [......................................................................]
  9 % [......................................................................]
 10 % [......................................................................]
 11 % [......................................................................]
 12 % [......................................................................]
 13 % [......................................................................]
 15 % [......................................................................]
 16 % [......................................................................]
 17 % [......................................................................]
 18 % [......................................................................]
 19 % [......................................................................]
 20 % [......................................................................]
 21 % [......................................................................]
 22 % [......................................................................]
 23 % [......................................................................]
 24 % [......................................................................]
 25 % [......................................................................]
 26 % [......................................................................]
 27 % [......................................................................]
 28 % [......................................................................]
 29 % [......................................................................]
 31 % [......................................................................]
 32 % [......................................................................]
 33 % [......................................................................]
 34 % [......................................................................]
 35 % [......................................................................]
 36 % [......................................................................]
 37 % [......................................................................]
 38 % [......................................................................]
 39 % [......................................................................]
 40 % [......................................................................]
 41 % [......................................................................]
 42 % [......................................................................]
 43 % [......................................................................]
 44 % [......................................................................]
 46 % [......................................................................]
 47 % [......................................................................]
 48 % [......................................................................]
 49 % [......................................................................]
 50 % [......................................................................]
 51 % [......................................................................]
 52 % [......................................................................]
 53 % [......................................................................]
 54 % [......................................................................]
 55 % [......................................................................]
 56 % [......................................................................]
 57 % [......................................................................]
 58 % [......................................................................]
 59 % [......................................................................]
 61 % [......................................................................]
 62 % [......................................................................]
 63 % [......................................................................]
 64 % [......................................................................]
 65 % [......................................................................]
 66 % [......................................................................]
 67 % [......................................................................]
 68 % [......................................................................]
 69 % [......................................................................]
 70 % [......................................................................]
 71 % [......................................................................]
 72 % [......................................................................]
 73 % [......................................................................]
 74 % [......................................................................]
 76 % [......................................................................]
 77 % [......................................................................]
 78 % [......................................................................]
 79 % [......................................................................]
 80 % [......................................................................]
 81 % [......................................................................]
 82 % [......................................................................]
 83 % [......................................................................]
 84 % [......................................................................]
 85 % [......................................................................]
 86 % [......................................................................]
 87 % [......................................................................]
 88 % [......................................................................]
 89 % [......................................................................]
 90 % [......................................................................]
 92 % [......................................................................]
 93 % [......................................................................]
 94 % [......................................................................]
 95 % [......................................................................]
 96 % [......................................................................]
 97 % [......................................................................]
 98 % [......................................................................]
 99 % [..............................                                        ]
Done
Finishing transfer
[Type Ctrl-\ + c to quit]

 ** LOADER **


U-Boot 2013.01_v1.03 (Nov 20 2014 - 16:39:45) Marvell version: 2014_T2.0p3

Board: WD_Glacier_DB-88F6720-V2
SoC:   MV88F6720 Rev A0
       running 2 CPUs
CPU:   ARM Cortex A9 MPCore (Rev 1) LE
       CPU 0
       CPU    @ 800 [MHz]
       L2     @ 400 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 534 [MHz]
       DDR 16Bit Width, FastPath Memory Access, DLB Enabled
DRAM:  512 MiB

Map:   Code:		0x1fed6000:0x1ff92c90
       BSS:		0x1ffefa20
       Stack:		0x1f9c5f20
       Heap:		0x1f9c6000:0x1fed6000

SF: Detected MX25L8006E with page size 64 KiB, total 1 MiB
*** Warning - bad CRC, using default environment

PCI-e 0: Detected No Link.
PCI-e 1: Detected No Link.
SF: Detected MX25L8006E with page size 64 KiB, total 1 MiB
MAC addr: 00:90:A9:EB:5A:DA
### Loading Firmware from USB 3.0 Disk ###
USB2.0 0: Host Mode
USB2.0 1: Device Mode
USB3.0 0: Host Mode
Board configuration detected:
	GE-PHY-0 on MAC0
SERDES configuration:
	Lane #0: PCIe0
	Lane #1: PCIe1
	Lane #2: SATA0
	Lane #3: USB3
Net:   egiga0 [PRIME]
*** ERROR: ping address not given
Hit any key to stop autoboot:  0 
(Re)start USB...
USB0:   Port (usbActive) : 0	Interface (usbType = 3) : USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
## Booting image at 00a00000 ...
### Loading Firmware from USB 2.0 Disk ###
(Re)start USB...
USB0:   Port (usbActive) : 1	Interface (usbType = 2) : USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
## Booting image at 00a00000 ...
### Loading Firmware from Disk ###

Reset IDE: 
Marvell Serial ATA Adapter
Integrated Sata device found

** Bad device ide 0 **
** Bad device ide 0 **
## Booting image at 00a00000 ...
### Loading Rescure Firmware from Disk ###
** Bad device ide 0 **
** Bad device ide 0 **
## Booting image at 00a00000 ...
### Start network installation ###
RX_ICMP
rx_icmp(): Listening to incoming WD ICMP beacons for 3 second!
Error...
rxIcmp - rxIcmp

Usage:
rxIcmp Start Listening to incoming WD ICMP beacons
## Booting image at 00a00000 ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>> 
Marvell>> 
Marvell>> 

> Old (debian 10) kwboot does not work, but kwboot
> 2024.04-rc3 works just fine with backup.

Cool! the new kwboot has a lot of bug fixes. Boards that could not be kwboot before are now possible. Even the Zyxel NAS326 (Armada 380) can be kwboot (I have built a new u-boot for this, but there is some problem with the board serial port, so I have not released it). We're all indebted to Pali Rohar (a very smart guy).


> Here's successful (not interrupted by user and
> without drive connected) bootlog

Alright!

> Funny (strange?) thing is that even changing order
> of kwboot parameters can cause upload errors

It looks like kwboot did not have enough testing for the Armada 375 board. Most of the fixes have been tested on Armada 38x boards (by Pali, me, and a few other u-boot developers).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi, All!
Trying to find out...
Is there a way to get the fully working system without an internal hdd?
I'm trying to install full Debian to usb-ssd (Boot, System/RootFS, swap) and use the internal hdd only for Data (single ext4 parition)...
Thanks...



Edited 1 time(s). Last edit at 01/29/2025 06:47AM by ksp3.

ksp3,

> Trying to find out...
> Is there a way to get the fully working system
> without an internal hdd?

> I'm trying to install full Debian to usb-ssd
> (Boot, System/RootFS, swap) and use the internal
> hdd only for Data (single ext4 parition)...


Yes, that should be the way boot full Debian system and free up the internal HDD. Create rootfs on the USB drive.

Which instruction you follow to insall on HDD, if you did?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
>
> Create rootfs
> on the USB drive.


I've stucked with rootfs mounting
The boot process interrupts with rootfs not found...

USB0:   Port (usbActive) : 0    Interface (usbType = 3) : USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
reading /boot/uImage
5192860 bytes read in 64 ms (77.4 MiB/s)
reading /boot/uRamdisk
5257173 bytes read in 69 ms (72.7 MiB/s)
## Booting image at 00a00000 ...
## Booting kernel from Legacy Image at 00a00000 ...
   Image Name:   Linux-6.6.2-mvebu-tld-1
   Created:      2025-01-29   9:48:04 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5192796 Bytes = 5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 00f00000 ...
   Image Name:   initramfs-6.6.2-mvebu-tld-1
   Created:      2023-12-12  22:03:52 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5257109 Bytes = 5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 6.6.2-mvebu-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Mon Nov 20 18:44:27 PST 2023
[    0.000000][    T0] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[    0.000000][    T0] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000][    T0] OF: fdt: Machine model: WD MyCloud Gen2
[    0.000000][    T0] Memory policy: Data cache writealloc
[    0.000000][    T0] INITRD: 0x00f00000+0x00504000 overlaps in-use memory region
[    0.000000][    T0]  - disabling initrd
[    0.000000][    T0] Zone ranges:
[    0.000000][    T0]   Normal   [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000][    T0]   HighMem  empty
[    0.000000][    T0] Movable zone start for each node
[    0.000000][    T0] Early memory node ranges
[    0.000000][    T0]   node   0: [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000][    T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000][    T0] percpu: Embedded 29 pages/cpu s25364 r8192 d85228 u118784
[    0.000000][    T0] Kernel command line: root=/dev/ram console=ttyS0,115200

* * *

[    3.541977][    T1] Please append a correct "root=" boot option; here are the available partitions:
[    3.551096][    T1] 1f00            1024 mtdblock0
[    3.551107][    T1]  (driver?)
[    3.559084][    T1] 0800       117220824 sda
[    3.559093][    T1]  driver: sd
[    3.566660][    T1]   0801         4194304 sda1 7192e0d2-a019-44ca-ad79-edfc978b4397
[    3.566671][    T1]
[    3.576668][    T1]   0802        92053504 sda2 7dd4c0fd-aaea-410b-96e1-a99aab383bbe
[    3.576678][    T1]
[    3.586670][    T1]   0803        20971520 sda3 1520f883-373a-4beb-9b93-965ad44e254c
[    3.586679][    T1]
[    3.596682][    T1] List of all bdev filesystems:
[    3.601450][    T1]  ext3
[    3.601457][    T1]  ext4
[    3.604094][    T1]  iso9660
[    3.606730][    T1]  udf
[    3.609638][    T1]
[    3.614383][    T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

It seems that kernel didn't see any usb partitions (only sda's from hdd), but the usb flash contains second ext3 partition with rootfs extracted.
And i dont know how to change "root=/dev/ram" command...

ksp3,

The initrd has grown larger than 5MB!

-rw-r--r--  1 root root  5257109 Dec 12 14:03 initrd.img-6.6.2-mvebu-tld-1

Sorry I did not notice that when I released the MVEBU rootfs. I did not have this box limitation in mind.

This is OK for all other boxes, but not this WD MyCloud Gen2. The initrd must be shrunk further to boot successfully.

So you have the right idea that you boot with USB rootfs first and enter the envs while at u-boot prompt.

Now you can change the bootcmd so that it it will boot the kernel at the new address temporarily.

Therefore, for now

- load the uImage to 0xa00000
- load the uInitrd to 0x3000000

(If you're not sure how, please post your u-boot envs as how you prepare to boot the USB rootfs)

And then boot

bootm 0xa00000 0x3000000

And then log into Debian, you would shrink the initrd. As described in the release thread

Quote

Note 7. Shrink initramfs to smaller size (Optional):

In Debian bookworm, the default compression is zstd. However, to keep it simple, the initramfs (initrd.img-6.6.2-mvebu-tld-1) in this rootfs was compressed using gzip, which is perfectly OK. If you need to have a smaller initramfs (for example, you are trying to fit it in a limited sized NAND partition), see here for tutorial: HowTo Shrink initramfs.

And reboot and boot with the stock envs for kernel location (let it boot with the bootm 0xa00000 0xf00000).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 01/30/2025 02:28PM by bodhi.

bodhi,

Thank you for your help!

Hi Bodhi, any progress with uboot/kwboot on this platform?

Hi osa,

I've not done anything yet for u-boot on box with Armada 375. Perhaps I will start in a couple of months from now.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

osa et al,

Please someone post the kernel bootlog (dmesg ) for this box. Also if you know the exact Ethernet chip model.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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?