Hello,

I can confirm that both armStoneMX8MPr2-V4 and armStoneMX8MP-V24 rev v1.10 have the same configuration regarding UART_B.

However both boards have a RS485 converter equipped on the UART_B port. So TTL communication will not be possible with these board variants per default. If you need TTL level please also contact Sales for a customer specific variant.

If you have further questions, regarding this issue, please open a new thread, as this gets so specific for the release thread.

Your F&S Support Team

Hello,

Unfortunalty, the armStoneMX8MPr2 is a own standalone board, which needs its own Deivce Tree and Board configuration. Using exact the same SW on both boards is not possible. However if you really do not make use of the WLAN chitp i would recommend to contact Sales about a board variant of the armStoneMX8MP without WLAN chip. It should still be possible to create a board specific variant.

Your F&S Support Team

Hello and welcome to the forum,

unfortunately, the college, who is an expert with the i.MX8ULP is currently not in the office, but i'll try to answer your questions as good as I can, until he comes back.

Is the PMIC located on the PicoCoreMX8ULP module itself or on the carrier board?

The PMIC is located on the PicoCore module

If the PMIC is present and managed by the BSP, could you please indicate the relevant DTS/DTSI file(s) where its configuration is defined?

The PMIC is managed by a special RISC-V core with a firmware binary, provided by NXP, shipped with the F&S Nboot

https://github.com/Freescale/m…/firmware-upower_1.3.1.bb

It is documented here

https://www.nxp.com/docs/en/us…de/uPower_USERS_GUIDE.pdf

Are there any board-specific overlays, BSP components, or reference designs that contain the PMIC settings?

The pmic is manly configured by the bootloaders and the ATF. Normally there are no additional configurations necessary.

Do you have a special use case, where you additional configure the PMIC?

Since UART_B is marked as being controlled by the Cortex-M33, is the 88W8997 BLE/Bluetooth controller managed entirely by the M33 core?

Yes UART_B is controlled by the M33. The M33 runs a Freertos based firmware called realtimed. You can find the source code here

https://github.com/FSEmbedded/realtimed

The idea is that the MCORE exposes an UART-TTY to linux via the RPMSG protocoll and the SRTM service structure

https://github.com/FSEmbedded/…vices/srtm_uart_service.c

It will be used to configure and control the Bluetooth chip entirely by Linux.

However, the UART control signals are not fully implemented in the M33, so Bluetooth will not work on the PicoCoreMX8ULP in the current release.
F&S i.MX8ULP Yocto Release 2025.11.1 (fsimx8ulp-Y2025.11.1).

We will come back to you or further information on the development state, when out college is back.

Your F&S Support Team

There is an issue in the fsimx6sx-Y2026.06 release, that prevents the release form building, when adding the meta-silex-fus layer.

To fix this issue you can update meta-silex-fus to commit

9e6b7784640fb118103da71399ef66245055af54

If you do not use the Silex Wlan chip we recommend removing the meta-silex layer from your build

Remove the line form your onf/bblayers.conf :

A F&S Development Machine with preinstalled fsimx6ul-Y2026.07 Release can be found here

New F&S Development Machine - Fedora40-arm32

F&S Development Machine with Fedora 40 arm32 V1.4 (14.07.2026)

There is a new Virtual Machine with Fedora40 in your download section available

My F&S / Tools-Linux /VirtualMachines/Fedora40/32-bit)/ F_S_Development_Machine-Fedora_40_arm32_V1.4.ova

The structure of the virtual machine is listed below.

Content:

• fsimx6-Y2026.06 (/home/developer/fsimx6-Y2026.06)
• fsimx6-B2026.05 (/home/developer/fsimx6-B2026.05)
• fsimx6sx-B2026.06 (/home/developer/fsimx6sx-B2026.06)
• fsimx6sx-Y2026.06 (/home/developer/fsimx6sx-Y2026.06)
• fsimx6ul-B2026.07 (/home/developer/fsimx6ul-B2026.07)

New Content:

• fsimx6ul-Y2026.07 (/home/developer/fsimx6ul-Y2026.07)

Removed Content:

-

F&S i.MX6UL Yocto Release 2026.07 (fsimx6ul-Y2026.07)

This is a major release for F&S modules based on the i.MX6UL SoC, and the NXP lf-6.6.52-2.2.2 release.

