Current state of Sheild recovery knowledge?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Current state of Sheild recovery knowledge?

duanev
Attempting to resurrect my Sheild (I had it upgraded to 1.51sp1 in March but haven't touched it since) but today it doesn't boot  :^

Via the serial cable it looks like I'm at a place similar to:
http://itus.accessinnov.com/How-do-I-completely-reset-td131.html
where I can't get to stage 3:

    ...
    reading u-boot-octeon_sff7000.bin
    Could not read u-boot-octeon_sff7000.bin, trying failsafe
    Error: environment variable octeon_stage3_failsafe_bootloader is not set.
    Octeon sff7000#

except that:
1) I only have an itusrestoreimage (no u-boot-octeon_sff7000.bin or other image files)
2) no dhcp command (why?)
3) no bootoctlinux (is this a binary file instead of a boot command?)
3) loadb/xmodem isn't downloading anything - they just time out
    (I'm using linux, screen, and sx from lrzsz - don't have windows)

Octeon sff7000# version

U-Boot 2013.07 (Development build, svnversion: u-boot:exported, exec:) (Build time: Dec 01 2014 - 16:34:53)
mips64-octeon-linux-gnu-gcc (Cavium Inc. Version: SDK_3_1_0 build 32) 4.7.0
GNU ld (Cavium Inc. Version: SDK_3_1_0 build 32) 2.23.52

On Linux I can use:
    # screen -L /dev/ttyUSB0 115200

Also tried minicom but with default settings I see output but can't type.


I do have an SD card but # mmc list never shows device 2.
I've formatted the SD card as close to: http://itus.accessinnov.com/Build-your-own-OpenWRT-Image-td422.html
as possible (with a type c FAT32 and a type 83 ext3 partition) but it won't show up.


Any ideas?  It would be really nice to get the sd card to work...

Is it possible to load and execute the itusrestoreimage manually?

For 10 watts it sure does get hot ...

And has anyone else seen that spark that sometimes appears when plugging the power into the Sheild?
Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

Roadrunnere42
Hi duanev

what people in the pass have experience is if power is turned off to the Shield and power is switched back on the Shield will not boot, if the Shield was in the process for doing a factory restore then it gets corrupted.

Right lets try and sort this, When your booting the Shield you must not have an sd card insert, if you do it usually load a very early version of the firmware, could be used to copy over new image files.

Try this
1) make sure no sd card insert
2) factory restart via ping  ( remove poewer hold ping in and then reconnect power continue to hold pin in for  30 seconds)
3) wait 10 minutes
4) can you log in ?

if you can't log in can you take screen shots of the boot process screen via the serial cable

yes the box does get hot and yes i do see the flash when i plug the power lead in,  I usually turn mine off via the wall socket switch.

Roadrunnere42
Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

duanev
Sorry, got side tracked there for a while :)

Ok, with no SD card, holding the reset button down (with a paperclip) before power on, and holding the reset down with the clip for 30 seconds after powering up the ITUS, seems to do nothing at all.  The serial port output does not appear to recognize the reset, or wait for the reset button to be released, it just proceeds with the normal stage 1 and 2 boot ending at the Octeon sff7000# prompt.
Try this
1) make sure no sd card insert
2) factory restart via ping  ( remove poewer hold ping in and then reconnect power continue to hold pin in for  30 seconds)
3) wait 10 minutes
4) can you log in ?

if you can't log in can you take screen shots of the boot process screen via the serial cable
Here is the captured output (with the ctrl characters embedded):

