[BUG : STM32CubeProgrammer 2.6.0] Space in "Program Files" makes external loader loading failing

[SimonF]

Hello,

I cannot use correctly TouchGFX Designer. When I use "run Target", when arriving at the step of stmCubeProgrammer, I have this issue :

...
-------------------------------------------------------------------
 STM32CubeProgrammer v2.6.0 
 -------------------------------------------------------------------
 
 Error: External loader c:\program cannot be loaded.
 Error: External loader files\stmicroelectronics\stm32cube\stm32cubeprogrammer\bin\externalloader\n25q128a_stm32469i-disco.stldr cannot be loaded.
 ST-LINK SN : 066EFF3530384E5043221930
 ST-LINK FW : V2J36M26
 Board : 32F469IDISCOVERY
 Voltage : 3.24V
 SWD freq : 4000 KHz
 Connect mode: Normal
 Reset mode : Software reset
 Device ID : 0x434
 Revision ID : Rev A
 Device name : STM32F469xx/F467xx
 Flash size : 2 MBytes
 Device type : MCU
 Device CPU : Cortex-M4
....

As you can see the path for the external loader path is splited in 2 parts because of the space in "Program Files". It seems that I am the only one with this issue ? I did not have this issue with the previous release of TouchGFX.

[Martin KJELDSEN]

Hi, i'll investigate if this is an issue with CubeProgrammer 2.6.0. That seems to be an internal error message.

/Martin

[Uwe Bonnes]

<sarcasme> Spaces and backslashes in filennames are such a great achievment</sarcasme>

[SimonF]

@Martin KJELDSEN​ , I updated CubeProgrammer because I thought it was the issue. Thus, I had the same problem with previous release of CubeProgrammer.

I also reinstalled TouchGFX to the default folder just in case ^^

[Martin KJELDSEN]

Oh, okay! That's really strange. There must be an internal refernce in cubeprogrammer to the loader files (stldr) but it fails because its inside program files. That's never been a problem here. I have 32-bit and 64-bit versions installed in both program files and program files (x86)

[SimonF]

Do you mean that I am the "only" one having this issue ?

Can I test something to resolve this issue then ? Reinstall something with a previous release, or something else ?

Thank you.

[Martin KJELDSEN]

​It's not something I've heard about before, no, hmm. I'm not an expert on CubeProgrammer to be honest.

I've added the CubeProgrammer topic to the post. Let's see if we can get some answers.

/Martin

[Martin KJELDSEN]

I added this post to the STM32CubeProgrammer community as well

[SimonF]

For the people more aware of STM32CubeProgrammer side. When using with the GUI (ie not with TouchGFX), I have no problem to add the external loader (by checking the right light under the "External loaders" menu) when connecting to the board. And thus, I can flash successfully the binary created by TouchGFX and I have the correct interface I have designed.

[SimonF]

Hello @Martin KJELDSEN​ ,

I used the STM32CubeProgrammer CLI to test if it is TouchGFX related. And it is not. I have the same problem. Strangly, as I said, I don't seem to have the problem when using the CubeProgrammer GUI.

Should I create a new topic because it has nothing to do with TouchGFX ?

[SimonF]

I confirm it works perfectly with STM32CubeProgrammer 2.5.0

[Martin KJELDSEN]

So you're saying it works fine with the GUI, but not with the CLI? I think that since you added the topic CubeProgrammer to this post, it should be fine. Maybe we'll get some attention from people. I'll try to do some tests here, because i've never seen it before.

 

/Martin

[SimonF]

Yes, I confirm that with STM32CubeProgrammer GUI in 2.6.0, I select the external Loader, I connect with the st-link to the board. I select the target.hex file and I download it in the MCU. The UI is then working correctly.

It doesn't not work if I use TouchGFX to flash : the display is completly "bugged". I mean : I download the Clock example and I see the form of the second and minute hands but it is wrong color and noisy.

[Houda GHABRI]

Hi @SimonF​ ,

I confirm , this is a known limitation with the space in the paths.

To resolve this problem, you can modify your command to directly call the external loader file, so you use externalloader\n25q128a_stm32469i-disco.stldr instead of the full path.

I hope this will help you.

Houda

[SimonF]

Hello @Houda GHABRI​ ,

To avoid this problem, I went back to STM32CubeProgrammer 2.5.0 ! Isn't it strange that when updating from 2.5 to 2.6, there is a new limitation about spaces ? ^^'

Thank you for posting a workaround for people that really need the 2.6.0 version.

[MLec]

Hi. I confirm same behavior on my side.

Also worked worked with STM32CubeProgrammer 2.5.0.