Community
cancel
Showing results for 
Search instead for 
Did you mean: 
mo_bri
New Contributor I
1,318 Views

D2000 Update ROM broken

Jump to solution

I used the D2000 with the compass example and had the UART down another FTDI working fine. Then I tried the 2 UART example, and to do this I had to configure UART B to be used, I swapped over the links for J9,J10 and J11 to UART B. I then realized I hadn't downloaded the example firmware yet, so I swapped the links back and now I can not ever seem to download anything to it. I have tried on2 other fresh PCs (never installed D200 before), and I can se it is not a driver or OS or host PC issue.

It looks like it just can not seem to spin up the clock, and the JTAG handshake fails. :

Open On-Chip Debugger 0.8.0-dev-g377d3f24-dirty (2017-04-11-19:24)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.sourceforge.net/doc/doxygen/bugs.html

Info : only one transport option; autoselect 'jtag'

adapter speed: 1000 kHz

trst_only separate trst_push_pull

adapter speed: 1000 kHz

trst_only separate trst_push_pull

(likely Digital Pin 0)

Info : clock speed 1000 kHz

Error: JTAG scan chain interrogation failed: all ones

Error: Check JTAG interface, timings, target power, etc.

Error: Trying to use configured scan chain anyway...

Error: quark_d2000.cltap: IR capture error; saw 0xff not 0x1

Warn : Bypassing JTAG setup events due to errors

adapter speed: 3 kHz

Error: Target not examined yet

Runtime Error: C:/IntelSWTools/ISSM_2016.2.094/tools/debugger/openocd//scripts/target/quark_d2000.cfg:90:

in procedure 'clk32M'

in procedure 'mww' called at file "C:/IntelSWTools/ISSM_2016.2.094/tools/debugger/openocd//scripts/target/quark_d2000.cfg", line 90

Trying from the telnet putty shell on 4444 locahost, and I tried this whilst running openocd with th d200 config file.

clk32m

jtag_recovery

But they all fail in the openocd window with :

pen On-Chip Debugger 0.8.0-dev-g377d3f24-dirty (2017-04-11-19:24)

 

Licensed under GNU GPL v2

 

For bug reports, read

 

http://openocd.sourceforge.net/doc/doxygen/bugs.html http://openocd.sourceforge.net/doc/doxygen/bugs.html

 

Info : only one transport option; autoselect 'jtag'

 

adapter speed: 1000 kHz

 

trst_only separate trst_push_pull

 

adapter speed: 1000 kHz

 

trst_only separate trst_push_pull

 

(likely Digital Pin 0)

 

Info : clock speed 1000 kHz

 

Error: JTAG scan chain interrogation failed: all ones

 

Error: Check JTAG interface, timings, target power, etc.

 

Error: Trying to use configured scan chain anyway...

 

Error: quark_d2000.cltap: IR capture error; saw 0xff not 0x1

 

Warn : Bypassing JTAG setup events due to errors

Running clk32M gives :

Open On-Chip Debugger

 

> clk32M

 

adapter speed: 3 kHz

 

Target not examined yet

 

Runtime Error:

 

C:/IntelSWTools/ISSM_2016.2.094/tools/debugger/openocd//scripts/target/quark_d2000.cfg:90:

 

in procedure 'clk32M'

 

in procedure 'mww' called at file

 

"C:/IntelSWTools/ISSM_2016.2.094/tools/debugger/openocd//scripts/target/quark_d2000.cfg",

 

line 90

I cant load an rom, due to it says target not examined yet.

0 Kudos
1 Solution
174 Views

Hi marcuso,

You may refer here for JTAG recovery.

Thanks.

Soffi

View solution in original post

2 Replies
175 Views

Hi marcuso,

You may refer here for JTAG recovery.

Thanks.

Soffi

View solution in original post

mo_bri
New Contributor I
174 Views

Thanks this worked perfectly. I connected GND to D0 on the board and left it plugged in while I reflashed the ROM/Boot Loader with the ISSM (the Eclipse IDE) etc. I reset it a few times, and it bounced back to life.

Reply