Debix Model A Boot0000 Problem

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Debix Model A Boot0000 Problem

317 Views
qbic
Contributor I

Hello,

I want to build an Image for the Debix Model A which is now supported by NXP in the latest yocto version. But when I boot the device I get the following output on the UART console:

 

U-Boot SPL 2024.04+g674440bc73e+p0 (Jun 06 2024 - 10:05:34 +0000)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 3732MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
WDT:   Started watchdog@30280000 with servicing every 1000ms (60s timeout)
Trying to boot from BOOTROM
Boot Stage: Primary boot
image offset 0x8000, pagesize 0x200, ivt offset 0x0
Failed to find node!, err: -1!
Failed to find node!, err: -1!
NOTICE:  Do not release JR0 to NS as it can be used by HAB
NOTICE:  BL31: v2.10.0  (release):lf-6.6.23-2.0.0
NOTICE:  BL31: Built : 10:04:22, May 29 2024


U-Boot 2024.04+g674440bc73e+p0 (Jun 06 2024 - 10:05:34 +0000)

CPU:   i.MX8MP[8] rev1.1 at 1200 MHz
Reset cause: POR
Model: Polyhex Debix Model A i.MX8MPlus board
DRAM:  2 GiB
Core:  86 devices, 22 uclasses, devicetree: separate
WDT:   Started watchdog@30280000 with servicing every 1000ms (60s timeout)
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... OK
In:    serial@30890000
Out:   serial@30890000
Err:   serial@30890000
Net:   eth1: ethernet@30bf0000 [PRIME]
Normal Boot
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
52441 bytes read in 4 ms (12.5 MiB/s)
Card did not respond to voltage select! : -110
No EFI system partition
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
Loading Boot0000 'mmc 1' failed
EFI boot manager: Cannot load any image
Card did not respond to voltage select! : -110
u-boot=>

 

 

output of printenv:

 

arch=arm
baudrate=115200
board=imx8mp_debix_model_a
board_name=imx8mp_debix_model_a
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootaa64.efi; if fdt addr -q ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi
boot_efi_bootmgr=if fdt addr -q ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr;fi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf}
boot_fdt=try
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_syslinux_conf=extlinux/extlinux.conf
boot_targets=mmc1 mmc2
bootcmd=run distro_bootcmd
bootcmd_mmc1=devnum=1; run mmc_boot
bootcmd_mmc2=devnum=2; run mmc_boot
bootdelay=2
bootfstype=fat
bootm_size=0x10000000
console=ttymxc1,115200 earlycon=ec_imx6q,0x30890000,115200
cpu=armv8
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
distro_bootpart_uuid=076c4a2a-01
efi_dtb_prefixes=/ /dtb/ /dtb/current/
eth1addr=10:07:23:6d:e5:0a
ethact=ethernet@30bf0000
ethprime=eth1
fdt_add_r=0x80000000
fdt_addr_r=0x43000000
fdtaddr=43000000
fdtcontroladdr=bdf31fa0
fdtfile=imx8mp-debix-model-a.dtb
fileaddr=43000000
filesize=ccd9
image=Image
initrd_addr=0x43800000
kernel_addr_r=0x40480000
load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile}
loadaddr=0x40480000
mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi
mmcpart=1
mmcroot=/dev/mmcblk1p2 rootwait rw
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then part uuid ${devtype} ${devnum}:${distro_bootpart} distro_bootpart_uuid ; run scan_dev_for_boot; fi; done; setenv devplist
scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;run boot_efi_bootmgr;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootaa64.efi; then echo Found EFI removable media binary efi/boot/bootaa64.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinux_conf}; run boot_extlinux; echo EXTLINUX FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scriptaddr=0x40480000
soc=imx8m
stderr=serial@30890000
stdin=serial@30890000
stdout=serial@30890000
vendor=polyhex

Environment size: 3229/4092 bytes

 

 

I hope somebody can help me out here or could explain what this "Loading Boot0000 'mmc 1' failed" message means. If any important information is missing please tell me.

 

Thank you!

Tags (3)
0 Kudos
Reply
1 Reply

279 Views
JorgeCas
NXP TechSupport
NXP TechSupport

Hello,

I suggest you check your build process directly with Debix since our BSP only has our EVKs machines.

Here more information:

JorgeCas_2-1722462109993.png

JorgeCas_3-1722462118455.png

Best regards.

0 Kudos
Reply