cancel
Showing results for 
Search instead for 
Did you mean: 

Upgraded from 2.4 to 2.7, now get "tf-a-stm32mp157c-dk2-serialboot.stm32 missing"

JSpra
Associate III

Hi,

I just upgraded my STM32CubeProgrammer to 2.7 and now getting error that can't find tf-a-stm32mp157c-dk2-serialboot.stm32.

I tried this on three other images that have worked in past, get same error.

tf-a-stm32mp157c-dk2-serialboot.stm32 is not found on file system for any of these images.

Specifics:

target: stm32mp157c-dk2

host: Windows 10

Images built on WSL.

Unfortunately I deleted 2.4 before installing 2.7, also tried 2.6, 2.5 and get same problem.

Have any suggestions ?

1 ACCEPTED SOLUTION

Accepted Solutions
JSpra
Associate III

Well….. I think I sorted it out. It looks like STM32CubeProgrammer does not support symbolic links in WSL. This is something I knew of a couple years back and had script to run after build to remove symbolic links. This script got deleted and I totally forgot about why I needed it.

View solution in original post

3 REPLIES 3
JSpra
Associate III

Following instructions here, https://wiki.st.com/stm32mpu/wiki/STM32CubeProgrammer#Preparing_the_USB_serial_link_for_flashing

I'm not seeing a response when running Bootloader.bat when running it in Admin PowerShell. Just see quick flash of application window.

Also, don't see DFU in device manager list.

Could this be contributing to the issue?

JSpra
Associate III

Update:

I do see the USB device show up in Universal Serial Bus Device as DFU in HS Mode @ Device ID /0x500, .....

So it's finding the USB device.

Documentation may be out of date, does not show this correctly.

JSpra
Associate III

Well….. I think I sorted it out. It looks like STM32CubeProgrammer does not support symbolic links in WSL. This is something I knew of a couple years back and had script to run after build to remove symbolic links. This script got deleted and I totally forgot about why I needed it.