Release Notes¶
Yocto mx95-yocto-walnascar-6.12.20_2.0.0-v1.4
Release Notes¶
| Based on release | Yocto: Poky 5.2, BSP: NXP 6.12.20_2.0.0, Linux: lf-6.12.y |
| Release tag | mx95-yocto-walnascar-6.12.20_2.0.0-v1.4 |
| Release manifest | imx-6.12.20-2.0.0.xml |
| Date | 01/02/2026 |
| Supported platforms | DART-MX95 |
| SOM revision | v1.2 |
| File System build system | Yocto Walnascar |
| Recovery SD card link | mx95__yocto-walnascar-6.12.20_2.0.0-v1.4__android-15.0.0_2.0.0-v1.1.wic.zst |
| Recovery SD card SHA256 | a2d52938d734fc766d18f69ebd354882184f3b561829d648f773bc6a1982c68f |
| Cortex M7 U-Boot support | MCUXPRESSO_25.06.0_V1.0_DART-MX95 |
| Cortex M7 Linux remoteproc support | MCUXPRESSO_25.06.0_V1.0_DART-MX95 |
Relevant git Repositories¶
After downloading the image, visit our Recovery SD card guide to learn how to program a recovery SD card.
Change Log¶
| Change List | Description |
|---|---|
| Release 1.4 | |
| Mayor Update | |
|
Reset the ethernet phy only if exists |
U-Boot change |
| U-Boot Updates | Click here for a full detailed change list |
| meta-variscite-bsp-imx Updates | Click here for a full detailed change list |
| meta-variscite-sdk-imx Updates | Click here for a full detailed change list |
| Release 1.3 | |
| U-Boot Updates | Click here for a full detailed change list |
| Kernel Updates | Click here for a full detailed change list |
| meta-variscite-bsp-common Updates | Click here for a full detailed change list |
| meta-variscite-bsp-imx Updates | Click here for a full detailed change list |
| meta-variscite-sdk-imx Updates | Click here for a full detailed change list |
| Release 1.2 | |
| System Manager Updates | Click here for a full detailed change list |
| meta-variscite-bsp-common Updates | Click here for a full detailed change list |
| meta-variscite-bsp-imx Updates | Click here for a full detailed change list |
| Release 1.1 | |
| Add support for Cortex M7 core from U-Boot and Linux user space | |
| System Manager Updates | Click here for a full detailed change list |
| U-Boot Updates | Click here for a full detailed change list |
| Kernel Updates | Click here for a full detailed change list |
| meta-variscite-bsp-common Updates | Click here for a full detailed change list |
| meta-variscite-bsp-imx Updates | Click here for a full detailed change list |
| meta-variscite-sdk-common Updates | Click here for a full detailed change list |
| meta-variscite-sdk-imx Updates | Click here for a full detailed change list |
| Release 1.0 | |
| Initial Yocto Walnascar 6.12.20_2.2.0 release | Based on NXP Yocto Walnascar 6.12.20_2.0.0 and NXP Linux Kernel lf-6.12.y |
| i.MX95 B0 Migration | Starting with Walnascar 6.12.20_2.0.0 only i.MX95 B0 is supported. |
| Known Issues | |
| Tensorflow build fetch error |
Due to possible checksum changes in the files hosted at https://gitlab.arm.com/kleidi/kleidiai/-/archive/, TensorFlow Lite may no longer be built from source. Unless these files are already present in your local download cache, the build will fail. As a workaround, the Machine Learning package must be removed from the build. Add the following to the conf/local.conf:For the image fsl-image-gui/fsl-image-gui-chromium:RDEPENDS:packagegroup-variscite-imx-ml:mx9-nxp-bsp:remove = "packagegroup-imx-ml"For the image fsl-image-qt6, in addition:RDEPENDS:packagegroup-imx-gopoint:remove = "imx-nnstreamer-examples"
|
| Inaccurate timing on audio playback |
Audio Playback can fail or may be perceived as timing inaccurate, especially when different sample rates are used and the audio device is accessed directly. As a workaround, it is recommended to either use the default sample rate (48kHz), start playback twice in a row, or use the mixer instead of direct access. The underlying reason is a faulty synchronization of the clock settings, which can result in a mismatch between the SAI and the codec clock.
|
| The following Variscite BSP feature are not supported yet: |
WBE device tree
|
| Note | |
| Allow using only one camera: |
Due to a limitation in the current kernel implementation of MIPI-CSI control chain, only the cameras actually present must be enabled.
In order to use a single camera, only that specific camera can be enabled, while the other and related chain items must be disabled.
|