Supported Boards

• PicoCOM1.2
• PicoCOMA7
• efusA7UL
• PicoCoreMX6UL
• PicoCoreMX6UL100

Please see the new revision of following file

FSiMX6UL_FirstSteps_eng.pdf

for a description of how everything is installed and used. This doc sub-directory also contains other documentation, for example about the hardware of the boards and the starter kits.

Please note that Yocto releases use a 'Y' for the version number. The version counting is independent form other releases.

Content

The release consists of the following files and directories:

Warning The precompiled images are for testing and evaluation purposes only! DO NOT USE in production or mission-critical environments!

How to build

Use the latest F&S Development Machine from the F&S website To build the example release binaries, run:

Highlights

Here are some highlights of this release.

1. New Linux Kernel 6.6.142

The Linux kernel is now based on 6.6.142, which offers several new bug and security fixes.

2. Update U-Boot v2021.04-fs1.4

Fix several open CVEs. See sbom/cyclonedx/vex-u-boot-v2021.04-fs1.4.json for details.

3. New Yocto version 5.0.18 Scarthgap

Updating poky to Version 5.0.18 Scarthgap. Updating other layers to their latest commits.

The meta-fus layer in now split into meta-fus-bsp and meta-fus-sdk. The meta-fus-bsp layer adds basic board support, while meta-fus-sdk adds additional features, which are note necessary to run the board.

The meta-fus layer is now based on meta-freescale and not meta-imx. meta-freescale offers better long time support and more stable releases, while meta-imx supports the newest features but is not as stable and suitable for production. The meta-imx layers are still downloaded for reference, but not included into the build. If you need features from them, please consider adding the changes to your own meta-layer.

4. Improve linux-examples-fus

Update the examples to the new linux version.

5. New Docker based building system

The F&S releases now support Docker containers as default building machines. By using the Docker environment, the build process can be executed on any Linux host, as long as the Docker is installed. Starting FS_Development_Machine-Fedora-40_V0.2 Docker will be pre-installed and the development machines will not support support building the releases directly anymore.

If you do not want to use Docker, please check the Dockerfile for the dependencies. https://github.com/FSEmbedded/docker-fus/

1. Download manifest repository
   Code

   1. git clone -b fsimx6ul-Y2026.07 https://github.com/FSEmbedded/releases-fus.git
2. Prepare Yocto-Build environment Run setup-yocto to prepare your Yocto-Build environment. The script will read the repo manifest.xml file and syncs all repositories that are needed for Yocto.
   Code

   1. cd releases-fus/ ./setup-yocto <yocto-buildir>
3. Prepare Docker-Environment The ./setup-yocto script is capable of setting up a Docker environment in which the bitbake program can be executed for the Yocto system. This command will open a docker shell, where you can execute all yocto commands as usual.
   Code

   1. ./setup-yocto <yocto-buildir> --docker cd yocto-fus/

6. New Version naming for F&S Linux, U-Boot and meta-fus

Linux and U-Boot and meta-fus now get their own version number to be more transparent and flexible. The Version numbers reflect the Version of the original package, if needed the NXP version and the F&S Version. For example the linux version name is composed like this

[Version Orig. Kernel]-[Version IMX]-[Version FS]

linux-v6.6.101-2.2.1-fus1.0

This way it is easier to recognize the applied patch levels and the same package versions can be used in multiple releases.

The actual packages versions are marked as annotated tags in the git history. The Name of the overall release (like fsimx93-Y2025.08) is still set as a light tag.

7. New CVE Tracker Tool fs-cve-tracker

The F&S CVE Tracker Tool can help you to keep track of the current CVE status of your yocto image. It will launch a local version of Dependency Track and upload the SBOM of your Yocto Build to it. Dependency Track will scan your SBOM for vulnerabilities, which can be downloaded in VEX format. The F&S CVE Tracker Tool can also be used to improve your VEX file by marking already fixed CVEs or sorting out CVEs which affect components that are not in your build configuration.

You can also use Dependency Track to audit the remaining CVEs an generate Audit Reports for your documentation.

For a quick start you can run the following command after your Yocto Build has finished:

This command will install Dependency Track to your system, upload the SBOM from your build and improve your vulnerabilities scan to sort out as many false positives as possible.

Please note that this may take a while on first run.

8. Silex WLAN-Chip support

