cube programmer sd card image download- STM32MP1

[Ara.1]

These are log i got during download, any clue

STM32_Programmer_CLI -c port=usb1 -tm 20000 -w flashlayout_mp1som-image/FlashLayout_sdcard_mp1som-mystm32mp1-basic.tsv

    -------------------------------------------------------------------

                       STM32CubeProgrammer v2.5.0                 

     -------------------------------------------------------------------

USB speed  : High Speed (480MBit/s)

Manuf. ID  : STMicroelectronics

Product ID : DFU in HS Mode @Device ID /0x500, @Revision ID /0x0000

SN         : 001F00213438510838333630

FW version : 0x0110

Device ID  : 0x0500

Device name : STM32MP1

Device type : MPU

Device CPU : Cortex-A7

Start Embedded Flashing service

Memory Programming ...

Opening and parsing file: tf-a-mp1som-pxl7-trusted.stm32

 File         : tf-a-mp1som-pxl7-trusted.stm32

 Size         : 245364 Bytes

 Partition ID : 0x01

Download in Progress:

[==================================================] 100%

File download complete

Time elapsed during download operation: 00:00:00.465

RUNNING Program ...

 PartID:     :0x01

Start operation done successfully at partition 0x01

Flashlayout Programming ...

[==================================================] 100%

Running Flashlayout Partition ...

Flashlayout partition started successfully

Memory Programming ...

Opening and parsing file: u-boot-mp1som-pxl7-trusted.stm32

 File         : u-boot-mp1som-pxl7-trusted.stm32

 Size         : 790180 Bytes

 Partition ID : 0x03

Download in Progress:

[==================================================] 100%

File download complete

Time elapsed during download operation: 00:00:00.666

RUNNING Program ...

 PartID:     :0x03

reconnecting the device ...

Error:

Unable to reconnect the target device: time out expired

Error: Start operation failed at partition 0x03

Error: TSV flashing service failed

This is a coustom build open-st image

On Ubuntu terminal i see following log:

-------------------------build-mp1som/tmp-glibc/deploy/images/mp1som$ dmesg | tail

[30232.038713] usb 1-5: device descriptor read/64, error -71

[30232.274455] usb 1-5: new high-speed USB device number 100 using xhci_hcd

[30232.423922] usb 1-5: New USB device found, idVendor=0483, idProduct=df11

[30232.423933] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[30232.423940] usb 1-5: Product: DFU in HS Mode @Device ID /0x500, @Revision ID /0x0000

[30232.423945] usb 1-5: Manufacturer: STMicroelectronics

[30232.423951] usb 1-5: SerialNumber: 001F00213438510838333630

[30246.952313] usb 1-5: USB disconnect, device number 100

[30248.890048] usb 1-5: new high-speed USB device number 101 using xhci_hcd

[30254.177938] usb 1-5: device descriptor read/64, error -110

--------------~build-mp1som/tmp-glibc/deploy/images/mp1som$ dmesg | tail

[30290.893477] usb usb1-port5: attempt power cycle

[30291.545421] usb 1-5: new high-speed USB device number 103 using xhci_hcd

[30296.801391] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

[30302.177296] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

[30302.385249] usb 1-5: device not accepting address 103, error -62

[30302.513257] usb 1-5: new high-speed USB device number 104 using xhci_hcd

[30307.557111] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

[30312.929409] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

[30313.137046] usb 1-5: device not accepting address 104, error -62

[30313.137099] usb usb1-port5: unable to enumerate USB device

if i connect a fresh sd card 16 GB and create a bootable image using DD, Board boots successfully.

[Eldam]

Hello Ara.1,

We also face this issue when using ST-DK2 (discovery kit). We don't know what the real cause, but we have this problem on a inux laptop and this issue doesnt appear on another linux pc.

First, i suggest you to try to update (=try to use STM32_Programmer_CLI with) the DK2 starter kit on a dk2 board (you have one isnt it?)

If its ok, do the same with your board.

If not , try another PC, usb cable, usb power and all related "connection" things

good luck

[Ara.1]

whats the ubuntu version you used , where it was working ???

[PatrickF]

May I suggest to read those FAQ:

https://community.st.com/s/article/FAQ-STM32MP1-STM32CubeProgrammer-USB-reconnect-error-at-STM32MP1-boot-device-flashing

https://community.st.com/s/article/FAQ-STM32MP1-How-to-create-a-device-tree-with-STM32CubeMx-for-your-design

https://community.st.com/s/article/FAQ-STM32MP1-Bring-up-procedure

also one common pitfall when building your own board is around HSE settings. The BootROM has automatic HSE detection (oscillator or crystal) whereas this setting is fixed in device tree (thus making uBoot stopping to work as it could killing its clock). Our board are using digital bypass with external oscillator (and so our default DT).

please have a look to https://wiki.st.com/stm32mpu/wiki/Clock_device_tree_configuration_-_Bootloader_specific#DT_configuration_for_HSE

[Eldam]

ubuntu 16.04

do you have the same issue with restoring DK2 stater kit?

do you work on custom board?

[Ara.1]

No, i do not have DK2 stater kit

Yes, work on custom board

even i am working on Ubuntu same version

I tried in windows-64 bit too

stm_cube_downloadlog.log is attached failure log

[Eldam]

Ah Custom board, ok, i'm sorry, ive no hint anymore, there is too much possibility of mistake.

wish you good luck!

[Hgs.1]

In the meantime I have noticed that even more garbage is created if I leave the "/ CS" signal in the new site "Low" state for the entire time a command is processed (sending and receiving)!