STM32MP157D-DK1 board disconnects during flashing service

[Chrozick]

I've been following the STM32MP15 Discovery kits - Starter Package tutorial to set up my STM32MP157D-DK1 board and am having trouble flashing the SD card via the CubeProgrammer CLI. It successfully loads partitions 0x01, 0x03, then the board disconnects and the flash fails. 

Here's screenshots of the CLI output as well as a picture of the board:

Additional info:

• My PC is running Windows 10
• LD6 (red LED between USER1 and USER2 buttons) flashes rapidly after disconnect
• LD8 (blue LED left of micro-USB port) is lit after disconnect

Here's the troubleshooting I've done so far:

• Resetting the board before it times out results in the flash operation restarting from the beginning and failing in the same way
• Using device manager to scan for hardware changes after disconnect does nothing
• USB driver switched to libusbK via Zadig
• Formatted the SD card to wipe previous partitions
• Used different cords and USB ports
• Attempted to flash from other .tsv files (tutorial calls for FlashLayout_sdcard_stm32mp157c-dk2-optee.tsv)

Any help would be greatly appreciated.

[jasonj2]

I had encountered roughly the same problem on my custom board. I don't have a clue for it. After FIP was flashed and target board resetted, the USB device cannot be enumerated by HOST, and STM32CubeProgrammer timed out.

I had searched the community, there are many suggests about the FAQ at https://community.st.com/s/article/FAQ-STM32MP1-STM32CubeProgrammer-USB-reconnect-error-at-STM32MP1-boot-device-flashing, but the page was archived by ST, I have no ideal about how to access the FAQ.

Is there anyone can help about the problem? Or help to access the FAQ?

[PatrickF]

hi @Chrozick ,

this is two  common pitfalls which could make this to happen:

1. Supply is detected as non-compliant with USB Type-C standard. Red led bright and there is message on the board console log (STLINK USB Virtual Com Port).
2. When using Linux over a Virtual Machine, when downloaded uBoot starts, the USB port newly enumerated should be defined to connect automatically to the virtual machine (as usually by default connected to Windows OS).

Could you share the board console log by connecting STLINK connector to a PC and running a terminal emulator on the related Virtual Com Port?

Regards.