Hello all,
Currently, I am trying to set up debugging functionality for a custom board using the JLink Plus. When I use the JLink RTT Viewer, I get the following:
LOG: J-Link RTT Viewer V7.70d: Logging started. LOG: Terminal 0 added. LOG: Connecting to J-Link via USB... LOG: Device "NRF52" selected. LOG: InitTarget() start LOG: InitTarget() end LOG: Found SW-DP with ID 0x53A01477 LOG: DPIDR: 0x27201477 LOG: CoreSight SoC-400 or earlier LOG: Scanning AP map to find all available APs LOG: AP[2]: Stopped AP scan as end of AP map has been reached LOG: AP[0]: AHB-AP (IDR: 0x44770011) LOG: AP[1]: JTAG-AP (IDR: 0x02880000) LOG: Iterating through AP map to find AHB-AP to use LOG: AP[0]: Skipped. Could not read CPUID register LOG: AP[1]: Skipped. Not an AHB-AP LOG: InitTarget() start LOG: InitTarget() end LOG: Found SW-DP with ID 0x2BA01477 LOG: DPIDR: 0x2BA01477 LOG: CoreSight SoC-400 or earlier LOG: Scanning AP map to find all available APs LOG: AP[2]: Stopped AP scan as end of AP map has been reached LOG: AP[0]: AHB-AP (IDR: 0x24770011) LOG: AP[1]: JTAG-AP (IDR: 0x02880000) LOG: Iterating through AP map to find AHB-AP to use LOG: AP[0]: Core found LOG: AP[0]: AHB-AP ROM base: 0xE00FF000 LOG: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM) LOG: Found Cortex-M4 r0p1, Little endian. LOG: FPUnit: 0 code (BP) slots and 0 literal slots LOG: CoreSight components: LOG: ROMTbl[0] @ E00FF000 ERROR: Could not find core in Coresight setup LOG: RTT Viewer connected
Other programs show similar issues, such as the JLink commander. I believe that this issue has something to do with the APPROTECT functionality built into the architecture, but I do not have much knowledge on the subject. I have seen a few posts here and there discussing how there were changes to the default APPROTECT functionality, but I don't want to get ahead of myself. Does anyone know what a typical cause and/or solution to this issue is?
Thanks!
Joseph
