That's interesting! It kernel-panicked but that's OK. I guess it's because possibly I'm using ext4 and for some reason it can't mount rootfs. But at least during boot stages I see the MTD devices so post 4.16.1 does work with the marvell mtd driver. Do you happen to know what was wrong in my kernel .config file? armada-nand armada-nand.0: Initialize HAL based Nby buco - Debian
I did use the same .config except for my notes in the paragraph below. I used exactly the same DTS file for both building 4.14.260 and 5.16.rc7. It does bother me now since I can't upgrade libc6 due to a problem in gcc where it overflows on kernel minor revision numbers greater than 255. Mine is 4.14.260 now. So to work around the problem, I have to boot 5.16.x, apt upgrade libc6, then reby buco - Debian
Just wondering if it's possible to have U-boot ported to the Western Digital My Cloud Mirror (gen1). I have one running Linux hooked up to a serial console and I can test/supply info if wanted. Also, I don't know how much work it would be so I'm not sure if it's worth the effort.by buco - uBoot
I didn't see .2 properly, I flashed it already and luckily it works well! It's with a 4.14.260 because of a bug starting from 4.16.1 where the nand flash is no longer probed correctly by the kernel. I tried 5.16 and still no luck. It doesn't bother me too much. root@mcm:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.260 (rooby buco - Debian
ha :) root@mcm:~# cat /proc/mtd dev: size erasesize name mtd0: 10000000 00020000 "pxa3xx_nand-0" mtd1: 00500000 00020000 "u-Boot" mtd2: 00500000 00020000 "uImage" mtd3: 00500000 00020000 "ramdisk" mtd4: 0c900000 00020000 "image.cfs" mtd5: 00f00000 00020000 "rescue firmware" mtd6: 01400000 00020000 "config&quoby buco - Debian
Second post since the post length was too long for one post. This is the boot process from U-boot till the Debian prompt with my "custom" kernel. It might very well be that I "forgot" to enable something in the kernel. I do see a lot of errors which I still need to sift through :) EDIT: I attached the .config file of my kernel. EDIT2: I think the erorrs are unrelated.by buco - Debian
@bodhi, thanks for your reply. Asking support, no info given, ... sorry :) BootROM 1.08 Booting from NAND flash lHigh speed PHY - Version: 2.1.2 (COM-PHY-V20) Update PEX Device ID 0x67100 High speed PHY - Ended Successfully DDR3 Training Sequence - Ver 4.5.0 DDR3 Training Sequence - Ended Successfully Status = MV_OK BootROM: Image checksum verification PASSED ** LOADER **by buco - Debian
Hi, I adopted someone's old Western Digital My Cloud Mirror Gen1 (Marvell-370) which was under a water leak and no longer booted. I took it apart, I cleaned it up, solderde a serial connection on UART, put other disks in it, installed Debian on it and sure enough, it's up and running again! This is my first time playing with the ARM boot process and it's been a learning curve soby buco - Debian