i.MX ProcessorsのトピックRe: Kernel Source git link and build procedure for iMX95 FRDM board

Kernel Source git link and build procedure for iMX95 FRDM board

Harish_V — Wed, 03 Jun 2026 13:35:30 GMT

I have recently FRDM iMX95 Development board. Can you please share the build steps , getting started and kernel source git link.
From where do we get the prebuild base Image from. Kindly provide the solution for this. Thanks.

Re: Kernel Source git link and build procedure for iMX95 FRDM board

dbaluta — Fri, 05 Jun 2026 08:26:31 GMT

There are a lot of ways to do this. I will let NXP SE/CAS engineers to offer their answer and use it as the official one.

What works for me.

1) If you want LTS NXP kernel (stable kernel)

$ git clone https://github.com/nxp-imx/linux-imx.git

$ git checkout lf-6.18.y

$ export ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-

$ make imx_v8_defconfig

$ make -j8

# this will create Image, dtb and modules.

2) If you want bleeding edge kernel

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

# now copy imx_v8_defconfig from linux-imx tree and use the same steps to get Image, dtb and modules.

For prebuild images you can just use IMX95 FRDM landing page: https://www.nxp.com/document/guide/getting-started-with-frdm-imx95:GS-FRDM-IMX95?section=get-software

Re: Kernel Source git link and build procedure for iMX95 FRDM board

Harish_V — Wed, 10 Jun 2026 07:15:41 GMT

Hi, Thank you for your reply. I have built and checked the booting. It works fine.
I had bought OS08A20 camera module from NXP along with the kit to validate the ISP. I am able to stream in preflashed binaries but if I try to stream in the environment with my replaced Image and modules , I am facing the following issue. I have attached the gstreamer error and corresponding dmesg log.

BUILD
root@imx95-15x15-lpddr4x-frdm:~# GST_DEBUG=3 gst-launch-1.0 libcamerasrc camera-name="${CAMERA0}" ! video/x-raw, width=3840, height=2160, format=YUY2 ! queue ! waylandsink
Setting pipeline to PAUSED ...
[0:00:44.561152921] [750] INFO Camera camera_manager.cpp:340 libcamera v0.0.0+6489-lf-6.18.2-1.0.0
[0:00:44.679792462] [754] INFO IPAProxy ipa_proxy.cpp:180 Using tuning file /usr/share/libcamera/ipa/nxp/neo/os08a20.yaml
[0:00:44.679997696] [754] INFO NxpNeoIPA neo_ipa.cpp:146 nxpneo: IPANxpNeo NXPNEO_IPA_v0.0.0+6489-lf-6.18.2-1.0.0
[0:00:44.681633606] [754] INFO Camera camera_manager.cpp:223 Adding camera '/base/soc/bus@42000000/i2c@42540000/os08a20_mipi@36' for pipeline handler nxp/neo
Pipeline is live and does not need PREROLL ...
0:00:00.393998203 750 0xffffa4000dc0 FIXME default gstutils.c:4169:gst_element_decorate_stream_id_internal:<libcamerasrc0> Creating random stream-id, consider implementing a deterministi
c way of creating a stream-id
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
0:00:00.394882923 750 0xffffa4000dc0 WARN default gstlibcamera-utils.cpp:369:gst_libcamera_stream_formats_to_caps: Unsupported DRM format R10
0:00:00.394955545 750 0xffffa4000dc0 WARN default gstlibcamera-utils.cpp:369:gst_libcamera_stream_formats_to_caps: Unsupported DRM format R12
New clock: GstSystemClock
0:00:00.395147188 750 0xffffa4000dc0 WARN default gstlibcamera-utils.cpp:369:gst_libcamera_stream_formats_to_caps: Unsupported DRM format XVUY
[0:00:44.685461470] [756] INFO Camera camera.cpp:1215 configuring streams: (0) 3840x2160-YUYV/sYCC
0:00:00.0 / 99:99:99.

