ERROR: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 2)

Ask the Community
Close
Ask the Community
nav search Icon
Forums gray-arrow gray-arrow
Resources gray-arrow gray-arrow
About gray-arrow gray-arrow
Groups gray-arrow gray-arrow
nav-user Account

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob

ERROR: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 2)

MaSt_4567191
Level 4
Level 4
10 likes given 5 likes given First like received
‎Jan 24, 2020 07:04 AM
‎Jan 24, 2020 07:04 AM
Jump to solution

Here I am again

the issue have been solved some days ago but moving on it reappeared ... very frustrating

Unfortunately I cannot reopen a closed discussion so here I am

The design is a CX3 configuration design, the hardware is based on the denabola board

I did not touch the clock configration just after main entry

According to

: Fix “Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 2) @ Off 0x5” Error...

I added

monitor memU32 0xE0052000 = 0x00080015

monitor sleep 1000

in the startup tab of the run commands text box. Does not work ....

monitor memU32 0xE0052000 = 0x00080014

monitor sleep 1000

does not work as well

0 Likes
Subscribe
1 Solution

Re: ERROR: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 2)

YashwantK_46
Moderator
Moderator
Moderator
100 solutions authored 50 solutions authored 50 likes received
In response to MaSt_4567191
‎Jan 27, 2020 05:31 AM
‎Jan 27, 2020 05:31 AM
Jump to solution

Hello,

The code snippet that you have added in response:2 checks for the event CX3_USB_SUSP_EVENT_FLAG.

This event is set when the UVC driver sends a request for the device to enter suspend/ low power mode to save power since there is no activity.

The code snippet handles this event and puts the CX3 to suspend mode completely by using CyU3PSysEnterSuspendMode() API until there is a wakeup event.

During this time, the J-TAG can't communicate with CX3 CPU as it is in suspend mode and that's the reason for the error that you see.


The workaround for this would be to comment out the line or comment out the entire if (eventFlag & CX3_USB_SUSP_EVENT_FLAG) condition to avoid the handling of any suspend mode requests from host:

// status = CyU3PSysEnterSuspendMode (CY_U3P_SYS_USB_BUS_ACTVTY_WAKEUP_SRC, 0, &wakeReason);

This will prevent the device from going into low power mode even if the hosts requests for it and so, the J-TAG can communicate with CX3.

Regards,

Yashwant

View solution in original post

5 Replies