The Silex-WLAN Chip is supported in this release, but not enabled by default. To add it to the build, uncomment the following lines in the fs-release-manifest.xml

Known Issues

• No Blutetooth support for Silex and NXP WLAN driver

Changelog

The following list shows the most noticeable changes in this release in more detail since our last release for this platform. For a detailed description please check the respective git histories.

u-boot-v2021.04-fs1.4

• Fix several open CVEs

linux-v6.6.142-2.2.2-fus1.1

• Update to version 6.6.142
• Fix Linux CMA allocation for boards >= 2GB DRAM
• Update Silex Wlan driver to Kernel 6.6
• Add GPIO line names to the devicetrees

meta-fus-yocto-5.0.18-fus1.1

• Split meta-fus in meta-fus-bsp and meta-fus-sdk
• Update layer to yocto scarthgap
• Add dynamic layers for basler and qt6
• Clone fus specific gits from github again (Do not use the local gits anymore)
• Add additional test packages to the fus-image-sdt
• Use meta-freescale as base layer instead of meta-imx
• Add possibility to add Chromium and SPDX generation via the fus-setup-release script
• Add bcsend support to connect to the board via FSDeviceSpy
• Improve remote desktop support
• Add experimental kernel mainline support
• Add chromium support with NXP hardware acceleration patches
• Add OpenSSL Provider for SE050 security chip
• Update fus-image-std packages
• Update to Yocto 5.0.18
• Add F&S Release Name to fus-image-std
• Remove glmark2 from fus-image-std
• Only create SBOM for runtime-packages for now
• Add u-boot-fus explicitly to the CylconeDX SBOM
• Use NXP wlan driver as default driver

linux-examples-fus-fus1.1

• Port ADC test tool to i.MX8MM using the recommended IIO framework
• Migrate gpio.c from deprecated sysfs to libgpiod
• Upgrade PWM control to Hz and percentage with polarity support

nbootimx6ul_53 (VN53)

• Support additional boards
• Add quick memtest

Documentation

• FSiMX6UL_FirstSteps_eng.pdf
• LinuxOnFSBoards_eng.pdf

Please download the hardware documentation directly from our website. Then you always have the newest version.

For further support please contact us in the F&S Forum

Hello,

we use linux-fus-debug to get defconfig specific cve checks for our kernel.

If you also want to use this feature you could add a linux-fus-debug.bbappend in your layer and add

If you don't want to use this feature you could add the following line in your linux-fus-de.bb

or base your linux-fus-de.bb on linux-fus.inc and not linux-fus_6.6.bb

I hope this helps,

Your F&S Support Team

A F&S Development Machine with preinstalled fsimx6sx-Y2026.06 Release can be found here
New F&S Development Machine - Fedora40-arm32

F&S Development Machine with Fedora 40 arm32 V1.2 (26.06.2026)

There is a new Virtual Machine with Fedora40 in your download section available

My F&S / Tools-Linux /VirtualMachines/Fedora40/32-bit)/ F_S_Development_Machine-Fedora_40_arm32_V1.2.ova

The structure of the virtual machine is listed below.

Content:

• fsimx6-Y2026.06 (/home/developer/fsimx6-Y2026.06)
• fsimx6-B2026.05 (/home/developer/fsimx6-B2026.05)
• fsimx6sx-B2026.06 (/home/developer/fsimx6-B2026.06)

New Content:

• fsimx6sx-Y2026.06 (/home/developer/fsimx6-Y2026.06)

Removed Content:

-

A F&S Development Machine with preinstalled fsimx6-Y2026.06 Release can be found here
New F&S Development Machine - Fedora40-arm32

F&S i.MX6SX Yocto Release 2026.06 (fsimx6sx-Y2026.06)

This is a major release for F&S modules based on the i.MX6SX SoC, and the NXP lf-6.6.52-2.2.2 release.

Supported Boards

• efusA9X, efusA9r2X
• PicoCoreMX6SX
• PicoCOMA9X

Please see the new revision of following file

FSiMX6SX_FirstSteps_eng.pdf

for a description of how everything is installed and used. This doc sub-directory also contains other documentation, for example about the hardware of the boards and the starter kits.

Please note that Yocto releases use a 'Y' for the version number. The version counting is independent form other releases.

Content

The release consists of the following files and directories:

Warning The precompiled images are for testing and evaluation purposes only! DO NOT USE in production or mission-critical environments!

How to build

Use the latest F&S Development Machine from the F&S website To build the example release binaries, run:

Highlights

Here are some highlights of this release.

1. New Linux Kernel 6.6.142

The Linux kernel is now based on 6.6.142, which offers several new bug and security fixes.

2. Update U-Boot v2021.04-fs1.4

Fix several open CVEs. See sbom/cyclonedx/vex-u-boot-v2021.04-fs1.4.json for details.

3. New Yocto version 5.0.18 Scarthgap

Updating poky to Version 5.0.18 Scarthgap. Updating other layers to their latest commits.

The meta-fus layer in now split into meta-fus-bsp and meta-fus-sdk. The meta-fus-bsp layer adds basic board support, while meta-fus-sdk adds additional features, which are note necessary to run the board.

The meta-fus layer is now based on meta-freescale and not meta-imx. meta-freescale offers better long time support and more stable releases, while meta-imx supports the newest features but is not as stable and suitable for production. The meta-imx layers are still downloaded for reference, but not included into the build. If you need features from them, please consider adding the changes to your own meta-layer.

4. Improve linux-examples-fus

Update the examples to the new linux version.

5. New Docker based building system

The F&S releases now support Docker containers as default building machines. By using the Docker environment, the build process can be executed on any Linux host, as long as the Docker is installed. Starting FS_Development_Machine-Fedora-40_V0.2 Docker will be pre-installed and the development machines will not support support building the releases directly anymore.

If you do not want to use Docker, please check the Dockerfile for the dependencies. https://github.com/FSEmbedded/docker-fus/

1. Download manifest repository
   Code

   1. git clone -b fsimx6sx-Y2026.06 https://github.com/FSEmbedded/releases-fus.git
2. Prepare Yocto-Build environment Run setup-yocto to prepare your Yocto-Build environment. The script will read the repo manifest.xml file and syncs all repositories that are needed for Yocto.
   Code

   1. cd releases-fus/ ./setup-yocto <yocto-buildir>
3. Prepare Docker-Environment The ./setup-yocto script is capable of setting up a Docker environment in which the bitbake program can be executed for the Yocto system. This command will open a docker shell, where you can execute all yocto commands as usual.
   Code

   1. ./setup-yocto <yocto-buildir> --docker
   2. cd yocto-fus/

6. New Version naming for F&S Linux, U-Boot and meta-fus

Linux and U-Boot and meta-fus now get their own version number to be more transparent and flexible. The Version numbers reflect the Version of the original package, if needed the NXP version and the F&S Version. For example the linux version name is composed like this

[Version Orig. Kernel]-[Version IMX]-[Version FS]

linux-v6.6.101-2.2.1-fus1.0

This way it is easier to recognize the applied patch levels and the same package versions can be used in multiple releases.

The actual packages versions are marked as annotated tags in the git history. The Name of the overall release (like fsimx93-Y2025.08) is still set as a light tag.

7. New CVE Tracker Tool fs-cve-tracker

The F&S CVE Tracker Tool can help you to keep track of the current CVE status of your yocto image. It will launch a local version of Dependency Track and upload the SBOM of your Yocto Build to it. Dependency Track will scan your SBOM for vulnerabilities, which can be downloaded in VEX format. The F&S CVE Tracker Tool can also be used to improve your VEX file by marking already fixed CVEs or sorting out CVEs which affect components that are not in your build configuration.

You can also use Dependency Track to audit the remaining CVEs an generate Audit Reports for your documentation.

For a quick start you can run the following command after your Yocto Build has finished:

This command will install Dependency Track to your system, upload the SBOM from your build and improve your vulnerabilities scan to sort out as many false positives as possible.

Please note that this may take a while on first run.

Known Issues

• No Blutetooth support for Silex

Changelog

The following list shows the most noticeable changes in this release in more detail since our last release for this platform. For a detailed description please check the respective git histories.

u-boot-v2021.04-fs1.4

• Fix several open CVEs

linux-v6.6.142-2.2.2-fus1.0

• Update to version 6.6.142
• Fix Linux CMA allocation for boards >= 2GB DRAM
• Update Silex Wlan driver to Kernel 6.6

meta-fus-yocto-5.0.18-fus1.0

