STM32F030F4P6 programming using ST-LINKV2 issue

[FWu.3]

https://www.youtube.com/watch?v=Vld0xUj48J4

I did follow the video, but I could not flash successfully.

I use STM32F030F4P6 kit and ST-LINK V2.

Open On-Chip Debugger 0.11.0+dev-00449-g53fa0f7 (2022-06-09-09:45) [https://github.com/STMicroelectronics/OpenOCD]

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

Info : STLINK V2J40S7 (API v2) VID:PID 0483:3748

Info : Target voltage: 2.912107

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : clock speed 4000 kHz

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x0bb11477

Info : STM32F030F4Px.cpu: Cortex-M0 r0p0 processor detected

Info : STM32F030F4Px.cpu: target has 4 breakpoints, 2 watchpoints

Error: STM32F030F4Px.cpu -- clearing lockup after double fault

Polling target STM32F030F4Px.cpu failed, trying to reexamine

Info : STM32F030F4Px.cpu: Cortex-M0 r0p0 processor detected

Info : STM32F030F4Px.cpu: target has 4 breakpoints, 2 watchpoints

Info : starting gdb server for STM32F030F4Px.cpu on 3333

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

Info : device id = 0x10006444

Info : flash size = 32kbytes

Error: Failed to read memory at 0xfffffffe

shutdown command invoked

Info : dropped 'gdb' connection

Also, "Launch terminated" popped up and showed me "Could not verify ST device! Please verify that the latest version of the GDB-server is used for the connection".

I am thinking I am using OCD, not GDB. Why did I get this warning?

Thanks a lot!!!

The error I got

[FWu.3]

I tried different chips(F446) by using the same ST-LINK V2. They work​.

Is there any different version or has something changed in the F030 chip?

[Imen.D]

Hello @FWu.3​,

Try to change RDP and check if Read Out Protection is enabled.

Check VRef pin voltage. Is the power supply pins VDD, VDDA at 3.3V?

Imen

[FWu.3]

How can I check RDP?

Yes VDDA is 3.3V

[Tesla DeLorean]

CM0(+) parts generally have slower connectivity speed tolerances.

These low pin count devices also have pin level conflicts. You kind of want a short spin loop in the reset Handler to give the debugger an access window, and you want to avoid going into low power modes, reassigning pin function or disabling debug connectivity if you want to be able to reconnect to the device.

Y​ou should have NRST wired, and you can try pulling BOOT0 pin High.