This repository describes the attempt at resuscitation of a ReadyNAS NV+v2.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
Edoardo Putti 05a1009a3a add hardware manual for readynas 2 years ago
201101_Marvell_Kirkwood_88F6281_2_Hardware_Spec.pdf add PDF for target SOC 2 years ago
201101_Marvell_Kirkwood_88F6281_3_Functional_Spec.pdf add PDF for target SOC 2 years ago
LICENSE Initial commit 2 years ago
Makefile add more commands to the Makefile 2 years ago
README.md add bios dump, update readme 2 years ago
ReadyNAS_Duov2_NV+v2_HW_en_23-Mar-12.pdf add hardware manual for readynas 2 years ago
bios.bin add bios dump, update readme 2 years ago
kwbimage.cfg dump of the steps taken so far 2 years ago
uboot-NV+-1.0.05 dump of the steps taken so far 2 years ago

README.md

readynas-resurecction

This document describes the attempt at resuscitation of a ReadyNAS NV+v2.

This device is not booting but power is present wherever we tested. The most likely explanation for it not booting is that the SPI flash containing the BIOS is faulty.

As the SOC is produced by Marvell and they advertise a UARTBoot mode which is simply triggered by an handshake there is still hope to confirm it's just a bad BIOS.

Starting from a firmware update image we have reversed what was possible using binwalk. Then after binwalk had done its job we were left with binaries for u-boot, initrd and kernel.

The image for the UARTBoot is created using mkimage and a board configuration which was sourced by the chromium project and most likely is not for the board we have.

Once the image has been created we can UARTBoot using the kwboot tool.

The firmware package we have started from can be downloaded here.

The board configuration has been taken from the chromium project source but is also available in this repository from the SOC vendor tools.

bios dump

We have dumped the SPI flash that most likely contains the BIOS and it went well. We have also verified we can reliably dump it. As it is now it does not look like the SPI flash is corrupted or malfunctioning.