IAR Ijet jtag with RT1060 eval board

ye1 · ‎03-07-2019

I m using i.mxrt1060 eval board with iar ijet jtag. When putting the board in SWD mode i do manage to debugging with no issues... but We need to use JTAG for many project based reasons. When switching to JTAG The following error appears in IAR(see long under).

I have removed the Jumpers J(47-50) and J44 to disconnect open SDA. Any thing else needed to be done in this case ?

Thu Mar 07, 2019 16:03:56: JTAG test failed - the TDO/SWDIO pin held permanently low.

I confirm this behavior when measuring JTAG_TDO is is always low....

IAR configs are ijet :

reset -> Core

interface us set ti JTAG

Thu Mar 07, 2019 16:03:52: IAR Embedded Workbench 8.32.3 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\bin\armproc.dll)
Thu Mar 07, 2019 16:03:52: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\config\debugger\NXP\iMXRT.dmac
Thu Mar 07, 2019 16:03:52: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\config\debugger\NXP\iMXRT_Trace.dmac
Thu Mar 07, 2019 16:03:52: None of the application was placed in flash memory.
Thu Mar 07, 2019 16:03:52: Downloaded C:\Users\ye\freertos_event\debug\freertos_event.out to flash memory.
Thu Mar 07, 2019 16:03:52: 0 bytes downloaded into FLASH (0.00 Kbytes/sec)
Thu Mar 07, 2019 16:03:52: Loading the I-jet/JTAGjet driver
Thu Mar 07, 2019 16:03:52: Probe: Probe SW module ver 1.61
Thu Mar 07, 2019 16:03:52: Probe: Option: trace(Auto,size_limit=100%)
Thu Mar 07, 2019 16:03:52: Probe: I-jet-Trace SW module ver 1.63
Thu Mar 07, 2019 16:03:52: Probe: Found I-jet-Trace, SN=100133
Thu Mar 07, 2019 16:03:52: Probe: I-jet-Trace-A/R/M detected.
Thu Mar 07, 2019 16:03:52: Probe: Opened in USB 3.0 mode
Thu Mar 07, 2019 16:03:52: Probe: I-jet-Trace, FW ver 1.5 (2016/06/06, USB 2016/01/25), HW Ver:B
Thu Mar 07, 2019 16:03:52: Probe: USB reading speed 381.6 MB/sec Data verified.
Thu Mar 07, 2019 16:03:52: Probe: 17552 pkts/s
Thu Mar 07, 2019 16:03:52: Probe: Internal probe memory is already enabled (power-save mode)
Thu Mar 07, 2019 16:03:52: Probe: Opened connection to I-jet-Trace:100133
Thu Mar 07, 2019 16:03:52: INFO: Input voltage 4999mV USB current 36mA, External current 772mA
Thu Mar 07, 2019 16:03:52: INFO: TrgPwr current limit set to ~600mA
Thu Mar 07, 2019 16:03:52: Adapter: ctrl read: 0x80552005
Thu Mar 07, 2019 16:03:52: Adapter: powered on previously.
Thu Mar 07, 2019 16:03:52: Adapter: ADA-IJT-MICTOR Rev: C1
Thu Mar 07, 2019 16:03:52: Adapter: Init done.
Thu Mar 07, 2019 16:03:52: Probe: Mictor+MIPI20 adapter detected
Thu Mar 07, 2019 16:03:52: Probe: Versions: JTAG=1.84 Trace=2.06 SWO=1.40 A2D=1.71 Stream=1.50 SigCom=1.04 CUSB3=1.39
Thu Mar 07, 2019 16:03:52: Emulation layer version 4.46
Thu Mar 07, 2019 16:03:52: Notification to core-connect hookup.
Thu Mar 07, 2019 16:03:52: CPU status FAILED
Thu Mar 07, 2019 16:03:55: MultiCore: Asynchronous core execution FORCED.
Thu Mar 07, 2019 16:03:55: MultiCore: Synchronous core execution DISABLED.
Thu Mar 07, 2019 16:03:55: LowLevelReset(core, delay 200)
Thu Mar 07, 2019 16:03:56: Fatal error: Failed to connect to CPU Session aborted!
Thu Mar 07, 2019 16:03:56: JTAG test failed - the TDO/SWDIO pin held permanently low.
Thu Mar 07, 2019 16:03:56: IAR Embedded Workbench 8.32.3 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\bin\armproc.dll)
Thu Mar 07, 2019 16:03:57: Logging to file: C:\Users\ye\freertos_event\cspycomm.log
Thu Mar 07, 2019 16:03:57: Loading the I-jet/JTAGjet driver

jorge_a_vazquez · ‎03-15-2019

Hi Yassine Elfarri

Regarding your questions;

is this pull just adds the possibility to use bondery scan or does include jtag debugging ?

JTAG_MOD set to high configures the JTAG interface to mode compliant with IEEE1149.1 standard. JTAG_MOD set to low configures the JTAG interface for common SW debug adding all the system TAPs to the chain.

I found that the fuse 0x460 is set to SWD by default can we change this to jtag?

In order to change the fuses configuration I would recommend the following appnote:

https://www.nxp.com/docs/en/application-note/AN4686.pdf

