Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
968 Views

D2000 debug error with CRB JTAG

Host OS: Windows 7 64bit

Target: D2000 MCU on my board

Flash/Debug interface: CRB's JTAG

Code: ISSM "hello world" example

The target board is connected to host via CRB's JTAG connector,

I have used the OpenOCD command to flash MCU, but it show "write flash disabled", the log as below:

And I have used the "mdw"/"mww" command to read/write CTRL register, but it's look like not working.

The log as below: 

Open On-Chip Debugger

> reset halt

JTAG tap: quark_d2000.cltap tap/device found: 0x0e786013 (mfg: 0x009, part: 0xe786, ver: 0x0)

Enabling lmt core tap

JTAG tap: quark_d2000.lmt enabled

target state: halted

target halted due to debug-request at 0x00000000 in real mode

target state: halted

target halted due to debug-request at 0x00000000 in real mode

> clk32M

adapter speed: 3 kHz

adapter speed: 1000 kHz

JTAG tap: quark_d2000.cltap tap/device found: 0x0e786013 (mfg: 0x009, part: 0xe786, ver: 0x0)

Enabling lmt core tap

JTAG tap: quark_d2000.lmt enabled

target state: halted

target halted due to debug-request at 0x00000000 in real mode

> del_flash0

0xb0100014: b0100014

> mdw 0xb0100018 20

0xb0100018: b0100018 b010001c b0100020 b0100024 b0100028 b010002c b0100030 b0100034

0xb0100038: b0100038 b010003c b0100040 b0100044 b0100048 b010004c b0100050 b0100054

0xb0100058: b0100058 b010005c b0100060 b0100064

> mww 0xb0100018 0

> mdw 0xb0100018 20

0xb0100018: b0100018 b010001c b0100020 b0100024 b0100028 b010002c b0100030 b0100034

0xb0100038: b0100038 b010003c b0100040 b0100044 b0100048 b010004c b0100050 b0100054

0xb0100058: b0100058 b010005c b0100060 b0100064

>

So far, I can't debug with ISSM or OpenOCD command,

Is there any suggestion about this issue? thanks!

0 Kudos
3 Replies
Pedro_M_Intel
Employee
73 Views

Hello AmandaLee,

As you can see in the introductory video in http://www.intel.com/content/www/us/en/embedded/products/quark/mcu/issm-getting-started-windows-vide... Intel® Quark™ Microcontroller Getting Started on Windows*: Video if the USB driver has a bad installation it might produce issues when trying to flash or debug the board. In that case you should run the script install.bat found in C:\IntelSWTools\ISSM_2016.y.xxx\tools\debugger\driver\.

Have you tried this? Did it make any difference?

-Peter.

idata
Community Manager
73 Views

Hi Peter,

Thank you for your assistance.

I already installed usb driver(ISSM directory) and the OpenOCD Jtag device also be detect on host.

You can see the log that D2000 device ID can be found, but it can't be flash or debug.

Is there anything else i can try?

Thanks!

Amanda

Michelle_C_Intel
Employee
73 Views

Hi Amanda,

What JTAG debugger are you using ? I see that you are using the default 'd2000_onboard.cfg' configuration file to connect to the board - Can you make sure you use the correct FDTI interface configuration file.

The configuration files for Olimex and Flyswatter are provided ....

Olimex :

bin\openocd.exe -f scripts\interface\ftdi\olimex-arm-usb-ocd-h.cfg -f scripts\board\quark_d2000.cfg

Flyswatter :

bin\openocd.exe -f scripts\interface\ftdi\flyswatter2.cfg -f scripts\board\quark_d2000.cfg

If you have the correct configuration file , you can also try connecting Digitial Pin 0 to GND , reset the board and try flashing again ....

Also , double chek your configuration ... the image below is one we used sucessfully with Olimex Debugger.

--Michelle.

Note : Remove all sleeves from Jumpers J9, J10, J11, J15, J17

Pin 1 – Black – (3.3V)

 

Pin 3 – Yellow - TRST

 

Pin 4 – Blue - GND

 

Pin 5 – White - TDI

 

Pin 7 – Red - TMS

 

Pint 9 – Green - TCK

 

Pin 13 – Orange TDO
Reply