grrrr pi@raspi:~ $ ./kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-a38x-GrandTeton_2014T3_PQ-nand-uart.bin -p kwboot version 2022.07-00607-g36b661dc91 Sending boot message. Please reboot the target.../ Sending boot image header (70528 bytes)... 0 % [......................................................................] 12 % [.............................................................by i5Js - Debian
Almost!! pi@raspi:~ $ ./kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-a38x-GrandTeton_2014T3_PQ-nand-uart.bin -p kwboot version 2022.07-00607-g36b661dc91 Sending boot message. Please reboot the target...| Sending boot image header (70528 bytes)... 0 % [......................................................................] 12 % [..........................................................by i5Js - Debian
It hard to complete it pi@raspi:~ $ ./kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-a38x-GrandTeton_2014T3_PQ-nand-uart.bin -p kwboot version 2022.07-00607-g36b661dc91 Sending boot message. Please reboot the target.../ Sending boot image header (70528 bytes)... 0 % [..................................................+............+......] 12 % [.................................+..........by i5Js - Debian
Anyway.... pi@raspi:~ $ sudo ./kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-a38x-GrandTeton_2014T3_PQ-nand-uart.bin -p kwboot version 2022.07-00607-g36b661dc91 Sending boot message. Please reboot the target...- Sending boot image header (70528 bytes)... 0 % [.++++++++++.+.++.+++++++++++++++EE xmodem: Bad message pi@raspi:~ $ ./kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-a38x-GrandTetby i5Js - Debian
Question, just to learn and understand, what it is worth??by i5Js - Debian
Hi, Yes, the u-boot is patched, I have used CyberPK's (https://forum.doozan.com/read.php?2,28939,98649#msg-98649) Should I use another? I guess I could save the envs, but I never did it, because I was testing the uImages and Rams. I know it's patched, because, as he says in his post, the USB 1 is now active. With the stock uBoot, the USB 2 was active.by i5Js - Debian
root@debian:~# cat /proc/cmdline console=ttyS0,115200 root=/dev/sda2 mtdparts=pxa3xx_nand-0:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@215m(config),10m@235m(reserve1),10m@245m(reserve2) earlyprintk=serial root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00500000 00020000 "u-boot" mtd1: 00500000 00020000 "kernel"by i5Js - Debian
Indeed, that was the issue: Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@215m(config),10m@235m(reserve1),10m@245m(reserve2)' Marvell>> setenv bootargs "console=ttyS0,115200 root=/dev/sda2 $mtdparts earlyprintk=serial" Marvell>> setenv ipaddr 192.168.1.110; setenvby i5Js - Debian
Perhaps because the memory where I am booting both? [ 0.000000][ T0] INITRD: 0x01200000+0x00934000 overlaps in-use memory region - disabling initrd [ 0.000000][ T0] Zone ranges: [ 0.000000][ T0] Normal [ 0.000000][ T0] HighMem [ 0.000000][ T0] Movable zone start for each node [ 0.000000][ T0] Early memory node ranges [ 0.000000][ T0]by i5Js - Debian
Hi, I am unable to boot with your kernel. I have followed yours steps as follow: root@virtsrv:/mnt/root/boot# cp -a zImage-5.13.8-mvebu-tld-1 zImage.fdt root@virtsrv:/mnt/root/boot# cat dts/armada-385-wd-ex2-ultra.dtb >> zImage.fdt root@virtsrv:/mnt/root/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.13.8-mvebu-tld-1 -d zImage.fdt uImageby i5Js - Debian
The issue with your kernel is it can't detect the usb to continue booting into Debian. Tomorrow I will double-check your steps, perhaps I missed something. Thanks for your help!by i5Js - Debian
root@wdmycloud:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 6.0.10+ (root@virtsrv) (arm-none-eabi-gcc (15:8-2019-q3-1+b1) 8.3.1 20190703 (release) , GNU ld (2.35.2-2+14+b2) 2.35.2) #1 SMP Tue Nov 29 14:49:09 CET 2022 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache,by i5Js - Debian
root@wdmycloud:~# cat /proc/cmdline console=ttyS0,115200 root=/dev/sda2 mtdparts=pxa3xx_nand-0:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@215m(config),10m@235m(reserve1),10m@245m(reserve2) earlyprintk=serial root@wdmycloud:~# cat /proc/mtd dev: size erasesize nameby i5Js - Debian
First Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@215m(config),10m@235m(reserve1),10m@245m(reserve2)' Marvell>> setenv bootargs console=ttyS0,115200 root=/dev/sda2 $mtdparts earlyprintk=serial Marvell>> printenv bootargs bootargs=console=ttyS0,115200 root=/dev/sda2 mtdpaby i5Js - Debian
I have tested sdb2 and sdc2, just in case, but it didn't work either, same error message.by i5Js - Debian
yours: Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@215m(config),10m@235m(reserve1),10m@245m(reserve2)' Marvell>> setenv bootargs 'console=ttyS0,115200 root=/dev/sda2 $mtdparts earlyprintk=serial' Marvell>> setenv ipaddr 192.168.1.110; setenv serverip 192.168.1by i5Js - Debian
my kernel Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@215m(config),10m@235m(reserve1),10m@245m(reserve2)' Marvell>> setenv bootargs 'console=ttyS0,115200 root=/dev/sda2 $mtdparts earlyprintk=serial' Marvell>> setenv ipaddr 192.168.1.110; setenv serverip 192.168.by i5Js - Debian
with your kernel and Ramdisk Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@215m(config),10m@235m(reserve1),10m@245m(reserve2)' Marvell>> setenv bootargs 'console=ttyS0,115200 root=/dev/sda2 $(mtdparts) earlyprintk=serial' Marvell>> Marvell>> setenv initrd_by i5Js - Debian
Hello, Logs below: Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@215m(config),10m@235m(reserve1),10m@245m(reserve2)' Marvell>> setenv bootargs 'console=ttyS0,115200 root=/dev/sda2 $(mtdparts) earlyprintk=serial' Marvell>> setenv initrd_high 0xffffffff Marvellby i5Js - Debian
Ok, today I can’t, but I will tomorrow. One question about the u-boot: is there any way to troubleshoot the ext2 driver? Perhaps a new version ? Thanksby i5Js - Debian
I can print the fw envs: root@wdmycloud:~# fw_printenv 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 console=ttyS0,115200 bootargs_dflt=$console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lby i5Js - Debian
I have compiled the kernel one more time, following this script (https://github.com/piotrekzurek/WDMC-Ex2-Ultra) It has some improvements, and it seems he plays with the nand creating more partitions, I guess for stock kernel and Debian. Anyway, apart of that, this time, it boots successfully, and it detects the mtd partitions. Logs below: OPTIONS: I18n Compiled on Aug 13 2017, 15:25:3by i5Js - Debian
Probably I have missed something in my linux.conf to compile the kernel..by i5Js - Debian
With my own kernel compiled: BootROM - 1.73 Booting from NAND flash General initialization - Version: 1.0.0 Detected Device ID 6820 High speed PHY - Version: 2.0 Load WD GrandTeton Serdes Config: board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 06 | SATA0 | | 1 | 05 | PCIe0 | | 2by i5Js - Debian
I have several logs here: With your uImage: BootROM - 1.73 Booting from NAND flash General initialization - Version: 1.0.0 Detected Device ID 6820 High speed PHY - Version: 2.0 Load WD GrandTeton Serdes Config: board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 06 | SATA0 | | 1 | 05 | PCIeby i5Js - Debian
Let's see now. Marvell>> printenv 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 console=ttyS0,115200 bootargs_dflt=$console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_pby i5Js - Debian
Is there any way to save the output into a file? Printenv > output.text?by i5Js - Debian
Hi bodhi, below the logs requested: Press CTRL-A Z for help on special keys BootROM - 1.73 Booting from NAND flash General initialization - Version: 1.0.0 Detected Device ID 6820 High speed PHY - Version: 2.0 Load WD GrandTeton Serdes Config: board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 06 | SATA0by i5Js - Debian
Hi, Many thanks. The idea is get a kernel an uImage thin enough to fit into a nand. As I said, my idea is not to test a lot, just to have a box with latest OMV. I have followed this repository to compile my own kernel, using the dts for ex2 ultra I found here: https://github.com/Heisath/wdmc2-kernel The first issue I have had is I am unable to boot from USB. I don’t know why, but it iby i5Js - Debian
I do not expect to update the keener frequently , I just want to install open media vault and perhaps a Pi-hole.by i5Js - Debian