Using the J-Link probe to connect to an STM32L062 chip on a custom PCB with SES 7.12a as the IDE, I am now unable to connect the J-Link to the processor, even though this setup has worked previously with no issues. The log for connecting is :
Connecting ‘J-Link’ using ‘USB 4294967295’
Loaded C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 7.12a/bin/JLink_x64.dll
Firmware Version: J-Link ARM V8 compiled Nov 28 2014 13:44:46
DLL Version: 7.86c
Hardware Version: V8.00
Target Voltage: 3.306
Device "STM32L062K8" selected.
Current Speed: 4000 kHz
InitTarget() start
SWD selected. Executing JTAG -> SWD switching sequence.
DAP initialized successfully.
InitTarget() end - Took 20ms
Found SW-DP with ID 0x0BC11477
DPv0 detected
CoreSight SoC-400 or earlier
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: 0x04770031)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xF0000000
CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p1, Little endian.
Connect fallback: Reset via Reset pin & Connect.
RESET (pin 15) high, but should be low. Please check target hardware.
InitTarget() start
SWD selected. Executing JTAG -> SWD switching sequence.
DAP initialized successfully.
InitTarget() end - Took 19ms
Found SW-DP with ID 0x0BC11477
DPv0 detected
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xF0000000
CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p1, Little endian.
Failed to initialize CPU module in firmware because probe is low on memory (heap).
Failed to connect to target.
Given that so much activity seems to be happening successfully, it doesn't look like it's a wiring issue between the J-Link and the PCB (I've also tried this on two different boards with the same result). Although the log is complaining about the reset line, we have never attached anything to this pin other than the J-Link before and it hasn't been a problem. The fact that the log says the PROBE is low on memory is what I don't understand. How does the J-Link itself run out of memory, and if it did, why wouldn't unplugging it solve the issue?
Connecting ‘J-Link’ using ‘USB 4294967295’
Loaded C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 7.12a/bin/JLink_x64.dll
Firmware Version: J-Link ARM V8 compiled Nov 28 2014 13:44:46
DLL Version: 7.86c
Hardware Version: V8.00
Target Voltage: 3.306
Device "STM32L062K8" selected.
Current Speed: 4000 kHz
InitTarget() start
SWD selected. Executing JTAG -> SWD switching sequence.
DAP initialized successfully.
InitTarget() end - Took 20ms
Found SW-DP with ID 0x0BC11477
DPv0 detected
CoreSight SoC-400 or earlier
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: 0x04770031)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xF0000000
CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p1, Little endian.
Connect fallback: Reset via Reset pin & Connect.
RESET (pin 15) high, but should be low. Please check target hardware.
InitTarget() start
SWD selected. Executing JTAG -> SWD switching sequence.
DAP initialized successfully.
InitTarget() end - Took 19ms
Found SW-DP with ID 0x0BC11477
DPv0 detected
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xF0000000
CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p1, Little endian.
Failed to initialize CPU module in firmware because probe is low on memory (heap).
Failed to connect to target.
Given that so much activity seems to be happening successfully, it doesn't look like it's a wiring issue between the J-Link and the PCB (I've also tried this on two different boards with the same result). Although the log is complaining about the reset line, we have never attached anything to this pin other than the J-Link before and it hasn't been a problem. The fact that the log says the PROBE is low on memory is what I don't understand. How does the J-Link itself run out of memory, and if it did, why wouldn't unplugging it solve the issue?