Posts by fs-support_PG

    i.MX8M-Plus Linux Pre-Release Yocto 4.0

    A new pre-release is available for fsimx8mp.

    It is based on the following components:

    Yocto 4.0 (Kirkstone)

    Linux Kernel 5.15.52

    U-Boot 2020.04


    Please note that this is a pre-release, which is only meant for testing and not suitable for production!

    There may be huge changes to the software and the distribution method in the future.

    The pre-release gits may be deleted or replaced.

    Please report any bugs in this thread.

    Please make sure to update to the fsimx8mp-Y2022.011 Release before installing the pre-release.

    Building the Pre-Release

    1. Download the virtual machine F_S_Development_Machine-Fedora_35_V1.0-pre.ova from My F&S Tools-Linux/VirtualMachines/Fedora35/ and import it to VirtualBox.

    2. Run git clone to download the pre-release. Go to releases-fus-pre/fsimx8mp-Yocto/

    3. Run ./setup-yocto <BUILDIR_NAME> and go to <BUILDIR_NAME>/yocto-fus/

    4. Run  DISTRO=fus-imx-wayland MACHINE=fsimx8mp .

    5. Run bitbake fus-image-std


    we have further investigated the issue and a Hotfix would be to mute the Lineout before rebooting

    amixer sset 'Lineout' mute


    We will create a patch that will do this automatically when unloading the driver.

    This however will not fix the issue if the Board is resetted by a Hardware reset.

    We will have to further investigate this.

    Your F&S Support Team


    we can reproduce the issue if we play a sound in Linux and reboot.

    We than here a frequent noise starting from Uboot until the SGTL driver loads.

    The issue does not occur from a cold start.

    Is this correct?

    We will have to further investigate on this.

    Your F&S Support Team

    There is no GPU hardware acceleration for on IMX8. You can try to build X11 with software acceleration only, but this will not be very performant.

    We have no description on how to do this and can not support it.

    Weston/Wayland has a RDP backend for remote display control. A description on how to use it can be found on:…n/LinuxOnFSBoards_eng.pdf

    Chapter 8.20 RDP

    Also I saw that TeamViewer offers an experimental Wayland backend but we never tested it.


    Your F&S Support Team

    F&S i.MX8M-Mini Yocto Release Y2021.04.2 (fsimx8mm-Y2021.04.2)

    Please see the file


    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 minor release for all F&S boards and modules based on the i.MX8M-Mini CPU (Solo, Dual and Quad), i.e. PicoCoreMX8MM. More boards may be added to this family in the future. All these boards can work with software that is created from this release package.

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


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


    If you copy the contents of this archive to an SD card, you can install our precompiled standard system in a very straightforward and comfortable way on the board. The SD card archive is meant for people who just want to try a release first without having to download the quite large main archive. Its content is also contained in the main release archive, so if you want to download the main archive anyway, you don't need to bother with the SD card archive.

    These tar archives are compressed with bzip2. So to see the files, you first have to unpack the archives

    1. tar xvf fsimx8mm-Y2021.04.2.tar.bz2

    This will create a directory fsimx8mm-Y2021.04.2 that contains all the files of the release.

    Please read the file doc/FSiMX8MM_FirstSteps_eng.pdf. It describes the first steps when working with the board and gives references to further reading.


    Known Issues

    The Link LED of the PicoCoreMX8MMr2 revision 1.00 is inverted. It will be on, if no link is detected and off if a link is detected.

    The Activity will be indicated through blinking as expected. Unfortunately, this can not be fixed by software.


    Here are some highlights of this release.

    1. Support for PicoCoreMX8MMr2

    Add support for the new PicoCoreMX8MMr2 board version, that features the rtl8211f ethernet phy.

    2. Rework Device Tree structure

    Derive the device trees for the picocoremx8mm and picocoremx8mmr2 from a common picocoremx8mm.dtsi, so changes can be easily applied to both of them.

    3. Improve the rtl8211f phy support

    Improve the realtek phy by making the following features configurable:

    - Disable CLKOUT

    - ALDPS mode

    - Spread-Spectrum Clocking for RXC, SYSCLK and CLKOUT

    - Setting one LED for each: link indication and activity

    - Disable GBit


    The following list shows the most noticeable changes in this release in

    more detail since our last pre i.MX8M-Mini 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

    change log.

    u-boot-2018.03-fsimx8mm-Y2021.04.2 (15.09.2022)


    Supported boards: PicoCoreMX8MM PicoCoreMX8MMr2 PicoCoreMX8MX

    - Add Board-Configs for the PicoCoreMX8MMr2

    - Add rx delay support for RTL8211F

    - Improve phy realtek LED setup

    - Add PicoCoreMX8MMr2 support

    - Add N-boot History file for nboot-fsimx8mm-2021.04.1

    - Change ingress delay for KSZ9893R Ethernet switch on fsimx8mm/mn

    - Move LED configuration of Realtek PHY to board_phy_config

    - Enable ALDPS mode and disable EEE LED indication

    - Improve picocoremx8mmr2 device tree

    - Disable phy CLKOUT for PicoCoremx8MMr2

    - Disable ethernet before booting linux for fsimx8mm

    linux-5.4.70-fsimx8mm-Y2021.04.2 (15.09.2022)


    Supported boards: PicoCoreMX8MM PicoCoreMX8MMr2 PicoCoreMX8MX

    - Improve picocoremx8mm device tree layout

    - Add PicoCoreMX8MMr2 support

    - net: phy: realtek: Support SSC for the RTL8211F

    - Add rtl8211f phy led mode fixup via device tree

    - Add support for Marvel BT modules on fsimx8mm

    - Support more features for Realtek PHY

    - Improve realtek driver

    - Improve picocoremx8mmr2 device tree

    yocto-3.0-fsimx8mm-Y2021.04.2 (16.09.2022)


    Supported boards: PicoCoreMX8MM PicoCoreMX8MMr2 PicoCoreMX8MX

    - Add picocoremx8mmr2 DTS and remove unused picocoremx8mm DTS

    - Remove mono from yocto-fus

    - Add alsa tinycompress mirror

    - Fix fsimx8mm devicetree conf

    atf-5.4.70-fsimx8mm-Y2021.04.2 (19.09.2022)


    Supported boards: PicoCoreMX8MM

    - NXP version rel_imx_5.4.70_2.3.2

    - Add domain permission for UART2 on M4

    - Add DEBUG_CONSOLE for imx8mn

    - Add possibility to deactivate debug UART for fsimx8mp

    - Add domain permission for UART2 on M7

    firmware-imx-8.10.1 ddr synopsys (19.09.2022)




    (no changes)



    - Update to version 1.7 of FSiMX8MM_FirstSteps_eng.pdf

    - Update to version 0.13 of LinuxOnFSBoards_eng.pdf

    Please download the hardware documentation directly from our website.

    Then you always have the newest version.

    Update to F_S_Development_Machine-Fedora_27_V1.8 (21.09.2021)

    There is a new Virtual Machine with Fedora27 in your download section available (My F&S / Tools-Linux / Fedora27 / F_S_Development_Machine-Fedora_27_V1.8.ova). Below are the changes compared to the previous version F_S_Development_Machine-Fedora_27_V1.6.ova.

    (F_S_Development_Machine-Fedora_27_V1.7.ova was skipped due to errors in release fsimx8mm-Y2021.04.1.)

    New Content:

    • fsimx8mm-Y2021.04.2 (/home/developer/fsimx8mm-Y2021.04.2)

    Removed Content:

    • fsimx8mm-Y2021.04 (/home/developer/fsimx8mm-Y2021.04)

    Your F&S Support Team


    please use fsimx8mm_wayland_defconfig for i.MX8MM.

    We decided to not use the term "std" anymore to make it more transparent that there is no X11 support for i.MX8 boards anymore.

    All config giles can be found in the configs/ directory in the buildroot main directory.

    Your F&S Support Team


    we try to provide a new Yocto Release for the i.MX8MP in September/October.

    This Release will be based on Kernel 5.15 and Yocto Kirkstone (4.0).

    Your F&S Support Team


    are you running X11?

    If so you have to adapt the file /etc/X11/xorg.conf

    mount -o remount,rw /

    vi ]/etc/X11/xorg.conf /

    and change the section "Device" to the following to disable GPU support:

    1. Section "Device"
    2.     Identifier  "Kernel Framebuffer Device"
    3.     Driver      "fbdev"
    4.     Option      "fbdev" "/dev/fb0"
    5. EndSection


    mount -o remount,ro /

    and reboot the board.

    Now the display should work.

    Your F&S Support Team

    Your welcome.

    I noticed there is also a define at the beginning of the device tree that adds this change for you.

    Just comment out the define CONFIG_PICOCOMA9X_GPU like this and it should work too:

    1. //#define CONFIG_PICOCOMA9X_GPU

    Your F&S Support Team


    There are some i.MX6SX SoC variants without GPU.

    When the Kernel tries to initialize the GPU here, the board hangs.

    This is a known issue and the Device Tree GPU node will be disabled automatically by Uboot in future releases.

    For now you will have to disable the GPU node by hand.

    Please try to add the following code to your picocoma9x.dts Device Tree:

    1. &gpu3d {
    2.     status = "disabled";
    3. };

    Your F&S Support Team

    Hello Benni and welcome to the forum,

    As this is an international forum I will answer in English.

    You want to connect a LVDS-Display to the LVDS0 channel and you get a framebuffer device but not picture on the screen.

    By default the PicocoreMX8MP uses the LVDS1 channel for LVDS displays so please make sure that your cable connects the right pins.

    You also have to make sure that your PicocoreMX8MP variant supports LVDS on both channels by hardware. Currently this is only possible wit PicocoreMX8MP-V2.

    Finlay, you will have to enable the lvds-channel@0 port in your device-tree and disable lvds-channel@1 and lvds1_panel:

    I hope this helps.

    Your F&S Support Team