^M
OCTEON eMMC stage 1 bootloader^M
^M
Partition: 1, start: 0x0000000000000800, size: 0x0000000000200001^M
OCTBOOT2BIN not found^M
OCTBOOT2BAK not found^M
OCTBOOT2BIN not found^M
OCTBOOT2BAK not found^M
OCTBOOT2BIN not found^M
OCTBOOT2BAK not found^M
OCTBOOT2BIN not found^M
OCTBOOT2BAK not found^M
OCTBOOT2BIN not found^M
OCTBOOT2BAK not found^M
OCTBOOT2BIN not found^M
OCTBOOT2BAK not found^M
OCTBOOT2BIN not found^M
OCTBOOT2BAK not found^M
OCTBOOT2BIN not found^M
OCTBOOT2BAK not found^M
OCTBOOT2BIN not found^M
^M
Error: Trying embedded failsafe...^M
Success.^M
Branching to stage 2 at: 0xFFFFFFFF81004000^M
board_init_f: Done calling 4 (0xc00756b0)^M
Calling 5: 0xc002b3a8^M
board_init_f: Boot flag: 0x2^M
__octeon_setup_clocks: cpu: 1000000000, bus: 600000000^M
__octeon_setup_clocks: core: 1000000000, I/O: 600000000^M
board_init_f: Done calling 5 (0xc00756b4)^M
Calling 6: 0xc00413a8^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 6 (0xc00756b8)^M
Calling 7: 0xc002b294^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 7 (0xc00756bc)^M
Calling 8: 0xc002b58c^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 8 (0xc00756c0)^M
Calling 9: 0xc002f934^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 9 (0xc00756c4)^M
Calling 10: 0xc0053920^M
board_init_f: Boot flag: 0x2^M
Board TLV descriptor Read - RHino continues ... 2 board 0x40 major 1 minor 0, DDR HERTZ 0 hz^M
Rhino: early board init, mem_clk 0x29b ..^M
board_init_f: Done calling 10 (0xc00756c8)^M
Calling 11: 0xc0025978^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 11 (0xc00756cc)^M
Calling 12: 0xc0024cf0^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 12 (0xc00756d0)^M
Calling 13: 0xc002b32c^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 13 (0xc00756d4)^M
Calling 14: 0xc00473b8^M
board_init_f: Boot flag: 0x2^Mboard_init_f: Done calling 14 (0xc00756d8)^M
Calling 15: 0xc0037d90^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 15 (0xc00756dc)^M
Calling 16: 0xc002b2b0^M
board_init_f: Boot flag: 0x2^M
^M
^M
U-Boot 2013.07 (Development build, svnversion: u-boot:exported, exec:) (Build time: Dec 01 2014 - 16:34:53)^M
^M
board_init_f: Done calling 16 (0xc00756e0)^M
Calling 17: 0xc0022204^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 17 (0xc00756e4)^M
Calling 18: 0xc00237b8^M
board_init_f: Boot flag: 0x2^M
Initializing DRAM^M
U-Boot is not RAM-resident^M
Found DDR configuration for SFF7000^M
Rhino: cpu_id 0xd9602 board_type 0x40 major 0x1 minor 0x0  mask 1 ...^M
Initializing DDR, clock = 667000000hz, reference = 50000000hz^M
LMC0_DCLK_CNT: 0xffffffffffffffff^M
Cavium Inc. OCTEON SDK version 3.1.0_p4, build 534: $Revision: 101360 $^M
EARLY FILL COUNT                              : 13, cpu_hertz:1000000000, ddr_hertz:667000000^M
LMC0 Asserting DDR_RESET_L^M
DDR Reference Hertz = 50000000^M
clkr:  0, en[5]:  6, clkf:   79, pll_MHz: 4000, ddr_hertz: 666666666, error:   333334^M
clkr:  0, en[2]:  3, clkf:   39, pll_MHz: 2000, ddr_hertz: 666666666, error:   333334^M
clkr:  1, en[2]:  3, clkf:   79, pll_MHz: 2000, ddr_hertz: 666666666, error:   333334^M
clkr:  2, en[2]:  3, clkf:  119, pll_MHz: 2000, ddr_hertz: 666666666, error:   333334^M
clkr:  2, en[1]:  2, clkf:   79, pll_MHz: 1333, ddr_hertz: 666666666, error:   333334^M
clkr:  0, en[5]:  6, clkf:   79, pll_MHz: 4000, ddr_hertz: 666666666, error:   333334 <==^M
LMC0 De-asserting DDR_RESET_L^M
LMC0: Measured DDR clock: 666666480, cpu clock: 1000000000, ddr clocks: 111111419^M
LMC0: measured speed: 666666480 hz^M
^M
Initializing DDR interface 0, DDR Clock 666666480, DDR Reference Clock 50000000, CPUID 0x000d9602^M
spd_addr        : 0x0019^M
spd_org         : 0x0002^M
row_lsb = column_bits_start + col_bits + bank_bits = 15^M
pbank_lsb = row_lsb + row_bits + bunk_enable = 30^M
row bits: 15, col bits: 10, banks: 8, ranks: 1, dram width: 16, size: 1024 MB^M
DRAM Interface width: 32 bits ^M
spd_cas_latency : 0x00fe^M
spd_twr         : 0x0078^M
spd_trcd        : 0x006e^M
spd_trrd        : 0x0030^M
spd_trp         : 0x006e^M
spd_tras        : 0x0118^M
spd_trc         : 0x0186^M
spd_trfc        : 0x0820^M
spd_twtr        : 0x003c^M
spd_trtp        : 0x003c^M
spd_tfaw        : 0x00f0^M
spd_addr_mirror : 0x0000^M
^M
------ Board Custom Configuration Settings ------^M
MIN_RTT_NOM_IDX                               : 1^M
MAX_RTT_NOM_IDX                               : 5^M
MIN_RODT_CTL                                  : 1^M
MAX_RODT_CTL                                  : 5^M
DQX_CTL                                       : 4^M
CK_CTL                                        : 4^M
CMD_CTL                                       : 4^M
CONTROL_CTL                                   : 4^M
MIN_CAS_LATENCY                               : 0^M
OFFSET_EN                                     : 1^M
OFFSET_UDIMM                                  : 2^M
OFFSET_RDIMM                                  : 2^M
DDR_RTT_NOM_AUTO                              : 0^M
DDR_RODT_CTL_AUTO                             : 0^M
RLEVEL_COMP_OFFSET                            : 7^M
RLEVEL_COMPUTE                                : 0^M
DDR2T_UDIMM                                   : 1^M
DDR2T_RDIMM                                   : 1^M
FPRCH2                                        : 2^M
-------------------------------------------------^M
Desired CAS Latency                           :     10^M
CAS Latencies supported in DIMM               : 5 6 7 8 9 10 11^M
CAS Latency                                   :     10^M
DDR Clock Rate (tCLK)                         :   1500 ps^M
Core Clock Rate (eCLK)                        :   1000 ps^M
Medium Timebase (MTB)                         :    125 ps^M
Minimum Cycle Time (tCKmin)                   :   1250 ps^M
Minimum CAS Latency Time (tAAmin)             :  13750 ps^M
Write Recovery Time (tWR)                     :  15000 ps^M
Minimum RAS to CAS delay (tRCD)               :  13750 ps^M
Minimum Row Active to Row Active delay (tRRD) :   6000 ps^M
Minimum Row Precharge Delay (tRP)             :  13750 ps^M
Minimum Active to Precharge (tRAS)            :  35000 ps^M
Minimum Active to Active/Refresh Delay (tRC)  :  48750 ps^M
Minimum Refresh Recovery Delay (tRFC)         : 260000 ps^M
Internal write to read command delay (tWTR)   :   7500 ps^M
Min Internal Rd to Precharge Cmd Delay (tRTP) :   7500 ps^M
Minimum Four Activate Window Delay (tFAW)     :  30000 ps^M
LMC_SCRAMBLE_CFG0                             : 0x0000000000000000^M
LMC_SCRAMBLE_CFG1                             : 0x0000000000000000^M
LMC_CONFIG                                    : 0x1008090a2c290044^M
LMC_CONTROL                                   : 0x000007801f038024^M
TIMING_PARAMS0                                : 0x000065112ccc3400^M
TIMING_PARAMS1                                : 0x0000f2bd34592970^M
CAS Write Latency                             :      7^M
Write recovery for auto precharge (WRP)       :      5^M
MODEREG_PARAMS0                               : 0x0000000000a30002^M
RTT_NOM       0,   0,   0,  40 ohms           :  0,0,0,3^M
RTT_WR        0,   0,   0,   0 ohms           :  0,0,0,0^M
DIC          40,  40,  40,  40 ohms           :  0,0,0,0^M
MODEREG_PARAMS1                               : 0x0000000000000600^M
LMC_NXM                                       : 0x000000000000040e^M
WODT_MASK                                     : 0x0000000000000001^M
RODT_MASK                                     : 0x0000000000000000^M
DYN_RTT_NOM_MASK                              : 0x00^M
PHY_CTL                                       : 0x0000001200000000^M
PHY_CTL                                       : 0x0000001200200000^M
Performing Write-Leveling^M
MODE32B                                       : 1^M
Rank(0) Wlevel Debug Results                  : 00000 00000 00000 00000 00000 0001e 0001f 000f0 000f8^M
Rank(0) Wlevel Rank   0x3, 0x0000600000000082 :     0     0     0     0     0     0     0     4     2^M
MODE32B                                       : 1^M
Waiting 159448 usecs for ZQCS calibrations to start^M
Performing Read-Leveling^M
RLEVEL_CTL                                    : 0x00000000553c3f20^M
RLEVEL_OFFSET                                 :      2^M
RLEVEL_OFFSET_EN                              :      1^M
DDR__PTUNE/DDR__NTUNE                         : 8/7^M
^M
RTT_NOM       0,   0,   0,  40 ohms           :  0,0,0,3^M
Read ODT_CTL                                  : 0x5 (120 ohms)^M
Rank(0) Rlevel Debug Test Results  8:0        : 00000 00000 00000 00000 00000 00ffe 00fff 001f0 001f0^M
Rank(0) Rlevel Rank   0x3, 0x00C6186186249186 :     6     6     6     6     6     9     9     6     6 (57)^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=5][rankx=0].score:57^M
Read ODT_CTL                                  : 0x4 (60 ohms)^M
Rank(0) Rlevel Debug Test Results  8:0        : 00000 00000 00000 00000 00000 000fe 000ff 001f0 001f0^M
Rank(0) Rlevel Rank   0x3, 0x00C6186186145186 :     6     6     6     6     6     5     5     6     6 (15)^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=4][rankx=0].score:15^M
Read ODT_CTL                                  : 0x3 (40 ohms)^M
Rank(0) Rlevel Debug Test Results  8:0        : 00000 00000 00000 00000 00000 000fe 000f7 001f0 001f0^M
Rank(0) Rlevel Rank   0x3, 0x00C6186186145186 :     6     6     6     6     6     5     5     6     6 (9)^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=3][rankx=0].score:9^M
Read ODT_CTL                                  : 0x2 (30 ohms)^M
Rank(0) Rlevel Debug Test Results  8:0        : 00000 00000 00000 00000 00000 000fe 000f7 001f0 001f0^M
Rank(0) Rlevel Rank   0x3, 0x00C6186186145186 :     6     6     6     6     6     5     5     6     6 (9)^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=2][rankx=0].score:9^M
Read ODT_CTL                                  : 0x1 (20 ohms)^M
Rank(0) Rlevel Debug Test Results  8:0        : 00000 00000 00000 00000 00000 00000 000f6 00000 001f0^M
Rank(0) Rlevel Rank   0x3, 0x00C6186186005006 :     6     6     6     6     6     0     5     0     6 (234)^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=1][rankx=0].score:234^M
DDR__PTUNE/DDR__NTUNE                         : 8/7^M
Evaluating Read-Leveling Scoreboard.^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=5][rankx=0].score:57^M
rodt_score:57, best_rodt_score:9999999^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=4][rankx=0].score:15^M
rodt_score:15, best_rodt_score:57^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=3][rankx=0].score:9^M
rodt_score:9, best_rodt_score:15^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=2][rankx=0].score:9^M
rodt_score:9, best_rodt_score:9^M
rlevel_scoreboard[rtt_nom=2][rodt_ctl=1][rankx=0].score:234^M
rodt_score:234, best_rodt_score:9^M
RTT_NOM       0,   0,   0,  40 ohms           :  0,0,0,3^M
RTT_WR        0,   0,   0,   0 ohms           :  0,0,0,0^M
DIC          40,  40,  40,  40 ohms           :  0,0,0,0^M
Read ODT_CTL                                  : 0x3 (40 ohms)^M
Rank(0) Rlevel Rank   0x1, 0x0046186186145186 :     6     6     6     6     6     5     5     6     6 (9)^M
DDR2T                                         :      1^M
Performing software Write-Leveling^M
Rank Address: 0x0^M
Testing byte 0 delay  2^M
1: [0x8000000004000000] 0x00000000000000BF expected 0x00000000000000FF xor 0000000000000040^M
        byte 0 delay  2 Errors^M
