STM32CubeProgrammer - can't open file and program MCU after removing folder

[Bogdan Golab]

Posted on April 09, 2018 at 19:40

Summary:

Once you remove a folder you used lately the STM32CubeProgrammer cannot open a file and consequently program the MCU.

How to reproduce:

1. Select 'Erasing & Programming' window, open a file (either hex or bin) and program the MCU (I tested RAM programming through UART but ST-Link mode seems to be also affected)

The file 'testCode.bin' was located here:

C:\Users\abg015\Desktop\serilal-proto\test-code\

2. Remove/Rename (this is crucial) the folder where the file is located, e.g.

rename the folder:

C:\Users\abg015\Desktop\serilal-proto\test-code\

to:

C:\Users\abg015\Desktop\serilal-proto\test-code2\

3. Since then you cannot navigate to any folder using 'Browse' button, The 'Browser' button do es NOT react to mouse clicking. So you cannot open any file, neither program the MCU since then.

4. Once you restore the folder (previously removed/renamed) you can open any new file.

[Bogdan Golab]

Posted on April 09, 2018 at 19:47

Leaving the STM32CubeProgrammer and starting it again does NOT fix the issue. You need to restore the removed/renamed folder.

Some details about the PC:

- 64 bit, Windows 8.1

[Juraj Dudak]

Posted on April 12, 2018 at 11:15

This is beginer programmer error.

You can fix this by deleting config.properties file.

In Ubuntu, file is located at: /home/<USER>/.STM32CubeProgrammer

[AvaTar]

Posted on April 12, 2018 at 11:28

This is beginer programmer error.

Exactly.

Another version I know of is a path string in the config file that exceeds the internal file name buffer length.

I know applications that crash on those ...

[Bogdan Golab]

Posted on April 12, 2018 at 12:12

I can cope with this myself. I reported the behavior in case the ST would like to improve things.

[AvaTar]

Posted on April 12, 2018 at 12:18

But it speaks volumes about the level of ST's internal testing ...

[Bogdan Golab]

Posted on April 12, 2018 at 12:26

The buffer overflow violates basic app security requirements.

I believe the ST has the security compliance review (and testing) process process implemented although in case the problem is rather related to (more advanced) functional testing.

Anyway, it's not critical issue but might be surprising to someone who uses temporary folder structure.

[Imen.D]

Posted on April 13, 2018 at 10:45

Hello,

Your comments are shared internally for further review.

We will keep you informed about the taken actions or explanation if needed.

Best Regards,

Imen

[Pavel A.]

Posted on April 13, 2018 at 14:10

Here, here, guys. Who writeth code without bugs, throweth the first stone

- pa

[AvaTar]

Posted on April 13, 2018 at 19:14

My company use to make software for SIL 2 / SIL 3 devices.

And I spent 90 per cent of the time with testing and documentation.

Ask ST how they test their 'giftware'.