DS210j - flash chip failure and image rebuilding February 25, 2021 02:58PM |
Registered: 6 weeks ago Posts: 4 |
Re: DS210j - flash chip failure and image rebuilding February 25, 2021 04:05PM |
Admin Registered: 10 years ago Posts: 15,246 |
> 0x00000000-0x00080000 : "RedBoot" > 0x00080000-0x00280000 : "zImage" > 0x00280000-0x003c0000 : "rd.gz" > 0x003c0000-0x003d0000 : "vendor" > 0x003d0000-0x003f0000 : "RedBoot Config" > 0x003f0000-0x00400000 : "FIS directory"
[ 7.364601][ T1] 0x000000000000-0x000000080000 : "RedBoot" [ 7.371383][ T1] 0x000000080000-0x000000280000 : "zImage" [ 7.377942][ T1] 0x000000280000-0x0000003c0000 : "rd.gz" [ 7.384453][ T1] 0x0000003c0000-0x0000003d0000 : "vendor" [ 7.391052][ T1] 0x0000003d0000-0x0000003f0000 : "RedBoot config" [ 7.398293][ T1] 0x0000003f0000-0x000000400000 : "FIS directory"
Re: DS210j - flash chip failure and image rebuilding March 01, 2021 01:58PM |
Registered: 6 weeks ago Posts: 4 |
U-Boot 2015.10-tld-1 (Nov 06 2015 - 16:19:43 -0800) ZyXEL NSA310 1-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 256 MiB (ECC not enabled) WARNING: Caches not enabled NAND: 0 MiB *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Net: egiga0 PHY reset timed out MV88E1318 PHY initialized on egiga0 Hit any key to stop autoboot: 0 NSA310>Should i see SPI flash memory in log at this moment? Since old flash chip was fried i'm afraid of damaged CPUs SPI interface. "sflash info" gives unknown command.
Re: DS210j - flash chip failure and image rebuilding March 01, 2021 04:15PM |
Admin Registered: 10 years ago Posts: 15,246 |
Re: DS210j - flash chip failure and image rebuilding March 02, 2021 01:52PM |
Registered: 6 weeks ago Posts: 4 |
Tried as well. T5325 does not boot, dreamplug stops at ram detection. Pitty, because SPI was ready according to log ;)Quote
bodhi
have you tried
> uboot.2017.07-tld-1.t5325.mtd0.kwb or
> uboot.2017.07-tld-1.dreamplug.mtd0.kwb?
Re: DS210j - flash chip failure and image rebuilding March 02, 2021 04:09PM |
Admin Registered: 10 years ago Posts: 15,246 |
Re: DS210j - flash chip failure and image rebuilding March 03, 2021 02:02PM |
Registered: 6 weeks ago Posts: 4 |
U-Boot 2015.10-tld-1 (Nov 06 2015 - 16:19:43 -0800) ZyXEL NSA310 1-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 256 MiB (ECC not enabled) WARNING: Caches not enabled NAND: 0 MiB *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Net: egiga0 PHY reset timed out MV88E1318 PHY initialized on egiga0 Hit any key to stop autoboot: 0 NSA310> setenv ipaddr 192.168.1.50 NSA310> setenv serverip 192.168.1.10 NSA310> tftpboot 0x2000000 zImage Using egiga0 device TFTP from server 192.168.1.10; our IP address is 192.168.1.50 Filename 'zImage'. Load address: 0x2000000 Loading: T TFTP error: First block is not block 1 (0) Starting again NSA310> tftpboot 0x2000000 zImage Using egiga0 device TFTP from server 192.168.1.10; our IP address is 192.168.1.50 Filename 'zImage'. Load address: 0x2000000 Loading: ################################################################# ######################################### 7.5 MiB/s done Bytes transferred = 1551032 (17aab8 hex) NSA310> tftpboot 0x8000000 rd.bin Using egiga0 device TFTP from server 192.168.1.10; our IP address is 192.168.1.50 Filename 'rd.bin'. Load address: 0x8000000 Loading: ################################################################# ### 7.5 MiB/s done Bytes transferred = 995110 (f2f26 hex) NSA310> bootm 0x2000000 0x8000000 ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-2.6.32.12 Created: 2016-04-26 8:30:18 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1550968 Bytes = 1.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 08000000 ... Image Name: synology_88f6281_210j 5967 Created: 2016-04-26 9:42:51 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 995046 Bytes = 971.7 KiB Load Address: 00800000 Entry Point: 00800000 Verifying Checksum ... OK Loading Kernel Image ... OK Using machid 0x118f from environment Starting kernel ... Uncompressing Linux... done, booting the kernel.