2024-01-10 02:30 AM
Hello everyone,
I encountered a problem while debugging my program.
CubeIDE Version 1.14 , CubeProgrammer Version 2.9.0, ST-Link Version V2J43S7
The ST-Link/V2 is found. You can erase the Chip (STM32H753BIT6) but can't download the .elf file (CubeProgrammer).
In the CubeIDE you can't debug but the ST-Link and the STM32-Controller is found.
We tried following steps:
The error:
The debug configurations:
If you have any idea...
2024-01-11 09:38 AM
Hello @MWetter
First let me thank you for posting.
Could you try downloading the elf file with STM32CubeProgrammer as standalone application.
Also could you try to change the GDB server port number (increase it by 4 at least)
KR,
Semer.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2024-01-15 10:48 PM - edited 2024-01-15 10:50 PM
I tried downloading the elf file with the STM32CubeProgrammer.
It did not work.
Also changing the server port did not work.
Have you any idea why?
Thank you very much
2024-01-16 12:41 AM
Hello @MWetter
Since the issue is still existing using CubeProgrammer, I believe it's either the programmer tool is failing or some HW issue with the board.
I will redirect you to the STM32CubeProgrammer forum and send the question to the responsible team.
KR,
Semer.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2024-01-17 01:57 AM
Hello @MWetter ,
I find it weird that you have CubeIDE Version 1.14 with CubeProgrammer Version 2.9.0. Normally you would have CubeProgrammer 2.15.
In any case could you please try downloading an ELF file with STM32CubeProgrammer v2.15 (standalone) on your pc and send us the verbosity 3 log.
Since you've managed to download binaries on your custom hardware using another pc, I highly doubt it's a hardware issue.
Thanks,
Aziz
2024-01-18 02:30 AM
2024-01-18 08:16 AM
Hello @MWetter,
From the logs you sent, your .ELF file contains an external memory segment. The initialization of the external loader fails (and by consequence the external flash erase will fail). Are you using an external memory on your custom Hardware ? If not, the fail is expected, if yes, could you specify it's reference and attach your external loader ?
Thanks,
Aziz
2024-01-18 09:58 AM
Supposedly ST's own MX25LM51245G_STM32H7B3I-DISCO-SFIx.stldr
Most assuredly NOT going to work with an H753, which I'm pretty sure doesn't support OCTOSPI, and has a completely different die and pin muxing.