Hi. I have a J-Link Pro. I found that when I connect to an Cortex-M33 FPGA, it could not detect/identify the ITM module. But it can detect the ITM from a Cortex-M3 part. On further investigation, I realized that the JLink probably could not identify the ITM because the PID/CID register values are different from a Cortex-M3 part. For Cortex-M33, the ITM programmer's model is:

infocenter.arm.com/help/topic/…_en/jfa1443803152369.html


For Cortex-M3, the ITM programmer's model is:
infocenter.arm.com/help/topic/…_en/ric1417175942276.html



The Coresight components identified by the JLink after connection with Cortex-M33 are:


CoreSight components:
ROMTbl[0] @ E00FE000
ROMTbl[0][0]: E00FF000, CID: B105100D, PID: 000BB4C9 ROM Table
ROMTbl[1] @ E00FF000
ROMTbl[1][0]: E000E000, CID: B105900D, PID: 000BBD21 SCS
ROMTbl[1][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT
ROMTbl[1][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB
ROMTbl[1][3]: E0000000, CID: B105900D, PID: 000BBD21 ???
ROMTbl[1][5]: E0041000, CID: B105900D, PID: 002BBD21 ETM
ROMTbl[1][6]: E0042000, CID: B105900D, PID: 000BBD21 ETB
ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BBD21 TPIU
ROMTbl[0][2]: E00FD000, CID: B105F00D, PID: 001BB101 TSG
Cortex-M33 identified.



Is there a way to force the JLink Pro to identify the entry at ROMTbl[1][3] to be the ITM ?