STM32F030F4 + CubeIDE + JLink can't verify device

[tcoin]

Hello,

I have a dev board based on STM32F030F4. When I try to attach to the device using my Segger JLink Edu, I am getting a "Could not verify ST device" error.

Here is the log from Cube:

SEGGER J-Link GDB Server V7.88h Command Line Version

JLinkARM.dll V7.88h (DLL compiled Jun 16 2023 09:21:40)

Command line: -port 2331 -s -device STM32F030F4 -endian little -speed 1000 -if swd -vd
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: yes
Generate logfile: off
Verify download: on
Init regs on start: off
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: STM32F030F4
Target device parameters: none
Target interface: SWD
Target interface speed: 1000kHz
Target endian: little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link EDU Mini V1 compiled Jun 6 2023 10:50:57
Hardware: V1.00
S/N: 801025834
Feature(s): FlashBP, GDB
Checking target voltage...
Target voltage: 3.28 V
Listening on TCP/IP port 2331
Connecting to target...
Halting core...
Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
GDB client (conn. 11) requested target.xml from GDB Server
Reading common registers: Read register 'r0' (4 bytes) from hardware: 0xFFE70000
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x00001454
Read register 'r3' (4 bytes) from hardware: 0x80000000
Read register 'r4' (4 bytes) from hardware: 0x04000020
Read register 'r5' (4 bytes) from hardware: 0x00000048
Read register 'r6' (4 bytes) from hardware: 0x00E000E0
Read register 'r7' (4 bytes) from hardware: 0x00000800
Read register 'r8' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r9' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'r10' (4 bytes) from hardware: 0x88F7FF1F
Read register 'r11' (4 bytes) from hardware: 0x88F7FF1F
Read register 'r12' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'sp' (4 bytes) from hardware: 0x58060020
Read register 'lr' (4 bytes) from hardware: 0x51EDFF1F
Read register 'pc' (4 bytes) from hardware: 0x74EDFF1F
Read register 'xpsr' (4 bytes) from hardware: 0x00000081
Read 4 bytes @ address 0x1FFFED74 (Data = 0xD1010BC0)
Read 2 bytes @ address 0x1FFFED74 (Data = 0x0BC0)
Received monitor command: ReadAPEx 0x0 0xF8
O.K.:0xE00FF003
Received monitor command: ReadMemAP 0x0 0xE00FFFD0 0x8 0x0
O.K.:0x00000004,0x00000000,0x00000000,0x00000000,0x00000071,0x000000B4,0x0000000B,0x00000000
GDB closed TCP/IP connection (Socket 11)
Restoring target state and closing J-Link connection...
Shutting down...

I though it was a counterfait ST, but it looks like the CHIP ID is correct, according to JLinkExe tool. The SW-DP ID returned matches the one from the cubeide configuration file stm32f0x.cfg (0x0BB11477)

SEGGER J-Link Commander V7.84f (Compiled Feb 7 2023 16:51:58)
DLL version V7.84f, compiled Feb 7 2023 16:51:27

For all available command line options please refer to:
https://wiki.segger.com/J-Link_Commander#Batch_processing

Connecting to J-Link via USB...O.K.
Firmware: J-Link EDU Mini V1 compiled Jun 6 2023 10:50:57
Hardware version: V1.00
J-Link uptime (since boot): 0d 00h 10m 39s
S/N: 801025834
License(s): FlashBP, GDB
USB speed mode: Full speed (12 MBit/s)
VTref=3.284V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: STM32F030F4
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "STM32F030F4" selected.


Connecting to target via SWD
InitTarget() start
SWD selected. Executing JTAG -> SWD switching sequence.
DAP initialized successfully.
InitTarget() end
Found SW-DP with ID 0x0BB11477
DPIDR: 0x0BB11477
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: 0x04770021)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
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] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB008 SCS
[0][1]: E0001000 CID B105E00D PID 000BB00A DWT
[0][2]: E0002000 CID B105E00D PID 000BB00B FPB
Memory zones:
Zone: Default Description: Default access mode
Cortex-M0 identified.
J-Link>

 What am I missing ?

Thank you in advance

[johnmus]

I have the exact problem like you. Hope someone have solution