Hi,
I am having issues debugging my STEVAL-IDB008V2 board using the ST-LINK/v2 debugger through Keil v5. When I try to load the program in Keil, I get the error message: ''No target connected'' or the error message ''Error while accessing a target ressource. Ressource perhaps not available or a wrong access was attempted''.
I am able to connect to the board using the BlueNRG-1 ST-LINK Utility.
What I tried so far:
-Erase the chip before loading the program -Loading the program when the board runs the bootlader (DI07 set HIGH, DL2 ON) -Loading the program when the board runs the flash application (DI07 set LOW, DL2 OFF) -Loading the program when the board is in DFU USB (RESETIN set LOW, DL2 flashes) -Loading the program with different debug settings (Normal, with Pre-reset, under Reset) and clock settings -Updating the FW of the ST-LINK/V2
My current settings for the Debug tab:
Debug Adapter: ST-LINK/V2 Serial Number: 50FF71067871515218580667 Version HW: v2 Version FW: V2J32S7
Target Com: Port SW Clock Req: 1.8MHz Clock Selected: 1.8Mhz
Debug: Connect & Reset Options: Connect: Normal Reset: Autodetect Reset after Connect (checked)
Cache Options: Cache Code(checked) Cache Memory(checked)
Download Options: Verify Code Download (unchecked) Download to Flash (unchecked)
SW Device: ID CODE: 0x0BB11477 Device Name: ARM CoreSight SW-DP
Furthermore, as you can see from the debug settings, the ST-LINK/V2 is recognized in Keil and Keil identifies the BlueNRG-2 as 0x0BB11477 (IDCODE)/ ARM CoreSight SW-DP (Device Name).
Any help would be much appreciated.
Cheers, Xavier
I just wanted to also note that the ST-Link Utility works fine, program/erase & debug. The problem lies with uVision.
That doesn't line up with:
"Other examples such as BLE_SensorDemo use the JTAG pins to communicate with the LSM6DS3 and make the debugging process impossible"
If the JTAG (sic?) lines are being corrupted by the hardware, then no debugger is going to be able to get around that, surely?!