i.MX ProcessorsのトピックRe: Unable to handle kernel paging request at virtual address 0033b273912fd041

Unable to handle kernel paging request at virtual address 0033b273912fd041

bora — Wed, 29 Jan 2025 15:47:56 GMT

Hi,

The board doesn't boot. At the beginning I get an erro "Unable to handle kernel paging". I attached the output.

I appreciate, if you can help.

Best regards,

Re: Unable to handle kernel paging request at virtual address 0033b273912fd041

Bio_TICFSL — Thu, 30 Jan 2025 12:36:30 GMT

Hello,

Please, Try to erase and build and program again you image, there is nothing we can do when this error appear.

Regards

Re: Unable to handle kernel paging request at virtual address 0033b273912fd041

NXP_USER_05 — Wed, 31 Dec 2025 12:08:50 GMT

Hi @bora ,

We are working with a custom i.MX8M Plus DDR4 board that includes 32 MB QSPI NOR flash.
Our objective is to boot U-Boot, Linux kernel, device tree, and initramfs (rootfs.img) entirely from QSPI flash, without using SD/eMMC.

We are able to successfully boot up to U-Boot (flash.bin) from QSPI flash.

-----Flash Layout and Image Sizes----------------

QSPI flash size: 32 MB

flash.bin (U-Boot + SPL) ~2.4 MB
Image.gz (Kernel) ~15 MB
imx8mp-evk.dtb ~85 KB
rootfs.img ~12.6 MB

----QSPI Offset Layout----------
flash.bin @ 0x00000000
Image.gz @ 0x0024D000
imx8mp-evk.dtb @ 0x010A6B00
rootfs.img @ 0x010BB800

U-Boot Environment Setup

After booting into U-Boot from QSPI, we configure the following environment variables to load the kernel, device tree, and initramfs from flash:

sf probe 0
setenv loadaddr 0x40480000 // kernel
setenv fdt_addr 0x43000000 //dtb
setenv initrd_addr 0x43800000 //rootfs (minimal initramfs)
setenv kernel_comp_addr_r 0x50000000
setenv kernel_comp_size 0x04000000

Reading Images from QSPI Flash

sf read ${loadaddr} 0x0024D000 0x00E59A6F
sf read ${fdt_addr} 0x010A6B00 0x00014BBA
sf read ${initrd_addr} 0x010BB800 0x00C04DB0

Boot Command

setenv bootargs console=${console},${baudrate} earlycon=${earlycon},${baudrate} rdinit=/dev

booti ${loadaddr} ${initrd_addr} ${fdt_addr}

Issue Observed

The kernel starts executing but hangs at “Starting kernel …”.
Please refer to the attached kernel boot log (kernel_bootlog1).

When using the following boot arguments:

setenv bootargs setenv bootargs "console=ttymxc1,115200 earlycon root=/dev/ram0 rw rdinit=/sbin/init loglevel=8"

The kernel progresses further but hangs midway during boot.
Please refer to the attached kernel boot log (kernel_bootlog2).

Attached the kernel DTS and kernel defconfig for reference.
Kindly let us know if any modifications are required.

Also getting same error like you Unable to handle kernel paging request at virtual address. can you please give any suggistions to resolve it and successful kernel boot.

Questions:

1. Are there any recommended changes required in the kernel DTS for booting initramfs entirely from QSPI on a custom i.MX8M Plus DDR4 board?

2. Are there any additional boot arguments recommended by NXP for initramfs-based boot on i.MX8MP from QSPI flash?

3. What could be the possible reason for the kernel not booting correctly?
We followed the same procedure that works successfully on the i.MX8MP LPDDR4 EVK, where the kernel and root filesystem boot properly from QSPI flash.
The only differences in our setup are the flash.bin and device tree, which were modified according to the DDR configuration of our custom board.

thank you.

Re: Unable to handle kernel paging request at virtual address 0033b273912fd041

NXP_USER_05 — Mon, 02 Feb 2026 12:56:24 GMT

Hi @Bio_TICFSL

I am working on an i.MX8M Plus DDR4 custom board and I am able to successfully boot the system entirely from QSPI flash (32MB).

My current boot components are:

flash.bin (U-Boot)

Image.gz (Linux kernel)

imx8mp-ddr4-evk.dtb

core-image-minimal-initramfs.cpio.gz

Since my board does not have SD card or eMMC, I am using initramfs as the root filesystem.

Now I want to include gcc inside core-image-minimal-initramfs.cpio.gz, so that I can compile applications directly on the target without relying on any external storage.

Changed the conf/local.conf and then build using command

$bitbake core-image-minimal-initramfs

Also attached the local.conf file for your reference.

It generated core-image-minimal-initramfs.cpio.gz but in bin/ and usr/bin respective folders gcc is not present and getting like below after booting kernel and cpio.gz.

~ # gcc
/bin/sh: gcc: not found

~ # ls
bin dev home init.d media proc run sys usr
boot etc init lib mnt root sbin tmp var

Could you please advise:

What is the correct Yocto method to include gcc in an initramfs image?

Are there any recommended configurations or limitations when using gcc inside initramfs (RAM usage, image size, etc.)?

Any guidance or reference to NXP-supported Yocto practices would be very helpful.

Thank You.