New IT forum
27 June 2022, 10:56:45 am *
Welcome, %1$s. Please login or register.

: GertDuino now in stock.
 
Pages: [1]

Author Topic: bricked and no prompt. recovery procedure fails  (Read 3198 times)

rhubarb

  • Newbie
  • *
  • Posts: 1
bricked and no prompt. recovery procedure fails
« on: 12 February 2014, 08:48:41 pm »

Hi
I tried to flash a new UBOOT and ended up with an unresponsive DP (ie no prompt whatsoever)

Malcolm pointed me to to this link http://www.newit.co.uk/forum/index.php/topic,2835.0.html

Unfortunately I get an error when doing the reset sequence in the 3rd window

1st window is the screen command. A blank screen is OK I presume

2nd window works OK if I switch on the DP 1 ms before hitting enter. (otherwise I get errors such as UNEXPECTED: 0xfc0000e3 error). But after a few attempts I can now nail the timing every time

3rd window gives the error below. I see others have this error but I have not found a solution. (directory dp_unbrick contains the .elf file by the way)

[email protected]:~/dp_unbrick$ telnet localhost 4444
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> reset;sheevaplug_init;load_image u-boot.elf;resume 0x00600000
JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
JTAG tap: feroceon.cpu       UNEXPECTED: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
JTAG tap: feroceon.cpu  expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Trying to use configured scan chain anyway...
Bypassing JTAG setup events due to errors
Halt timed out, wake up GDB.
timed out while waiting for target halted
Runtime Error: /usr/share/openocd/scripts/board/sheevaplug.cfg:30:
in procedure 'sheevaplug_init'
in procedure 'wait_halt' called at file "/usr/share/openocd/scripts/board/sheevaplug.cfg", line 30


So I am stuck . any help appreciated

Peter
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: bricked and no prompt. recovery procedure fails
« Reply #1 on: 12 February 2014, 10:58:36 pm »

Quote
JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
This is historically indicative of a communication problem between the JTAG and the plug.
Search the forum for '0xfc0000e3' and you should get a lot of relevant hits.
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!
Pages: [1]
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!