Hi, Sure I can look at doing that. On the driver side I would be interested in taking a look. Is there anything I can checkout on git for example. It would be great to be able to compile my own kernel so I can tweak code / drivers and see the effects.by spiderdijon - Debian
The auto booting debian from USB works well which is great, but the sata controller issue persists. The unit only has 4 drive bays. It also has two e-sata ports on the rear which connect directly to the SoC (not via PCI-E). Drives are only detected in 2/4 bays which is consistent with the missing sata controller. I have had a look at other DTS files which turn up on google and there appears to beby spiderdijon - Debian
I have tried many combinations of HDDs and the outcome is always the same. The first sata controller fails to start and is missing once booted into debian. There is a slight difference in the PCI-E section of the dtb between the xp-db and rn2120. Using fdt-viewer: armada-xp-db.dtb pcie@1,0 clocks = <0x00 0x00 0x00 0x07 0x00 0x00 0x00 0x05>; armada-xp-netgear-rn2120.dtb pcie@1,0by spiderdijon - Debian
I have also been doing further research on the PCI issue and the missing Marvell 88SE9170 SATA Controller. root@debian:~# lspci 00:02.0 PCI bridge: Marvell Technology Group Ltd. MV78230 ARM SoC (rev 02) 00:05.0 PCI bridge: Marvell Technology Group Ltd. MV78230 ARM SoC (rev 02) 01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9170 PCIe 2.0 x1 2-port SATA 6 Gb/s Controller (revby spiderdijon - Debian
Do these envs need to be saved permanently at this point? Not much point adding them to the script on the USB drive as the USB drive is already present! :)by spiderdijon - Debian
It appears to boot the uboot but is missing loading env variables from SPI flash. With ID bytes of 0xFF 0xFF 0xFF it's likely it's actually not accessing anything at all. Is this because there is no SPI NOR Flash on this device? It looks like it uses NAND flash instead? I guess the purpose of this test was just to see if it got this far as it's for a different device and it did!by spiderdijon - Debian
I assumed I would kwboot the uboot.rn2120.rescue.img file is that correct? If so it did not work: root@poepi:/home/pi# ./kwboot_static -b uboot.rn2120.rescue.img -t /dev/ttyUSB0 kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimage v1 with NAND boot signature Image has invalid data checksum uboot.rn2120.rescue.img: Invalid image. root@poepi:/home/pi# md5sum uboot.rn2120.rby spiderdijon - Debian
I tried the script to boot the device into debian with just a single line and it works well. There is a typo in your instructions: boot.scr / uboot.scr but otherwise very clear, thank you. You are correct with the pci 0000:00:01.0 issue, I seem to only have 2 / 4 drive bays working (they all function in the default OS)by spiderdijon - Debian
bodhi Wrote: ------------------------------------------------------- > Congrats! could you do a kwboot run with my built > kwboot static version. This is to make sure that > it could be recommended to others. > I can confirm the static built kwboot also works: root@poepi:/home/pi# ./kwboot_static -b mtd0.rn2120 -t /dev/ttyUSB0 kwboot version 2024.04-rc3-00001-g0861eab8by spiderdijon - Debian
Ah! Success on the kwboot. I found another thread : https://forum.doozan.com/read.php?3,95249 and it seems the power button needs to be pressed and held down during the first stage (bootloader?) upload. I was able to successfully boot using mtd0.rn2120 backup file. Interestingly it worked fine without the -a flag. I also managed to build kwboot from source but I doubt that helped. root@poepiby spiderdijon - Debian
I have tried the kwboot again and still no luck: pi@poepi:~$ ./kwboot_static -a -b mtd0.rn2120 -t /dev/ttyAMA4 -p kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimage v1 with NAND boot signature Patching image boot signature to UART Sending boot message. Please reboot the target...\ Sending boot image header (112640 bytes)... 0 % [.....................................by spiderdijon - Debian
Looks good! cpuinfo reports two processors now. However what ever is causing pci 0000:00:01.0: not ready after 65535ms; giving up Is still present. BootROM 1.20 Booting from NAND flash General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.8 (COM-PHY-V22) Update Device ID PEX0782311AB Update Device ID PEX1782311AB Update Device ID PEX2782311AB Update Deviceby spiderdijon - Debian
Thanks - The static linked binary works but the result is the same: root@poepi:/home/pi# ./kwboot_static -a -b uboot.2024.04-rc3-tld-1.ds414.kwb -t /dev/ttyAMA4 -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 targetby spiderdijon - Debian
Wrong thread sorryby spiderdijon - uBoot
I'll wait for your static build of kwboot. Even with setting up the targets: make rpi_4_defconfig make tools It still doesn't seem to build kwboot. It builds kwbimage.o but that is as far as it goes.by spiderdijon - Debian
Here is the full serial log with all commands entered: BootROM 1.20 Booting from NAND flash General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.8 (COM-PHY-V22) Update Device ID PEX0782311AB Update Device ID PEX1782311AB Update Device ID PEX2782311AB Update Device ID PEX3782311AB Update Device ID PEX4782311AB Update Device ID PEX5782311AB Update Device ID PEX6by spiderdijon - Debian
Switching from trying kwboot (I got it to 20% once in about 100 tries!), this is the console log from modifying the envs: root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0 0x20000 0x20000 root@debian:~# cat /proc/mtd dev: size erasesize name mtd0by spiderdijon - Debian
I'm having difficulty executing the binary on the pi. I think it's due to an incompatible glibc. Could you link the repo where the kwboot development work is going on so I can compile it from source? Edit: I think I found it: https://source.denx.de/u-boot/u-boot/ (?) but now having difficulty in producing a kwboot binary. It doesn't seem to build it with the "make tools-onlby spiderdijon - Debian
I've read a few threads relating to kwboot. Possibly I might be having a issue because I'm starting kwboot first and then powering on the NAS? Is there a suggested sequence?by spiderdijon - Debian
I'm actually having great difficulty in getting kwboot to work. I have tried several systems including a raspberry pi and it never gets past a few percent: Rpi using usb serial dongle root@poepi:/home/pi# root@poepi:/home/pi# kwboot -b uboot.2024.04-rc3-tld-1.ds414.kwb -t /dev/ttyUSB0 -p kwboot version 2023.01 Patching image boot signature to UART Aligning image header to Xmodem bloby spiderdijon - Debian
OK great. Thank you for the instructions, they were very clear. I have successfully booted into debian and updated the rootfs and kernel. Here is the log: BootROM 1.20 Booting from NAND flash General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.8 (COM-PHY-V22) Update Device ID PEX0782311AB Update Device ID PEX1782311AB Update Device ID PEX2782311AB Update Deviceby spiderdijon - Debian
Thanks for your response. It makes some sense but I'm not entirely sure. This is my understanding: 1. recreate the bootable usb drive but with the different kernel you specified above 2. using the same setenv commands above, boot the usb drive 3. Once booted temporarily into debian, install the full kernel (or should this be rootfs which would make sense with chroot?) Actually yes itby spiderdijon - Debian
Here is the output with the modified bootcmd_exec ootROM 1.20 Booting from NAND flash General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.8 (COM-PHY-V22) Update Device ID PEX0782311AB Update Device ID PEX1782311AB Update Device ID PEX2782311AB Update Device ID PEX3782311AB Update Device ID PEX4782311AB Update Device ID PEX5782311AB Update Device ID PEX6782311by spiderdijon - Debian
Here is the serial console from the boot attempt, it appears to hang at "Starting Kernel ..." with no further serial activity. BootROM 1.20 Booting from NAND flash General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.8 (COM-PHY-V22) Update Device ID PEX0782311AB Update Device ID PEX1782311AB Update Device ID PEX2782311AB Update Device ID PEX3782311AB Uby spiderdijon - Debian
Hi Bodhi, Thanks for replying! Here is the serial console log: BootROM 1.20 Booting from NAND flash General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.8 (COM-PHY-V22) Update Device ID PEX0782311AB Update Device ID PEX1782311AB Update Device ID PEX2782311AB Update Device ID PEX3782311AB Update Device ID PEX4782311AB Update Device ID PEX5782311AB Update Devby spiderdijon - Debian
Hi, I have just obtained a RN2120 which is a 1U rack system with a dual core armada XP. I see a few references to working debian systems with this model, but nothing explicit on how to actually achieve it. Does anyone have any pointers on where to start? Many thanks!by spiderdijon - Debian