PREBUILD
root@imx95-15x15-lpddr4x-frdm:~# GST_DEBUG=3 gst-launch-1.0 libcamerasrc camera-name="${CAMERA0}" ! video/x-raw, width=3840, height=2160, format=YUY2 ! queue ! waylandsink
Setting pipeline to PAUSED ...
[0:01:11.941028172] [784] INFO Camera camera_manager.cpp:340 libcamera v0.0.0+6489-lf-6.18.2-1.0.0
[0:01:12.052290407] [788] INFO IPAProxy ipa_proxy.cpp:180 Using tuning file /usr/share/libcamera/ipa/nxp/neo/os08a20.yaml
[0:01:12.052450707] [788] INFO NxpNeoIPA neo_ipa.cpp:146 nxpneo: IPANxpNeo NXPNEO_IPA_v0.0.0+6489-lf-6.18.2-1.0.0
[0:01:12.053531983] [788] INFO Camera camera_manager.cpp:223 Adding camera '/base/soc/bus@42000000/i2c@42540000/os08a20_mipi@36' for pipeline handler nxp/neo
Pipeline is live and does not need PREROLL ...
0:00:00.380374002 784 0xffffa0000dc0 FIXME default gstutils.c:4169:gst_element_decorate_stream_id_internal:<libcamerasrc0> Creating random stream-id, consider implementing a deterministi
c way of creating a stream-id
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
0:00:00.381201872 784 0xffffa0000dc0 WARN default gstlibcamera-utils.cpp:369:gst_libcamera_stream_formats_to_caps: Unsupported DRM format R10
0:00:00.381301351 784 0xffffa0000dc0 WARN default gstlibcamera-utils.cpp:369:gst_libcamera_stream_formats_to_caps: Unsupported DRM format R12
0:00:00.381493811 784 0xffffa0000dc0 WARN default gstlibcamera-utils.cpp:369:gst_libcamera_stream_formats_to_caps: Unsupported DRM format XVUY
[0:01:12.057204764] [790] INFO Camera camera.cpp:1215 configuring streams: (0) 3840x2160-YUYV/sYCC
0:00:00.525188577 784 0xffffa0000be0 WARN wlwindow gstwlwindow.c:546:gst_wl_window_new_internal: init surface_state fail, fallback to scale=1 fullscreen (1920x1048)
Redistribute latency...

DMESG log of failure case
[ 20.994118] ox05b1s 3-0036: Camera os08a20 detected, chip_id=530841
[ 40.900644] kauditd_printk_skb: 26 callbacks suppressed
[ 40.900670] audit: type=1334 audit(1781075420.425:26): prog-id=21 op=UNLOAD
[ 45.294168] ox05b1s 3-0036: Failed to apply mode 3840x2160,bpp=12
[ 100.138752] ox05b1s 3-0036: Runtime PM usage count underflow!

How to resolve this. Kindly help me, thanks

Re: Kernel Source git link and build procedure for iMX95 FRDM board

dbaluta — Wed, 10 Jun 2026 08:48:33 GMT

@Harish_V I think this is another question. The initial question was about linux trees.

If you decide to create another question, please specify the exact tree / latest commit has on your tree, dts you have used, addition code that you added to the dts. Also, I'm not familiar with camers so i cannot help.

Also if the code is with upstream tree (e.g linux-next, linux mainline) then you can also send an email to IMX upstream community at imx@lists.linux.dev

Re: Kernel Source git link and build procedure for iMX95 FRDM board

Harish_V — Wed, 10 Jun 2026 08:52:54 GMT

Hi.

This is my current branch.
FRDM/build/linux-imx$ git branch -a
lf-6.12.y
* lf-6.18.y
remotes/origin/HEAD -> origin/lf-6.12.y
remotes/origin/git.kernel.org/linux-stable/linux-2.6.11.y

The last commit was,

FRDM/build/linux-imx$ git log
commit f49f45233f7b10006ce7e9c826ee882bb14ac8b5 (HEAD -> lf-6.18.y, tag: lf-6.18.2-1.0.0, origin/lf-6.18.y)
Author: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
Date: Wed Feb 11 12:59:05 2026 +0000

MA-24383 Revert "LF-16490-3 dts: arm64: freescale: Set default FSYNC interval for Maxim CSI SerDes"

This reverts commit ee3206dd51df41e8386c87723fb790e416cab463.

It appears that, when FSYNC is enabled, and one sensor's frames are
delayed more than the others after exposure is increased, the other
sensor's streaming cannot be activated. Streaming only works well when
it is started simultaneously on all sensors.

Hence, disable default FSYNC setting until we figure out what the
problem is.

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
Reviewed-by: Robert Chiras <robert.chiras@nxp.com>
Tested-by: Antoine Bouyer <antoine.bouyer@nxp.com>
Acked-by: Jason Liu <jason.hui.liu@nxp.com>

commit 5304400e20c8036690bd7718e2d8e3ed01b23037
Author: Gaurav Jain <gaurav.jain@nxp.com>
Date: Tue Feb 10 16:17:57 2026 +0530

LF-17497 uio: v2x prime: add reserve memory map

added support for
- read reserved memory node from device tree
- create map1 for reserved memory
- this is mapped in user space using mmap.

Signed-off-by: Gaurav Jain <gaurav.jain@nxp.com>
Reviewed-by: Pankaj Gupta <pankaj.gupta@nxp.com>
Acked-by: Jason Liu <jason.hui.liu@nxp.com>

This was cloned from https://github.com/nxp-imx/linux-imx, which you had mentioned.

Re: Kernel Source git link and build procedure for iMX95 FRDM board

dbaluta — Wed, 10 Jun 2026 09:03:12 GMT

OK, I see so with the pre-flashed binaries it works but with code build by you it doesn't. You need to do a bisection. Figure out which kernel is the pre-flashed binary and work to the current patch to see which is the faulty patch.

Otherwise, yes - please create another question specifically for this so the proper NXP support person to handle your issue.