i.Mx8MQ u-boot boot up issue

[neel_desai]

Hi NXP Team,

We have used imx8mq_evk for development purposes. Based on the imx8mq evk design we have developed a custom board.

Flash process:

Below are the processes which we have followed:

1. I have refer to the DDR calibration tool and doing a DDR stress test.

2. After the stress test successfully,  I have generated lpddr.c file.

3. After generating lpddr.c stress file I have integrated this file into the u-boot.

4. Compile the u-boot and flash the u-boot using uuu tool.

Boot process:

Below are the processes which we have followed After flashing the images:

• I changed the boot pin setting and set it as an internal boot mode

Boot process observation:

Below are the logs which I have received in the UART console at boot-up time.

###################################################

U-Boot 2019.04-lf-5.4.y_v2019.04+g08ae210 (Oct 05 2020 - 14:24:44 +0000)

CPU: Freescale i.MX8MQ rev2.1 1500 MHz (running at 1000 MHz)
CPU: Commercial temperature grade (0C to 95C) at 33C
Reset cause: POR
Model: i.MX8MQ
DRAM: 4 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... MMC: no card present
*** Warning - No block device, using default environment

In: serial
Out: serial
Err: serial

BuildInfo:
- ATF 7b3389d
- U-Boot 2019.04-lf-5.4.y_v2019.04+g08ae210

MMC: no card present
Detect USB boot. Will enter fastboot mode!
Net:
Error: ethernet@30be0000 address not set.

Error: ethernet@30be0000 address not set.
eth-1: ethernet@30be0000
Fastboot: Normal
Boot from USB for mfgtools
*** Warning - Use default environment for mfgtools
, using default environment

Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd
_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot 0; f
i;
Hit any key to stop autoboot: 0
u-boot=>
u-boot=>
u-boot=>
u-boot=> U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 201
9.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201
U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-
lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U
-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.
4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot
2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v
201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019
.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U-Boot 2019.04-lf-5.4.y_v201 U

Questions:

1. Why u-boot stuck after reaching command prompt?

[AldoG · Accepted solution]

Hello,

I see no errors in the log you had shared, is the boot log I presume, the only thing that I could say about this is that you had stopped at uboot.

Does it not start kernel automatically if you let the countdown finish?
Once uboot start do not input any character to the serial terminal since this will stop uboot as you can see in your test.

Hope this helps,
Regards,
Aldo.