Thanks Bodhi, I've been looking around and not much shows up. Going back to the DS215j, I want to try to compile and use the Synology DSM kernel (v3.2.4) with your Debian DeBootstrap install. How do I compile a kernel from source and use it within a Debian Debootstrap install. I guess I'll need some of Synologies custom libraries, but I'm not sure I've searched onlineby ZooMoo - Debian
This is not looking good without the docs. What is the latest SoC / NAS you'd recommend that's supported?by ZooMoo - Debian
I put the request for releasing the Armarda 375 documentation via their Request Information contact page https://www.marvell.com/request-information.html No response at all from Marvell. Maybe because I'm a nobody and not a registered company with an NDA? Are you able to try as well?by ZooMoo - Debian
Nice Bodhi! I've tested the LED/Beeps and they are working as expected. Shutdown (shutdown -h now) also works with the message: reboot: Power down qnap_power_off: triggering power-off.. I'll put in a request to Marvell for the very old Amarda 375 specification documents.by ZooMoo - Debian
Bodhi, Sorry, no luck in my search. It must be under an NDA :( Is the only way to get it is from Marvell/AMD or whoever owns it by signing an NDA?by ZooMoo - Debian
Synologies DSM 6.2 uses the v3.2.4 kernel which I compared to the stock kernel for the same version. To get the respective kernel sources for the armada 375: linux-3.x.txz https://global.synologydownload.com/download/ToolChain/Synology%20NAS%20GPL%20Source/6.2-25556/armada375/linux-3.x.txz Location of .config which shows the kernel version (# Linux/arm 3.2.40 Kernel Configuration): ./6by ZooMoo - Debian
A puzzle indeed. Given Synologies DSM uses the 3.x Kernel, then it may be a regression in later kernels (?). I'd like to try compiling a 3.x kernel to see if it works and rule out a regression in the 6.x kernel. How do you prepare the Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 file (https://forum.doozan.com/read.php?2,32146)? Do you have a build script?by ZooMoo - Debian
The DS215j doesn't support POE (https://global.download.synology.com/download/Document/Hardware/DataSheet/DiskStation/15-year/DS215j/enu/Synology_DS215j_Data_Sheet_enu.pdf). Would've been a cool feature though.by ZooMoo - Debian
Quotebodhi Either that, or the kernel misidentified the chip. Looking at the driver source, it looks like the 88E1510 is used as a catch all for the family of 88E151x PHY chips. It also contains a workaround for the 88E1514 bug. ./linux-stable/drivers/net/phy/marvell.c ... static int m88e1510_config_init(struct phy_device *phydev) { static const struct { u16 reg17, reg16;by ZooMoo - Debian
No luck re-running sgmii (armada-375-synology-ds215j_sgmii.tar) but the information maybe useful: root@debian:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII FIBRE ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frameby ZooMoo - Debian
It's odd though that u-boot shows it detect rgmii and not sgmii. U-Boot 2013.01-g5d1ab78 (Oct 27 2015 - 11:38:34) Marvell version: 2014_T2.0p3 mvBoardTwsiGet: Twsi Read fail mvBoardIoExpValSet: Error: Read from IO Expander failed Board: SYNO-DS215j SoC: MV88F6720 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU @ 800 L2by ZooMoo - Debian
I've tried to find the detailed specifications for the WD MyCloud Gen 2, but not much luck. The only official support page for the WD Cloud Gen 2 is the slightly differently named "WD Cloud Mirror Gen 2" WD Cloud Mirror (Gen 2) https://support-en.wd.com/app/products/product-detailweb/p/137 Yet, there are no hardware specifications. I found the manual else where (https://by ZooMoo - Debian
1. armada-375-synology-ds215j-jan-20.tar After fresh reboot: root@debian:~# mii-tool -v eth0 eth0: negotiated 1000baseT-FD flow-control, link ok product info: vendor 00:0a:c2 or 00:50:43, model 29 rev 1 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertisingby ZooMoo - Debian
bodhi Wrote: > Please try these 2 tests. In each test we turn off > auto negotiation. > > 1. With armada-375-synology-ds215j-jan-20.tar. > Boot, log into Debian and > > > /usr/sbin/ethtool -s eth0 autoneg off > ifdown > ifup > root@debian:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII FIBRE ] Supported liby ZooMoo - Debian
Thanks Bodhi. I started looking for the specification documents for both the Marvell Amada 375 (88F6720) and the ETH Marvell 88E1514. Which may help with the DTS. I cannot find anything for the Marvell Amada 375 (88F6720) (maybe under NDA???...), even the kernel docs only mentions the product brief and not the hardware specs. https://docs.kernel.org/arch/arm/marvell.html Armada 375 Flavby ZooMoo - Debian
Another approach I've tried is to extract the DTB and convert it to a DTS from the Synology DSM installation PAT file. However, it has not worked, see below. Download DSM from: https://archive.synology.com/download/Os/DSM/6.2.4-25556 Extract file: $ binwalk -e DSM_DS215j_6.2.4-25556.pat $ cd _DSM_DS215j_6.2.4-25556.pat.extracted/ Install extract-dtb tool: $ pipx insby ZooMoo - Debian
Here is the initial u-boot log of the DS215j. 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 TWSI Read failed Error reading from TWSI DDR3 Training Sequeby ZooMoo - Debian
Do you think the problem lies in the DTS (missing some parameter setting or adjustment) or it's a problem with the kernel/driver?by ZooMoo - Debian
Is there additional debugging / flags I can turn on to show where the problem could be?by ZooMoo - Debian
Thanks Bodhi, Checking the logs, I get everything you've listed above except for ethact and ethprime. $ cat synology_ds215j_eth1_v2025-03-12.log | grep -E "RGMII0|PON|SERDES|Lane |Net:|syno:|Using egiga|ethact|ethprime" RGMII0 Module on MAC0 PON ETH SERDES on MAC1 SERDES configuration: Lane #0: PCIe0 Lane #1: SATA1 Lane #2: SATA0 Lane #3: USB3 Net: egiga0,by ZooMoo - Debian
I've tried the latest version, but you were correct, it didn't fix this problem: root@debian:~# dmesg | grep eth mvpp2 f10f0000.ethernet: using 3 shared buffers mvpp2 f10f0000.ethernet eth0: Using hardware mac address 00:00:00:00:00:04 mvpp2 f10f0000.ethernet eth0: validation of mii with support 00,00000000,00000000,000066ff and advertisement 00,00000000,00000000,000066ff failedby ZooMoo - Debian
Hi Bodhi, I just compared this latest DTS (armada-375-synology-ds215j_mii.tar (20 KB)) with the version from 20th Jan, and they are the same. They both contain phy-mode = "rgmii-id"; . Should it be phy-mode = "mii"?by ZooMoo - Debian
Here are the results for using the DTS from https://forum.doozan.com/read.php?2,138851,138913#msg-138913. According to ethtool the ports show three options, TP, MII and Fibre whilst the Synology DSM OS only has TP/MII. Eth0 then wrongly sets the port to Fibre when an ethernet cable is plugged in. In the WD MyCloud Gen2 (Glacier, Armada 375) thread (https://forum.doozan.com/read.php?2,94839)by ZooMoo - Debian
> It does look like SGMII is incorrect. We shoul dgo back to the previous DTB, with RGMII-ID. I've used the following dtb file from your download: armada-375-synology-ds215j_rgmii.tar (20 KB) This is the correct one? Once booted, I get the following output from ifconf and ethtool. The following message appears when disconnected the ethernet cable: mvpp2 f10f0000.etheby ZooMoo - Debian
I've compared the output of ifconfig, ethtool, etc between the stock DSM OS and debian. Booting the stock DSM OS I can connect to the network so it's not a network issue. DSM $ sudo ifconfig -a eth0 Link encap:Ethernet HWaddr <MACADDRESS> inet addr:192.168.1.238 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: <IP6 ADDRESSS>/64by ZooMoo - Debian
Sorry, there was a problem between keyboard and seat. I used the wrong kernel (6.12.6) to build the image, instead of the correct kernel (6.6.2). ~# sudo su - ~# cd /media/user1/usb_stick/boot/ /media/user1/usb_stick/boot# cp -a zImage-6.6.2-mvebu-tld-1 zImage.fdt /media/user1/usb_stick/boot# cat ./dts/armada-375-synology-ds215j_gmii/armada-375-synology-ds215j.dtb >> zImage.fdtby ZooMoo - Debian
Thanks Bodhi, I've tried each DBT version, but in all three cases, eth0 was missing. Below is the kernel log for gmii, but I've compared the logs for the other two versions and they are the same. The likely error is the following in the logs: Configuration file wrong or corrupted <13>Feb 25 02:06:59 root[2084]: Cannot read u-boot env ethaddr Creation of the bootby ZooMoo - Debian
I still cannot find the u-boot source... this will help right? I'll contact Synology to ask where it is.by ZooMoo - Debian
> Try using a different ethernet cable and/or plug it in to a different switch. Shouldn't the router and cable be ok? The router and cable are the same ones I used when you got me to "setenv ipaddr" whilst in u-boot. ping worked in the case of u-boot. Even if ping works within u-boot, could something else be wrong with the router/cable? Strangely, when I unplug the ethby ZooMoo - Debian