Hi bodhi, I never extracted the dtb from the nas, I am using the stock one, which is automatically loaded by u-boot. I only changed the kernel image and nothing else to avoid breaking the boot process. I didn't find any documentation regarding the PIC. I attach the dmesg log of the debian boot to this post. regards, Martinby lonestar - Debian
Hi bodhi, unfortunately I don't know how to tell. To take a closer look at the board I would have to dismantle it, which I so far have avoided. Is there some easier way? regards, Martinby lonestar - Debian
Ok, my project is now finished: The site https://smallhacks.wordpress.com/2012/04/17/working-with-synology-hardware-devsynobios-and-devttys1/ helps a lot about controlling LEDs and FAN. printf "V10" > /dev/ttyS1 sets the fan speed to 10% printf "\\x38" > /dev/ttyS1 sets the status LED green. The site has further constants which can be used to control theby lonestar - Debian
1) Goal: I wanted to boot debian on my ds218play. Final idea is to have a NAS with an 4 TB SSD and a 6 TB HDD, where the HDD can shut down when unused (and not spin up for several days). Additionally I wanted to limit the changes to the NAS as much as possible. During tests with my other NAS (ds214) I had issues when saving the u-boot environment, so I wanted to keep this as-is. As a resby lonestar - Debian
I did some further tests and even found the original kernel config of synology in their gpl sources. Unfortunately when I use this config on an 6.0.8 kernel the kernel gets quite big (>20MB) u-boot seems to only support the typical 8MB image, as I get "Loading Kernel Image ... Image too large: increase CONFIG_SYS_BOOTM_LEN". As I want to avoid having to flash the u-boot instanceby lonestar - Debian
Hi, Update: see guide at: https://forum.doozan.com/read.php?2,135588,135872#msg-135872 (=later post in this thread) back again. As I have finished my tests with the ds214 and it working as my "productive" NAS now I wanted to see whether I can get my ds218play working. This is a bit different, as it uses an Realtek rtl1296 cpu. I managed to connect the UART to it and stop atby lonestar - Debian
Hi, with a lot of help from bodhi I managed to get my own debian onto my Synologx DS214 NAS. For those of you who want to repoduce this I created a small summary below. Note that I assume here that you know your way around linux. This is not intended to be a full beginners guide. === State === Currently the following periphery is working and tested on my NAS: - two SATA ports - front anby lonestar - Debian
Hi bodhi, I changed the message title. I will create an installation guide somewhen in next few days. regards, Martinby lonestar - Debian
Hi bodhi, I checked the led bahvior: For debian: - hdd leds are yellow on u-boot (regardless of whether a disk is in there) - hdd leds turn off when kernel starts to load and never turn on again - status led remain off all the time For stock: - hdd leds are yellow on u-boot (regardless of whether a disk is in there) - hdd leds turn off when kernel starts - hdd leds are still off whenby lonestar - Debian
Hi bodhi, front usb works using the first patch. (I tested with my self-built kernel and initrd which is actually just your kernel config + enabling the bcache driver) Cheers, Martinby lonestar - Debian
Ah I missed the question in the last post :) The front usb is the usb2 port. This doesn't work in linux The back usbs are usb3 (connected to the pcie controller). These work. Thanks, Martinby lonestar - Debian
Hi bodhi, I have for now recompiled the stock u-boot to change the default boot command to boot from the front usb (the only one that works on stock). So I have a working NAS where I can do some experiments. For me the hardware support is sufficient for now. Regarding your list: - RTC works - LEDs do not show up in /sys/class/led (not needed for me at the moment) - hw monitoring: I didnby lonestar - Debian
Hi bodhi, very good news and I want to apologize for the additional work that I caused. Both SATA work when using stock u-boot with your kernel and the new device tree. Replug is a little strange as the device nodes in /dev don't get reliably updated, but replugging is not a requirement for me at least. I tried to read and write from a file from one of the disks and it worked fine.by lonestar - Debian
Hi bodhi, I did some experiments today and I am now able to compile and boot stock u-boot. This means we can add traces wherever we like :) As a first test I enabled the tracing in mvLog.h and partially enabled the REG_DEBUG tracing. REG_DEBUG can't be fully enabled as u-boot won't boot any more afterwards. A comment mentions this only work with Lauterbach and I guess it is caby lonestar - Debian
Hi bodhi, i did the tests again with the original 6.0.7 kernel. Behavior is the same as previously in post from "December 04, 2022 01:06PM" Attached the two logs. I used only one disk in either SATA 1 or SATA2. thanks, Martinby lonestar - Debian
Hi bodhi, ok I will do the tests with the original kernel. Might take a few days as I will be rather busy this week. thanks, Martinby lonestar - Debian
Hi bodhi, my box supports hotplug of sata devices. I tested with the 7200 drive: In SATA1: - drive starts without spinning - ide reset in u-boot does not spin up - in linux drive spins up but is not detected - after unplugging, waiting, plugging the drive does not spin In SATA2: - drive starts without spinning - ide reset in u-boot spins up drive - in linux the drive is not detecby lonestar - Debian
Hi bodhi, sorry, I apparently misunderstood you at that time. I redid the last tests: First of all: when using stock u-boot with self-built kernel+initrd ethernet WORKS!!! With your latest patch, which added the regulators both drives are spinning (I did a ide reset in u-boot and at that time the SATA2 drive started) Unfortunately there are still no disks detected in debian. Thinkingby lonestar - Debian
Hi bodhi, I have so far failed to boot debian from stock u-boot. Will have to try more tomorrow. In stock u-boot: Press Ctrl+C to abort autoboot in 3 second Marvell>> md.l f1018000 8 f1018000: 00000000 00000000 00000000 00000000 ................ f1018010: 11110000 00004000 00000000 00000000 .....@.......... Marvell>> md.l f1018100 1 f1018100: 00000000 .... Marvby lonestar - Debian
Hi bodhi, a maybe important difference is that the disk that does not spin up at all in the self-built u-boot is a 7200 rpm disk. The other one is a 5400 rpm disk. I tested with stock u-boot: ide reset found the 7200 disk in sata 2. but not the 5400 drive in sata 1. Then I exchanged the two disks: it found the 5400 disk in sata 2 but not the 7200 in sata 1. This was reproducible.by lonestar - Debian
Hi bodhi, a very morising idea, yet no improvement so far. see attached dmesg.txt. Added a dump of sys/class/regulators, to confirm that the setting arrived at the kernel. Test was done with - 2 disks (see dmesg), - one disk that failed to spin up on any of the two sata ports alone in both of the ports. results: exactly the same behavior as before. thanks, Martinby lonestar - Debian
Hi bodhi, they are both 3.5" HDDs regards, Martinby lonestar - Debian
Hi bodhi, I did some further tests now with two different disks: Disk1: - spins up on sata 1 when link down is shown, but link never goes up - spins up on sata 2 before u-boot loads and never stops Disk2: - doesn't spin up on any of the two sata ports. Note that both disks work in stock image. This looks to me that this is not just a device tree issue, but maybe some timeoutby lonestar - Debian
Hi bodhi, SATA 1 regulator works correctly. For SATA 2 even when all are configured the disk does not spin up (previously I only tested with one disk). I will have to do further tests, but it likely won't happen before the weekend. thanks, Martinby lonestar - Debian
the corresponding output from stock: lonestar@ds214:/$ cat /proc/interrupts CPU0 CPU1 5: 4666 4188 axp_irq axp_local_clockevent 8: 26 0 axp_irq mv_eth 31: 92 0 axp_irq mv64xxx_i2c 41: 1188 0 axp_irq serial 42: 1 0 axp_irq serial 45: 0 0 axp_iby lonestar - Debian
i did a cat /proc/interrupts as suggested by a friend: root@debian:~# cat /proc/interrupts CPU0 CPU1 24: 5120 10230 MPIC 5 Level armada_370_xp_per_cpu_tick 25: 0 0 MPIC 3 Level arm-pmu 33: 2 0 MPIC 51 Level f1060900.xor 34: 2 0 MPIC 94 Level f10f0900.by lonestar - Debian
Hi bodhi, Interesting fact: the drive is correctly powered up after ata2 link down message. This is the same behavior as on stock image. So at least this part seems to be ok. Unplugging network during dhcp request leads to the following messages: Quote Listening on LPF/eth0/00:50:43:02:02:00 Sending on LPF/eth0/00:50:43:02:02:00 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255by lonestar - Debian
I think we are on the right track with the sata controller: stock firmware: Quote [ 150.114185] sata_mv sata_mv.0: version 1.28 [ 150.114250] sata_mv sata_mv.0: cannot get clkdev [ 150.118980] sata_mv sata_mv.0: slots 32 ports 2 [ 150.124957] scsi0 : sata_mv [ 150.128240] scsi1 : sata_mv [ 150.131399] ata1: SATA max UDMA/133 irq 55 [ 150.135512] ata2: SATA max UDMA/133 irq 55 [by lonestar - Debian
Hi bodhi, doesn't work yet: on u-boot sata init blocks forever. On linux the following lines are in the dmesg output: Quote [ 3.286187][ T1] scsi host0: sata_mv [ 3.291223][ T1] scsi host1: sata_mv [ 3.295841][ T1] ata1: SATA max UDMA/133 irq 37 [ 3.300665][ T1] ata2: SATA max UDMA/133 irq 37 [ 3.636269][ T674] ata1: SATA link down (SStatus 0 SControby lonestar - Debian
Hi bodhi, I am currently looking at the GPL source code of synology which seems to be the correct one: https://master.dl.sourceforge.net/project/dsgpl/Synology%20NAS%20GPL%20Source/24922branch/armadaxp-source/u-boot-armada-2011.12.txz?viasf=1 While I am a software developer myself, my knowledge of u-boot is very limited. An interesting detail, that I have found so far: In file mvBoardEnvby lonestar - Debian