CCR1072-1G-8S+ dead

Hello,

I have a CCR1072-1G-8S+ that shows no sign of life at power-on. I removed the SPI NOR (Winbond W25X40, 512 KB) and read it with a programmer. The size is exactly 524288 bytes, and the read is consistent: the last 24 KB read back as 0xFF while the rest reads as 0x00, so this does not look like a stuck-at-zero reader.

Layout of what is on the chip:

  • 0x00000–0x00024: a small header (non-zero), then zeros up to 0xFFFF
  • 0x10000–0x10FFF: 4 KB of real data, the tail of a Tilera loader (same structure as the end of the first stage in tilegx-7_25.fwf: AAAAAAAA55555555 marker, section table, DEADBEEF, then a compressed stream), but from a different build than 7.25 (size word 0x20178 vs 0x221b8)
  • 0x11000–0x79FFF: all zeros (including 0x40000, where a backup loader would be)
  • 0x7A000–0x7FFFF: all 0xFF

So both bootloader copies are gone. have the tilegx .fwf from the RouterOS npk, but I can’t flash it as is because I don’t know the NOR layout (offsets, header at 0x0, main/backup copy placement).

Could anyone with a working CCR1072-1G-8S+ (or any CCR with the same board) dump the W25X40 and share the 512 KB .bin? Please mention the current RouterBOOT version if you know it. I understand the dump may contain unit-specific data (MAC/serial/hard config). If you know where those regions are, feel free to mask them; I only need the loader and the layout. I can also share my dump and the analysis if it helps anyone else.

Thanks!

It seems that the structure is slightly different in devices with NAND memory; on an SPI flash drive, there are only HARD and SOFT config partitions, while the bootloader is on the NAND. In any case, the data from the HARD config partition needs to be saved.

Thanks for your reply. In fact, I have experience with other Cloud router models having the same problem. When I cloned the SPI flash from a working device, the dead device revived, but it took on the serial and MAC address of the working device. Right now, I don't have a working device dump to test it.

This information is contained in the “HARD” section; it’s easy to find when viewing the dump in a hex editor. (It may be written the other way around: “draH.”) When restoring the device, the “HARD” section in the donor dump is replaced with data from the dump of the non-functioning device. After that, everything works. This section also specifies whether the boot process originates from SPI flash or NAND.)