Failure at line 13

Discussions concerning TrueSTUDIO for STM32 9.0.0 and later versions.

Moderators: Markus Girdland, Mattias Norlander

phoenix2000
Posts: 15
Joined: Sun Aug 12, 2018 11:02 am

Re: Failure at line 13

Postby phoenix2000 » Sat Dec 22, 2018 1:38 pm

Unfortunately, the new version 9.2.0 has the same problem and I can't understand why this continues:?

philbrooksjazz wrote:I'm having the same issue - very frustrating!!

I had some luck with disabling verify in the debug configuration settings.

Run -> Debug Configuration -> Debugger Tab -> Misc section -> uncheck "Verify Flash Download"

But it comes and goes, too early to tell if this is a real fix - but so far working.


I test it but it didn't work for me.
-------------------------------
Dear truestudio group.
I just create a test project with cubemx for stm32f429 discovery board and init the peripherals with the default values the cube gives me and no more thing I do. but still, the truestudio cannot load the program. can't you duplicate this process? please, do some thing. :|

Manix
Posts: 1
Joined: Sat Dec 22, 2018 4:18 pm

Re: Failure at line 13

Postby Manix » Sat Dec 22, 2018 4:37 pm

Hi phoenix2000,
got the same problem when updating from 9.0.1 to 9.2.0
Tool ask me to update the ST-Link Firmware , what i did .
...the the obscure "Failure at line 13" popped up.
So Line 13 is the "load" command .
To get a more detailed info about what's happen , you can switch the Log File on .
Goto "Debug Configurations"/Debugger tab; in the lower section under "Misc" you can enable the Log file.
In the LOG File I found that he has some problems to access files , but still goes on to do something and crash later.
I think the new Version 9.2.0 in conjunction with the new ST-LINK firmware has still a problem.
To go back to the old versions, you have to load old Firmware in ST-LINK and you must remove all the references to the new tool
9.2.0 in the config files . Best is to overwrite them with "old-working" versions.
Files are : .cproject .settings\* project.elf.launch

...hope the Bits and Bytes will be with you ;)

phoenix2000
Posts: 15
Joined: Sun Aug 12, 2018 11:02 am

Re: Failure at line 13

Postby phoenix2000 » Mon Dec 24, 2018 10:25 am

Manix wrote:Hi phoenix2000,
got the same problem when updating from 9.0.1 to 9.2.0
Tool ask me to update the ST-Link Firmware , what i did .
...the the obscure "Failure at line 13" popped up.
So Line 13 is the "load" command .
To get a more detailed info about what's happen , you can switch the Log File on .
Goto "Debug Configurations"/Debugger tab; in the lower section under "Misc" you can enable the Log file.
In the LOG File I found that he has some problems to access files , but still goes on to do something and crash later.
I think the new Version 9.2.0 in conjunction with the new ST-LINK firmware has still a problem.
To go back to the old versions, you have to load old Firmware in ST-LINK and you must remove all the references to the new tool
9.2.0 in the config files . Best is to overwrite them with "old-working" versions.
Files are : .cproject .settings\* project.elf.launch

...hope the Bits and Bytes will be with you ;)

Thanks dear Monix, for your offering solution.

bertrand
Posts: 5
Joined: Sun Feb 25, 2018 2:17 pm

Re: Failure at line 13

Postby bertrand » Fri Jan 18, 2019 2:32 pm

For information I had the same issue by using a ST-Link V2 after using a ST-Link V3.
I used the Legacy JTAG of the ST-Link V3 to be like a ST-Link V2 and all is running fine.

From now, I have to switch to V3 in any case.

Bertrand
useful serial debug app with plotter : https://github.com/mindstorm38/debug-sensor

DaveB
Posts: 2
Joined: Tue Nov 27, 2018 7:52 pm

Re: Failure at line 13

Postby DaveB » Sun Feb 10, 2019 9:27 pm

Just to keep this thread running. I also had this problem with trueStudio 9.1.0 "Failure at line 13"

I have been running with no problems on several Nucleo boards (STM32F030, STM32H743). However, when I tried to run on my custom hardware, the STM32F030 worked fine, but the STM32H50 did not. To be clear I was just running some very simple code that should be located in on-chip flash. The only work around I have found so far is to change the build settings | Target Settings | Code Location from Flash to RAM. This means true studio will load the binary into RAM instead of flash and then run it.

Oh, there is one more catch. You have to go into the debug configuration | Startup Scripts and comment out the second "monitor reset" that is after the "load" command. This is because we are now running out of RAM. Because, if you load the code into RAM, then do a reset, you will lose it.