Testing byte 0 delay 10^M
        byte 0(0x0) delay 10 Passed^M
Testing byte 1 delay  4^M
1: [0x8000000004000000] 0x000000000000BF00 expected 0x000000000000FF00 xor 0000000000004000^M
        byte 1 delay  4 Errors^M
Testing byte 1 delay 12^M
        byte 1(0x0) delay 12 Passed^M
Testing byte 2 delay  0^M
1: [0x8000000004000000] 0x0000000000BF0000 expected 0x0000000000FF0000 xor 0000000000400000^M
        byte 2 delay  0 Errors^M
Testing byte 2 delay  8^M
        byte 2(0x0) delay  8 Passed^M
Testing byte 3 delay  0^M
1: [0x8000000004000000] 0x00000000BF000000 expected 0x00000000FF000000 xor 0000000040000000^M
        byte 3 delay  0 Errors^M
Testing byte 3 delay  8^M
        byte 3(0x0) delay  8 Passed^M
Rank(0) Wlevel Rank   0x1, 0x0000200000A4218A :     0(e)  0(e)  0(e)  0(e) 10(e)  8     8    12    10    ^M
LMC0 Configuration Completed: 1024 MB^M
Measured DDR clock 666666480 Hz^M
Mem size in MBYTES: 1024^M
RHino: new Ram size 1024MiB (0x40000000)^M
Ram size 1024MiB (0x40000000)^M
Clearing memory from 0 to 1048576^M
Done clearing memory^M
board_init_f: Done calling 18 (0xc00756e8)^M
Calling 19: 0xc002b2f0^M
board_init_f: Boot flag: 0x2^M
Empty memory test^M
board_init_f: Done calling 19 (0xc00756ec)^M
Calling 20: 0xc0025a18^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 20 (0xc00756f0)^M
Calling 21: 0xc0053918^M
board_init_f: Boot flag: 0x2^M
board_init_f: Done calling 21 (0xc00756f4)^M
Calling 22: 0xc002ed50^M
board_init_f: Boot flag: 0x2^M
SFF7000 board revision major:1, minor:0, serial #: ^M
OCTEON CN7020-AAP pass 1.2, Core clock: 1000 MHz, IO clock: 600 MHz, DDR clock: 667 MHz (1334 Mhz DDR)^M
Rhino: End of display banner ...^M
board_init_f: Done calling 22 (0xc00756f8)^M
board_init_f: Done calling init sequence^M
 flushing L2 cache...^M
  Invalidating icache^M
  Done.^M
  Unlocking U-Boot from cache...^M
