F&S MX8MM Yocto Release Y2024.10 (fsimx8mm-Y2024.10)

This is a maintenance release for F&S modules of the i.MX8MM SoC family, based on the NXP lf-5.15.71_2.2.2 release.

Supported Boards

• PicocoreMX8MM-DDR3L
• PicocoreMX8MM-LPDDR4
• PicocoreMX8MMr2-LPDDR4
• FS8MMOSM-SF

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 'Y' for the version number. The version counting is independent form other releases.

Content

The release consists of the following files and directories:

How to build

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

Code

1. git clone -b fsimx8mm-Y2024.10 https://github.com/FSEmbedded/releases-fus.git
2. cd releases-fus
3. ./setup-yocto <build_dir>
4. cd <build_dir>/yocto-fus
5. DISTRO=fus-imx-wayland MACHINE=fsimx8mm . fus-setup-release.sh
6. bitbake fus-image-std

Highlights

Here are some highlights of this release.

1. Update Linux Kernel to patch level 5.15.160

This fixes several smaller bugs and CVEs.

For more information please see

https://cdn.kernel.org/pub/lin…el/v5.x/ChangeLog-5.15.72

to

https://cdn.kernel.org/pub/lin…l/v5.x/ChangeLog-5.15.160

Also adds support for the new F&S LVDS Displays and improves the

Cortex-M support in Linux and adds SPI-NOR flash support to the

efusmx8mp.

2. Improved boot loader U-Boot 2021.04

Several bug fixes and improvements, like the Resource Domain Control

support in U-Boot device tree and an improved xhci USB driver.

3. Tested with Yocto poky layer version 4.0.20

This fixes several smaller bugs and CVEs, like CVE-2024-6387 OpenSSH

signal handler race condition.

For more information, please see

https://docs.yoctoproject.org/…release-notes-4.0.19.html

to

https://docs.yoctoproject.org/…release-notes-4.0.20.html

Adding support for FSOSM8MM

Adding support for the FSOSM8MM modules to the architecture specific releases

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-2021.04-fsimx8mm-2024.10

• Add support for OSM8MM
• Include imx_tmu driver for fsimx8m(m/n/p)
• Fix USB handling for fsimx8mm
• Adjust size of CMA only for DRAM > 1GB

linux-5.15.160-fsimx8mm-2024.10

• Add support for OSM8MM
• Use bitbanging for SPI_A on ADP-OSM-BB
• Handle backlight control better for OSM8MM
• Update version of PCoreBBDSI for fsimx8mm
• Fix basler support for fsimx8mm
• Fix pwm frequency for pca963x

meta-fus-fsimx8mm-2024.10

• Add support for OSM8MM
• Fix name for new display Device-Tree from PicoCoreMX8MMr2-LPDDR4

linux-examples-fus-fs1