I don't understand why this would be, but I suspect the complex memory architecture of the H7 is at the root of it. Any just wanted to add one more thing to try for anyone else that is stuck here.

Good Luck

awatson
Posts: 1
Joined: Wed Feb 13, 2019 1:20 pm

Re: Failure at line 13

Postby awatson » Wed Feb 13, 2019 2:10 pm

Hi,

Is there any news on this issue? A colleague of mine and myself have been having this issue with the STM32L151CBT6A (doesn't happen with the old non-A version which is no longer produced).

Happens with Atollic TrueSTUDIO 9.1.0 and 9.2.0. Downgrading to 8.x or 9.0.1 seems to fix it.

This issue appears with both the ST-Link/V2 and ST-Link/V2 ISOL (tested with several of each tool, same problem every time)

Here's the part of the log file that seems related to the problem :

Code: Select all

[3.048] handleFlashPacket():  Writing to C:\Users\Andrew\AppData\Local\Temp\ST-LINK_GDB_server_a42476.srec
[3.145] spawnCubeProgrammer():   ------ Switching to STM32CubeProgrammer -----
[3.145] file_utils_spawn():  Spawning ""C:\Program Files (x86)\Atollic\TrueSTUDIO for STM32 9.1.0\Servers\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" --connect port=SWD sn=49FF6D065178505009351587 mode=UR reset=hwRst --download C:\Users\Andrew\AppData\Local\Temp\ST-LINK_GDB_server_a42476.srec --log C:\Users\Andrew\AppData\Local\Temp\STM32CubeProgrammer_a42476.log"
[5.032] file_utils_spawn():  Return code 1
[5.032] spawnCubeProgrammer():  Encountered Error when opening C:\Program Files (x86)\Atollic\TrueSTUDIO for STM32 9.1.0\Servers\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe
[5.034] spawnCubeProgrammer():  14:17:10:329
[5.034] spawnCubeProgrammer(): 
[5.034] spawnCubeProgrammer():  14:17:10:329 Log output file:   C:\Users\Andrew\AppData\Local\Temp\STM32CubeProgrammer_a42476.log
[5.034] spawnCubeProgrammer():  14:17:10:706 STLinkUSBDriver.dll loaded
[5.034] spawnCubeProgrammer():  14:17:10:709 STLinkUSBDriver.dll loaded
[5.034] spawnCubeProgrammer():  14:17:10:709 ST-LINK SN  : 49FF6D065178505009351587
[5.034] spawnCubeProgrammer():  14:17:10:709 ST-LINK FW  : V2J32S7
[5.034] spawnCubeProgrammer():  14:17:10:710 Voltage     : 3.01V
[5.034] spawnCubeProgrammer():  14:17:10:716 SWD freq    : 4000 KHz
[5.034] spawnCubeProgrammer():  14:17:10:716 Connect mode: Under Reset
[5.034] spawnCubeProgrammer():  14:17:10:716 Reset mode  : Hardware reset
[5.035] spawnCubeProgrammer():  14:17:10:901 Device ID   : 0x429
[5.035] spawnCubeProgrammer():  14:17:11:377 Reading data...
[5.035] spawnCubeProgrammer():  14:17:11:378 r ap 0 @0x40023C1C 0x00000004 bytes
[5.035] spawnCubeProgrammer():  14:17:11:378 Database: Config 0 is active.
[5.035] spawnCubeProgrammer():  14:17:11:380 flash loader C:/Program Files (x86)/Atollic/TrueSTUDIO for STM32 9.1.0/Servers/STM32CubeProgrammer/bin/FlashLoader/0x429.stldr is loaded
[5.035] spawnCubeProgrammer():  14:17:11:380 Reading data...
[5.035] spawnCubeProgrammer():  14:17:11:381 r ap 0 @0x40023C1C 0x00000004 bytes
[5.035] spawnCubeProgrammer():  14:17:11:381 Database: Config 0 is active.
[5.035] spawnCubeProgrammer():  14:17:11:381 Device name : STM32L100x6xxA/STM32L100x8xxA/STM32L100xBxxA/STM32L15xx6xxA/STM32L15xx8xxA/STM32L15xxBxxA
[5.035] spawnCubeProgrammer():  14:17:11:381 Device type : MCU
[5.035] spawnCubeProgrammer():  14:17:11:381 Device CPU  : Cortex-M3
[5.035] spawnCubeProgrammer():  14:17:11:381
[5.035] spawnCubeProgrammer():  14:17:11:381
[5.035] spawnCubeProgrammer(): 
[5.035] spawnCubeProgrammer():  14:17:11:381 Memory Programming ...
[5.035] spawnCubeProgrammer():  14:17:11:381 Opening and parsing file: C:\Users\Andrew\AppData\Local\Temp\ST-LINK_GDB_server_a42476.srec
[5.035] spawnCubeProgrammer():  14:17:11:388   File          : C:\Users\Andrew\AppData\Local\Temp\ST-LINK_GDB_server_a42476.srec
[5.035] spawnCubeProgrammer():  14:17:11:388   Size          : 96080 Bytes
[5.035] spawnCubeProgrammer():  14:17:11:388   Address       : 0x08003000
[5.035] spawnCubeProgrammer():  14:17:11:388
[5.035] spawnCubeProgrammer(): 
[5.035] spawnCubeProgrammer():  14:17:11:388 Erasing Segment <0> Address <0x08003000> Size <96080>Bytes
[5.035] spawnCubeProgrammer():  14:17:11:388 Erasing memory corresponding to segment 0:
[5.035] spawnCubeProgrammer():  14:17:11:388 Memory erase...
[5.035] spawnCubeProgrammer():  14:17:11:388 Error: Flash loader cannot be loaded
[5.035] spawnCubeProgrammer():  14:17:11:388
[5.036] spawnCubeProgrammer(): 
[5.036] spawnCubeProgrammer():  14:17:11:388 Error: failed to erase memory
[5.036] spawnCubeProgrammer():   ------ Switching context -----
[5.060] reset_hw_wtchpt_module():  Hardware watchpoint supported by the target
[5.065] Device_Initialise():  SWD frequency = 4000 kHz
[5.065] Device_Initialise():  ST-LINK Firmware version : V2J32S7
[5.066] Device_Initialise():  Device ID: 0x429
[5.066] Device_Initialise():  PC: 0x8000300
[5.067] Device_Initialise():  ST-LINK detects target voltage = 3.00 V
[5.067] STM32_AppReset():  Enter STM32_AppReset() function
[5.176] STM32_AppReset():  NVIC_DFSR_REG = 0x00000009
[5.177] STM32_AppReset():  NVIC_CFGFSR_REG = 0x00000000
[5.178] STM32_AppReset():  XPSR = 0x01000000
[5.179] Device_Initialise():  ST-LINK device status: HALT_MODE
[5.179] initServerContext():  ST-LINK device initialization OK
[5.180] handleFlashPacket():  Error in STM32CubeProgrammer

rutuja
Posts: 2
Joined: Mon Mar 04, 2019 6:59 am

Re: Failure at line 13

Postby rutuja » Tue Mar 05, 2019 6:41 am

I was not ready to discover any purpose behind the disappointment other than looking in the .log document where it expressed that the debugger couldn't keep in touch with memory at 0x92xxxxx (x's are real qualities that I don't review right now). I have no clue why it was endeavoring to compose there. I erased the whole undertaking and supplanted it by the file and the issue is fixed. Have no clue why it is fixed.

Chettuser
Posts: 6
Joined: Wed Apr 10, 2019 6:10 pm
Location: Moscow

Re: Failure at line 13

Postby Chettuser » Wed Apr 10, 2019 6:26 pm

Hello!
I have a problem:
https://youtu.be/W_CCOHc7rM4
STM32F0308-DISCO (onboard ST-Link have V2.J31.S0 - so wanted Atollic ;) )
Thank You!

PS: I install STM32CubeProgrammer from site st.com. In this program, I can upgrade ST-Link, but I can not make Connect;
Error: No debug probe detected.

Chettuser
Posts: 6
Joined: Wed Apr 10, 2019 6:10 pm
Location: Moscow

Re: Failure at line 13

Postby Chettuser » Sun Apr 21, 2019 12:46 pm

I temporarily solved this problem: Downgrade to version 9.0.1. But I need STM32G0! :?
The problem is somewhere in a bunch of ST-LINK_gdbserver v5 + and Atollic. Gdbserver v4.2.x is work, v5.x.x - don't work.
I hope that the developers fix this problem with the server in v9.4.

alexandr idushy
Posts: 10
Joined: Fri May 03, 2019 4:17 pm

Re: Failure at line 13

Postby alexandr idushy » Fri May 03, 2019 4:31 pm

I reproduced it in work with the L475RC. Resolved this problem with the help of the user manual. I made all as in chapter "USING ST-LINK UTILITY INSIDE ATOLLIC".


Return to “TrueSTUDIO for STM32 discussions”

Who is online

Users browsing this forum: No registered users and 2 guests