Replacing the CPU worked in my case. Not sure if reballing of old one could fix it, or maybe chip itself was faulty.by twizzter - uBoot
I took a shot and replaced ram chips transplanted from cheap laptop ram module. No luck. Seems like faulty CPU. Aliexpress offers those, marked as 1296PB-VA1-CG and 1296PB-VB0-CG. Marking on mine was: RTD1296PB I61CCE2 GJ03A1 Guess i need NDA'd datasheet to check for differences between VA1/VB0 versionsby twizzter - uBoot
Thanks for your reply. Did a quick insight into dumps we have now. Datablocks 0x20800-0x2143C and 0x084060-0x94D60 are the same. Since both of our devices are bricked, this knowledge does not solve anything ;) Quote There's probably some other check, as in the form of a CRC sum for the serial number. In my case CPU hasn't proceed to the readout of a vendor area, and dump yoby twizzter - uBoot
Ace Ventura, have you managed to recover that device? Same problem here. I've extracted uboot, zimage and RD from pat file, rebuilded flash image but device wont start, ending with 5-5verify fsbl fail as well. Sniffed booting process using logic analyzer: -at first CPU reads data block 0x20800-0x2143C -next, reads longer block 0x084060-0x94D60 Both steps seemed to be a proper readouby twizzter - uBoot
Apparently kernel does not contain earlyprintk: Marvell>> setenv bootargs 'console=ttyS0,115200 ip=off initrd=0x00800040,4M root=/dev/md0 rw syno_hw_version=DS212j ihd_num=2 netif_num=1 earlyprintk=serial' Marvell>> printenv bootcmd=bootm F8080000 F8280000 baudrate=115200 loads_echo=0 ipaddr=192.168.101.224 serverip=192.168.101.111 rootpath=/mnt/ARM_FS/ netmasby twizzter - uBoot
Thanks for the hint! Printenv says: Marvell>> printenv bootcmd=bootm F8080000 F8280000 baudrate=115200 loads_echo=0 ipaddr=192.168.101.224 serverip=192.168.101.111 rootpath=/mnt/ARM_FS/ netmask=255.255.0.0 stdin=serial stdout=serial stderr=serial console=console=ttyS0,115200 mtdparts=cfi_flash:0x380000(root),0x80000(uboot)ro mainlineLinux=no CASset=min enaMonExt=no enaCpby twizzter - uBoot
Update: I searched within various PAT update files and found DS212j uboot, thought it's worth trying because of similar CPU/mem architecture. I flashed memory with image composed of 212jboot+210jrd+210jzimage. Device boots but hangs up on kernel boot: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | |by twizzter - uBoot
Unfortunately, box does not boot from this image. Weird, as according to Syno's website 210j and 211j are equipped with same hw base components - 88F6281+DDR2 128 MB. Edit: Tried to kickstart using NSA310 uboot and TFTPd 210's zimage+rd: 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 (by twizzter - uBoot
Thanks for explanation. Quotebodhi have you tried > uboot.2017.07-tld-1.t5325.mtd0.kwb or > uboot.2017.07-tld-1.dreamplug.mtd0.kwb? Tried as well. T5325 does not boot, dreamplug stops at ram detection. Pitty, because SPI was ready according to log ;) Dumped flash from working 110j to try its uboot, no luck again. At this moment i'm running out of ideas. Probably need to duby twizzter - uBoot
Thanks for quick answer Bodhi. Used kwboot and only kwb which worked was uboot.2015.10-tld-1.nsa310.mtd0.kwb. Other files were not able to boot at all or hanged during ram detection. So currently i'm at: 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 noby twizzter - uBoot
DS210j, board ADM22L1 v1.3, Went dead suddenly, currently only blue led blinks. No sings of life from debug console. Found that flash chip is damaged - stayed quite hot when touched and i wasn't able to read/erase/write it in external programmer due to overcurrent error. Appeared that i need new chip (25P32) programmed with rebuilt image. Altough i've managed to extract rd and zby twizzter - uBoot