(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 FSInstaller is exactly for the USB serial download mode. You can connect the BOOT_SELn_1V8 to the neighboring GND pin at a cold start. The device should now be recognized by the FSInstaller and flashing should now be possible. Be sure to enter the correct serial number of the board.

The memory layout did change over the versions of the NBoot, so the old UBoot probably flashed the new UBoot to a wrong starting block.

If hope this helps you so far.

Your F&S Support Team

There is an update for the newer ADP-OSM-BB revision 1.30 and a fix for highspeed USDHC cards on SDIO_A.

This is available in the release osm8mp-Y2025.04.1: GitHub - FSEmbedded/releases-fus at osm8mp-Y2025.04.1

Your F&S Support Team

There is an update for the newer ADP-OSM-BB revision 1.30 and a fix for highspeed USDHC cards on SDIO_A.

This is available in the release osm8mm-Y2024.10.2: GitHub - FSEmbedded/releases-fus at osm8mm-Y2024.10.2

Your F&S Support Team

Hello Didier,

• UART_B is the direct UART signal with TTL, so a RS232 transceiver is still needed. For revision 1.00 switch the RX- and TX-signal.
• UART_C on pin 36 + 38 should already be the RS232 signals and active. No need to change the device-tree. You will need to make sure that pin 23 + 25 are left open, as the TTL signals also get rooted there.

Your F&S Support Team

Hello Didier,

it is the label on the HDMI port, but revision 1.00 is enough.

For UART_B the RX and TX pads are switched, but you can set them right via the pinctrl in the Device-Tree.

Under arch/arm64/boot/dts/F+S/armstonemx8mp.dtsi:

You will need to change this to the following:

This bug is only present at revision 1.00 of the armStoneMX8MP. As revision 1.10 is already out, please contact Support@fs-net.de with this.

Your F&S Support Team

Hello,

for UART_B and UART_C there are different hardware variants. Could you post the revision of your board as well as the serial number on the label?

If you do not want to share the serial number here, you can also write an E-Mail to support@fs-net.de with the information and a short summary of the problem with the UART_B and UART_C.

For the hardware options:

• UART_B on pins 13 + 15 can be RS485 or TTL signals directly (default is RS485 on Rev. 1.10)
• UART_C on pins 36 + 38 can be RS232 from UART_C or RS232 from UART_D (default is RS232 from UART_C)

I hope this clarifies the connector pins a bit. For more information I will need the revision and the serial number of the board you are using.

Your F&S Support Team

Hello,

the mipi-dsi unit waits for the DRM-chain to successfully load. There is a MIPI2LVDS converter on the PicoCore module, which gets initialized pretty late in the logs:

As you can see, the converter gets initialized correctly and afterwards the framebuffer is allocated.

Could you check if the backlight is activated for the display? Meanwhile, we will test this on our side.

Your F&S Support Team

F&S i.MX8M-Plus OSM specific Yocto Release 2025.04 (osm8mp-Y2025.04)

Please see the file

doc/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.

This is a maintenance release specific for the module "FS 8MP OSM-SF".

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

The release consists of the following files and directories:

• README.txt Release notes (this text)
• setup-yocto Script to download and install the Yocto release
• fs-release-manifest.xml Release Manifest, containing the used versions as git hashes
• binaries/ Precompiled images (full names)
• sdcard/ Precompiled images (names as expected by install script)
• doc/ Hardware and software manuals, schematics

Here are some highlights of this release.

1. Update Linux Kernel to patch level 5.15.160

This fixes several smaller bugs and CVEs.

For more information please see

https://cdn.kernel.org/pub/lin…el/v5.x/ChangeLog-5.15.72

to

https://cdn.kernel.org/pub/lin…l/v5.x/ChangeLog-5.15.160

Also adds support for the new F&S LVDS Displays and improves the Cortex-M support in Linux and adds SPI-NOR flash support to the efusmx8mp.

2. Improved boot loader U-Boot 2021.04

Several bug fixes and improvements, like the Resource Domain Control support in U-Boot device tree and an improved xhci USB driver.

3. Tested with Yocto poky layer version 4.0.20

This fixes several smaller bugs and CVEs, like CVE-2024-6387 OpenSSH signal handler race condition.

For more information, please see

https://docs.yoctoproject.org/…release-notes-4.0.19.html

to

https://docs.yoctoproject.org/…release-notes-4.0.20.html

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

The following list shows the most noticeable changes in this release in more detail since our last release for this platform.

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 change log.

u-boot-v2021.04-fs1.0

Supported boards: OSM8MP

- Add support for OSM8MP

linux-v5.15.160-fs1.0

Supported boards: OSM8MP

- Fix old display for fssmmx8mp

- Enable mipi-csi (CSI_B) for fssmmx8mp

- Fix USB OTG role detection on fssmmx8mp

- Handle 0-bits in empty pages

- Add support for OSM8MP

meta-fus-yocto-4.0.20-fs1.0

Supported boards: OSM8MP

- fs-setup-release: ensures active shell, when sourced script failes

- Add support for OSM8MP

- Use only annotated Tag for UBoot version

- Remote "-F+S" from UBoot header under Yocto

atf-5.15.71-fsimx8mp-2024.07

Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP efusMX8MP FSSMMX8MP OSM8MP

- Fix poweroff command and ON/OFF button in imx_system_off()

- Fix debug build console for fsimx8mp

firmware-imx-8.10.1 ddr synopsys

(no changes)

linux-examples-fus-fs1

(no changes)

Documentation

- Update to version 1.8 of FSiMX8MP_FirstSteps_eng.pdf

- Update to version 0.22 of LinuxOnFSBoards_eng.pdf

Please download the hardware documentation directly from our website.

Then you always have the newest version.

F&S i.MX8M-Mini OSM specific Yocto Release 2024.10.1 (osm8mm-Y2024.10.1)

Please see the file

doc/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.

This is a maintenance release specific for the module "FS 8MM OSM-SF".

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

The release consists of the following files and directories:

• README.txt Release notes (this text)
• setup-yocto Script to download and install the Yocto release
• fs-release-manifest.xml Release Manifest, containing the used versions as git hashes
• binaries/ Precompiled images (full names)
• sdcard/ Precompiled images (names as expected by install script)
• doc/ Hardware and software manuals, schematics

Attention

Here are some highlights of this release.

1. Update Linux Kernel to patch level 5.15.160

This fixes several smaller bugs and CVEs.

For more information please see

https://cdn.kernel.org/pub/lin…el/v5.x/ChangeLog-5.15.72

to

https://cdn.kernel.org/pub/lin…l/v5.x/ChangeLog-5.15.160

Also adds support for the new F&S LVDS Displays and improves the Cortex-M support in Linux and adds SPI-NOR flash support to the efusmx8mp.

2. Improved boot loader U-Boot 2021.04

Several bug fixes and improvements, like the Resource Domain Control support in U-Boot device tree and an improved xhci USB driver.

3. Tested with Yocto poky layer version 4.0.20

This fixes several smaller bugs and CVEs, like CVE-2024-6387 OpenSSH signal handler race condition.

For more information, please see

https://docs.yoctoproject.org/…release-notes-4.0.19.html

to

https://docs.yoctoproject.org/…release-notes-4.0.20.html

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

The following list shows the most noticeable changes in this release in more detail since our last release for this platform.

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 change log.

u-boot-2021.04-osm8mm-2024.10.1

Supported boards: OSM8MM

- Remove unwanted internal pull-ups for osm8mm

linux-5.15.160-osm8mm-2024.10.1

Supported boards: OSM8MM

- Remove unwanted internal pull-ups for osm8mm

- Add support for new LVDS display on osm8mm

- Set LED7 for F&S displays to unused

- Add hysteresis for touch interrupt on ADP-OSM-BB

- Set Atheros ethernet phy link detection to interrupt

- Increase deassert delay for reset of Realtek phy

meta-fus-osm8mm-2024.10.1

Supported boards: OSM8MM

- Add support for LVDS display on osm8mm

atf-5.15.71-fsimx8mm-2024.10

(no changes)

firmware-imx-8.10.1 ddr synopsys

(no changes)

Examples

(no changes)

Documentation

- Update to version 1.9 of FSiMX8MM_FirstSteps_eng.pdf

- Update to version 0.22 of LinuxOnFSBoards_eng.pdf

Please download the hardware documentation directly from our website.

Then you always have the newest version.

Hello,

the GPIO Reference Card is now updated.

Thank you for the update on your situation.

Your F&S Support Team

Hello,

you can check the GPIO Reference Card for the PicoCOMA9X. The pin J1-63 is shared between the pads LCD_HSYNC and LCD_B2.

Otherwise, it seems that there currently is an error in the Reference Card for the signals LCD_B3 to LCD_B6 that the gpio numbers are off about one IO.

The correct mapping should be as followed, but I will check that again:

J1-63: LCD_HSYNC (GPIO3_IO26 -> gpio# 90) and LCD_B2 (GPIO3_IO01 -> gpio# 65)

J1-54: LCD_B3 (GPIO3_IO02 -> gpio# 66)

J1-55: LCD_B4 (GPIO3_IO03 -> gpio# 67)

J1-56: LCD_B5 (GPIO3_IO04 -> gpio# 68)

J1-57: LCD_B6 (GPIO3_IO05 -> gpio# 69)

If your tests are successful with the updated mapping, please reply shortly.

Your F&S Support Team

Hello,

a software reset will cause the CPU to pull the WDOG_B of the external PMIC. The PMIC will then pull the POR for the CPU, so the reset cause in perspective of the CPU will always be POR.

A way to distinguish a "real" POR from a SW-Reset would be to access the RESETSRC (0x29) register of the PMIC. You can look up the register in the datasheet for the BD71847 under chapter "3.3.10 Reset Source Indicators". If you need that value in the RootFS, you could read that register in UBoot and set the reset_cause for bdinfo to that value under board/F+S/common/fs_fdt_common.c.

After Power-On:

After SW-Reset (UBoot or Linux):

A HW-Reset can't be distinguished from a Power-On though. I hope the information helps.

Your F&S Support Team

Hello,

the second case [2] with the reboot at shutdown / poweroff is related to the post. Thank you for referencing it.

The commit for the ATF is pushed on our Github and will be in the upcoming release: Fix poweroff command and ON/OFF button in imx_system_off() · FSEmbedded/atf-fus@2465c76 · GitHub

The first case [1] is currently unknown and I can't reproduce it. I am trying it with the release fsimx8mp-2023.09. Do you use a baseboard of your own or are you using a starterkit of ours? If you are using a starterkit the revision of it would be good to know too.

Your F&S Support Team

Hello,

can you check whether the crc32 binary is present? You can do this with the command "which crc32".

We had a release version, where we included a crc-check in our bootloader-images, but didn't throw an error if the crc32 binary was not present.

This might be the issue in your Ubuntu host machine. The crc32 command should be in the "libarchive-zip-perl" package under Ubuntu.

Your F&S Support Team

Hello,

please communicate in English for this Forum, as others might need a solution for the same issue.

Translated question:

Quote

I would like to boot my Yocto image from SD-Card.

There is no bootloader image in the SD-Card. Do I need a U-Boot specific to the board and should the U-Boot image be in a partition of the SD-Card?

Our boards usually boot from the onboard eMMC, so the U-Boot image for the early startup is in the Bootpartition from the eMMC.

If you want to boot your Yocto root filesystem and/or the Linux kernel with Device-Tree from the SD-Card, you can do so by entering some commands in U-Boot:

If you just want to boot your Yocto rootFS, you can leave out the commands run .kernel_mmc and run .fdt_mmc.

If you want to set the boot medium to the eMMC again, you can do this with the same commands, just with setenv mmcdev 0.

The U-Boot expects on the boot medium a FAT partition, which includes Device-Trees and the kernel image, and an ext4 partition, which contains the root filesystem. It may be that you need to edit the environments in the U-Boot, if your SD-Card has another partiton layout.

I hope I could clarify the boot process for you.

Your F&S Support Team

Hello,

to investigate why the touchscreen is not responding, we will need some additional information:

• Boardvariant (V3I / V4)
• The release you are currently using (e.g. fsimx6ul-B2022.04)
• Type of the display (RGB / LVDS)

Your F&S Support Team

Hello,

the i.MX 93 does not support hardware acceleration for OpenGL. The Pixel Pipeline (PXP) only provides hardware acceleration for basic 2D conversion, e.g. scaling, color space conversion, rotation and composite alpha blending and color key.

These functions are provided for the G2D driver and will be called for the usage of Wayland/Weston.

Your F&S Support Team

Hello,

it seems you did receive special NBoot+UBoot for a DRAM with 4GB. In our official release these changes are not present yet as they complicate the standard memory layout significantly. This is also the cause why the UBoot currently sees 0 Bytes for the DRAM.

Please contact us for this case directly through our support E-Mail address.

Your F&S Support Team

Hello,

in the following thread you will find the fix for the yocto-download script on older Fedora Machines:

Fix for repo tool on older F&S Development Machines - Linux and Applications - (fs-net.de)

Your F&S Support Team