^M
 Done.^M
RHino: relocation to DRAM ... RAM_SIZE 40000000^M
Rhino: N63XX and newer addr 0x50000000  offset 0x30000000 ...^M
U-Boot link addr: 0xc0004000^M
Top of RAM usable for U-Boot at: 50000000^M
Using TLB mapping size of 0x400000 bytes for DRAM mapping.^M
Reserving 1920k for U-Boot at: 4f804000^M
Clearing 0x7fc000 bytes at addr 0x4f804000^M
u_boot_base_phys: 0x4f804000, len: 0x1e0000^M
Reserving 2056k for malloc() at: 4f9e4000^M
Stack top physical address: 0x4fc16000^M
Reserving 80 bytes for Board Info at: 0x4fc15fb0^M
Reserving 320 Bytes for Global Data at: 0x4fc15e70^M
Reserving 128k for boot params() at: 4fbf5e70^M
Stack Pointer at:   4fbf5e60, stack size: 0x00030000^M
Base DRAM address used by u-boot: 0x4f804000, size: 0x7fc000^M
DRAM: 1 GiB^M
Top of fixed address reserved memory: 0x0006c188^M
gd address: ffff9910, new_addr: 0x4fc15e70^M
Relocating bd from: ffff9a50 to 0x800000004fc15fb0, size: 0x50^M
Relocating gd from: ffff9910 to 0x800000004fc15e70, size: 0x140^M
relocating and jumping to code in DRAM at addr: 0x4f804000^M
Virtual stack top: 0xc03f5e60, virt new gd: 0xc0415e70^M
Now running in RAM - U-Boot at: ffffffffc0004000^M
Relocation offset: 0x0, monitor base: 0xc0004000^M
U-Boot memory end: c01d8200^M
Setting heap memory to start at 0xc01e0000, size: 0x202000^M
Adding map entry for 0xc0004000, address: 0x4f804000, size: 0x400000, index: 0^M
About to flush L2 cache^M
ram size: 0x40000000 (1073741824), sizeof=8^M
Clearing DRAM.....Clearing base address: 0x100000, size: 0xff00000, ub_base: 0x4f804000, ub_size: 0x7fc000^M
Stack: 0xc03f5c60^M
Done clearing memory, ub_base: 0x4f804000^M
.Clearing base address: 0x20000000, size: 0x30000000, ub_base: 0x4f804000, ub_size: 0x7fc000^M
Stack: 0xc03f5c60^M
Done clearing memory, ub_base: 0x4f804000^M
 done^M
