Failure at line 13

Discussions concerning TrueSTUDIO for STM32 9.0.0 and later versions.

Moderators: Markus Girdland, Mattias Norlander

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

Re: Failure at line 13

Postby Chettuser » Tue May 07, 2019 9:43 am

I also repeated how it was done in the manual, but I also get an error:

Code: Select all

Hardware watchpoint supported by the target
SWD frequency = 4000 kHz
ST-LINK Firmware version : V2J33S25
Device ID: 0x460
PC: 0x1fff2b44
ST-LINK device status: HALT_MODE
ST-LINK detects target voltage = 3.22 V
ST-LINK device status: HALT_MODE
ST-LINK device initialization OK
Waiting for debugger connection...
Waiting for connection on port 61234...
Accepted connection on port 61234...
Debugger connected
TraceCaptureStart and SWV event set to APP_TRUE
ST-LINK device status: RUN_MODE
Received Ctrl-C from the client
TraceCaptureStart and SWV event set to APP_FALSE (1)
Device not halted(0), performing Ctrl-C
Device halted

After pressing PAUSE:

Code: Select all

Program received signal SIGINT, Interrupt.
0x1fff2122 in ?? ()

The address changes every time:
No source available for "0x1fff2136"

:?:

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

Re: Failure at line 13

Postby alexandr idushy » Tue May 07, 2019 10:26 am

it is other story. i dot`t know how this resolve.

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

Re: Failure at line 13

Postby alexandr idushy » Sat May 11, 2019 8:21 am

try the simple project to make sure, the problem is with debugging.

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

Re: Failure at line 13

Postby Chettuser » Fri May 17, 2019 6:13 pm

I tried to install IDE on someone else's computer. And ... Everything works there! I do not know the reason. :oops:
I do not want to reinstall the system.

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

Re: Failure at line 13

Postby alexandr idushy » Fri May 17, 2019 6:29 pm

all may be in this great and terrifying worldd ;)

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

Re: Failure at line 13

Postby alexandr idushy » Fri May 17, 2019 6:35 pm

try reinstall atollic.
try install near atollic other version.
reinstall drivers.
win update.
... and
reinstall Win, sorry

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

Re: Failure at line 13

Postby Chettuser » Sat May 25, 2019 4:52 pm

It seems I managed to fix the problem!
I reinstalled the USB drivers. I do not understand how this could affect, but it works!

obviously, Windows was created by aliens!
:lol:

PS: Chipset driver too.
Last edited by Chettuser on Tue May 28, 2019 6:59 pm, edited 2 times in total.

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

Re: Failure at line 13

Postby alexandr idushy » Sat May 25, 2019 4:58 pm

only Garry Potter have this known

jensenXnewman
Posts: 1
Joined: Tue Jun 11, 2019 7:58 pm

Re: Failure at line 13

Postby jensenXnewman » Tue Jun 11, 2019 8:04 pm

I started getting this error (except at line 6) after trying to enable the SMPS on an STMWB55 and it seems to be device specific. If I change boards I don't get the error; it only occurs on the board I tried to enable the SMPS on (I removed the code I thought would enable the SMPS). Also, if I try to erase the device using STM32 ST-Link utility, I get the error "some flash pages are read protected"

MeeVal
Posts: 1
Joined: Tue Aug 13, 2019 8:31 am

Re: Failure at line 13

Postby MeeVal » Tue Aug 13, 2019 8:37 am

I had same problem. It was caused by enabled protection on the chip. I used ST-link utility to disable protection and erase chip. now it works :-)


Return to “TrueSTUDIO for STM32 discussions”

Who is online

Users browsing this forum: No registered users and 1 guest