Steps 3.c root@debian:/# cd /media/sdb1/boot root@debian:/media/sdb1/boot# dd if=uImage of=/dev/sdb bs=1MiB seek=10 4+1 records in 4+1 records out 5075485 bytes (5.1 MB, 4.8 MiB) copied, 0.0292306 s, 174 MB/s root@debian:/media/sdb1/boot# dd if=uInitrd of=/dev/sdb bs=1MiB seek=20 9+1 records in 9+1 records out 9488618 bytes (9.5 MB, 9.0 MiB) copied, 0.0482732 s, 197 MB/s root@debiaby bonk1990 - Debian
Steps 2.b root@debian:~# fdisk /dev/sdb Welcome to fdisk (util-linux 2.33.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0x6e5f77a4. Command (m for help): g Created a new GPT disklabel (GUID: 7004DF3A-A8B9-534Aby bonk1990 - Debian
In order not to lose: Marvell>> printenv CASset=max MALLOC_len=5 MPmode=SMP ata_hdd_enable=syno_hdd_enable=15 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=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0by bonk1990 - Debian
I'm sorry again. There was one step that i should do by myself and i failed... Now everythink works great: Marvell>> mw.l f1018100 00008000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd_addr 0x3000000 Marvell>> setenv load_image 'echo loading uImage from raw HDD ...; scsi device 0; scsi read $load_image_addr 0x5000 0x2F00'by bonk1990 - Debian
I'm sorry. I caused this problem when I was using fdisk. Should be: First sector (2048-62533262, default 2048): 102400 not: First sector (2048-62533262, default 2048): 51200by bonk1990 - Debian
So I tried to update kernel and save genereted files to raw sectors. This is log: root@debian:/boot# e2fsck /dev/sdb1 e2fsck 1.44.5 (15-Dec-2018) rootfs: clean, 24113/1954064 files, 356717/7810257 blocks root@debian:/boot# ls . linux-headers-5.2.9-mvebu-tld-1_1.0_armhf.deb .. linux-headers-5.9.3-mvebu-tld-1_1.0_armhf.deb Systeby bonk1990 - Debian
Thanks, good thinking! I will update kernel. I hope that writing to raw sector now (not before rootfs creation) will not break everything.by bonk1990 - Debian
Changed fstab, with extra usb Press Ctrl+C to abort autoboot in 3 second Marvell>> mw.l f1018100 00008000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_image 'echo loading uImage from raw HDD ...; scsi device 0; scsi read $load_image_addr 0x5000 0x2F00' Marvell>> setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=by bonk1990 - Debian
Marvell>> mw.l f1018100 00008000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_image 'echo loading uImage from raw HDD ...; scsi device 0; scsi read $load_image_addr 0x5000 0x2F00' Marvell>> setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts earlyprintk=serial"' Marvell>by bonk1990 - Debian
i will not forget. I'm still open for testing. Is there a way to resolve problem with ssh server start? Should I remove some files from bootfs?by bonk1990 - Debian
Ok, so now i have this: root@debian:~# e2fsck /dev/sdb1 e2fsck 1.44.5 (15-Dec-2018) rootfs: clean, 24100/1954064 files, 341011/7810257 blocks root@debian:~# reboot Broadcast message from root@debian (ttyS0) (Wed Using makefile-style concurrent boot in runlevel 6. [ ok ] Stopping hotplug events dispatcher: systemd-udevd. [ ok ] Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon. [....] Sby bonk1990 - Debian
root@debian:/# e2fsck /dev/sdb e2fsck 1.44.5 (15-Dec-2018) ext2fs_open2: Bad magic number[ 1007.779919][ T1686] sdb: sdb1 in super-block e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/sdb The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it reallyby bonk1990 - Debian
By wipe do you mean: dd if=/dev/zero of=/dev/sdb bs=1MiB ?by bonk1990 - Debian
Marvell>> mw.l f1018100 00008000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_image 'echo loading uImage from raw HDD ...; scsi device 0; scsi read $load_image_addr 0x5000 0x2F00' Marvell>> setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts earlyprintk=serial"' Marvell>by bonk1990 - Debian
I'm very greatful for your help! Procedure: root@debian:~# dd if=/dev/zero of=/dev/sdb bs=1MiB count=50 50+0 records in 50+0 records out 52428800 bytes (52 MB, 50 MiB) copied, 0.533839 s, 98.2 MB/s root@debian:~# fdisk /dev/sdb Welcome to fdisk (util-linux 2.33.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command.by bonk1990 - Debian
Ok, I will create hdd rootfs one again. Marvell>> mw.l f1018100 00008000 Marvell>> scsi init AHCI init for unit0 Target spinup took 0 ms. SATA link 1 timeout. Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: ST4000VN008-2DR1 Rev: SC60 Type: Hard Disk Capacity: 3815447.8 MB =by bonk1990 - Debian
Ok, I can boot with tftp and another HDD: Marvell>> mw.l f1018100 00008000 Marvell>> setenv ipaddr 192.168.0.20 Marvell>> setenv serverip 192.168.0.1 Marvell>> setenv load_initrd_addr 0x3000000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_image 'echo loading uImage from tftpserver ...; tftpboot $load_image_addr uImage' Maby bonk1990 - Debian
I have the same error: SCSI device 0: Device 0: (0:0) Vendor: ATA Prod.: ADATA SP600 Rev: 2.9 Type: Hard Disk Capacity: 30533.8 MB = 29.8 GB (62533296 x 512) ... is now current device SCSI read: device 0 block # 40960, count 20224 ... 20224 blocks read: OK ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-5.2.9-mvebu-tld-1 Creatby bonk1990 - Debian
I hope Synology will send me that in respond for my request.by bonk1990 - Debian
This is official repo: https://github.com/MarvellEmbeddedProcessors/u-boot-marvell Maybe it is from github: https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/commit/071ddd9220bb42ee6bc854cc7ec5d91205eb7637 Another one: https://github.com/embeddedarm/u-boot-armada38xby bonk1990 - Debian
bodhi Wrote: ------------------------------------------------------- > I found > it quite strange that it is under > armada38x-source: > > https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/24922branch/armada38x-source/ > > but the RS816 and DS116 don't have a build script. > Only other Synology boxes that use Armada 370 and > XPby bonk1990 - Debian
To bad. Thanks for info. Maybe u-boot-mv-3.6.0.txz? Maybe -mv means Marvell?by bonk1990 - Debian
Hm, will that be good? https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/24922branch/armada38x-source/by bonk1990 - Debian
I don't know what is wrong yet, but I have a question. If (in future) i want to update kernel i need to zero first 50MB of HDD every time (every kernel update)? If i'm not wrong this command break partition table on HDD. Second question: usb rootfs How to update kernel? By this procedure? cd /boot dd if=uImage of=rs816.uImage.mtd2.kwb bs=7104k conv=sync flashcp -v rs816.uImageby bonk1990 - Debian
Boot procedure with USB and tftp works fine. And it is the same address? setenv ipaddr 192.168.1.19 setenv serverip 192.168.1.20 setenv usb_setup 'setenv usbActive 1; setenv usbType 3; usb start;' setenv load_initrd_addr 0x3000000 setenv load_image_addr 0x02000000 setenv load_image 'echo loading uImage from tftpserver ...; tftpboot $load_image_addr uImageby bonk1990 - Debian
I was testing with 4TB HDD because I wanted to hear that disk was powered up. After that I switch to 32GB SSD. It is correct size.by bonk1990 - Debian
My test: Press Ctrl+C to abort autoboot in 3 second Marvell>> mw.l f1018100 00008000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd_addr 0x3000000 Marvell>> setenv load_image 'echo loading uImage from raw HDD ...; scsi device 0 ; scsi read $load_image_addr 0x5000 0x2F00' Marvell>> setenv load_initrd 'eby bonk1990 - Debian
I have tested every bit. This is correct command: mw.l f1018100 00008000 So GPIO number 23... Don't know why, but it is. Marvell>> mw.l f1018100 00008000 Marvell>> scsi reset Reset SCSI AHCI init for unit0 Target spinup took 0 ms. SATA link 1 timeout. Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found scanning bus for devices... Device 0: (0:0) Venby bonk1990 - Debian
Marvell>> md.l f1018100 1 f1018100: 00000000 .... Marvell>> md.l f1018140 1 f1018140: 00040000 .... So: mw.l f1018100 00080000 But: Marvell>> mw.l f1018100 00080000 Marvell>> scsi reset Reset SCSI AHCI init for unit0 SATA link 0 timeout. SATA link 1 timeout. Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found scanning bus for devices...by bonk1990 - Debian
armada-385-synology-ds116.dtb reg_sata0: pwr-sata0 { compatible = "regulator-fixed"; regulator-name = "pwr_en_sata0"; regulator-min-microvolt = <12000000>; regulator-max-microvolt = <12000000>; enable-active-high; regulator-boot-on; gpio = <&gpio0 15 GPIO_ACTIVE_HIGH>; I have no idea how to use it in "mw.l" command.by bonk1990 - Debian