Clearing DRAM ECC errors^M
Initializing phy mem list: ram_size: 0x40000000, low reserved size: 0x80000^M
Bootloader boot memory descriptor at 8006c108^M
Allocating named block for used memory.^M
Copying FDT from 0xc0054c70 to 0x80000, 3630 bytes^M
Increase FDT size to 0x20000^M
Performing board FDT fixups^M
BOOTLOADER_BOOTMEM_DESC_ADDR: 0x6c100^M
BOOTLOADER_BOOTMEM_DESC_SPACE: 0x6c108^M
size of bootmem desc: 56, location: 8006c108^M
Setting up simple executive support^M
Enabling all cores^M
octeon_enable_all_cores^M
Powering up cores on node 0^M
Relocating environment^M
Using default environment^M
^M
Environment relocated^M
Allocating idle core named block^M
Linux reserved load size 0x10000000^M
Adjusted memory top is 0x40000000^M
Setting load address to 0x20000000, size 0x10000000^M
Reserving 0xf000000 bytes of memory at 0x100000 for the Linux kernel^M
bootmem descriptor address (looked up): 0x6c108^M
Setting up U-Boot prompt for board type 64.^M
prompt environment variable not set.^M
Setting prompt to Octeon sff7000# ^M
Reading eeprom...^M
Performing OCTEON FDT fixups^M
Packing flat device tree^M
Setting numcores to 2^M
ethaddr not found in environment^M
Setting IP address...^M
Done.^M
Reserving first 1MB of memory^M
Initializing stdio...^M
Initializing jump table...^M
Initializing console...^M
Console initialized^M
Setting stdin, stdout and stderr to serial port^M
Setting load address...^M
Configuring misc...^M
MMC:   Octeon MMC/SD0: 1^M
Doing late board init...^M
Setting serial number to ^M
Entering main loop.^M
Hit any key to stop autoboot:  3 ^H^H^H 2 ^H^H^H 1 ^H^H^H 0 ^M
reading u-boot-octeon_sff7000.bin^M
Could not read u-boot-octeon_sff7000.bin, trying failsafe^M
Error: environment variable octeon_stage3_failsafe_bootloader is not set.^M
Octeon sff7000# 
Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

duanev
In reply to this post by Roadrunnere42
Browsing around I've found a few commands that give some results:

Octeon sff7000# mmc list
Octeon MMC/SD0: 1
Octeon sff7000#

Only 1 device is listed regardless of whether I've booted with an SD card in the slot or not.  I understand the SD card should appear as:

Octeon MMC/SD0: 1 
Octeon MMC/SD2: 2

