failing first boot when using sd -> eMMC adapter

[BlueFlame]

Hi All,

I bought a nice SD to eMMC adapter with a 32GB eMMC module for the orange PI PC.

Unfortunately it does not go through first boot.

Formatting goes okay, flashing goes okay, booting does not.

With Armbian_20.08.1_Orangepipc_focal_current_5.8.5.img.xz image there is no more terminal output after "Uncompressing Linux... done, booting the kernel.".

With the Armbian_20.05.4_Orangepipc_focal_current_5.4.45.img.xz image I had laying around (and have successfully used on this OpiPC on a normal SD card before), this is the terminal output:

 

U-Boot SPL 2020.04-armbian (Jun 15 2020 - 06:08:51 +0200)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2020.04-armbian (Jun 15 2020 - 06:08:51 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
Net:   phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... 1 USB Device(s) found
scanning bus usb@1c1d400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3789 bytes read in 1 ms (3.6 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
152 bytes read in 1 ms (148.4 KiB/s)
11634345 bytes read in 551 ms (20.1 MiB/s)
7163872 bytes read in 341 ms (20 MiB/s)
Found mainline kernel configuration
29475 bytes read in 4 ms (7 MiB/s)
4185 bytes read in 4 ms (1021.5 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11634281 Bytes = 11.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 494e7000, end 49fff669 ... OK
   Loading Device Tree to 49477000, end 494e6fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    5.496839] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[    5.503254] sunxi-mmc 1c0f000.mmc: send stop command failed
[    5.509577] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[    5.515900] sunxi-mmc 1c0f000.mmc: send stop command failed
[    6.874824] sun4i-codec 1c22c00.codec: Failed to register our card
[    6.908187] sun4i-codec 1c22c00.codec: Failed to register our card
[    6.936994] debugfs: Directory '1c22c00.codec' with parent 'H3 Audio Codec' already present!
[   12.084564] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[   12.090920] sunxi-mmc 1c0f000.mmc: send stop command failed
[   12.151934] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[   13.155270] sunxi-mmc 1c0f000.mmc: send stop command failed

 

Any help greatly appreciated.

Board: Orangepi PC

[BlueFlame]

P.s.

Also tried a 16GB eMMC module, same result.

Tried an SD card just to be sure (64GB Samsung Evo Plus) and that one boots with only the 1c22c00 messages and is then usable and works.

[NicoD]

Not sure. But you can try. 
Try booting with normal sd-card. Then check the device name of your eMMC with a SD-card reader.
"lsblk"
Then change in /boot/armbianEnv.txt the name that's used there. 

Just a guess. 

[BlueFlame]

Hi Nico,

 

Thanks for your reply.

 

Nowadays they are using the device UUID in the armbianEnv.txt file. I checked it after your suggestion, but it matches.

Do you have any other ideas?

 

I think it's more a kernel support issue if that's possible?

Edited November 20, 2020 by BlueFlame

[BlueFlame]

I also tried the eMMC module on an OrangePi Prime and there it works.

 

Maybe hardware related and not solvable via Armbian after all

(OPI PC -> H3, OPI Prime -> H5)

Ah well, It then also might work on my OPI Zero Plus boards (and that's where I originally bought them for to get rid of the extra ssd's). Will post here once I test.

[Kazymir]

I have the same problem, i allways search...