# HummingBoard Mate. MicroSD Booting Error

**URL:** https://community.solid-run.com/t/hummingboard-mate-microsd-booting-error/763
**Category:** NXP i.MX8M Plus
**Tags:** iMX8M-plus
**Created:** [November 20, 2023, 9:25am UTC](https://community.solid-run.com/t/hummingboard-mate-microsd-booting-error/763 "2023-11-20T09:25:24Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![EnricAR](https://avatars.discourse-cdn.com/v4/letter/e/ba8739/32.png) [@EnricAR](https://community.solid-run.com/u/EnricAR)
#### Post date: [November 20, 2023, 9:25am UTC](https://community.solid-run.com/t/hummingboard-mate-microsd-booting-error/763/1 "2023-11-20T09:25:24Z")

</div>

I am following the “[HummingBoard Mate & i. MX8M Plus SOM Quick Start Guide](https://solidrun.atlassian.net/wiki/spaces/developer/pages/263192632/HummingBoard+Mate+i.MX8M+Plus+SOM+Quick+Start+Guide)” and I’m doing the booting from SD card option.  
I am booting this img: sr-imx8-debian-bullseye-20230623-cli-imx8mp-sdhc.img  
Once I have connected the power supply, the boot process starts. After about an hour, the board reaches this point:

```auto
U-Boot SPL 2020.04-00026-g0909dfb6 (Jun 14 2023 - 07:15:46 +0000)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 3000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
DDR 4G Samsung identified!
DDRINFO: start DRAM init
DDRINFO: DRAM rate 4000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from BOOTROM
image offset 0x8000, pagesize 0x200, ivt offset 0x0
NOTICE: BL31: v2.2(release):rel_imx_5.4.70_2.3.0-0-gf1d7187f
NOTICE: BL31: Built : 07:15:43, Jun 14 2023

U-Boot 2020.04-00026-g0909dfb6 (Jun 14 2023 - 07:15:46 +0000)

CPU: i.MX8MP[8] rev1.1 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 24C
Reset cause: POR
Model: NXP i.MX8MPlus LPDDR4 SolidRun board
DRAM: 4 GiB
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using defau lt environment

[*]-Video Link 0probe video device failed, ret -2

        [0] lcd-controller@32e80000, video
        [1] mipi_dsi@32e60000, video_bridge
        [2] adv7535@39, panel
probe video device failed, ret -2
In: serial
Out: serial
Err: serial

 BuildInfo:
  - ATF f1d7187
  - U-Boot 2020.04-00026-g0909dfb6

```

After another 1 hour, this error is reached. Where the u-boot command line appears:

```auto
switch to partitions #0, OK
mmc1 is current device
flash target is MMC:1
Net: board_get_mac: interface 0: using mac from tlv eeprom: D0:6 3:B4:04:C9:26

Warning: ethernet@30bf0000 using MAC address from ROM
eth1: ethernet@30bf0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2544 bytes read in 19 ms (129.9 KiB/s)
## Executing script at 40480000
26333696 bytes read in 8516 ms (2.9 MiB/s)
SCRIPT FAILED: continuing...
Found U-Boot script /boot/boot.scr
2544 bytes read in 18 ms (137.7 KiB/s)
## Executing script at 40480000
26333696 bytes read in 8515 ms (2.9 MiB/s)
SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc2(part 0) is current device
**No partition table - mmc 2**
starting USB...
Bus usb@38100000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@38200000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@38100000 for devices... 1 USB Device(s) found
scanning bus usb@38200000 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-d0-63-b4-04-c9-26
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-imx8m-imx8mp_solidrun
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-imx8m
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
EQOS_DMA_MODE_SWR stuckFAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
EQOS_DMA_MODE_SWR stuckFAILED: -110Config file not found
EQOS_DMA_MODE_SWR stuckFAILED: -110EQOS_DMA_MODE_SWR stuckFAILED:-110
u-boot=> 

```

I cannot reach the debian login.

Can anyone see anything in the logs? Thank you

---

<div class="post-metadata">

### Author: ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)
#### Post date: [November 21, 2023, 3:48am UTC](https://community.solid-run.com/t/hummingboard-mate-microsd-booting-error/763/2 "2023-11-21T03:48:06Z")

</div>

This boot up should happen within seconds. What uSDHC card are you using?

---

<div class="post-metadata">

### Author: ![EnricAR](https://avatars.discourse-cdn.com/v4/letter/e/ba8739/32.png) [@EnricAR](https://community.solid-run.com/u/EnricAR)
#### Post date: [November 21, 2023, 10:36am UTC](https://community.solid-run.com/t/hummingboard-mate-microsd-booting-error/763/3 "2023-11-21T10:36:42Z")

</div>

I’m using a SanDisk Ultra 32GB microSDHC UHS-I and I used win32diskimager to flash the img. file.  
The img. I flashed is sr-imx8-debian-bullseye-20230623-cli-imx8mp-sdhc.img

I also tried with a SanDisk Edge 16GB microSDHC UHS-I.  
I also tried with an 8GB microSDHC SpeedClass 4(C4)  
I also tried with a Transcend 2GB microSD

---

<div class="post-metadata">

### Author: ![EnricAR](https://avatars.discourse-cdn.com/v4/letter/e/ba8739/32.png) [@EnricAR](https://community.solid-run.com/u/EnricAR)
#### Post date: [November 23, 2023, 10:39am UTC](https://community.solid-run.com/t/hummingboard-mate-microsd-booting-error/763/4 "2023-11-23T10:39:04Z")

</div>

Which kind of uSDHC card should I use?  
Thanks

---

<div class="post-metadata">

### Author: ![amatus](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/amatus/32/281_2.png) [@amatus](https://community.solid-run.com/u/amatus)
#### Post date: [March 4, 2024, 11:53pm UTC](https://community.solid-run.com/t/hummingboard-mate-microsd-booting-error/763/5 "2024-03-04T23:53:20Z")

</div>

I had this same behavior: sr-imx8-debian-bullseye-20230623-cli-imx8mp-sdhc.img does not boot on the HummingBoard Mate. On my board the U-Boot environment contains the variable `fdtfile=freescale/imx8mp-hummingboard-mate.dtb` but the Debian image does not contain this file.
