Timeout error occured while waiting for acknowledgement

[k_ec]

i am trying flash in SD card for STM32MP157F-DK2. I am getting the error as mentioned below

Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1.0, flow-control = off
16:56:09 : Activating device: OK
16:56:09 : Board : --
16:56:09 : Chip ID: 0x500
16:56:09 : BootLoader protocol version: 4.0
16:56:11 : Start Embedded Flashing service
16:56:12 : Memory Programming ...
16:56:12 : Opening and parsing file: tf-a-stm32mp157f-dk2-usb.stm32
16:56:12 : File : tf-a-stm32mp157f-dk2-usb.stm32
16:56:12 : Size : 220.82 KB
16:56:12 : Partition ID : 0x01
16:56:12 : Download in Progress:
16:56:38 : File download complete
16:56:38 : Time elapsed during download operation: 00:00:26.388
16:56:38 : RUNNING Program ...
16:56:38 : PartID: :0x01

Start operation done successfully at partition 0x01
16:57:09 : Timeout error occured while waiting for acknowledgement.
16:57:40 : Timeout error occured while waiting for acknowledgement.
16:58:11 : Timeout error occured while waiting for acknowledgement.
16:58:42 : Timeout error occured while waiting for acknowledgement.
16:59:13 : Timeout error occured while waiting for acknowledgement.
16:59:13 : Error: GetPhase command not acknowledged after several retries!
16:59:13 : Error: Parition 0xBB not found in TSV File
16:59:13 : Error: TSV flashing service failed
16:59:14 : Disconnected from device.

what would be issue it is not moving further.. 

[PatrickF]

Hi,

please confirm you are using the latest CubeProgrammer and latest Starter Package https://www.st.com/en/embedded-software/stm32mp1starter.html

Today latest ecosystem is v5.1.0. the 6.0.0 is expected to be available very soon.

Maybe check the board UART console output (using board STLINK USB connector which provide a VCP) if any hurdle (e.g. USB Type-C non compliant power supply).

Regards.

[smanger]

I'm having the same problem using the 6.0.0 version.

any suggestions??

[PatrickF]

Hi @smanger @k_ec 

just realized that you are trying to flashload with UART. Is it intended ?

We strongly recommend to use USB (Linux image is too big for UART).

Note: UART could be used to load up to uboot for early debugging in case USB is not yet working during custom board bring up. In that case, you should use the "tf-a-stm32mp135f-dk-optee-programmer-uart.stm32" in your TSV file.

Regards.

[smanger]

I was able to get this working using the DFU. I'm using a Linux VM and was uncertain how to hook up the USB C-A cable and did I need an actual USB device.

The USB cable I used did not have the data lines. That threw me off. But once I changed cables:

• Windows recognized the DFU device.
• The CubeProgrammer on Windows could see the device.
• I was able to hand off the device to my Linux VM
• The Linux VM could see the DFU device
• I successfully programmed the Starter-Package image to the A7.

[PatrickF]

Hi,

Nice to see you solved your issue. Welcome to the STM32MP family !

Those Type-A <-> Type-C USB cables are a pretty common source of headache as the one provided with Phones or USB gadgets are often provided with charging lines only (which then are not allowed to display the USB logo).

Regards.