Robot9706

Sorry for off topic bumping Update on this post: After replacing the RAM chips the NAS works again. It seems using the recovery terminal to poke at RAM addresses to try and figure out which chip is broken works. I've uploaded all my findings for future use here: https://github.com/robot9706/DS218 Cheers, Bence.

Hi! Thanks for the comment! I think the SPI flash and its contents are correct. I can compile and transfer and kind of binary that I want into the RAM to run, however if I transfer these into DRAM they won't run (because they get corrupted). They run fine from the internal SRAM. So I desoldered two RAM chips because I think one of them is broken. The new chips will arrive next week, I'll post an update on how the fix went Cheers, Bence.

Hi guys! I have a broken DS218 NAS, it worked for 3+ years and then it randomly died. It's not really releated to this topic, but I think you guys might know more about this CPU than me :) The UART says the following and then the CPU halts. C1:80000000 C2 ? C3h hwsetting size: 00000B94 C4 f 5-5verify fsbl fail 0000003BC7 C1:80000000 C2 ?uu3-1 I verified the SPI flash contents, even reflashed the bootloader using the original synology loader but it fails. I also verified the data being read out using a logic analyser and everything seems to work just fine. Also tried flashing different bootloaders into the SPI flash (BPi UBoot) but nothing really works. The CTRL+Q on-chip-recovery terminal works, however it does not want to execute any code for some reason. I read somewhere that the FSBL might be encrypted, is it possible that the keys inside the CPU (efuse or OTP memory ?) somehow got corrupted and so now everything is just invalid? Does somebody has any info of what this "verify fsbl fail" means? Cheers, Bence.