• Split meta-fus in meta-fus-bsp and meta-fus-sdk
• Update layer to yocto scarthgap
• Add dynamic layers for basler and qt6
• Clone fus specific gits from github again (Do not use the local gits anymore)
• Add additional test packages to the fus-image-sdt
• Use meta-freescale as base layer instead of meta-imx
• Add possibility to add Chromium and SPDX generation via the fus-setup-release script
• Add bcsend support to connect to the board via FSDeviceSpy
• Improve remote desktop support
• Add experimental kernel mainline support
• Add chromium support with NXP hardware acceleration patches
• Add OpenSSL Provider for SE050 security chip
• Update fus-image-std packages
• Update to Yocto 5.0.18
• Add F&S Release Name to fus-image-std
• Remove glmark2 from fus-image-std
• Only create SBOM for runtime-packages for now
• Add u-boot-fus explicitly to the CylconeDX SBOM

linux-examples-fus-fus1.1

• Port ADC test tool to i.MX8MM using the recommended IIO framework
• Migrate gpio.c from deprecated sysfs to libgpiod
• Upgrade PWM control to Hz and percentage with polarity support

nbootimx6sx_52 (VN52)

(no changes)

Documentation

• FSiMX6SX_FirstSteps_eng.pdf
• LinuxOnFSBoards_eng.pdf

Please download the hardware documentation directly from our website. Then you always have the newest version.

For further support please contact us in the F&S Forum

Hello,

you could either set the bootdelay in U-Boot to -2, but then you wont be able to enter the Uboot console again until you delete the environment!

Or you could add a special character using the CONFIG_AUTOBOOT_STOP_STR

https://github.com/FSEmbedded/…2d61fb/boot/Kconfig#L1347

You will have to add this config to your uboot fsimx8mp_defconfig and rebuild Uboot.

Your F&S Support Team

Hello Didier,

could it be, that your device sets the serial port to a state, that causes U-Boot to stop?

By default, when pressing any button in U-Boot in the first 3 seconds it will enter the shell and wait for input.

Could you try to connect your device, boot and then switch to the null-modem and press enter, to see if you are in the U-Boot shell?

Your F&S Support Team

Hello,

there where some delays when updating kernel and U-Boot.

The new fsimx6 Yocto release is out and we are currently working on fsimx6sx and fsimx6ul.

We decided to stay on U-Boot 2021.04 for now and patched the open CVEs.

It should be done much faster than imx6 because the groundwork is already done.

However, we will first release Buildroot ans Yocto short after

We plan to be finished end of this or start of next month.

Please excuse the inconvenience

Your F&S Support Team

F&S Development Machine with Fedora 40 arm32 V1.0 (09.06.2026)

There is a new Virtual Machine with Fedora40 in your download section available

My F&S / Tools-Linux /VirtualMachines/Fedora40/32-bit)/ F_S_Development_Machine-Fedora_40_arm32_V1.0.ova

The structure of the virtual machine is listed below.

Content:

• fsimx6-Y2026.06 (/home/developer/fsimx6-Y2026.06)
• fsimx6-B2026.05 (/home/developer/fsimx6-B2026.05)

New Content:

Removed Content:

F&S i.MX6 Yocto Release 2026.06 (fsimx6-Y2026.06)

This is a major release for F&S modules based on the i.MX6 SoC, and the NXP lf-6.6.52-2.2.2 release.

Supported Boards

• armStoneA9, armStoneA9r3
• armStoneA9r2, armStoneA9r4
• efusA9, efusA9r2
• PicoMODA9
• NetDCUA9

Please see the new revision of following file

FSiMX6_FirstSteps_eng.pdf

for a description of how everything is installed and used. This doc sub-directory also contains other documentation, for example about the hardware of the boards and the starter kits.

Please note that Yocto releases use a 'Y' for the version number. The version counting is independent form other releases.

Content

The release consists of the following files and directories:

Warning The precompiled images are for testing and evaluation purposes only! DO NOT USE in production or mission-critical environments!

How to build

Use the latest F&S Development Machine from the F&S website To build the example release binaries, run:

Highlights

Here are some highlights of this release.

1. New Linux Kernel 6.6.129

The Linux kernel is now based on 6.6.129, which offers several new bug and security fixes.

2. Update U-Boot v2021.04-fs1.4

