Bodhi, > Please try this new DTB. I also attached the new > DTS. I see a change in the log but eth0 failed as before. [ 8.539630] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 2 is missing. [ 8.547939] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 9 is missing. [ 8.556263] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 Now addressesby jhackert - Debian
Bodhi, here is the pci output from stock uboot Marvell>> help pci pci - short or long list of PCI devices on bus 'bus' pci header b.d.f - show header of PCI device 'bus.device.function' pci display[.b, .w, .l] b.d.f [# of objects] - display PCI configuration space (CFG) pci next[.b, .w, .l] b.d.f address - modify, read and keep CFG addrby jhackert - Debian
Bodhi, you will find uboot sources here. > GPL > sources DS413J build 24922 The Synology website is not sooo helpful when it's about those older hardware. Janby jhackert - Debian
Bodhi, here is a dmesg from stock with all 4 HDD bays slotted. jh@DS413J:/$ dmesg [ 0.000000] Linux version 2.6.32.12 (root@build4) (gcc version 4.6.4 (Marvell GCC release 20150204-c4af733b 64K MAXPAGESIZE ALIGN CVE-2015-0235) ) #25556 Thu Mar 4 17:56:48 CST 2021 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIby jhackert - Debian
Bodhi, this is stock kernel. I just copied & pasted a part of my post from June 21, 2022 02:54AM where a full boot log with stock is documented. It was only meant to show that the HDDs are started after uboot. If it helps, I can stuff 4 HDDs in the box and post a dmesg from a stock boot. Will this be helpful? Janby jhackert - Debian
Bodhi, bodhi Wrote: ------------------------------------------------------- > This u-boot is old, therefore use the ide command > to test. Insert an HDD to the 1st slot. Shutdown > and repeat for other slots. > > > ide reset > ide part > There is no ide command in this uboot. I watched the boot process. All 4 disks are spun down when I stopped the uboot iby jhackert - Debian
Bodhi, I wonder why they use regulators-hdd-34 for a box with 4 disk slots in the dts file kirkwood-ds411.dts and then define only 3 regulators in kirkwood-synology.dtsi regulators-hdd-34 It is disk 1 (1st slot from top of the box) that is not detected. I heard about dts just a couple of days before and I'm far away from really understanding them completely but this looks suspby jhackert - Debian
Discovered an interesting site, quick navigation cross referencesby jhackert - Debian
Bodhi, eth0 still is not found. The error about PIN20 already in use seems to have gone though. old [ 8.546624][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 8 is missing. [ 8.554977][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 9 is missing. [ 8.563299][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 8.571275][by jhackert - Debian
Bodhi, here is a link to the GPL sources from 06/2020 that seems to contain exactly the stock uboot 3.5.9 that is shown in the log. GPL sources DS413J build 24922 I will try the new DTS now. Janby jhackert - Debian
Bodhi, the box does have 1 Ethernet port. Following is a log of a standard boot including environment and available uboot help commands. I spotted that they set syno_hw_version=DS413jv10 in the environment and netif_num=1. __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ Vby jhackert - Debian
Heya, after my DS214 is unbricked, it's time to brick my old DS413J ;) I'm curious how a Debian would perform on it. The first steps looked quite promising but ... no network, no fun. [ 8.556268][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 8.564242][ T1] kirkwood-pinctrl f1010000.pin-controller: pin PIN20 already requested by f1080000.satby jhackert - Debian
Hi bodhi, well, the DS214 boots now and is fully unbricked and functional again ;) What did I change? Believe it or not, I simply unplugged the serial connector before booting after reading this in the file /arch/arm/boot/dts/armada-xp-synology-ds414.dts /* Connected to a header on device's PCB. This * provides the main console for the device. * * Warning: the deby jhackert - uBoot
I used this pinout successfully with these boxes in the past: DS214 (trying to unbrick now), DS413J, DS413 and DS118. I would bet that if you see a connector with 6 pins that it will be the serial port and that is uses this layout. I do use only 2, 4 and 6. A common plug that is used for connecting servos in RC model flight fits perfectly. Janby jhackert - Debian
Yes, I do use the front USB port. At first, it was not discovered by uboot. I had to "setenv usbActive 1". Then uboot found it. I'll check your thread and try to find a combination that works. Or maybe using a different stick or a USB hard drive will do. I'll see. Janby jhackert - uBoot
Bodhi, when starting kwboot with Synology's stock uboot, nearly instantly after the string "sending boot image" the string "Booting from SPI flash" shows up. In comparison, when using the UART kwboot it looks like this jh@i6600:~/syno$ sudo kwboot -t -a -p -B 115200 -b u-boot-spl-2019.10-tld-1.ds414.kwb /dev/ttyUSB0 password for jh: Sending boot message. Pleaby jhackert - uBoot
Hi folks, maybe one of you has a hint on how to get my DS214 fixed again. I bricked it while having a power outage during a downgrade. The result was the blue blinking of death. No boot. As I had not heard about kwboot, I desoldered the eeprom because it could not be read reliably while sitting in the board. I discovered that the zImage partition was partially erased. The other ones lookedby jhackert - uBoot