MCU don't run after out of debug

Discuss how to use the features of Atollic TrueSTUDIO, including the editor, assembler, C/C++ compiler, linker, debugger, static code analysis and team collaboration tools.

Moderators: Markus Girdland, Mattias Norlander

forcewin
Posts: 4
Joined: Tue Jul 02, 2019 12:30 pm

MCU don't run after out of debug

Postby forcewin » Wed Jul 03, 2019 2:31 pm

I am still using truestudio, stm32cubeMx and stm32F746.
By the way, suddenly the MCUs are not working.
It works fine in debug mode, but stops when you exit debug mode.

I can reinstall truestudio and cubemx,
and also erased various vaccine programs...
I am trying to modify the debug configuration for a few days.
What should I do?

below showing console window:

STMicroelectronics ST-LINK GDB server. Version 5.1.0
Copyright (c) 2018, STMicroelectronics. All rights reserved.

Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled

Waiting for debugger connection...
Debugger connected
-------------------------------------------------------------------
STM32CubeProgrammer v1.3.0
-------------------------------------------------------------------

Log output file: C:\Users\maestro\AppData\Local\Temp\STM32CubeProgrammer_a17192.log
ST-LINK SN : 55FF6D067871515351552367
ST-LINK FW : V2J32S7
Voltage : 3.44V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x449
Device name : STM32F74x/STM32F75x
Device type : MCU
Device CPU : Cortex-M7

Memory Programming ...
Opening and parsing file: C:\Users\maestro\AppData\Local\Temp\ST-LINK_GDB_server_a17192.srec
File : C:\Users\maestro\AppData\Local\Temp\ST-LINK_GDB_server_a17192.srec
Size : 7356 Bytes
Address : 0x08000000

Erasing memory corresponding to segment 0:
Erasing internal memory sector 0
Download in Progress:

File download complete
Time elapsed during download operation: 00:00:00.477

Verifying ...

Download verified successfully

Debugger connection lost.
Shutting down...

forcewin
Posts: 4
Joined: Tue Jul 02, 2019 12:30 pm

Re: MCU don't run after out of debug

Postby forcewin » Thu Jul 04, 2019 7:58 am

I fail again today.
The ST-LINK driver is working well
startup scripts also seem to be wrong.
I do not see the word error.
Debug is also good. Very very good
But, when debug is finished, mcu is halt-halt-halt... endless stopping~.
The same is true if finished quit after load.
Sky and earth do not open the way.

startup scripts:
monitor flash set_parallelism_mode 2
load
set *0xE0042004 = (*0xE0042004) | 0x7
tbreak main
continue

forcewin
Posts: 4
Joined: Tue Jul 02, 2019 12:30 pm

Re: MCU don't run after out of debug

Postby forcewin » Thu Jul 04, 2019 1:14 pm

my settings is..

C/C++ Build / Settings / Target Settings
STM32F746IG: FLASH: 1024KB DTCMRAM: 64KB SRAM1: 240KB SRAM2: 16KB
Code Location: FLASH
Endianell: Little endian

C/C++ Build / Settings / Tool Settings
Other /
Output format: Intel Hex

C/C++ Build / Settings / Build Steps
Post-build steps /
Command: arm-atollic-eabi-objcopy.exe -O ihex "${BuildArtifactFileBaseName}.elf" "${BuildArtifactFileBaseName}.hex"

STM32 ST-LINK Utility.exe file:
open my .hex file -> Program & verify -> Start
22:06:59 : [T2.hex] opened successfully.
22:06:59 : [T2.hex] checksum : 0x000B6DCD
22:07:45 : ST-LINK SN : 55FF6D067871515351552367
22:07:45 : V2J32S7
22:07:45 : Connected via SWD.
22:07:45 : SWD Frequency = 4,0 MHz.
22:07:45 : Connection mode : Normal.
22:07:45 : Debug in Low Power mode enabled.
22:07:45 : Device ID:0x449
22:07:45 : Device flash Size : 1MBytes
22:07:45 : Device family :STM32F74x/F75x
22:08:08 : Memory programmed in 0s and 547ms.
22:08:08 : Verification...OK
22:08:08 : Programmed memory Checksum: 0x000B6DCD

But, why is the MCU stopped ?
Let me know this, please.

no problem in debug mode..

forcewin
Posts: 4
Joined: Tue Jul 02, 2019 12:30 pm

Re: MCU don't run after out of debug

Postby forcewin » Thu Jul 04, 2019 3:07 pm

ST-LINK =HALT_MODE appears in Truestudio's log file
I found Core state: Halted in the STM32 ST-LINK Utility program
After loading the hex file, enter halt_mode.
I do not know why.
It's too hard to start the MCU program right now.
Downgrade stm32cubeMx and try installing again.
Downgrade cubemx and try installing again.
I also install the stm32f7 series in the old version.
Can not be done, how can I do...?


Return to “Atollic TrueSTUDIO tool discussions”

Who is online

Users browsing this forum: MSN [Bot] and 4 guests