STM32F756VG can't be programmed with TS 9.2.0

Discussions concerning TrueSTUDIO for STM32 9.0.0 and later versions.

Moderators: Markus Girdland, Mattias Norlander

kurta999
Posts: 17
Joined: Thu Sep 06, 2018 8:27 am
Location: Slovakia
Contact:

STM32F756VG can't be programmed with TS 9.2.0

Postby kurta999 » Wed Jan 09, 2019 3:00 pm

I'm using ST-Link V3 and it cannot program this MCU. This bug exists since I started using ST-Link V3. With a nucleo board with ST-Link V2 I can program it without any problem.

Anyway ARM chip in this MCU is bugged, stepping tough code doesn't work. I hope this help identifing the problem. (we will throw out this MCU from every product, but currently we can't do that)
https://community.st.com/s/question/0D5 ... interrupts

Debugger response is the following:

Code: Select all

No symbol table is loaded.  Use the "file" command.
No symbol table is loaded.  Use the "file" command.
No symbol table is loaded.  Use the "file" command.
No symbol table is loaded.  Use the "file" command.
warning: Remote failure reply: E31
C:\Users\ATTILA~1.EFF\AppData\Local\Temp\truestudio5586337529767740930gdbscript:14: Error in sourced command file:
Remote communication error.  Target disconnected.: No error.


This is a bug, please report it.  For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

/home/build/gcc-arm-none-eabi-6-2017-q1-update/src/gdb/gdb/thread.c:817: internal-error: is_thread_state: Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
/home/build/gcc-arm-none-eabi-6-2017-q1-update/src/gdb/gdb/thread.c:817: internal-error: is_thread_state: Assertion `tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]

kurta999
Posts: 17
Joined: Thu Sep 06, 2018 8:27 am
Location: Slovakia
Contact:

Re: STM32F756VG can't be programmed with TS 9.2.0

Postby kurta999 » Thu Feb 28, 2019 1:38 pm

Similar issue present with STM32L443 and STM32F446. In our company nobody were able to debug these chips. After some days we realized that they can be debugged without any problem with TrueStudio 9.0.1 where the old ST-Link server was used. But afterwards the switch was done for CubeProgrammer, they cannot be debugged. Interesting part anyway that CubeMX programmer can connect to STM32L443, can be programmed, but cannot be debugged. For STM32F446 connection doesn't work.

Please try to fix it as quick as possible, because this is a MAJOR bug. I would not like to leave Atollic, but nowadays what happens here and on ST's side, its unbelivable. Now we need to revert back to 9.0.1 to be able to work with these chips.


In console:

[New Thread 1]
Reply contains invalid hex digit 108
You do not have the required permissions to view the files attached to this post.


Return to “TrueSTUDIO for STM32 discussions”

Who is online

Users browsing this forum: No registered users and 2 guests