I am having an issue when starting a debug session with an STM32 Nucleo board / St-Link. I get an error at line 6 of the debug script, which is the load command. This occurs with 9.1.0 and then I upgraded to 9.3.0 and it is the same.
The debug log shows an error with the stm cube programmer CLI exe, which I know was a new feature from 9.1.0 for programming. It generates an s record file in your application data temp folder and uses this with the CLI tool. I am thinking that this is the part of the process that is failing because I never see the files in that location - perhaps permissions related?
Code: Select all
[1.477] handleFlashPacket(): Writing to C:\Users\marwi1\AppData\Local\Temp\ST-LINK_GDB_server_a14088.srec
[1.501] spawnCubeProgrammer(): ------ Switching to STM32CubeProgrammer -----
[1.501] 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 mode=UR reset=hwRst --download C:\Users\marwi1\AppData\Local\Temp\ST-LINK_GDB_server_a14088.srec --verify --log C:\Users\marwi1\AppData\Local\Temp\STM32CubeProgrammer_a14088.log"
[4.054] file_utils_spawn(): Return code 1
[4.054] spawnCubeProgrammer(): Encountered Error when opening C:\Program Files (x86)\Atollic\TrueSTUDIO for STM32 9.1.0\Servers\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe
[4.054] spawnCubeProgrammer(): 09:16:06:715
[4.054] spawnCubeProgrammer(): 09:16:06:715 Log output file: C:\Users\marwi1\AppData\Local\Temp\STM32CubeProgrammer_a14088.log
[4.054] spawnCubeProgrammer(): 09:16:06:751 Error: No debug probe detected.
When I check the temp file location the ST-LINK_GDB_server_a14088.srec file is never creared and neither is STM32CubeProgrammer_a14088.log.
I have done the usual things like run Atollic as administrator, mark the ST-link GDB server exe as "run as administrator", check folder permissions etc.
I was wondering if this path is hard coded in the the application or if you can specify where the temp file goes - for me it could go in the project sub-folder.
Edit: Just to add to the above, I do see truestudio gdbscript and hwgdbscript temp files appear in the temp data folder on each debug session, so true studio can write here. Perhaps whatever exe is creating the srecord and log files above cannot?
I have noticed other people with a similar issue but no solution yet, any ideas?
Thank you in advance, Mark