Hope this helps.

Best regards

Jorge Alcala

View solution in original post

ye1 · ‎03-15-2019

The IAR used in my case is the latest version and the debugger firmware is the latest version as well. Those are one of the first things i have tested. I have test the debugger with MK10 microcontroller and it works flawlessly.

I have been first in contact with IAR support we ended up with the conclusion that the issue is with RT1060 MCU not the debugging tool.

unfortunately, you don't even try to read the post or answer the questions. At the moment we are holding off production of boards with this MCU because we can not resolve this issue. Can Nxp take this more seriously

"Added a pull-up resistor to jtag_mod pin to change microcontroller from SWD mode to JTAG mode" is this pull

just adds the possibility to use bondery scan or does include jtag debugging ?

I found that the fuse 0x460 is set to SWD by default can we change this to jtag?

What is the steps to change this eval board from SWD mode to jtag ?

Do you mind commenting on the previous posts?

any steps that could be done in another manner?

Why do i get jtag id but i can not debugg with jtag ? this issues is true for you IDE as well.

Why the CPU does mot respons to jtag commands ?

Does RT1060 support jtag debugging ?

jorge_a_vazquez · ‎03-15-2019

Hi Yassine Elfarri

Regarding your questions;

is this pull just adds the possibility to use bondery scan or does include jtag debugging ?

JTAG_MOD set to high configures the JTAG interface to mode compliant with IEEE1149.1 standard. JTAG_MOD set to low configures the JTAG interface for common SW debug adding all the system TAPs to the chain.

I found that the fuse 0x460 is set to SWD by default can we change this to jtag?

In order to change the fuses configuration I would recommend the following appnote:

https://www.nxp.com/docs/en/application-note/AN4686.pdf

Hope this helps.

Best regards

Jorge Alcala

ye1 · ‎03-18-2019

Hei Jorge,

We needed to fuse 0x460 and set the jtag_mod set low for debugging.

ye1 · ‎03-13-2019

Hei Jorge Antonio Alcala Vazquez

The post you refer to is one of the first things I have done.

I m using an external IAR ijet trace debugger, the IAR ijet trace debugger was tested and it is working.

Add all the DNP resistors
Disconnected all Jumpers J50,J49,J48,J47,J46,J44
Added a pull-up resistor to jtag_mod pin to change microcontroller from SWD mode to JTAG mode
I removed pull up ( R309) according to your own datasheet TDO shouldn't be pulled up or down
TDI had a capacitance (see picture under) to solve this I had to remove R323 and D18. Now the signal is the way it should be

After doing all this finally i can now read device ID which is 0x88C501D and the jtag clock is 12.5 MHz before this steps the clock managed 97KHz at best

Picture with Jtag id this is good news

Jtag_TDI had odd rise and fall due to capacitance in the line. This was correct by removing remove R323 and D18 components.

Now i m getting the following Error "CPU status failed " and "cannot initialize DAP access" ...... Why m i getting the following error?

Can i program RT1060 device using jtag ?

mar 13/14:21:18.438 INFO : Debug Log(info): JTAG clock detected: 12.5MHz

mar 13/14:21:18.438 INFO : JTAG clock detected: 12.5MHz

mar 13/14:21:18.458 INFO : Debug Log(info): Chain detected: 1 device, total IR length 5.

mar 13/14:21:18.458 INFO : Chain detected: 1 device, total IR length 5.

mar 13/14:21:18.458 INFO : Debug Log(info): BoardCfg=!5

mar 13/14:21:18.458 INFO : BoardCfg=!5

mar 13/14:21:18.458 INFO : Debug Log(info): Notification to core-connect hookup.

mar 13/14:21:18.458 INFO : Notification to core-connect hookup.

mar 13/14:21:18.458 DEBUG2 : <Call to _ExecDeviceCoreConnect: macro undefined
mar 13/14:21:18.458 DEBUG2 : <Call to execUserCoreConnect: macro undefined
mar 13/14:21:18.458 DEBUG2 : ConnectToHardware(), checking status (#1): Core 0: CpuStatus(status = <0x80: CPU_STATUS_MERR>) = 0
mar 13/14:21:18.458 INFO : Debug Log(info): CPU status FAILED
mar 13/14:21:18.498 INFO : Debug Log(info): Cannot initialize DAP access.Chain detected: 1 device, total IR length 5.

mar 13/14:21:18.498 INFO : Cannot initialize DAP access.Chain detected: 1 device, total IR length 5.

ye1 · ‎03-13-2019

My IAR configuration are the following :

Generate example project using MCUXpresso config Tools v5
QSPI Flash on the MIMXRT1060 EVK Board with dip switches set to 0010 where 1 is SW7-3
for project configs see pictures under

jorge_a_vazquez · ‎03-14-2019

Hi Yassine Elfarri

This issue should be caused by the low version of firmware of I-Jet. The updating of the firmware of I-jet can be done by updating your IAR to the latest version.

Since I-jet is from IAR company, I would also suggest contacting IAR support.

Regards

jorge_a_vazquez · ‎03-12-2019

Hi Yassine Elfarri

Please check the following post:

https://community.nxp.com/message/1109744

Hope this helps

Best regards

Jorge Alcala