Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Massimo_O_Intel
Employee
1,457 Views

Quark SE C1000 – OpenOCD can't connect to the board anymore

Hello

I'm currently getting these error messages every time I try to flash any program to my SE C1000 CRB:

Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED

Error: JTAG scan chain interrogation failed: all zeroes

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

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

Error: quark_se.cltap: IR capture error; saw 0x0 not 0x1

Warn : Bypassing JTAG setup events due to errors

I re-installed the drivers to rule out that the problem might be related to them, even though the board was correctly displayed both in Windows and in Unix.

Trying to run OpenOCD through command line results in the same messages above.

The impression here is that the FTDI mux selecting between JTAG and UART_B got stuck, maybe as a result of a malfunctioning execution of a program, thus preventing the openOCD connection.

Digging in the forum, I saw a few threads about an apparently similar issue on the Intel D2000.

In that case, there seems to be a recovery procedure which unlocks the board.

Any hint about possible causes and solutions on the SE C1000?

Thank you

0 Kudos
13 Replies
Michelle_C_Intel
Employee
106 Views

Hi ,

Can you try grounding J14 Pin 28 on the Board.

This will halt the boot process before any pin muxing is done - and so should allow you access to the JTAG if that is the issue.

-Michelle.

Massimo_O_Intel
Employee
106 Views

Hi Michelle

Thanks for answering.

Unfortunately I'm still getting those errors.

Is that the only step to be carried out?

Does it need to be in a specific sequence with the board power-up?

Thank you

Michelle_C_Intel
Employee
106 Views

This is the sequence you need to do :

- Power off the board - disconnect the USB

- Ground the J14 pin 28

- Reconnect the USB

- With the J14 pin 28 still grounded try to connect OpenOCD

Have you ever been able to connect to the JTAG ? or this happened after you flashed a ROM/Application to the board ?

-- Michelle.

Massimo_O_Intel
Employee
106 Views

I can confirm that the sequence I tried is what you're suggesting.

About your question: I had been using this board for a couple of month at least when the JTAG connection stopped working, during which I flashed countless times to it.

The issue showed up the first time while flashing a program to the board.

Thank you

Massimo

Michelle_C_Intel
Employee
106 Views

Are you working on Windows or Linux ?

Does the board display correctly in Device Manager / lsusb

On Windows you should see 'OpenOCD JTAG'

On Linux you should see it as 'FTDI Dual USB-UART/FIFO IC' when you do 'lsusb'

-- Michelle.

Massimo_O_Intel
Employee
106 Views

Tried on both platforms and the board is displayed correctly in both cases.

Michelle_C_Intel
Employee
106 Views

Can you post the full error message you get when you try to connect from the command line.

--Michelle

Massimo_O_Intel
Employee
106 Views

Hi Michelle

Here follows the command and its result:

/opt/intel/issm_2016.1.057/tools/debugger/openocd> bin/openocd -f scripts/board/quark_se_onboard.cfg

Open On-Chip Debugger 0.8.0-dev-gba72ade (2016-07-19-11:14)

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

jtag_ntrst_delay: 300

Info : clock speed 1000 kHz

Error: JTAG scan chain interrogation failed: all zeroes

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

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

Error: quark_se.cltap: IR capture error; saw 0x0 not 0x1

Warn : Bypassing JTAG setup events due to errors

Thanks for your help

-M

Michelle_C_Intel
Employee
106 Views

Was the default ROM flashed without any changes ?

Also, if you have an application that puts the Soc into deep sleep you may lose the JTAG access. As long as you have the default ROM flashed to the SoC then grounding J14 Pin 28 should 'unbrick' the board and get your JTAG access back.

-Michelle.

Massimo_O_Intel
Employee
106 Views

At the board initial setup, the ROM was flashed as per default, no customization.

I didn't run any application recently which switches the SoC into deep-sleep mode.

Tried the suggested maneuver (J14 Pin 28 to ground) but with no success.

One thing: the board I'm using is an old revision.

It should be something like "Atlas Hills - rev 1.0"

-Massimo

Michelle_C_Intel
Employee
106 Views

It should still work.

For that board just verify you are setting P3 pin 28 to ground - this is the equivalent of J14 pin 28 on the new boards. On both boards this is AP_GPIO15_I2S_RXD.

Massimo_O_Intel
Employee
106 Views

I had already compared the pin-out in my board and in an up-to-date one and verified that the functionalities for that pin match.

I was rather asking about other possible differences which may require a different action but you confirmed that it's not the case.

I guess that with no access through the JTAG there is no chance to erase the flash, correct?

Michelle_C_Intel
Employee
106 Views

Correct - If you cannot access the JTAG then you cannot erase the current flash - or flash a new ROM

--Michelle.

Reply