Posts by fs-support_KM

  • i.MX8M-Plus OSM specific Linux Release Y2025.04 (Yocto 4.0)

    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.

  • i.MX8M-Mini OSM specific Linux Release Y2024.10.1 (Yocto 4.0)

    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.

  • Two inputs change together (J1-54 and J1-63)

    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

  • Reset reason in U-Boot

    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:

    Code
    1. PicoCoreMX8MM-LPDDR4 # i2c dev 3
    2. Setting bus to 3
    3. PicoCoreMX8MM-LPDDR4 # i2c md 0x4b 0x29 1
    4. 0029: 80

    After SW-Reset (UBoot or Linux):

    Code
    1. PicoCoreMX8MM-LPDDR4 # i2c dev 3
    2. Setting bus to 3
    3. PicoCoreMX8MM-LPDDR4 # i2c md 0x4b 0x29 1
    4. 0029: 40


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



    Your F&S Support Team

  • reboot forces poweroff and vice versa

    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

  • Custom U-Boot can not be installed

    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

  • Boot Yocto image von SD Card in armStone MX8MP

    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:

    Code
    1. setenv mmcdev 2 // Sets the current mmc device for the following commands to SD-Card
    2. run .kernel_mmc // In boot process the kernel will be loaded from current mmc device (SD-Card now)
    3. run .fdt_mmc // Same for Device-Tree
    4. run .rootfs_mmc // Same for RootFS
    5. saveenv // Write the new environments into the eMMC, so they remain after a powercycle


    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

  • Picocore imx6ul100 touch screen

    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

  • Grafik/ Starter-Kit

    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

  • i.MX8M-Mini Linux Release Y2023.10 (Yocto 4.0)

    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

  • Fix for repo tool on older F&S Development Machines

    Error Report

    Our yocto-download script uses the repo tool to get all the yocto-layers and sources necessary for a successful build.

    The repo tool recently changed, so that our yocto-download script breaks on older Fedora Machines with the following error:


    Code
    1. $ ./yocto-download
    2. Getting download information (repo init)
    3. File "./repo", line 51
    4. def print(self, *args, **kwargs):
    5. ^
    6. SyntaxError: invalid syntax


    Solution

    The fix for this issue is fairly simple. The default python version must be set to python3. This can be done with the following command:


    Code
    1. sudo ln -sf /usr/bin/python3 /usr/bin/python


    python3 should already be present, but you can check this with ll /usr/bin/python*. In case it is not present, it can be installed with the package manager via sudo dnf install python3.



    Your F&S Support Team

  • i.MX8M-Mini Linux Release Y2023.10 (Yocto 4.0)

    Hello,


    could you try to use the version 7 of VirtualBox? In our "ReadMe.txt" for the virtual machine with Fedora, there is a note that there are problems with audio on version 6. The error message also refers to an audio entry, so the upgrade to version 7 might already fix it.



    Your F&S Support Team

  • Recovery Tool

    Recovery Tool for i.MX8 series (v1.1.6)

    Description:


    The Recovery Tool for the i.MX8 series provides a simple way to restore the firmware on the board up to a working U-Boot. The tool and a description, how to use it, can be accessed in the download section in "My F&S" under "BOARD_NAME/Linux/Recovery Tool/". The tool comes packed with the current latest NBoot and U-Boot from the release of the architechture. Firmware from another release can be applied by removing the NBoot and U-Boot from the folder and exchanging them with the ones from the target release.


    ATTENTION: You should never have multiple NBoot and U-Boot files in the folder of the Recovery Tool!


    Changes since v1.1.5;

    • Fix parsing of new NBoot
    • Add form and handling for boardrevision
    • Add checkbox to keep CMD for UUU open
    • Add simple and expert mode


    Supported boards:

    • armStoneMX8MP, efusMX8MP, PicoCoreMX8MP, PicoCoreMX8MPr2
    • PicoCoreMX8MM-DDR3L, PicoCoreMX8MM-LPDDR4, PicoCoreMX8MMr2-LPDDR4


    Releases for included firmware binaries:

    • fsimx8mm-Y2023.10
    • fsimx8mp-Y2023.09



    Your F&S Support Team

  • i.MX8M-Plus Recovery Tool

    Hello,


    Currently the tool is only available for Windows. We have a Linux port planned, but it will take some time until a prototype is ready for usage.

    If Windows is completely out of question and you need a solution now, you can send an E-Mail with the required release and the serial number of your board to our support address. The context, that a recovery tool is needed, should be also clear in the mail.



    Your F&S Support Team

  • Disable/Enable Ethernet

    It is possible to shut down the ethernet link with "ifconfig eth0 down". That way, the PHY should power down and disable further communication.

    You might want to disable the automatic link up + dhcp for wired connections, as Yocto adds that policy under /lib/systemd/network/80-wired.network. If you do this, you will need to run the commands "ifconfig eth0 up" and "udhcpc -i eth0" manually.


    I just tested that the genphy_suspend function from the ethernet PHY driver in the kernel gets called, when "ifconfig eth0 down" is issued. This way the generic power down over the mdio communication can be done.



    Your F&S Support Team

  • update.scr fails with fatal consequenses

    Hello,


    please see i.MX8M-Plus Recovery Tool.

    We are now providing a recovery tool for the fsimx8mp releases. The binaries in the tool are from release fsimx8mp-Y2023.03, but as long as the NBoot and UBoot fit together, you can exchange the UBoot binary to the release you want to recover to.


    The recovery tool is using the UUU tool, so if you know what you do, you can also edit the write-emmc-uboot.auto to write every image. The standard auto script flashes everything up to the UBoot, so the Linux kernel, Device-Tree and RootFS are still missing. But in UBoot, you should better use the install.scr/update.scr script with an USB-Stick.



    Your F&S Support Team