topic Re: FRDM-IMX93 updated kernel Image and modules in i.MX Processors

FRDM-IMX93 updated kernel Image and modules

Bugger — Wed, 07 May 2025 13:17:34 GMT

Steps

1. Build Yocto imx-image-core

2. Extracted and installed the SDK

3. Build the kernel and modules

4. copied the Image and modules to the SD card

5. extended the Image file with version (as nxp did with the the LTS Image file

6. After boot, uboot boot the lts image, not the new image

How to get uboot to boot the new Image. Where is this specified ? Other products use and extlinux folder to select the dtb and Image. How is thisto be done on FRDM ?

Re: FRDM-IMX93 updated kernel Image and modules

Chavira — Wed, 07 May 2025 14:17:52 GMT

HI @Bugger!

Thank you for contacting NXP Support!

You can check the next guides:

How to fix FRDM-IMx93 Linux Kernel BSP

Flash customized Linux Kernel Image and device tree using UUU Tool

If you have more inquiries please let me know

Best Regards!

Chavira

Re: FRDM-IMX93 updated kernel Image and modules

Bugger — Wed, 07 May 2025 15:15:15 GMT

I did read those documents, though they don't document how to build modules, where/how to copy them to the SD card for the specific linux kernel version (uname -a) . I was confused why the board does not use the root /boot folder Image.

1. checking uboot: it does use "Image" as the boot name.

2. The dts is defined by uboot.

it seems the FRDM-IMX93 board boots Image from mmcblk1p1 and not the rootfs /boot folder on mmcblk1p2 that has the Image with the LTS Image as wel.. After replacing Image on p1, it worked. Not sure why the Image is on /boot then ?

However now I face that modprobe cannot find the modules copied to the SD, even they are in the correct lib/modules folder, even they came from the same build tree..

P.s: Having the dts hardcoded by uboot is a bit inflexible. rather prefer uboot show a menu which dtb to boot

Re: FRDM-IMX93 updated kernel Image and modules

Bugger — Thu, 08 May 2025 04:38:29 GMT

Fixed it the module issue ( copied the wrong Image file). Now the board runs fine with config changes. Only pulling partial information information left and right over the internet and many attempts got a complete process and automated script working that does need Yocto for the kernel