Quote In serial console, try to initialize the drives. Can uboot see all drives and can you list each partition’s content? Only two drives or I am doing something wrong Marvell>> scsi init AHCI init for unit0 Target spinup took 0 ms. SATA link 1 timeout. SATA link 0 timeout. Target spinup took 0 ms. SATA link 2 timeout. SATA link 3 timeout. AHCI 0001.0000 32 slots 4 portby zifxify - Debian
Quote Do you mean only the HDD in slot 0 is enable? using your lastest dtb without soc sata, and without setting GPIO pin 37 as high, there's only drive (drive 2) available. Enabling soc sata also enables drive 1 (slot 0)by zifxify - Debian
with the rackstation in front of you, from left to right drives numbered 1 to 4. GPIO pin 15 (drive {2}) GPIO pin 37 (drive {3,4}) GPIO pin 6 turns on the led controller. For Ethernet and drive leds, I assume this works different than for example status led and power-on led controlled by UART1. Ethernet 1 led works correctly. When unplugging Ethernet 1 cable, led goes out. Ethernet 2 (nby zifxify - Debian
still one drive accessible root@debian:~# ls -al /dev/disk/by-path total 0 drwxr-xr-x 2 root root 120 Jan 25 09:37 . drwxr-xr-x 7 root root 140 Jan 25 09:37 .. lrwxrwxrwx 1 root root 9 Jan 25 09:38 platform-f10f8000.usb3-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sdb lrwxrwxrwx 1 root root 10 Jan 25 09:38 platform-f10f8000.usb3-usb-0:1:1.0-scsi-0:0:0:0-part1 -> ../../sdb1 lrwxrwxrwx 1by zifxify - Debian
Marvell>> boot (Re)start USB controller... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 USB1: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 Booting Debian . . . (Re)start USB... USB0: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices...by zifxify - Debian
Quote I think your/bohdi's next steps will be to try disabling the soc sata and confirm you're accessing those disks via sata then work on enabling the other disks, though you can do it the other way around. so this means one drive accessible through pcie and another accessible via soc sata I guess ? root@debian:~# ls -al /dev/disk/by-path total 0 drwxr-xr-x 2 root root 160 Jby zifxify - Debian
Quote But let's see how the new kernel version linux-4.19.1-mvebu-tld-1 behaves with the armada-385-synology-rs816.dtb, before we change the DTS. :) first two drives are accessible, mountable in Debian Marvell>> boot (Re)start USB controller... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 USB1: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1by zifxify - Debian
Quote I'm guessing it's the same for this synology device. If so enabling pcie in the device-tree should allow debian to find all 4 drives. something like this in the orginal dts ? pcie-controller { compatible = "marvell,armada-38x-pcie"; status = "okay"; device_type = "pci"; #address-cells = <0x3>; #size-cells = <0x2>by zifxify - Debian
Quote zifxify, Please try this new armada-385-synology-rs816.dtb. stops at random: fast init done Marvell>> boot (Re)start USB controller... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 USB1: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 Booting Debian . . . (Re)start USB... USB0: Port (usbActive) : 1 Interface (usbType = 3) : USB XHby zifxify - Debian
Quote We can move on to 4 SATA which is the next important issue. Are they all active in Debian? i.e. the disks can be mounted and accessed? The first two SATA ports are supplied with power but only the first one is working correctly. When inserting a drive in the second SATA port, nothing happens. Only harddrive 1 is active in Debian and can be mounted. SATA port {3,4} are not powered at allby zifxify - Debian
Quote Now try to set some test env. fw_setenv test1 yes fw_printenv test1 Reboot, interrupt serial console and printenv OK, back to testing and saving envs seems to work :) root@debian:~# fw_setenv test1 yes root@debian:~# fw_printenv test1 test1=yes Marvell>> printenv test1 test1=yesby zifxify - Debian
Quote All steps can be done using serial console. I was connected remotely to a laptop with a serial port (using SSH), and used a screen session to /dev/ttyS0. Quote When you said it just works, did you test these codes on /dev/tty1? Yes, in Debian and DSM as root echo X > /dev/ttyS1by zifxify - Debian
Quote This actually makes sense. As I said, I need to creat a new DTS. The reason for the SATA ports behavior is the RS816 has 4 SATA ports, but the DS116 has only 2 SATA ports. This behavior has nothing to do with Power Off. Ok, but the fact that the SATA ports are still powered after a shutdown. Is this normal behavior ? Quote Now try to set some test env. fw_setenv test1 yes fw_prinby zifxify - Debian
Quote And test the definition: fw_printenv root@debian:~# fw_printenv CASset=max MALLOC_len=5 MPmode=SMP ata_hdd_detect=syno_hdd_detect=39,39,39,39 ata_hdd_enable=syno_hdd_enable=37,37,37,37 autoload=no baudrate=115200 boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr bootargs= bootargs_dflt=$console $nandEcc $mtdparts_lgcy $bootargs_root nfsroot=$serby zifxify - Debian
little bit outdated ... Pure Debian Firmware: https://www.dropbox.com/sh/yz02o5l4nl7uhv5/AAA-GjIVUl6YQZcAmAiui8haa?dl=0 Stock Debian Firmware: https://www.dropbox.com/sh/r8r2ssn56mzjgf1/AACKVA1N_qNrm1cX8F9bm7Uja?dl=0by zifxify - Debian
Found this: https://www.synology-wiki.de/index.php/LEDs_und_Buttons and this just works. There's a second serial port on the device (also with header). Only the ethernet leds and drive leds chars I have not found yet.by zifxify - Debian
Quote 1. Does the power off work with ./boot/dts/armada-385-synology-ds116.dtb ? I actually meant armada-385-synology-ds116.dtb instead of ds116.dtb. (Debian) Poweroff from Debian works but SATA ports keeps active (drive spinning when actually plugging and unplugging the drives (after poweroff command ofcourse) in the two of four drive bays) and the power-on leds keeps flickering. (it'by zifxify - Debian
Quote Mtd1 indeed :) I forgot that I’ve already figured out this location from uboot envs! Lol, I don't even find it in the sources and you just read almost everything from envs :) some further remarks on the current working state of the rs816 (using the ds116.dtb) When I power off the device booted from debian, both sata ports {1,2} stay active until the device is reset (unpluggby zifxify - Debian
Quote Is that what's in stock OS? They are indeed not making any sense. Try again In stock OS, cat /etc/fw_env.config No, I did not know what I was doing, sorry. In stock OS there's not such a thing as fw_env.config I have searched in the u-boot sources (include/configs/board) for the RS816.h ( CONFIG_ENV_SIZE, CONFIG_ENV_SECT_SIZE ,CONFIG_ENV_OFFSET,... but no luck) But I tby zifxify - Debian
admin@SrvNas1:~$ ls -l /sys/class/leds/ total 0 admin@SrvNas1:~$ ls -lR /proc/device-tree/ ls: cannot access /proc/device-tree/: No such file or directoryby zifxify - Debian
What am I doing wrong ? This isn't correct :/ # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0x00000000 0x00400000 0x00001000 400 /dev/mtd1 0x00000000 0x00400000 0x00001000 400 (and only 2 of the 4 sata ports works because of ds116 dtb)by zifxify - Debian
root@debian:~# dmesg | grep -i spi [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi0.0:4m(boot),-(spi-rootfs) earlyprintk=serial init=/bin/systemd [ 1.240774] m25p80 spi0.0: found n25q064, expected mx25l6405d [ 1.246548] m25p80 spi0.0: n25q064 (8192 Kbytes) [ 1.251211] 2 cmdlinepart partitions found on MTD device spi0.0 [ 1.2by zifxify - Debian
bodhi Wrote: ------------------------------------------------------- > Awesome :) > > Now you should double check the system specs to > see if everything is what it supposed to be: RAM, > CPU, SPI, RTC, sensors,...etc. > > The LED lights should not be difficult. We can > figure out those from GPL source, or from stock OS > while it is running. The fans aby zifxify - Debian
is this the last line you see on serial console? [ 4.675845] random: fast init done yes but now with your mainline ds116 dtb, it does boot succesfully :) (thank you), although the lights aren't working correctly. Marvell>> boot (Re)start USB controller... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 USB1: Port (usbActive) : 1 Interface (usbTyby zifxify - Debian
bootlog when using the synology ds116 dtb. Marvell>> boot (Re)start USB controller... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 USB1: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 Booting Debian . . . (Re)start USB... USB0: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) founby zifxify - Debian
more luck dtc -I dtb -O dts -o armada-385-synology-rs816.dts dtbdump_3.dtb Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /soc has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /soc/bootrom has a reg or ranges property, but no unit name Warning (unit_address_vs_reg): Node /soby zifxify - Debian
I tried to extract and convert the dtb to dts. ./extract-dtb.py zImage Dumped 00_kernel, start=0 end=2380 Dumped 01_dtbdump__p@-.dtb, start=2380 end=2558520 Extracted 1 appended dtbs + kernel to dtb dtc -I dtb -O dts -o armada-385-synology-rs816.dts 01_dtbdump__p@-.dtb FATAL ERROR: Error reading DT blob: Bad addressby zifxify - Debian
Marvell>> boot (Re)start USB controller... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 USB1: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 Booting Debian . . . (Re)start USB... USB0: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices...by zifxify - Debian
This are all the commands I used to generate the rootfs system. sudo parted --script /dev/sdX \ mklabel msdos \ mkpart primary ext3 1MiB 100% sudo mkfs.ext3 -L rootfs /dev/sdX1 ROOTFSDIR=$(mktemp -d) sudo mount /dev/sdX1 $ROOTFSDIR sudo tar -C $ROOTFSDIR -jxvf Debian-4.12.4-mvebu-tld-1-rootfs-bodhi.tar.bz2 cp -a zImage-4.12.4-mvebu-tld-1 zImageby zifxify - Debian
I think, I did something wrong with the zImage but I just followed the instructions -> cp -a zImage-4.12.4-mvebu-tld-1 zImage Marvell>> boot (Re)start USB controller... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 USB1: Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00 Booting Debian . . . (Re)start USB... USB0: Port (usbActive) : 1 Interby zifxify - Debian