Connecting with debugger failing
Hello there,
I have a peculiar problem. Using Atolic studio, I cannot connect to the target board for debugging. I am using a Segger J-link. By using J-link console, everything seems correct:
J-Link>connect
Device "STM32L452VE" selected.
Connecting to target via SWD
Found SW-DP with ID 0x2BA01477
STM32 (connect): Can not attach to CPU. Trying connect under reset.
Found SW-DP with ID 0x2BA01477
STM32 (Protection Detection): Unexpected IDCODE DEV_ID 0x 462 found. Only checking the 1st flash bank for write protection.
Found SW-DP with ID 0x2BA01477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.
J-Link>What is new to me is this:
STM32 (Protection Detection): Unexpected IDCODE DEV_ID 0x 462 found. Only checking the 1st flash bank for write protection.I don't know either this is a glitch or indeed there is some protection (unlikely, since this is a brand new STM32 chip). The jlink console in True Studio doesnt tell much, the debug session simply doesnt start and ends like this:
https://pastebin.com/BARumA3W
Then I need to terminate the session since its stuck in a loop. Is this a hint?
WARNING: T-bit of XPSR is 0 but should be 1. Changed to 1.What could be the case in here since I can erase and write files into the memory via J-link console (the program never starts though)? Can this be an electrical issue since connection is OK? I would appreciate further help.