cancel
Showing results for 
Search instead for 
Did you mean: 

STM32MP157 unable to boot from SD

shobole
Associate

As part of our project, we are using an STM32MP157DAC custom board that has the same design with the STM32MP157D-DK1 development board except for a few changes (schematics of the design is attached)

The board generally works when trying to upload and debug code to the M4 core using JTAG-SWI connection.

However the board does not work when trying to boot from SD card. The steps in the wiki to populate the linux image to an SD card were used. The Cube Programmer software does not recognise the board.
I tried using command line by typing ifconfig (or lsusb), but the connection cannot be recognised.
To avoid the Cube Programmer, flashing the linux kernel U-Boot was also tested but no result obtained (The board still does not boot from the SD card).

Both booting processes (using cube programmer and u-boot) were tested with an STM32MP157F-EV1 with no problems.

 

Attached is our board's schematics (taken majorly from the reference board (STM32MP157D-DK1). Connection to the board for booting is provided through a typeC USB (OTG)

I have searched the internet but couldn't find a solution so far. Would appreciate any help

2 REPLIES 2
Olivier GALLIEN
ST Employee

Hi @shobole 

 

Can you share trace log from CubeProg and UART trace during CubeProg operation ? 

Thanks 

Olivier 

Olivier GALLIEN
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
shobole
Associate

Good day and thanks for your response


Below are the logs of the programmer:

  15:04:07 : STM32CubeProgrammer API v2.17.0 | Linux-64Bits
  15:04:32 : UR connection mode is defined with the HWrst reset mode
  15:04:32 : Error: Establishing connection with device failed



The last log is what I get when trying to upload. It makes sense since the board is not detectable.
Just to note, the st-link is properly functioning and we can code and debug the M4 core.

Since the booting is not done through UART, I haven't included the logs of it.