Hi Segger,
I have a situation where the BlueNRG2 goes to sleep.
JLinkExe then tries to connect to this board, but only succeeds half-ways.
It then reports that no flash memory words could be read, and so it decides to mass-erase my device.
This is scary. I have not asked to erase my device, just to connect to it.
Command used:
JLinkExe -device BLUENRG2 -if swd -speed 1000 -AutoConnect 1
See the log:
SEGGER J-Link Commander V6.32b (Compiled May 8 2018 18:28:28)
DLL version V6.32b, compiled May 8 2018 18:28:22
Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Apr 20 2018 16:47:09
Hardware version: V10.10
S/N: 50104725
License(s): GDB
VTref=1.909V
Device "BLUENRG2" selected.
Connecting to target via SWD
Found SW-DP with ID 0x0BB11477
Found SW-DP with ID 0x0BB11477
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: 0x04770021)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xF0000000
CPUID register: 0x410CC200. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p0, Little endian.
FPUnit: 4 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ F0000000
ROMTbl[0][0]: D00FF000, CID: 00000000, PID: 00000000 ???
The first word in flash memory could not be read. This indicates that the device is secured.
For accessing memory the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash.
Device will be unsecured now.
Executing ResetTarget()
****** Error: DAP error while reading DP-Ctrl-Stat register.
I have a situation where the BlueNRG2 goes to sleep.
JLinkExe then tries to connect to this board, but only succeeds half-ways.
It then reports that no flash memory words could be read, and so it decides to mass-erase my device.
This is scary. I have not asked to erase my device, just to connect to it.
Command used:
JLinkExe -device BLUENRG2 -if swd -speed 1000 -AutoConnect 1
See the log:
SEGGER J-Link Commander V6.32b (Compiled May 8 2018 18:28:28)
DLL version V6.32b, compiled May 8 2018 18:28:22
Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Apr 20 2018 16:47:09
Hardware version: V10.10
S/N: 50104725
License(s): GDB
VTref=1.909V
Device "BLUENRG2" selected.
Connecting to target via SWD
Found SW-DP with ID 0x0BB11477
Found SW-DP with ID 0x0BB11477
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: 0x04770021)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xF0000000
CPUID register: 0x410CC200. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p0, Little endian.
FPUnit: 4 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ F0000000
ROMTbl[0][0]: D00FF000, CID: 00000000, PID: 00000000 ???
The first word in flash memory could not be read. This indicates that the device is secured.
For accessing memory the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash.
Device will be unsecured now.
Executing ResetTarget()
****** Error: DAP error while reading DP-Ctrl-Stat register.