Posted by Roadrunnere42 on Jan 30, 2017; 11:07pm
URL: https://itus.accessinnov.com/Current-state-of-Sheild-recovery-knowledge-tp1249p1358.html

Hi Duanev

try using this tutorials found in tutorial of this forum named  Guide - How to fix/resurrect a bricked Shield (and updated to 1.51SP1 w/Feb & March 2016 hotfixes & fw_upgrade 8.3.1)

you will have to copy the files overs as it's clear that the file octboot2,bin is missing  this is need to boot in boot stage 3 which then loads u-boot-octeon_rhino_itx7x.bin, the shield is using the failsafe version 1 which is sort of good as it now allow you to upload the files as suggested in the above post. If i remember right it's a bit fiddly but do able. Be carefully with the command that are available in the stage2  as if you use the setenv it could write to the on board memory and you could brick the shield

the boot precess is
bootloader 1
which is the electronic  process which hands bootup to the software stage

bootloader 2 -octboot2,bin on fat mmc 1 which in your case is missing or corrupt

bootloader 3  u-boot-octeon_rhino_itx7x.bin

Just a quick break down of some of the commands and what they do

setenv loadaddr 0x400000

this just tell the shield that any programs that are upload start that the memory address 0x400000

go 0x400000

just runs the program that been loaded at 0x400000

The programs i used are
Windows
1. terterm  (set to comms port of serial cable, speed 115200 )
2. extra putty
3. winscp
4. solarwind or tftpd32
5. openssh

when you
fatls mmc 1 (this lists the contents of the mmc which should be something like)
        ItusrestoreIamge
        ItusrouterImage
        ItusgatewayImage
        ItusbridgeImage
        octboot2.bin
        restore/
        u-boot-octeon_rhino_itx7x.bin
        updates/
        backup/

There could be a octboot2.bak file which you could just rename to octboot2.bin not sure if all shields had the.bak file or if it was create before any updates.


Roadrunnere42