Skip to main content
P
Pratik Manvar
Visitor II
February 18, 2022
Solved

Not able to access eMMC from u-boot on STM32MP157C device

  • February 18, 2022
  • 2 replies
  • 1768 views

Hi STM-Team,

We have the custom board based on the STM32MP157C-Eval board.

In that, we are not able to access the eMMC from u-boot command prompt. Currently, we are booting from SD card and able to access it from u-boot command prompt.

We are able to see the 2 mmc devices but not able to access eMMC on dev-1. Please see below logs:

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

STM32MP> mmc list

STM32 SD/MMC: 1

STM32 SD/MMC: 0 (SD)

STM32MP> mmc dev 0

switch to partitions #0, OK

mmc0 is current device

STM32MP> mmc dev 1

<No output from this command>

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

But, with same configurations, we are able to access and create partitions of eMMC through fdisk command from filesystem command prompt. Also, see the below kernel boot-up logs:

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

[  3.976158] mmc1: new DDR MMC card at address 0001

[  3.989649] mmcblk1: mmc1:0001 IB2916 14.6 GiB

[  3.994868] mmcblk1boot0: mmc1:0001 IB2916 partition 1 4.00 MiB

[  4.000048] mmcblk1boot1: mmc1:0001 IB2916 partition 2 4.00 MiB

[  4.016430] mmcblk1rpmb: mmc2:0001 IB2916 partition 3 4.00 MiB, chardev (243:0)

[  4.030124] mmcblk1: p1

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

Please help us out why we are not able to access the eMMC from u-boot.

Thanks & Regards,

Pratik Manvar

    This topic has been closed for replies.
    Best answer by Pratik Manvar

    Hi Olivier,

    Sorry for the late response on this thread.

    Yes, we were able solve this issue. Actually, one GPIO pin (eMMC clock pin) has been utilized by something else for custom things in bootloader. Once, we changed that pin as per new designed schematics, the eMMC get initialized without any issue in bootloader.

    Thanks for your help.

    Regards,

    Pratik Manvar

    2 replies

    O
    OlivierK
    Technical Moderator
    March 8, 2022

    Hi Pratik Manvar (Community Member)

    Maybe your are already sorted out?

    just in case did you follow this?

    https://wiki.st.com/stm32mpu/wiki/U-Boot_overview#Generic_Distro_configuration

    you should have:

    STM32MP> mmc dev 0

    switch to partitions #0, OK

    mmc0 is current device

    STM32MP> mmc dev 1

    switch to partitions #0, OK

    mmc1(part 0) is current device

    [  3.467118] mmc0: new ultra high speed DDR50 SDHC card at address aaaa

    [  3.473494] mmcblk0: mmc0:aaaa SC16G 14.8 GiB 

    [  3.514541] mmcblk0: p1 p2 p3 p4 p5 p6 p7

    [  3.541167] mmc1: new DDR MMC card at address 0001

    [  3.545904] mmcblk1: mmc1:0001 004GA0 3.69 GiB 

    [  3.549734] mmcblk1boot0: mmc1:0001 004GA0 partition 1 2.00 MiB

    [  3.555800] mmcblk1boot1: mmc1:0001 004GA0 partition 2 2.00 MiB

    [  3.561266] mmcblk1rpmb: mmc1:0001 004GA0 partition 3 512 KiB, chardev (243:0)

    [  3.578150] mmcblk1: p1 p2 p3 p4 p5 p6

    Rgds,

    Olivier

    P
    Pratik ManvarAuthorAnswer
    Visitor II
    March 24, 2022

    Hi Olivier,

    Sorry for the late response on this thread.

    Yes, we were able solve this issue. Actually, one GPIO pin (eMMC clock pin) has been utilized by something else for custom things in bootloader. Once, we changed that pin as per new designed schematics, the eMMC get initialized without any issue in bootloader.

    Thanks for your help.

    Regards,

    Pratik Manvar

    O
    OlivierK
    Technical Moderator
    March 24, 2022

    Hi Pratik;

    Thanks for your feedback. Glad that you're sorted out.

    Regards,

    Olivier

    Terms & ConditionsAccessibility statement