F&S Development Machine with Fedora 40 V1.7 (01.10.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.7.ova

The structure of the virtual machine is listed below.

Content:

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

New Content:

• fsimx8mm-B2026.07.1 (/home/developer/fsimx8mm-B2026.07.1)
• fsimx93-Y2025.08.2 (/home/developer/fsimx93-Y2025.08.2)

Removed Content:

• fsimx8mm-B2026.07 (/home/developer/fsimx8mm-B2026.07)
• fsimx93-Y2025.08.1 (/home/developer/fsimx93-Y2025.08.1)

F&S i.MX8MM Buildroot Release 2026.07.1 (fsimx8mm-B2026.07.1)

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

Supported Boards

• PicoCoreMX8MM-DDR3L
• PicoCoreMX8MM-LPDDR4
• PicoCoreMX8MMr2-LPDDR4
• PicoCoreMX8MMr4-LPDDR4
• OSM-SF-MX8MM

Please see the new revision of following file

FSiMX8MM_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 Buildroot releases use a 'B' 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.147

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

2. New bootloader U-Boot 2024.04

The U-Boot is now based on 2024.04.

[!CAUTION]
To update from older releases, please:

1. Install U-Boot first
2. Then reset the board to start the new U-Boot
3. Then install NBoot.

3. New Buildroot version 2025.02.17

Buildroot now has a 3-year LTS cycle starting with 2025.02 with a patch level upgrade aproximatly every month.

Since the last release most packages have been updated to more current versions and sbom support has been implemented.

4. Improve linux-examples-fus

Update the examples to the new linux version.

5. Improve linux-examples-fus

Update the examples to the new linux version.

6. 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 fsimx8mm-2026.07.1 https://github.com/FSEmbedded/releases-fus.git

2. Prepare Buildroot-Build environment
   Run setup-buildroot to prepare your Buildroot-Build environment. The script will read the repo manifest.xml
   file and syncs all repositories that are needed for Buildroot.

   Code

   1. cd releases-fus/
   2. ./setup-buildroot

3. Prepare Docker-Environment
   The ./setup-buildroot script is capable of setting up a Docker environment in which the bitbake program
   can be executed for the Buildroot system. This command will open a docker shell, where you can execute
   all buildroot commands as usual.

   Code

   1. ./setup-buildroot --docker
   2. cd buildroot-fus/

7. New Version naming for F&S Linux, U-Boot and buildroot-fus

Linux, U-Boot and buildroot-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.

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 buildroot image.
It will launch a local version of Dependency Track and upload the SBOM
of your Buildroot 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 Buildroot 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

SD-Card detect will not work correctly on the PCore-BBDSI Starterkit. If you want to test SD-Card, you can add
the device tree flag "broken-cd" to the sdcard-node. This will be fixed in the next BBDSI revision.

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.9

• Add PicoCoreMX8MMr4 support

linux-v6.6.147-2.2.2-fus1.0

• Add PicoCoreMX8MMr4 suport
• Increase patch level of the kernel

buildroot-2025.02.17-fus1.0

• Increase buildroot patch level
• Add moal wlan driver to fsimx8mm defconfigs
• Add IW612 WLAN/BT firmware to fsimx8mm_defconfigs

atf-v2.10-fus1.4

• No changes

nboot-2026.08

• Add PicoCoreMX8MMr4 support

linux-examples-fus-fus1.1

• No changes

Documentation

• FSiMX8MM_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,

for Buildroot, we do not plan adding new platforms. A Yocto release with support for Boards with the i.MX8M Nano is still scheduled for this year.

Your F&S support Team

F&S Development Machine with Fedora 40 V1.6 (31.07.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.6.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)
• Added a new Docker Version, that supports the docker compose plugin

New Content:

• fsimx8mm-B2026.07 (/home/developer/fsimx8mm-B2026.07)

F&S i.MX8MM Buildroot Release 2026.07 (fsimx8mm-B2026.07)

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

Supported Boards

• PicoCoreMX8MM-DDR3L
• PicoCoreMX8MM-LPDDR4
• PicoCoreMX8MMr2-LPDDR4
• OSM-SF-MX8MM

Please see the new revision of following file

FSiMX8MM_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 'B' 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. New bootloader U-Boot 2024.04

The U-Boot is now based on 2024.04.

[!CAUTION]
To update from older releases, please:

1. Install U-Boot first
2. Then reset the board to start the new U-Boot
3. Then install NBoot.

3. New Buildroot version 2025.02.16

Buildroot now has a 3-year LTS cycle starting with 2025.02 with a patch level upgrade aproximatly every month.

Since the last release most packages have been updated to more current versions and sbom support has been implemented.

4. Improve linux-examples-fus

Update the examples to the new linux version.

3. Improve linux-examples-fus

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 fsimx8mm-B2026.07 https://github.com/FSEmbedded/releases-fus.git

2. Prepare Buildroot-Build environment
   Run setup-buildroot to prepare your Buildroot-Build environment. The script will read the repo manifest.xml
   file and syncs all repositories that are needed for Buildroot.

   Code

   1. cd releases-fus/
   2. ./setup-buildroot

3. Prepare Docker-Environment
   The ./setup-buildroot script is capable of setting up a Docker environment in which the bitbake program
   can be executed for the Buildroot system. This command will open a docker shell, where you can execute
   all buildroot commands as usual.

   Code

   1. ./setup-buildroot --docker
   2. cd buildroot-fus/

5. New Version naming for F&S Linux, U-Boot and buildroot-fus

Linux, U-Boot and buildroot-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.

6. 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 buildroot image.
It will launch a local version of Dependency Track and upload the SBOM of your Buildroot 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 Buildroot 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

SD-Card detect will not work correctly on the PCore-BBDSI Starterkit. If you want to test SD-Card, you can add the device tree flag "broken-cd" to the sdcard-node. This will be fixed in the next BBDSI revision.

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

• Update to U-Boot version 2024.04
• Add OP-TEE Support per default
• Add Secure-Boot support per default
• Add option to group ATF/TEE with U-Boot image
• Improve boot from device environment handling

linux-v6.6.142-2.2.2-fus1.1

• Merge fsimx8mm/mp/mn_defconfigs into single fsimx8_defconfig
• Update to version 6.6.129
• Fix OSM8MM USB host
• Fix fsimx8mm sdcard reset
• Remove unneeded Pull-Ups and Pull-Downs

buildroot-2025.02.15-fus1.0

• Improve fsmx8mm defconfigs
• Update ftom buildroot-2025.02.15 to buildroot-2025.02.16
• Fix Weston version selection and improve weston setup for init.d
• Add new boards and display devicetrees for fsimx8mm

atf-v2.10-fus1.4

• Apply changes from lf-6.6.52-2.2.2

nboot-2026.03

• Update to U-Boot version 2024.04

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

Documentation

• FSiMX8MM_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 Development Machine with Fedora 40 arm32 V1.3 (09.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.3.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)

New Content:

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

Removed Content:

-

F&S i.MX6UL Buildroot Release 2026.07 (fsimx6ul-B2026.07)

This is a major release for F&S modules based on the i.MX6UL SoC,
based on 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 Buildroot releases use a 'B' 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. New LTS Buildroot version 2025.02.15

Buildroot now has a 3-year LTS cycle starting with 2025.02 with a patch level upgrade aproximatly every month.

Since the last release most packages have been updated to more current versions and sbom support has been implemented.

3. Improve linux-examples-fus

Update the examples to the new linux version.

4. 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.3 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-B2026.07 https://github.com/FSEmbedded/releases-fus.git

2. Prepare Buildroot-Build environment
   Run setup-buildroot to prepare your Buildroot-Build environment. The script will read the repo manifest.xml
   file and syncs all repositories that are needed for Buildroot.

   Code

   1. cd releases-fus/
   2. ./setup-buildroot

3. Prepare Docker-Environment
   The ./setup-buildroot script is capable of setting up a Docker environment in which the bitbake program
   can be executed for the Buildroot system. This command will open a docker shell, where you can execute
   all buildroot commands as usual.

   Code

   1. ./setup-buildroot --docker
   2. cd buildroot-fus/

5. New Version naming for F&S Linux, U-Boot and buildroot-fus

Linux, U-Boot and buildroot-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.

6. 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 buildroot image.
It will launch a local version of Dependency Track and upload the SBOM
of your Buildroot 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 Buildroot 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.

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

• Add GPIO line names to the devicetrees
• Fix reassignment of values in the defconfig
• Fix fsimx6ul clocks
• Fix LVDS converter on picocoremx6ul100

buildroot-2025.02.15-fus1.0

• Improve fsimx6ul defconfigs
• Update to from buildroot-2025.02.13 to 2025.02.15
• Improve silex recipes and kernel patching
• Fix version detection for weston during configuration
• Improve TSC2004 udev rule

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.bin (VN53)

• more boards supported
• 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

F&S Development Machine with Fedora 40 arm32 V1.1 (18.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.1.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:

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

Removed Content:

F&S i.MX6SX Buildroot Release 2026.06 (fsimx6sx-B2026.06)

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

Supported Boards

• efusA9X
• efusA9Xr2
• 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 Buildroot releases use a 'B' 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. New LTS Buildroot version 2025.02.13

Buildroot now has a 3-year LTS cycle starting with 2025.02 with a patch level upgrade aproximatly every month.

Since the last release most packages have been updated to more current versions and sbom support has been implemented.

3. Improve linux-examples-fus

Update the examples to the new linux version.

4. 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.3 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-B2026.06 https://github.com/FSEmbedded/releases-fus.git

2. Prepare Buildroot-Build environment Run setup-buildroot to prepare your Buildroot-Build environment. The script will read the repo manifest.xml file and syncs all repositories that are needed for Buildroot.

   Code

   1. cd releases-fus/
   2. ./setup-buildroot <buildroot-buildir>

3. Prepare Docker-Environment The ./setup-buildroot script is capable of setting up a Docker environment in which the bitbake program can be executed for the Buildroot system. This command will open a docker shell, where you can execute all buildroot commands as usual.

   Code

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

5. New Version naming for F&S Linux, U-Boot and buildroot-fus

Linux, U-Boot and buildroot-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.

6. 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 buildroot image. It will launch a local version of Dependency Track and upload the SBOM of your Buildroot 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 Buildroot 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.

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.4.1

• Unify defconfigs of fsimx6, fsimx6l and fsimx6sx
• Fix Power Managent warning regarding fsimx6sx Boards without GPU
• Add Silex driver for Linux 6.6

buildroot-2025.02.13-fus1.1

• Improve fsimx6sx defconfigs
• Improve imx-gstreamer recipes for Linux 6.6
• Improve silex-wlanbt-fs package for Linux 6.6

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

• 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

F&S i.MX6 Buildroot Release 2026.05 (fsimx6-B2026.05)

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

Supported Boards

• armStoneA9
• armStoneA9r2
• armStoneA9r3
• armStoneA9r4
• efusA9
• efusA9r2
• PicoMADA9
• 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 Buildroot releases use a 'B' 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. New LTS Buildroot version 2025.02.13

Buildroot now has a 3-year LTS cycle starting with 2025.02 with a patch level upgrade aproximatly every month.

Since the last release most packages have been updated to more current versions and sbom support has been implemented.

3. Improve linux-examples-fus

Update the examples to the new linux version.

4. 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.3 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-B2026.05 https://github.com/FSEmbedded/releases-fus.git

2. Prepare Buildroot-Build environment Run setup-buildroot to prepare your Buildroot-Build environment. The script will read the repo manifest.xml file and syncs all repositories that are needed for Buildroot.

   Code

   1. cd releases-fus/
   2. ./setup-buildroot <buildroot-builddir>

3. Prepare Docker-Environment The ./setup-buildroot script is capable of setting up a Docker environment in which the bitbake program can be executed for the Buildroot system. This command will open a docker shell, where you can execute all buildroot commands as usual.

   Code

   1. ./setup-buildroot --docker
   2. cd buildroot-fus

5. New Version naming for F&S Linux, U-Boot and buildroot-fus

Linux, U-Boot and buildroot-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.

6. 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 buildroot image. It will launch a local version of Dependency Track and upload the SBOM of your Buildroot 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 Buildroot 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.

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
• armstonea9/netdcua9: Change spi cs to gpio cs

buildroot-2025.02.13-fus1.0

• Update to Buildroot LTS version 2025.02.13
• Update NXP packages to lf-6.6.52-2.2.2
• Switch to Buildroot provided Toolchain
• Remove deprecated package ramspeed
• Fix Linux version ID for SBOM generation

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

• FSiMX8MM_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,

the PicoCoreMX8MP and the PicoCoreMX8MPr2 have different u-boot devicetrees. Thus you need to add the same fix as the last time for the other devicetree. I appended two patches, one that only fixes r2, in the same way as last time, and another one that combines both patches into one. I hope this solves your issue.

Your F&S support team.

0001-Use-M7-DDR-as-shared-Memory-on-all-PicocoreMX8MP.patch

0001-Use-M7-DDR-as-shared-Memory-on-PicocoreMX8MPr2.patch

F&S i.MX8MM FreeRTOS Release V2026.04

This is a maintenance release for FreeRTOS BSP. This software can be used for all boards from F&S that are based on the i.MX8MM CPU from Freescale/NXP. Currently this is the Systems-on-Module (SOM) PicoCoremx8MM and FS 8MM OSM-SF. Further may be added to this family in the future. All these boards can work with software that is created from this release package.

The following list shows the most noticeable changes in this release in more detail since our last regular i.MX8MM FreeRTOS-BSP release. Please note that the source code is also used for other platforms. This is why you will also find references to other CPU types and F&S boards here in the changelog.

freertos-fsimx8mm-V2026.04.tar.bz2

This is the main release itself containing all sources, the binary images, the documentation, examples and the toolchain.

This tar archive is compressed with bzip2. So to see the files, you first have to unpack the archives

This will create a directory freertos-fsimx8mm-V2026.04 that contains all the files of the release.

For any questions regarding the usage of the examples please refer to the document doc/FreeRTOS_on_FSiMX8MM_Boards.pdf. It lists the purpose of all files and shows how to install and use everything.

Release Notes freertos-fsimx8mm-V2026.04

================================================================================

freertos-sdk-25.03-fsimx8mm-V2026.04 (09.04.2026)

-----------------------------------------------------------------------------

Supported boards: PicoCoreMX8MM, PicoCoreMX8MX, FS-OSM-8MM

- Original NXP MCUXpresso SDK_25_03_00_MIMX8MM6xxxLZ

- Move not ported examples to not_ported_examples/fsimx8mm

- Rename boards/evkmimx8mm directory to boards/fsimx8mm

- Fix syntax error in fsl_ecspi_cmsis.c

- Add .gitignore

- Add PicoCoreMX8MM and PicoCoreMX8MX support

- Rename base XML File

- Modify the examples for use with SEGGER J-Link

- Add osm8mm support

- Add support for building and cleaning all examples

- Change order of wdog example steps

Toolchain

---------------

new gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2

Documentation

------------------------

- Version 1.2 of FreeRTOS_on_FSiMX8MM_Boards.pdf

Hello Festus,

I can see two faults from your Information.

1. from what I can tell by your dd comand you might be writing to the wrong device. /dev/sdb looks like an usb device to me. Your SD card should look like /dev/mmcblk[dev number].

2. While the other Post you linked set mmcdev, the right variable on A9 Boards is usdhcdev. Set it to your SD card before running "run .rootfs_mmc" to your SD card. This command also assumes user partition 2, as the command is writen for mmc based Boards which always uses that partition for the rootfs. You can simply change te partition by editing the rootfs environment variable.

Here are the commands I used:

I tested the comands on the fsimx6-Y2024.04.1 release.

F&S Secure Boot Releae 2025.09 (fs-secure-boot-V2025.09)

This is a maintenance release for all F&S Boards with i.MX HAB support based on the fsimx6sx-2024.12 release.

Supported platforms

• fsimx6
• fsimx6ul
• fsimx6sx
• fsimx8mm
• fsimx8mn
• fsimx8mp

Please see the new revision of the following file

FS_Secure_boot.pdf

Highlights

Here are some of te Highlights of this release.

1. Secure U-Boot updated to 2021.04

• Secure Boot for fimx8mm, fsimx8mn and fsimx8mp is now compatible with the improved NBoot.
• secure boot configs for fsimx6, fsimx6ul and fsimx6sx have been updated to build an image small enough to be signed for NAND.
• Saving signed NBoots through the U-Boot has been made more robust
• Add hab_fuse and hab_close commands for fsimx8mm, fsimx8mn and fsimx8mp

2. fs-secure-boot-tool updated to V2025.09

• The tool has been updated to work with the improved NBoot.

3. op-tee updated to lf-5.15.71-2.2.1

• op-tee has been updated to 5.15.71-2.2.1 for better stability

Hello ETCE_SWD ,

when I use fsimx8mp-Y2024.07, I can see spidev1.0, spidev2.0 and spidev3.0. Can you please provide the output of the following commands?

cat /proc/device-tree/soc\@0/bus\@30800000/spi\@30820000/status

cat /proc/device-tree/soc\@0/bus\@30800000/spi\@30830000/status

cat /proc/device-tree/soc\@0/bus\@30800000/spi\@30840000/status

dmesg | grep -i spi

Your F&S support Team

Hello FaBier,

I have used the CAAM module for partition encryption in fsimx6-Y2024.04. I did not get the error messages you wrote. Do you get the error messages at boot or while working with the keys? I used caam-keygen to generate the keys, and managed them with keyctl. Do you use the same tools?

Your F&S support Team

Hello FaBier,

thank you for reaching out. We will take a look at this. If we need more Information, we will message you in this thread.

Your F&S support Team

Hello,

after investigating we have found a solution. In fsimx8mp-Y2024.07 we added RDC (ressource domain controller) configurations. These change which Domain has access to which part of the System. The Memory you are using is only accessible by the M7-Core after it is started. After stopping it, the Memory Configuration will be changed to the default where all domains have access.

To use the range as shared Memory you need to change a line in the file arch/arm/dts/picocoremx8mp-u-boot.dtsi (or the <boardname>-u-boot.dtsi of the board you are using)

You will need to change line 31 from

to

this will grant both Domains access to the Memory when the M-Core is running.

I appended a Patch with this change you can apply in uboot.

Your F&S support team.

Hello,

thank you for reaching out to us. The Information you gave in this thread will help us finding a solution. We will take a look at this and answer this thread as soon as we have new Information.

Your F&S support team.

F&S i.MX8MP FreeRTOS Release V2024.09

We have uploaded a new FreeRTOS version for boards and modules based on the i.MX8MP CPU to our server, i.e. the fsimx8mp architecture: PicoCoreMX8MP, armStoneMX8MP, efusMX8MP and FSSMMX8MP. This release is running on all platforms of this architecture.

This is a maintenance release. The release consists of the following file:

freertos-sdk-2.15.0-fsimx8mp-V2024.09.tar.bz2

This is the main release itself containing all sources, the binary images, the required NBoot version 2024.06, the documentation, examples and the toolchain.

This tar archive is compressed with bzip2. So to see the files, you first have to unpack the archives

This will create a directory freertos-sdk-2.15.0-fsimx8mp-V2024.09 that contains all the files of the release.

Please install the required NBoot version 2024.06 (included in this release) or higher.

For any questions regarding the usage of the examples please refer to the document doc/FreeRTOS_on_FSiMX8MP_Boards.pdf. It lists the purpose of all files and shows how to install and use everything.

Release Notes freertos-sdk-2.15.0-fsimx8mp-V2024.09

================================================================================

The following list shows the most noticable changes in this release in more detail. Please note that the source code is also used for other platforms. This is why you might also find references to other CPU types and F&S boards here in the changelog.

freertos-sdk-2.15.0-fsimx8mp-V2024.09 (15.07.2021)

----------------------------------------------------------------------------

Supported boards: PicoCoreMX8MP, armStoneMX8MP, efusMX8MP, FSSMMX8MP

Not tested: PicoCoreMX8MM, efusA9X, PicoCOMA9X, PicoCoreMX6SX, PicoCoreMX7ULP

- [fsimx8mp]: Move not ported examples to not_ported_examples

- [fsimx8mp]: Add possibility to build all examples at once

- [fsimx8mp]: Add PicoCoreMX8MP support

- [fsimx8mp]: Rename boards directory to fsimx8mp

- [fsimx8mp]: Change the rtos example directory to freertos in accordance with SDK2.15

- [fsimx8mp]: Fix building all examples in 2.15.0

- [fsimx8mp]: Add armstoneMX8MP support

- [fsimx8mp]: Add efusMX8MP support

- [fsimx8mp]: Add FSSMMX8MP support

- [fsimx8mp]: Modify the examples for use with SEGGER J-Link

- [fsimx8mp]: Rename base XML File

- [fsimx8mp]: Add default build type

- [fsimx8mp]: Fix SDMA examples

Toolchain

- new toolchain gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2

Documentation

- Updated version 1.3 of FreeRTOS_on_FSiMX8MM_Boards.pdf

Your F&S Support Team