I'm trying to build a yocto image for my IMX6ULL 14x14 EVK board by following this set of instructions:
However, when building an image, only u-boot seems to start. U-boot then never seems to get to an autoboot step or allow access to the console. So, the kernel never starts.
Here is my build configuration:
Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "imx6ull14x14evk" DISTRO = "fsl-imx-wayland" DISTRO_VERSION = "6.1-langdale" TUNE_FEATURES = "arm vfp cortexa7 neon thumb callconvention-hard" TARGET_FPU = "hard" meta meta-poky = "HEAD:b50f718e4cb73214e7ad298484ecdadd6cfeb866" meta-oe meta-multimedia meta-python = "HEAD:c354f92778c1d4bcd3680af7e0fb0d1414de2344" meta-freescale = "HEAD:09c47379218167dda9fb0098129909a667fea2ec" meta-freescale-3rdparty = "HEAD:96c1f6a6c2cad246687cd695e0873fcc6cdde935" meta-freescale-distro = "HEAD:1069c2f210b18cd707a4d8a82140a684a42a4ff6" meta-bsp meta-sdk meta-ml meta-v2x = "HEAD:82c29a7fab71e5e9c5fc28af554c0289d0a00262" meta-nxp-demo-experience = "HEAD:c057a681cf11923b22e16b9cdb0ad2b9187eced2" meta-arm meta-arm-toolchain = "HEAD:025124814e8676e46d42ec5b07220283f1bdbcd0" meta-chromium = "HEAD:e232c2e21b96dc092d9af8bea4b3a528e7a46dd6" meta-clang = "HEAD:22f1cc330d3501923d2dc27cd3fc424c69c3a73a" meta-gnome meta-networking meta-filesystems = "HEAD:c354f92778c1d4bcd3680af7e0fb0d1414de2344" meta-qt6 = "HEAD:4f7d02004cd78f0fca77489deb7487bfb301ea36" meta-parsec meta-tpm = "HEAD:2aa48e6f4e519abc7d6bd56da2c067309a303e80" meta-virtualization = "HEAD:8857b36ebfec3d548755755b009adc491ef320ab"
I have attempted to build core-image-minimal, imx-image-core, and imx-image-multimedia. All of these result in the same problem. Here is the console output from u-boot:
U-Boot 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000) CPU: i.MX6ULL rev1.1 792 MHz (running at 396 MHz) CPU: Industrial temperature grade (-40C to 105C) at 47C Reset cause: POR Model: i.MX6 ULL 14x14 EVK Board Board: MX6ULL 14x14 EVK DRAM: 512 MiB Core: 65 devices, 18 uclasses, devicetree: separate MMC: FSL_SDHC: 0, FSL_SDHC: 1 Loading Environment from MMC... *** Warning - bad CRC, using default environment [*]-Video Link 0 (480 x 272)  lcdif@21c8000, video In: serial Out: serial Err: serial switch to partitions #0, OK mmc1(part 0) is current device flash target is MMC:1 Net: Could not get PHY for FEC1: addr 1 Could not get PHY for FEC1: addr 1 Get shared mii bus on ethernet@2188000
After that, it seems to just hang with no access to the uboot console
When the system boots from the emmc (with what was shipped on the board), a kernel seems to start.
Any indication on what I need to do here?
Hi @mitchgaines0 ,
Sorry for the late response. Please help me with the following questions to pinpoint the root of your problem:
1. What BSP version are you trying to build?
2.What process are you following to flash your created image?
3. To what device are you flashing to?
4. From which OS are you flashing from?
I build yocto image follow the URL
It boots success. Maybe you can check the differences with yocto user guide, just for your reference.