cmp18, Marvell>> md.l 0xF1010000 8 f1010000: 01111111 00003311 33331100 33003333 .....3....3333.3 f1010010: 40000033 00004444 00000000 00000000 3..@DD.......... Marvell>> md.l 0xF1010100 1 f1010100: 00000080 .... Marvell>> md.l 0xF1010140 1 f1010140: 00018000 .... Marvell>> usb reset (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCby bodhi - Debian
cmp18, Here is another updated DTB. This time we'll get some more info. Power up, interrupt serial console and md.l 0xF1010000 8 md.l 0xF1010100 1 md.l 0xF1010140 1 usb reset md.l 0xF1010100 1 md.l 0xF1010140 1 And then boot into Debian like you did. Please post the entire serial console log.by bodhi - Debian
Thanks Trond!by bodhi - Debian
grumpy_old_bear, You could check the OpenWrt distro. They might have support for it. The LS1024A OpenWRT Linux-based SDK is optimized for both single- and dual-core operation. According to this info: https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-processors/layerscape-1024a-dual-core-processor:LS1024A QuoteThe LS1024A OpenWRT Linux-based SDK isby bodhi - Debian
Here is the latest update for the DTB. BTW, has anybody uploaded a stock boot log for this box here before? And is there any picture of the board?by bodhi - Debian
QuoteFixed. It appears that whoever created the page for the RN104 just copied my data for the RN102! Thanks Ray!by bodhi - Debian
> To confirm, here is the lspci of my RN104 : > > 00:01.0 PCI bridge: Marvell Technology Group Ltd. > 88F6710 ARM SoC (rev 01) > 00:02.0 PCI bridge: Marvell Technology Group Ltd. > 88F6710 ARM SoC (rev 01) > 01:00.0 USB controller: Fresco Logic FL1009 USB > 3.0 Host Controller (rev 02) > 02:00.0 SATA controller: Marvell Technology Group > Ltd. 88SE9215 PCby bodhi - Debian
adrien60, > I think you are wrong about the RN104, it has a > 88SE9215 4 port PCIE SATA controller > (http://web.archive.org/web/20240420194720/http://natisbad.org/NAS3/index.html) Thanks! Then the Wikidev is quite wrong. https://wikidevi.wi-cat.ru/Netgear_ReadyNAS_RN104 Will someone edit that page, thanks! > > I read elsewhere that the RN2120 has two 88SE9170 &by bodhi - Debian
Looks like we need a new DTB. usb_power: regulator@1 { compatible = "regulator-fixed"; reg = <1>; regulator-name = "USB Power"; regulator-min-microvolt = <5000000>; regulator-max-microvolt = <5000000>;by bodhi - Debian
MM, > also i found promwad.h and promwad.c from stock > u-boot sources, maybe they will be useful? These files are useful only for the LED, and recovery. No sight of USB power stuff. > > and forgot in the previous post: LED is always > green, power button - no action Try playing with the LEDs. echo none > /sys/class/leds/wtplug:red:stat echo default-on >by bodhi - Debian
All, Error in MM's log: [ 5.836334][ T52] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5.850461][ T52] hub 1-1:1.0: USB hub found [ 5.861972][ T52] hub 1-1:1.0: 7 ports detected [ 5.870201][ T52] hub 1-1:1.0: insufficient power available to use all downstream ports Have you checked the power supply?by bodhi - Debian
grumpy_old_bear, > As for the Debian, I have really basic skills with > it, so I prefer something with webUI, to set it > up, turn on and forget about it Unfortunately, I don't have kernel built for this box SoC! so I cannot help with installing Debian. Wishing you all the best, dealing with personal issue is very stressful.by bodhi - Debian
Hi Ray, > Curious as to why you're recommending the 370xp > kernel for the device rather than the > linux-6.11.6-mvebu-tld-1-bodhi.tar.bz2 kernel? The linux-6.11.6-mvebu-tld-1 kernel should work for most MVEBU boards, but won't work on these: RN102, RN104, Mirabox, and RN2120. This is due to the peculiarity with u-boot version installed in these boxes. It has a bug,by bodhi - Debian
adrien60, > I have 3 drives in my RN104, and they work. Thanks for the report. That mean something specific in RN2120 caused the problem. The RN2120 has Armada XP SoC., while the RN104 has Armada 370 SoC. They share common characteristics, but there are differences. > > BTW, I just noticed that the drives leds aren't > lit up, I don't know if that's normal.by bodhi - Debian
Hi Trond, Does all 4 drives working on your RN104? I'm wondering if the SATA PCI driver 88SE9170 on RN104 works (2 bays are connected to the PCIe bus). But it does not work on the ReadyNAS RN2120, also has the same 88SE9170 chipby bodhi - Debian
Hi phivo, > 6.11.6 kernel is even worse. It does not support > 2nd CPU or missing PCIe: Yes, 6.11.6-mvebu-370xp-tld-1 is a non-SMP kernel (intentionally). Kernel 6.7.5-mvebu-370xp-tld-3 has some problem running the other boxes (RN102/104 and Mirabox). So I had to go back to non-SMP. I just want to see if PCIe works on kernel 6.11.6-mvebu-370xp-tld-1 on this RN2120 box. Unforby bodhi - Debian
Alex, > it should be possible to bring > the box up with a stock uImage. Yes, in theory only. > but boptomg stops after > kernel being loaded That's normal. In order to boot stock kernel, most of the time you'll need to run stock u-boot. So kwboot the back up mtd0, and if it is successul, printenv and then post the serial console log.by bodhi - Debian
cmp18, > thank you so much! your dts/dtb are working fine > for my device (network and usb are working, iperf > ~700 Mbits/sec), but the device is working only > with kernel 6.6.3-kirkwood-tld-1 and older. With > newer kernels - the trouble that I wrote about > above: the device boot once out of ten times (and > works fine). in the other nine times - there is a >by bodhi - Debian
Ivan, > BTW, I am getting a new device, that I might need > your help with: DLink ShareCenter D-320 2 Bay > NAS. > It has a Marvell Kirkwood 88F6702 @ 1 > GHz according to > https://www.smallnetbuilder.com/nas/nas-reviews/d-link-dns-320l-sharecenter-2-bay-cloud-storage-2000-reviewed/ > > I will start a new thread for it once I obtain it. Perhaps continue withby bodhi - uBoot
Ivan, Quote> 12TB works just fine when rootfs is booted from > the USB, which makes me think that uboot driver is > not working well. Yes. It is indeed broken somewhere in mainline u-boot. So your plan to use USB rootfs is a good plan. I don't know when I will be able to revisit this and trouble shoot. I will try to debug using my 4TB HDD on another Kirkwood box.by bodhi - uBoot
Ivan, That's actually a very good test. The ID words have nothing DS211> sata init S/N: Firmware version: Product model number: Capablity: 0 sectors id[49]: capabilities = 0x0000 id[53]: field valid = 0x0000 id[63]: mwdma = 0x0000 id[64]: pio = 0x0000 id[75]: queue depth = 0x0000 id[76]: sata capablity = 0x0000 id[78]: sata features supported = 0x0000 id[79]: sataby bodhi - uBoot
Ivan, I've just posted the Dec 02 version above. > My plan was to use 2 x 12TB HDDs, and have the > rootfs installed on both, in case one fails it > will be still able to boot on the second one (I > assume this would work, wanted to give it a try > anyhow). I used 1TB HDD just for testing > purposes. > Since I can't boot from HDDs, I'll just use Uby bodhi - uBoot
Ivan, Here is the Dec 02 build. uboot.2024.10-tld-1.ds211.bodhi.tar.dec_02 sha256: 3d39a2be0fad1fc6a0aa4b709072819c69a67a5e30ed73a66da7810fd3d6199b This tarball contains 3 files. Ony the uboot.2024.10-tld-1.ds211.kwb is different from previous build. uboot.2024.10-tld-1.ds211.kwb uboot.2024.10-tld-1.ds211.environment.img uboot.2024.10-tld-1.ds211.environment The ATA ID wordsby bodhi - uBoot
Alex, > So, only question 1. remaining I don't see question 1. Can you repeat it?by bodhi - Debian
phivo, Please try the latest kernel: Latest released kernel: linux-6.11.6-mvebu-370xp-tld-1-bodhi.tar.bz2 (13 Nov 2024)by bodhi - Debian
Ivan > The power supply is original with 12V 6A. > I did run the old Synology OS with two 12TB HDD > drives, and it worked just fine, with OS installed > on the HHDs. > This makes me doubt that there is an issue with > the power, unless there are some boot time power > fluctuations. Power has 2 parts. Hardware and software. So the fact that you can run stock FW anby bodhi - uBoot
> Use hexedit to load the file and then search for > mtdparts. bootcmd=ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000 bootdelay=3 baudrate=115200 console=console=ttyS0,115200 mtdparts=mtdparts=orion_nand:0x0c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi)by bodhi - Debian
Alex, > is it poss. to get a mtd layout from? Use hexedit to load the file and then search for mtdparts.by bodhi - Debian
Alex, > with that dts compiled, > i'm able to bring the box up into stock rootfs > with all possible combination of > debian and stock uInitrd and uEnv.txt > (where i have the different paths for > stock and your dtb), - but stock uImage; > i have no output after stock uImage loads, > and there is no network activity on an > address i put in etc-networkby bodhi - Debian
Ivan, I'm convinced that there is a problem in u-boot regarding the large disk. It has nothing to do with SATA Identify. I've dumped the Identity words on my 4TB HDD and it looks fine. It seems flaky. Like there is not enough power. Large HDDs need 12V. For now, you should flash the Nov 22 version, which is OK with the normal HDD (i.e. 1TB) rootfs. And use it with the 12TB inby bodhi - uBoot