imx7ulpevk stuck at u-boot with core-image-minimal

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

imx7ulpevk stuck at u-boot with core-image-minimal

Jump to solution
747 Views
Raxesh-Oriya
Contributor III

I got a IMX7ULP-EVK. First tried flashing pre-built image(L4.19.35_1.1.0_images_MX7ULPEVK) and everything worked fine, no issue. Then moved ahead and generated core-image-minimal with following steps and u-boot stuck at early stage:

 

repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b warrior
repo sync
MACHINE=imx7ulpevk DISTRO=poky source setup-environment build
bitbake core-image-minimal
bmaptool copy core-image-minimal-imx7ulpevk-<timestamp>.rootfs.wic.gz /dev/sdb (sdb is uSD card here)

 

U-boot stuck with below logs in case of core-image-minimal:

 

U-Boot 2019.07+fslc+gca0ab15 (Jul 08 2021 - 12:12:24 +0000)

CPU: Freescale i.MX7ULP rev1.0 at 413 MHz
Reset cause: POR
Boot mode: Dual boot
Model: NXP i.MX7ULP EVK
DRAM: 1 GiB

 

U-boot works fine in case of pre-built image(L4.19.35_1.1.0_images_MX7ULPEVK):

 

U-Boot 2019.04-4.19.35-1.1.0+g4d377539a1 (Oct 29 2019 - 19:52:18 +0000)

CPU: Freescale i.MX7ULP rev2.1 at 500 MHz
Reset cause: POR
Boot mode: Dual boot
Model: NXP i.MX7ULP EVK
DRAM: 1 GiB
MMC: FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

No panel detected: default to RM68200_WXGA
Display: RM68200_WXGA (720x1280)
Video: 720x1280x24
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
flash target is MMC:0
Net: Net Initialization Skipped
No ethernet found.
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
7565456 bytes read in 373 ms (19.3 MiB/s)
Booting from mmc ...
21321 bytes read in 7 ms (2.9 MiB/s)
Kernel image @ 0x60800000 [ 0x000000 - 0x737090 ]
## Flattened Device Tree blob at 63000000
Booting using the fdt blob at 0x63000000
Using Device Tree in place at 63000000, end 63008348

Starting kernel ...

Booting Linux on physical CPU 0xf00
Linux version 4.19.35-1.1.0+g0f9917c56d59 (oe-user@oe-host) (gcc version 8.3.0 (GCC)) #1 SMP PREEMPT Wed Oct 30 14:13:39 UTC 2019
CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c53c7d
CPU: div instructions available: patching division code
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

.

.

 

There is huge difference in size between both the bootloader as given below:

Pre-built u-boot => 607KB 

core-image-minimal u-boot => 359KB

Questions:

  • Why u-boot retrieves different value of "CPU clock" and "Board Rev" in above logs?
  • Is there any additional configuration required to be set?
  • Why u-boot is unable to find MMC?
Labels (3)
0 Kudos
1 Solution
695 Views
Raxesh-Oriya
Contributor III

There was some unknown problem with U-boot 2019.07+fslc which comes as default one. Migrating to 2020.01 version of U-boot by fetching respective recipes did solve the issue.

View solution in original post

0 Kudos
1 Reply
696 Views
Raxesh-Oriya
Contributor III

There was some unknown problem with U-boot 2019.07+fslc which comes as default one. Migrating to 2020.01 version of U-boot by fetching respective recipes did solve the issue.

0 Kudos