Author Topic: eMMC on TE0821  (Read 477 times)

jhane

  • Active Member
  • *
  • Posts: 23
eMMC on TE0821
« on: August 26, 2020, 09:39:38 PM »
Hello,
  I have a TE821 and TE0703 carrier board and I'm trying to access the eMCC on mmc0.
 
 When the system boots, I get this message:
[   10.510153] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   10.544158] mmc0: mmc_select_hs200 failed, error -74
[   10.550680] mmc0: new MMC card at address 0001
[   10.555541] mmcblk0: mmc0:0001 IS008G 7.28 GiB
[   10.560279] mmcblk0boot0: mmc0:0001 IS008G partition 1 4.00 MiB
[   10.566379] mmcblk0boot1: mmc0:0001 IS008G partition 2 4.00 MiB
[   10.572389] mmcblk0rpmb: mmc0:0001 IS008G partition 3 4.00 MiB, chardev (245:0)
[   10.586272] mmc1: new high speed SDHC card at address 5048
[   10.592098] mmcblk1: mmc1:5048 DDINC 14.9 GiB
[   10.597439]  mmcblk1: p1 p2 p3
[   10.651610] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'

 So it seems something is recognized on mmc0.   However, there is supposed to be a 64 GByte emcc on here and this message only shot 7.27.   And there is the mmc_select_hs200 error.
 
 fdisk doesn't seems to have a valid partition table on mmcblk0 and if I try to mkfs on the boot0 partition I get strange permission errors.

 So the one caveat is that I have updated to Xilinx 2020.1 so this is the 5.4 kernel.  I've booted the 2019 reference design and I have same issues.

  Unclear on why the eMMC is the wrong size and why I can't access it.  Any ideas?

thanks,
jeff


jhane

  • Active Member
  • *
  • Posts: 23
Re: eMMC on TE0821
« Reply #1 on: August 27, 2020, 02:49:44 AM »

 OK, I'll answer this myself in case someone sees this

First, I clicked on the wrong part so that is why  I got the size wrong.

To get rid mmc_select_hs200 error you must add the following to the device-tree:

&sdhci0 {
    disable-wp;
    no-1-8-v;
};

When I went to add the no-1-8-v I discover the settings for sdhci1 were already defined as above in system-user.dtsi.  Disabling wp makes it easier to write to the device. 

I haven't used eMMC before and didn't realize these hard partitions already exist
/dev/mmcblk0boot0
/dev/mmcblk0boot1
/dev/mmcblk0rpmb

And you need to add partitions to the user area, so fdisk /dev/mmcblk0.  After that you can mkfs on the partitions, mount and copy files to them.

Now I just need to get u-boot to read the correct device for the image.ub

jeff