2025-10-09 5:30 AM
Hi,
I am trying to flash our software to our STM32MP13xx MPU. I am able to connect to the device using the STM32 Programmer CLI. The first file in the .tsv file list is downloaded succesfully to the device, but then I run into the following errors:
"
-------------------------------------------------------------------
STM32CubeProgrammer v2.19.0
-------------------------------------------------------------------
USB speed : Full Speed (12MBit/s)
Manuf. ID : STMicroelectronics
Product ID : DFU in FS Mode @Device ID /0x501, @Revision ID /0x1003
SN : 0015001E3033510430393732
DFU protocol: 1.1
Board : --
Device ID : 0x0501
Device name : STM32MP13xx
Device type : MPU
Revision ID : --
Device CPU : Cortex-A7
Start Embedded Flashing service
Opening and parsing file: tf-a-intuedrive-stm32mp135x-512m-usb.stm32
Memory Programming ...
File : tf-a-intuedrive-stm32mp135x-512m-usb.stm32
Size : 74.74 KB
Partition ID : 0x01
Download in Progress:
██████████████████████████████████████████████████ 100%
File download complete
Time elapsed during download operation: 00:00:01.512
RUNNING Program ...
PartID: :0x01
Reconnecting the device ...
Error: Unable to reconnect the target device: time out expired
Error: Start operation failed at partition 0x01
Error: TSV flashing service failed"
This failure to reconnect has been described online as a known issue and people often link to a page included in the STM32 MPUs Community FAQ (link: https://wiki.stmicroelectronics.cn/stm32mpu/wiki/STM32_MPUs_Community_FAQ)
The page in question is "FAQ : STM32MP1 STM32CubeProgrammer USB reconnect error at STM32MP1 boot device flashing"
If I try to access this page, it says that the page is archived
I would like to access the information on that page, could anyone retrieve it for me?
On the other hand, If anyone has information on how to reconnect successfully, please let me know.
Kind regards,
Robin
2025-10-09 6:45 AM
Hello
This page is actually not any more up to date and should be removed from the wiki.
For your issue it reveals that you TF-A had an issue to start and so CubeProgrammer went into time-out. If you open a console on the Debug console you should see the TF-A logs with panics or no logs even when TF-A is miss configured versus your PCB (like UART for console in TFA is different from the one on your PCB, or I2C instance for STPMIC in TFA is different on PCB) .
Kind Regards,
Emmanuel Combette