[BUG] U-boot does not detect emmc card in odroid-c2 for newer U-boot as 2020.04

[Heinrich Schuchardt]

On 16.11.20 15:16, Otto Meier wrote:
> I tried to build  an actual u-boot from git for my odroid-c2 board.
>
> It doesn't find the emmc card and therefore does not boot from it.
> emmc is Ok and boots with u-boot 2020.04 fine.
>
> Newer u-boot then 2020.04 show these messages:
>
> GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
> TE: 156394
> no sdio debug board detected
>
> BL2 Built : 11:44:26, Nov 25 2015.
> gxb gfb13a3b-c2 - jcao at wonton
>
> Board ID = 8
> set vcck to 1100 mv
> set vddee to 1050 mv
> CPU clk: 1536MHz
> DDR channel setting: DDR0 Rank0+1 same
> DDR0: 2048MB(auto) @ 912MHz(2T)-13
> DataBus test pass!
> AddrBus test pass!
> Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size:
> 0x000000b0
> Load bl30 from eMMC, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
> Sending bl30........................................OK.
> Run bl30...
> Load bl301 from eMMC, src: 0x0001c200, des: 0x01000000, size: 0x000018c0
> Wait bl30...Done
> Sending bl301.......OK.
> Run bl301...
> 31 from eMMC, src: 0x00020200, des: 0x10100000, size: 0x00011130
>
>
> --- UART initialized after reboot ---
> [Reset cause: unknown]
> [Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14
> tao.zeng at droid04]
> bl30: check_permit, count is 1
> bl30: check_permit: ok!
> chipidLoad bl33 from eMMC, src: 0x00034200, des: 0x01000000, size:
> 0x0009e8f0
> : ef be ad de d f0 ad ba ef be ad de not ES chip
> [0.271464 Inits done]
> secure task start!
> high task start!
> low task start!
> NOTICE:  BL3-1: v1.0(debug):4d2e34d
> NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
> INFO:    BL3-1: Initializing runtime services
> INFO:    BL3-1: Preparing for EL3 exit to normal world
> INFO:    BL3-1: Next image address = 0x1000000
> INFO:    BL3-1: Next image spsr = 0x3c9
>
>
> U-Boot 2021.01-rc2 (Nov 15 2020 - 19:06:55 +0100) odroid-c2
>
> Model: Hardkernel ODROID-C2
> SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
> DRAM:  2 GiB
> MMC:   mmc at 72000: 0, mmc at 74000: 1
> In:    serial
> Out:   serial
> Err:   serial
> Net:   eth0: ethernet at c9410000
> Hit any key to stop autoboot:  0
> Card did not respond to voltage select!
> Card did not respond to voltage select!
> MMC Device 2 not found
> no mmc device at slot 2
> starting USB...
> Bus usb at c9100000: USB DWC2
> scanning bus usb at c9100000 for devices... 2 USB Device(s) found
>
>
> Does anybody know how to fixes this breakage?
>
> Best regards
>
> Otto
>

On my Odroid C2 I cannot see the reported error.

The devices are numbered 0 and 1 and these are reported in your boot log.

Where do you select "MMC Device 2"? Do you have a boot.scr which tries
to select the wrong device number?

Please, provide the output of

mmc dev 0; mmc info
mmc dev 1; mmc info

Here is my boot log:

U-Boot 2021.01-rc1-00247-g530e3803ab (Nov 02 2020 - 19:41:17 +0100)
odroid-c2

Model: Hardkernel ODROID-C2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:b (0:1)
DRAM:  2 GiB
MMC:   mmc at 72000: 0, mmc at 74000: 1
In:    serial
Out:   serial
Err:   serial
Net:   eth_designware ethernet at c9410000: Can't get reset: -2
eth0: ethernet at c9410000
Hit any key to stop autoboot:  0
=> mmc info
Device: mmc at 72000
Manufacturer ID: 3
OEM: 5344
Name: ACLCE
Bus Speed: 50000000
Mode: SD High Speed (50MHz)
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 59.5 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
=> mmc dev 1
switch to partitions #0, OK
mmc1(part 0) is current device
=> mmc info
Device: mmc at 74000
Manufacturer ID: d6
OEM: 103
Name: SOD16
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: 4 MiB
User Capacity: 14.6 GiB WRREL
Boot Capacity: 4 MiB ENH
RPMB Capacity: 4 MiB ENH
Boot area 0 is not write protected
Boot area 1 is not write protected
=>

Best regards

Heinrich