but it does not.  This makes me suspect that the SD slot is not enabled or is broken.



On board flash however still appears to contains some files:

Octeon sff7000# mmc dev 1
mmc1(part 0) is current device
Octeon sff7000# fatls mmc 1 
            backup/
 40859016   itusrestoreimage 
            restore/
            updates/

1 file(s), 3 dir(s)
--------
Octeon sff7000# fatls mmc 1 backup
            ./
            ../
 27093426   bridge.tar.gz 
 49359310   gateway.tar.gz 

2 file(s), 2 dir(s)
--------
Octeon sff7000# fatls mmc 1 restore
            ./
            ../
 35862152   bridge.elf 
 58144392   router.elf 
 58078856   gateway.elf 
 27090234   bridge.tar.gz 
 49361121   router.tar.gz 
 49358939   gateway.tar.gz 

6 file(s), 2 dir(s)
--------
Octeon sff7000#


If I could get  u-boot-octeon_sff7000.bin  on that boot partition I think recovery could work.  Alas, I've had no luck with sz/rz.


Other boot loader commands show the three Linux partitions are intact:

Octeon sff7000# ext4ls mmc 1:3 /
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 opt
<DIR>       4096 rom
<DIR>       4096 www
<DIR>       4096 root
<SYM>          4 var
<DIR>       4096 lib
<DIR>       4096 sys
<DIR>       4096 overlay
<DIR>       4096 proc
<SYM>          3 lib64
<DIR>       4096 usr
<DIR>       4096 dev
<DIR>       4096 sbin
<DIR>       4096 tmp
<DIR>       4096 bin
<DIR>       4096 etc
<DIR>       4096 mnt
            1401 init
<DIR>       4096 include

All three paritions appear similar (likely one filesystem for bridge, router, and gateway modes), except partition 2 has four extra files:

...
               0 .fw_script_timer
              29 .do_date
               0 .do_upgrade
              74 HOTFIX_TEST.txt

indicating an upgrade was likely in progress.
Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

duanev
In reply to this post by duanev
Ho!  Some success!  I managed to get ymodem to work and upload both u-boot-octeon_rhino_itus7x.bin and then ItusrestoreImage (described at the end of this post).  The restore images runs for a while but the watchdog timer triggers a hard reset after a few tens of seconds of "inactivity".  If I don't punch the enter key while the restore image is booting I get this:
...
[ 4664.532058] em_nbyte: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTEON 64BIT '^M
[ 4664.532103] em_text: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTEON 64BIT '^M
[ 4664.532144] em_u32: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTEON 64BIT '^M
[ 4664.532193] ifb: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTE^M
*** NMI Watchdog interrupt on Core 0x00 ***^M
        $0      0x0000000000000000      at      0x0000000014009ce0^M
        v0      0x0000000000000001      v1      0x00000000000003e8^M
...
(reset)

which is about 500 lines of complaints about version mismatches, and then a watchdog interrupt.  I'm using the May 21, 2015 uboot but I don't know how to use the octboot2.bin roadrunner42 speaks of ...

