2023-12-20 06:32 AM
Hi,
I am trying to program STM32F030C8T6 with STM32CubeIDE. When I try to upload the code, it says the download was successful but then it fails to halt the device. I have tried setting "Reset behaviour" to "None" as other posts have suggested, but that only results to me getting another error with an unknown reason and it telling me to check power and cabling. I have done so, 5 times already and I have measured every part of the circuit with my multimeter. Everything is connected. What I find weird is that a week ago it was working fine. Only as I expanded the firmware by an order of magnitude, it stopped working. What could I do to get rid of this error?
Best regards,
Juhani
-------------------------------------------------------------------
STM32CubeProgrammer v2.14.0
-------------------------------------------------------------------
Log output file: C:\Users\Juhani\AppData\Local\Temp\STM32CubeProgrammer_a12652.log
ST-LINK SN : 38FF6B06304E4B3038591243
ST-LINK FW : V2J42S7
Board : --
Voltage : 3.17V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x440
Revision ID : Rev 2.0
Device name : STM32F05x/F030x8
Flash size : 64 KBytes
Device type : MCU
Device CPU : Cortex-M0
BL Version : 0x21
Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_a12652.srec
File : ST-LINK_GDB_server_a12652.srec
Size : 13.38 KB
Address : 0x08000000
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 13]
Download in Progress:
File download complete
Time elapsed during download operation: 00:00:00.947
Verifying ...
Download verified successfully
Could not halt device (19)
Target is not responding, retrying...
Target is not responding, retrying...
Shutting down...
Target is not responding, retrying...
Target is not responding, retrying...
Failed to read register cache
Target is not responding, retrying...
Target is not responding, retrying...
After this the LED on the ST-LINK/V2 lights up orange, which I know means communication failed.
2024-09-24
04:26 AM
- last edited on
2024-09-24
06:17 AM
by
Maxime_MARCHETT
I just encountered a similar situation, unable to stop the device (18). You may need to check the code problem. It may be that some IO ports have serious conflicts.
This post has been translated from Chinese to comply with the ST Community guidelines.