Fix several open CVEs. See sbom/cyclonedx/vex-u-boot-v2021.04-fs1.4.json for details.

3. New Yocto version 5.0.17 Scarthgap

Updating poky to Version 5.0.17 Scarthgap. Updating other layers to their latest commits.

The meta-fus layer in now split into meta-fus-bsp and meta-fus-sdk. The meta-fus-bsp layer adds basic board support, while meta-fus-sdk adds additional features, which are note necessary to run the board.

The meta-fus layer is now based on meta-freescale and not meta-imx. meta-freescale offers better long time support and more stable releases, while meta-imx supports the newest features but is not as stable and suitable for production. The meta-imx layers are still downloaded for reference, but not included into the build. If you need features from them, please consider adding the changes to your own meta-layer.

4. Improve linux-examples-fus

Update the examples to the new linux version.

5. New Docker based building system

The F&S releases now support Docker containers as default building machines. By using the Docker environment, the build process can be executed on any Linux host, as long as the Docker is installed. Starting FS_Development_Machine-Fedora-40_V0.2 Docker will be pre-installed and the development machines will not support support building the releases directly anymore.

If you do not want to use Docker, please check the Dockerfile for the dependencies. https://github.com/FSEmbedded/docker-fus/

1. Download manifest repository
   Code

   1. git clone -b fsimx6-Y2026.06 https://github.com/FSEmbedded/releases-fus.git
2. Prepare Yocto-Build environment Run setup-yocto to prepare your Yocto-Build environment. The script will read the repo manifest.xml file and syncs all repositories that are needed for Yocto.
   Code

   1. cd releases-fus/ ./setup-yocto <yocto-buildir>
3. Prepare Docker-Environment The ./setup-yocto script is capable of setting up a Docker environment in which the bitbake program can be executed for the Yocto system. This command will open a docker shell, where you can execute all yocto commands as usual.
   Code

   1. ./setup-yocto <yocto-buildir> --docker cd yocto-fus/

6. New Version naming for F&S Linux, U-Boot and meta-fus

Linux and U-Boot and meta-fus now get their own version number to be more transparent and flexible. The Version numbers reflect the Version of the original package, if needed the NXP version and the F&S Version. For example the linux version name is composed like this

[Version Orig. Kernel]-[Version IMX]-[Version FS]

linux-v6.6.101-2.2.1-fus1.0

This way it is easier to recognize the applied patch levels and the same package versions can be used in multiple releases.

The actual packages versions are marked as annotated tags in the git history. The Name of the overall release (like fsimx93-Y2025.08) is still set as a light tag.

7. Experimental Mainline Kernel support

We have added a patchset to enable mainline kernel support for fsimx6 boards to the meta-fus layer. You can test it by adding the following line to your conf/local.conf file in your yocto build directory:

Most of the peripheries are working. We are planning to enable the mainline kernel for older architectures per default. For further support please contact the F&S Forum.

8. New CVE Tracker Tool fs-cve-tracker

The F&S CVE Tracker Tool can help you to keep track of the current CVE status of your yocto image. It will launch a local version of Dependency Track and upload the SBOM of your Yocto Build to it. Dependency Track will scan your SBOM for vulnerabilities, which can be downloaded in VEX format. The F&S CVE Tracker Tool can also be used to improve your VEX file by marking already fixed CVEs or sorting out CVEs which affect components that are not in your build configuration.

You can also use Dependency Track to audit the remaining CVEs an generate Audit Reports for your documentation.

For a quick start you can run the following command after your Yocto Build has finished:

This command will install Dependency Track to your system, upload the SBOM from your build and improve your vulnerabilities scan to sort out as many false positives as possible.

Please note that this may take a while on first run.

Known Issues

• PCIe does not work correctly with some cards.

Changelog

The following list shows the most noticeable changes in this release in more detail since our last release for this platform. For a detailed description please check the respective git histories.

u-boot-v2021.04-fs1.4

• Fix several open CVEs

linux-v6.6.129-2.2.2-fus1.3

• Update to version 6.6.129
• Fix Linux CMA allocation for boards >= 2GB DRAM
• armstonea9/netdcua9: Change spi cs to gpio cs

meta-fus-yocto-5.0.17-fus1.1

