How to load the emmc?

General Discussion
#1

Just got the play board today, and it seems uboot only supports emmc.

  • with sd card inserted (I tried two) *
=> mmc rescan
=> mmc info
Device: mmc@fa10000
Manufacturer ID: 70
OEM: 100
Name: TB291
Bus Speed: 52000000
Mode: MMC High Speed (52MHz)
Rd Block Len: 512
MMC version 5.1
High Capacity: Yes
Capacity: 14.6 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 14.6 GiB
Boot Capacity: 4 MiB ENH
RPMB Capacity: 4 MiB ENH
Boot area 0 is not write protected
Boot area 1 is not write protected

In Linux the sdcard is present.

debian@BeaglePlay:~$ ls /dev/ | grep mmc
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0rpmb
**mmcblk1**
**mmcblk1p1**
**mmcblk1p2**

Is there a dfu mode that can be used to load images into the emmc?

Thanks!

#2

so emmc is first, booting from microSD, you need to hold the boot button…

which model of microSD?

i forget the mmc command line commands, in u-boot, switch to microSD via: mmc dev x

mmc dev 0 (or 1 ?)
mmc info

Regards,

#3

There are provided microSD “flasher” images that will overwrite the eMMC. So, our normal mode is flashing a microSD, then flashing the eMMC by booting that microSD.

Did you do mmc list from within u-boot?

I’m pretty sure we compiled in the DFU support, but I’ll probably not be able to check for you until after Embedded World. Hopefully you can just try it, but that can definitely go on the list to document.

1 Like
#4

our shipping u-boot branch is up: Commits · v2021.01-ti-BeaglePlay-Release · BeagleBoard.org / u-boot · GitLab

dfu is loaded… configs/am62x_evm_a53_defconfig · v2021.01-ti-BeaglePlay-Release · BeagleBoard.org / u-boot · GitLab

sorry i don’t use it…

Regards,

1 Like
#5

I’ll see you in Germany then!

#6

Ah ok, this was my mistake.

For some reason I thought:

mmc info

Show show all the mmc devices, but actually only shows the current device.

=> mmc list
mmc@fa10000: 0 (eMMC)
mmc@fa00000: 1 (SD)
mmc@fa20000: 2
=> mmc dev 1
switch to partitions #0, OK
mmc1 is current device

I am now dangerous, thanks for the suggestion!