Microcontroller stm32f030f4p6 is defined but not flashed in CubeIDE 1.11.0

Kondratev.Georgiy · ‎2023-01-02

Microcontroller stm32f030f4p6 is defined but not flashed in CubeIDE 1.11.0. It gives the message "The microcontroller is not original", while the CubeProgrammer flashes it perfectly, correctly determines the ID 0x444 Rev 1.0. If I try to flash it, it suggests using an earlier version of the GDB server. MK in appearance and marking is similar to the original. Tell me, maybe this development environment simply does not support this MK?

Rim LANDOLSI · ‎2023-01-03

Hello BAl K.1 ,

At first , let me thank you for reporting your issue.

Could you please supply the gdb server log-file and screenshots of the error message.

The log-file will be created if option “Log to file�? is enabled in the debug settings.

Regards,

Rim

Kondratev.Georgiy · ‎2023-01-03

Ok. I am now dealing with the creation of an external loader for a QSPI flash, I also have questions about it, or rather I will ask it later when there is more information.

Kondratev.Georgiy · ‎2023-01-04

information for the post.

Open On-Chip Debugger 0.12.0-rc1+dev-00061-g5e9b46d77 (2022-10-20-14:50) [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 : connected to stlink-server
Info : stlink-server API v1, version 1.3.0
Info : STLINK V2J40S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.214795
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
Info : starting gdb server for STM32F030F4Px.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Error: timed out while waiting for target halted
Error executing event gdb-attach on target STM32F030F4Px.cpu:
D:/ST/STM32CubeIDE_1.11.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.debug.openocd_2.0.400.202211031408/resources/openocd/st_scripts/gdb_helper.tcl:18: Error: TARGET: STM32F030F4Px.cpu - Not halted
in procedure 'gdb_attach_hook' called at file "D:/ST/STM32CubeIDE_1.11.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.debug.openocd_2.0.400.202211031408/resources/openocd/st_scripts/target/stm32f0x.cfg", line 136
in procedure 'first_gdb_attach_hook' called at file "D:/ST/STM32CubeIDE_1.11.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.debug.openocd_2.0.400.202211031408/resources/openocd/st_scripts/gdb_helper.tcl", line 18
Info : device id = 0x10006444
Info : flash size = 16 KiB
Warn : GDB connection 1 on target STM32F030F4Px.cpu not halted
shutdown command invoked
Info : dropped 'gdb' connection

[0.000] initConfigParams():  Configuration flags start
[0.000] initConfigParams():   external-init                  false
[0.000] initConfigParams():   pend-halt-timeout              (null)
[0.000] initConfigParams():   halt                           false
[0.000] initConfigParams():   config-file                    ""
[0.000] initConfigParams():   persistent                     false
[0.000] initConfigParams():  +log-file                       "D:\STM32CubeIDE\workspace_1.11.0\blink\Debug\st-link_gdbserver_log.txt"
[0.000] initConfigParams():  +log-level                      31
[0.000] initConfigParams():  +port-number                    61234
[0.000] initConfigParams():  +verbose                        true
[0.000] initConfigParams():   refresh-delay                  15
[0.000] initConfigParams():  +verify                         true
[0.000] initConfigParams():  +swd                            true
[0.000] initConfigParams():   swo-port                       61234
[0.000] initConfigParams():   cpu-clock                      8000000
[0.000] initConfigParams():   swo-clock-div                  128
[0.000] initConfigParams():  +initialize-reset               true
[0.000] initConfigParams():   debuggers                      false
[0.000] initConfigParams():  +serial-number                  "55FF6F065177485609381187"
[0.000] initConfigParams():  +apid                           0
[0.000] initConfigParams():   attach                         false
[0.000] initConfigParams():   shared                         false
[0.000] initConfigParams():   erase-all                      false
[0.000] initConfigParams():   memory-map                     ""
[0.000] initConfigParams():   ext-memory-loaders             false
[0.000] initConfigParams():   extload_init                   (null)
[0.000] initConfigParams():   extload                        (null)
[0.000] initConfigParams():  +stm32cubeprogrammer-path       "D:\ST\STM32CubeIDE_1.11.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.0.500.202209151145\tools\bin"
[0.000] initConfigParams():   temp-path                      ""
[0.000] initConfigParams():   preserve-temps                 false
[0.000] initConfigParams():   frequency                      0
[0.000] initConfigParams():   licenses                       false
[0.000] initConfigParams():   ignore-rest                    false
[0.000] initConfigParams():   version                        false
[0.000] initConfigParams():   help                           false
[0.000] initConfigParams():  Configuration flags end
[0.001] init():  STMicroelectronics ST-LINK GDB server. Version 7.1.0
Copyright (c) 2022, STMicroelectronics. All rights reserved.
[0.007] openDevice():  COM frequency = 4000 kHz
[0.007] openDevice():  Target connection mode: Under reset
[0.012] readFromTarget():  Reading ROM table for AP 0 @0xe00fffd0
[0.014] reset_hw_wtchpt_module():  Hardware watchpoint supported by the target 
[0.015] initContext():  ST-LINK Firmware version : V2J40S7
[0.015] initContext():  Device ID: 0x471
[0.015] initContext():  PC: 0x80003f0
[0.016] Device_GetStatus():  ST-LINK device status: HALT_MODE
[0.016] initContext():  ST-LINK detects target voltage = 3.22 V
[0.016] initServerContext():  
Error in initializing ST-LINK device.
Reason: [0.016] initServerContext():  ST-LINK: Could not verify ST device! Abort connection.

Kondratev.Georgiy · ‎2023-01-04

I searched by ID for what kind of MK it could be with the identifier 0x471 and this is STM32L4P5xx, or there is no code 0x444 in the database, or an error was made in the exchange protocol algorithm.

Rim LANDOLSI · ‎2023-01-05

Could you please share a picture of your board and the package of the product that you purchased, in fact it could be the device ID that does not match.

Kondratev.Georgiy · ‎2023-01-05

I would also doubt the authenticity of the MK, but CubeProgrammer, unlike the development environments from ST and Keil, determines the chip correctly, as can be seen on the screen post above. I purchased from the same seller the board for stm32f103c8t6, they load perfectly.

Kondratev.Georgiy · ‎2023-01-05

Of course, it is not always possible to believe what the seller writes and the photo that he attaches to the product. But I always try to buy goods from trusted sellers. and while there was an opportunity to buy Mk and developer boards in my region.

Rim LANDOLSI · ‎2023-01-16

Hello Kondratev.Georgiy ,

The problem with your mcu is that the identifier 0x471 refers to STM32L4P5xx not to stm32f030f4p6, the table below shows different device ID.

When trying to flash the device , it is recommended to use the latest version of the GDB server because this version of ST link GDB server contains device authentication.

When your question is answered, please close this topic by choosing Select as Best. This will help other users find that answer faster.

Thank you,

Rim