• Split meta-fus in meta-fus-bsp and meta-fus-sdk
• Update layer to yocto scarthgap
• Add dynamic layers for basler and qt6
• Clone fus specific gits from github again (Do not use the local gits anymore)
• Add additional test packages to the fus-image-sdt
• Use meta-freescale as base layer instead of meta-imx
• Add possibility to add Chromium and SPDX generation via the fus-setup-release script
• Add bcsend support to connect to the board via FSDeviceSpy
• Improve remote desktop support
• Add experimental kernel mainline support
• Add chromium support with NXP hardware acceleration patches
• Add OpenSSL Provider for SE050 security chip
• Update fus-image-std packages
• Update to Yocto 5.0.17
• Add F&S Release Name to fus-image-std
• Remove glmark2 from fus-image-std
• Only create SBOM for runtime-packages for now

linux-examples-fus-fus1.1

• Port ADC test tool to i.MX8MM using the recommended IIO framework
• Migrate gpio.c from deprecated sysfs to libgpiod
• Upgrade PWM control to Hz and percentage with polarity support

nbootimx6_51.bin (VN51)

(no changes)

Documentation

• FSiMX6_FirstSteps_eng.pdf
• LinuxOnFSBoards_eng.pdf

Please download the hardware documentation directly from our website. Then you always have the newest version.

For further support please contact us in the F&S Forum

F&S armStoneMX8MPr2 Yocto Release 2025.12 (armstonemx8mpr2-Y2025.12)

This is a minor release for the armStonemx8MPr2 module based on the i.MX8MP SoC, and the NXP lf-6.6.52-2.2.2 release.

Please note, that this release only supports the board armStoneMX8MPr2. Also there will be no F&S Development Machine, containing this release. It will be added in the next fsimx8mp-Y2025.12.1 release soon.

Supported Boards

• armStoneMX8MPr2

Please see the new revision of following file

FSiMX8MP_FirstSteps_eng.pdf

for a description of how everything is installed and used. This doc sub-directory also contains other documentation, for example about the hardware of the boards and the starter kits.

Please note that Yocto releases use a 'Y' for the version number. The version counting is independent form other releases.

Content

The release consists of the following files and directories:

Warning The precompiled images are for testing and evaluation purposes only! DO NOT USE in production or mission-critical environments!

How to build

Use the latest F&S Development Machine from the F&S website To build the example release binaries, run:

Highlights

Here are some highlights of this release.

1. New Linux Kernel 6.6.129

Add armstonemx8mpr2 support.

2. Update U-Boot v2024.04-fus1.8

Add armstonemx8mpr2 support.

3. New Yocto version 5.0.17 Scarthgap

Add armstonemx8mpr2 support.

Known Issues

Changelog

The following list shows the most noticeable changes in this release in more detail since our last release for this platform. For a detailed description please check the respective git histories.

u-boot-v2024.04-fus1.8

• Add armstonemx8mpr2 support

linux-v6.6.129-2.2.2-fus1.4

• Add armstonemx8mpr2 support

meta-fus-yocto-5.0.17-fus1.2

• Add armstonemx8mpr2 support

linux-examples-fus-fus1.1

(no changes)

nboot-fsimx8mp-2026.05

• Add armstonemx8mpr2 support

Documentation

• FSiMX8MP_FirstSteps_eng.pdf
• LinuxOnFSBoards_eng.pdf

Please download the hardware documentation directly from our website. Then you always have the newest version.

For further support please contact us in the F&S Forum

Hello,

yes we have scheduled a Yocto 5.0 release with kernel 6.6 for Q2.

Your F&S Support Team

F&S Development Machine with Fedora 40 V1.5 (28.04.2026)

There is a new Virtual Machine with Fedora40 in your download section available

My F&S / Tools-Linux /VirtualMachines/Fedora40/64-bit/ F_S_Development_Machine-Fedora_40_V1.5.ova

The structure of the virtual machine is listed below.

Content:

• fsimx8mp-Y2025.12 (/home/developer/fsimx8mp-Y2025.12)
• fsimx93-Y2025.08.1 (/home/developer/fsimx93-Y2025.08.1)

• fsimx8mm-Y2026.04 (/home/developer/fsimx8mm-Y2025.04)
• fsimx8ulp-Y2025.11.1 (/home/developer/fsimx8ulp-Y2025.11.1)

New Content:

• Added a new Docker Version, that supports the docker compose plugin