I next tried the 'octwd stop' command prior to booting (which did nothing - something turns the watchdog back on while the kernel is starting), and then pressing the enter key every few seconds during boot - which gave me a shell prompt:
...
[ 4105.408093] Freeing unused kernel memory: 32136K (ffffffff8089e000 - ffffffff82800000)^M
[ 4107.488274] init: Console is alive^M
[ 4107.503942] init: - watchdog -^M
[ 4108.519650] init: - preinit -^M
Press the [f] key and hit [enter] to enter failsafe mode^M
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level^M
[ 4108.594160] mmc0: Skipping voltage switch^M
[ 4108.640250] mmc0: host does not support reading read-only switch. assuming write-enable.^M
[ 4108.662273] mmc0: new high speed SDHC card at address 59b4^M
[ 4108.680711] mmcblk0: mmc0:59b4 USD00 30.0 GiB ^M
[ 4108.698393]  mmcblk0: p1^M
^M
^M
[ 4110.681366] procd: - early -^M
[ 4110.696562] procd: - watchdog -^M
[ 4111.388193] procd: - ubus -^M
[ 4112.403957] procd: - init -^M
Please press Enter to activate this console.^M
^M
^M
^M
BusyBox v1.23.2 (2015-08-19 20:18:50 PDT) built-in shell (ash)^M
^M
=========================================================================^M
|  ___ _____ _   _ ____    _   _      _                      _          |^M
| |_ _|_   _| | | / ___|  | \ | | ___| |___      _____  _ __| | _____   |^M
|  | |  | | | | | \___ \  |  \| |/ _ \ __\ \ /\ / / _ \| '__| |/ / __|  |^M
|  | |  | | | |_| |___) | | |\  |  __/ |_ \ V  V / (_) | |  |   <\__ \  |^M
| |___| |_|  \___/|____/  |_| \_|\___|\__| \_/\_/ \___/|_|  |_|\_\___/  |^M
|  ____  _   _ ___ _____ _     ____         ,-~~-.___.                  |^M
| / ___|| | | |_ _| ____| |   |  _ \       / |  '     \                 |^M
| \___ \| |_| || ||  _| | |   | | | |     (  )         0                |^M
|  ___) |  _  || || |___| |___| |_| |      \_/-, ,----'                 |^M
| |____/|_| |_|___|_____|_____|____/          ====           //         |^M
|                                  v1.0       /  \-'~;    /~~~(O)       |^M
|                                            /  __/~|   /       |       |^M
| Powered by OpenWrt                     -==(  _____| (_________|       |^M
=========================================================================^M
^M
^M
-^M
[email protected]?:/# [ 4114.157680] arc4: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTEON 64BIT '^M
[ 4114.181807] af_alg: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTEON 64BIT '^M
[ 4114.205456] arc4: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTEON 64BIT '^M
^M
[email protected]?:/# [ 4114.229405] af_alg: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTEON 64BIT '^M
[ 4114.253653] arc4: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTEON 64BIT '^M
[ 4114.277083] af_alg: version magic '3.10.20-rt14 SMP mod_unload OCTEON 64BIT ' should be '3.10.20 SMP mod_unload OCTEON 64BIT '^M
...

and when the complaints stopped I was able to run a few commands ... until the system spontaneously reboots:
...
[email protected]:/# df^M
Filesystem           1K-blocks      Used Available Use% Mounted on^M
tmpfs                   499396        48    499348   0% /tmp^M
tmpfs                      512         0       512   0% /dev^M
/dev/mmcblk0p1        31460352        32  31460320   0% /overlay^M
[email protected]:/# [ 4279.584354] br-lan: port 1(eth1) entered disabled state^M
[ 4279.601891] br-lan: port 2(eth2) entered disabled state^M
[ 4279.640582] device eth1 left promiscuous mode^M
[ 4279.657100] br-lan: port 1(eth1) entered disabled state^M
[ 4279.675522] device eth2 left promiscuous mode^M
[ 4279.692031] br-lan: port 2(eth2) entered disabled state^M
[ 4279.751412] reboot: Restarting system^M
^M
OCTEON eMMC stage 1 bootloader^M
^M
Partition: 1, start: 0x0000000000000800, size: 0x0000000000200001^M
OCTBOOT2BIN not found^M
...

This seems to be due to the update script which is supposed to run in the restore image, and of course reboot when it is done.  But nothing gets restored... so I'm going to have to figure out how to kill the script so I can fix some things manually.  If I connect the eth0 port to my network I can ping out from the Shield until the reboot, but curl fails with this:

curl: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

which is quite surprising - if the restore script depends on curl I would expect all the dependent shared libs to be in the restore image.



Ymodem

So to get ymodem to work with screen, first cd to the directory with the Shield binary images and then run screen and use ctrl-a followed by ':' when the loady command begins to send 'C' characters:
# screen /dev/ttyUSB0 115200
(boot Shield)
Octeon sff7000# setenv loadaddr 0x400000
Octeon sff7000# loady

Press ctrl-a and ':' and then type 'exec !! sz -Y u-boot-octeon_rhino_itus7x.bin'.  ymodem should commence in a few seconds and give you a running block transfer count... and finally:
Sending:
Ymodem sectors/kbytes sent:   0/ 0k
Transfer complete
Modem - CRC mode, 8(SOH)/1111(STX)/0(CAN) packets, 6 retries
## Total Size      = 0x00115ef0 = 1138416 Bytes
Octeon sff7000#

Then type:
Octeon sff7000# go 0x00400000

to execute uboot (stage 3).   Once the stage 3 boot stops, repeat this process for the ItusrestoreImage downloaded from dropbox (mentioned in other threads on this forum - search for its md5sum df253dc31c8001337a537d59dcd5996d ):
Octeon cust_private_rhino_itus7x(ram)# setenv loadaddr 0x400000
   Octeon cust_private_rhino_itus7x(ram)# loady
ctrl-a:exec !! sz -Y ItusrestoreImage
   (wait 61 minutes! lol) 
   Octeon cust_private_rhino_itus7x(ram)# octwd stop   ??
   Octeon cust_private_rhino_itus7x(ram)# bootoctlinux 0x400000 numcores=2 mem=0

press enter several times to activate console during boot ...

Wish I knew all the command line options that bootoctlinux accepts, they might be kernel command line args ...
Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

Roadrunnere42
Hi duanev

It's been sometime since messing with the boot process of the shield , but I think the reason you get the reboot is because your using the wrong version of octbin2.bin, your screen shoot shows version 1.0 of snoopy sitting on his kennel, this is the embedded safety version, which i think uses an older version of octbin2.bin. I believe that there is 3 versions of octboot2.bin floating around.
Failsafe version
RC1 version
sp1.51 version

I had this happen several times when messing around with the shield.

These two files are for shield sp1.51  and should be upload together
octboot2.bin
u-boot-octeon_rhino_itus7x.bin

I had a bricked shield which I got working again, did post how sometime ago, will try and find my files and repost

Roadrunnere42
Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

duanev
I tried loady'ing octboot2 and then go but the Shield hung ... How do we update or install or use otchboot2? (I've not been able too alter the mmc dev 1 onboard flash yet)

On Jan 29, 2017 4:30 AM, "[hidden email] [via Itus Networks Owners Forum]" <[hidden email]> wrote:
Hi duanev

It's been sometime since messing with the boot process of the shield , but I think the reason you get the reboot is because your using the wrong version of octbin2.bin, your screen shoot shows version 1.0 of snoopy sitting on his kennel, this is the embedded safety version, which i think uses an older version of octbin2.bin. I believe that there is 3 versions of octboot2.bin floating around.
Failsafe version
RC1 version
sp1.51 version

I had this happen several times when messing around with the shield.

These two files are for shield sp1.51  and should be upload together
octboot2.bin
u-boot-octeon_rhino_itus7x.bin

I had a bricked shield which I got working again, did post how sometime ago, will try and find my files and repost

Roadrunnere42


If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/Current-state-of-Sheild-recovery-knowledge-tp1249p1353.html
To unsubscribe from Current state of Sheild recovery knowledge?, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

Roadrunnere42
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




Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

duanev
Haha!  Success!

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

Yes, that is the sequence when all is well, I had to first get octboot2.bin, u-boot-octeon_rhino_itus7x.bin, and a clean copy of the ItusrestoreImage onto the mmc1 root partition.  Here's how:

- get ymodem working (see previous post in this thread)
- use ymodem to send u-boot-octeon_rhino_itus7x.bin to the shield and run it:

        # screen -L save1.log /dev/ttyUSB0 115200
        <ctrl-a> : zmodem auto
           Octeon sff7000# setenv loadaddr 0x400000
           Octeon sff7000# loady
           (waits for ymodem)
        <ctrl-a> : exec !! sz -Y u-boot-octeon_rhino_itus7x.bin
           (wait about 1 minute --- 1138K bytes)
           ...
           Octeon sff7000# go 0x400000

- connect the shield eth0 to a network with a dhcp server
- then ymodem send the latest ItusrestoreImage (that is mentioned here in other posts).  This will test your patience - it takes 61 minutes to download the restore image!

           Octeon cust_private_rhino_itus7x(ram)# setenv loadaddr 0x400000
           Octeon cust_private_rhino_itus7x(ram)# loady
        <ctrl-a> : exec !! sz -Y ItusrestoreImage
           (wait 61 minutes)
           ...
           Octeon cust_private_rhino_itus7x(ram)# bootoctlinux 0x400000 numcores=2 mem=0
           (press enter several times to activate console during boot ...)
           (then after you see the snoopy ascii art and a prompt, *quickly* paste in this mv command (X windows cut/paste is very handy here)
           #       mv /etc/rc.common /etc/xx.common

this moves the auto reinstall script out from under /etc/rc.local while /etc/rc.local is running and causes a prompt to return after mmc drivers are loaded and eth0 is activated.

- at which point hopefully the mmc 1 partition table is intact:

        [email protected]:/# fdisk -l

        Disk /dev/mmcblk0: 3.6 GiB, 3867148288 bytes, 7553024 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes
        Disklabel type: dos
        Disk identifier: 0x00000000

        Device         Boot   Start     End Sectors  Size Id Type
        /dev/mmcblk0p1 *       2048 2099200 2097153    1G  c W95 FAT32 (LBA)
        /dev/mmcblk0p2      2101248 3842047 1740800  850M 83 Linux
        /dev/mmcblk0p3      3842048 5582847 1740800  850M 83 Linux
        /dev/mmcblk0p4      5582848 7323647 1740800  850M 83 Linux

        ...

- then mount the boot partition (FAT32) on /mnt

        # mount /dev/mmcblk0p1 /mnt

- scp the new boot files to /mnt

        # scp 192.168.0.2:itus/u-boot-octeon_rhino_itus7x.bin /mnt
        # scp 192.168.0.2:itus/ItusrestoreImage /mnt
        # scp 192.168.0.2:itus/octboot2.bin /mnt

- and reboot making sure all file buffers are written out

        # umount /mnt
        # sync
        # sync
        # reboot

At this point octboot2.bin should be used instead of the fallback, which should do the stage 3 boot of u-boot-octeon_rhino_itus7x.bin, which should intern run the restore image one more time (let it run uninterrupted), and that should reinstall 1.5sp1

Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

user8446
Administrator
WOW, nice work guys!
Running in bridge mode, 1.51 SP1 fw
Reply | Threaded
Open this post in threaded view
|

Re: Current state of Sheild recovery knowledge?

Roadrunnere42
Duanev

Glade to see your shield is back up and running.

roadrunnere42