Posts by fs-support_PG

    Hello,


    as you can see from the Device Tree the the VBUS power is controlled via hardware by the USB_OTG_PWR pin, not the GPIO pin:


    https://github.com/FSEmbedded/…oot/dts/efusa9x.dts#L1825

    https://github.com/FSEmbedded/…sa9x.dts#L1200C7-L1200C11

    https://github.com/FSEmbedded/…boot/dts/efusa9x.dts#L513


    The pinmux is not at GPIO, so you cannot control it with the GPIO commands.

    I am nor sure, why the USB_OTG_PWR keeps the power when unloading the driver.

    However, you can try to switch to the GPIO implementation by commenting/uncommenting the respective lines in the device tree I posted.


    Your F&S Support Team

    Hello,


    We added an example on how to use the etnaviv driver with an efusa9 some releases ago.

    Hower, this might differ a little, depending on which display and board type is used.


    to activate the etnaviv driver, there are several steps, that need to be done.


    1. Use the fsimx6_etnaviv_defconfig

    https://github.com/FSEmbedded/…/fsimx6_etnaviv_defconfig

    2. Make some adjustments to the Device Tree: See

    https://github.com/FSEmbedded/…t/dts/efusa9q-etnaviv.dts

    3. Make some adjustments to the Buildroot defconfig

    https://github.com/FSEmbedded/…iv_experimental_defconfig


    However the Buildroot has not been fully tested with the B2024.04 release, so there could be some issues here.

    Mostly, you need to make sure that the Mesa driver has the etnaviv config activated.


    Your log indicates, that the main issue seems to be your display.

    There is an example in the device tree on how to use a LVDS display. Maybe you can try to adapt this to your Device Tree?

    https://github.com/FSEmbedded/…s/efusa9q-etnaviv.dts#L52

    https://github.com/FSEmbedded/…s/efusa9q-etnaviv.dts#L98


    Your F&S Support Team

    Did you try this?


    Code
    1. killall weston
    2. echo 0 > /sys/class/graphics/fb2/blank
    3. echo 16 >/sys/class/graphics/fb2/bits_per_pixel
    4. weston --tty=1 --device=/dev/fb0,/dev/fb2 --clone-mode &

    from https://community.nxp.com/t5/i…put-messed-up/m-p/1778606


    Maybe also with fb0?


    I don' see the IPU warnings as an acute issue. These may occur on high system load and maybe loading both displays causes a lot of load.

    If they do not occur regular, i think you can ignore them for nor.


    You can also try to reduce the resolution of your HDMI display if possible. This should cause less load.


    Code
    1. # Get available modes
    2. cat /sys/class/graphics/fb2/modes
    3. echo <yourMode> > /sys/class/graphics/fb2/mode


    You can also contact us directly by mail if you need support via meeting.


    Your F&S Support Team

    Hello,


    we did not notice any color change, when enabling the clone-mode on any display.

    However, I thing it is important to unblank the HDMI display before starting weston with the clone mode.

    Is this done correctly?


    Your F&S Support Team

    Hello,


    please test the following:


    Set fb0 to lvds and fb1 to hdmi in your device tree

    Code
    1. #define CONFIG_EFUSA9_MXCFB0    DISPLAY_LVDS0
    2. #define CONFIG_EFUSA9_MXCFB1    DISPLAY_HDMI


    Boot your board and run the following commands:

    Code
    1. killall weston
    2. echo 0 > /sys/class/graphics/fb2/blank
    3. weston --tty=1 --device=/dev/fb0,/dev/fb2 --clone-mode &


    This should open a weston instance, that mirrors the framebuffer from /dev/fb0 to /dev/fb1.

    It worked in our tests with fsimx6-Y2024.04


    Your F&S Support Team

    Hello,


    I think the main issue here is, that NXPs i.MX6 i GPU Vivante driver does not support DRM, but only the deprecated framebuffer-backend.

    And I don't think the will support DRM for i.MX6 in the future.

    https://github.com/nxp-imx/met…/imx-base-extend.inc#L107


    One approach would be, to switch to the open source Etnaviv driver, which supports the DRM backend.


    Another would be to try to use the same framebuffer for both outputs. This however would require the displays to support the same resolution.

    Would this be an option?


    Your F&S Support Team

    I can confrim, that it does not work without the HW fix on the BBDSI. It does not get any link



    With the fix it loads it gets the connection and loads the driver


    Code
    1. root@fsimx8mp:~# lspci
    2. 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
    3. 01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02)


    We added the capacities on the BBDSI on these lanes:



    Could you check your fix again?

    F&S i.MX8M-Mini Yocto Pre Release 2025.04 (fsimx8mm-Y2025.04-pre)

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


    This is a pre-release, so no binaries will be delivered.

    Please download the sources from

    https://github.com/FSEmbedded/…ree/fsimx8mm-Y2025.04-pre



    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 major pre-release for all F&S boards and modules based on the

    i.MX8M-Mini CPU (Solo, Dual and Quad), i.e. PicoCoreMX8MM(r2)-LPDDR4,

    PicoCoreMX8MM-DDR3L, OSM8MM. 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.


    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    ! Attention !

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    This is a pre-release and not suitable for production!

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    ! Attention !

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


    This pre release is based on NXP lf-6.6.52-2.2.0 release.


    Here are some highlights of this release.


    1. New Linux Kernel based on lf-6.6.52-2.2.0 with patchleve 6.6.69

    The F&S Kernel is now based on the linux-fslc kernel.

    https://github.com/Freescale/linux-fslc/

    The fslc kernel has LTS updates for the NXP release versions, so security

    fixes can be applied more easily.


    2. Old bootloader U-Boot 2021.04


    In the final release, the bootloader will be based on version 2024.04.


    3. New Yocto version 5.0 Scarthgap


    Updating Yocto to Version 5.0.8 Scarthgap.


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


    git clone -b fsimx8mm-Y2025.04-pre 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.


    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.


    ./setup-yocto --docker



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


    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-fs0.1-pre

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

    Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP

    efusmx8mp SMARCMX8MP





    linux-v6.6.69-fs0.5-pre

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

    Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP

    efusmx8mp SMARCMX8MP


    - Update fsimx8 boards to Kernel 6.6




    meta-fus-yocto-5.0.8-fs0.1-pre

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

    Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP

    efusmx8mp SMARCMX8MP


    - Update fsimx8 boards to Yocto 5.0

    - Use Kernel and U-Boot version specific recipes




    atf-5.15.71-fsimx8mp-2024.07

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

    Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP

    efusmx8mp SMARCMX8MP


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

    F&S i.MX8M-Plus Yocto Pre Release 2025.03 (fsimx8mp-Y2025.03-pre)

    This is a pre-release, so no binaries will be delivered.

    Please download the sources from

    https://github.com/FSEmbedded/…ree/fsimx8mp-Y2025.03-pre



    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 major pre-release for all F&S boards and modules based on the

    i.MX8M-Plus CPU (Solo, Dual and Quad), i.e. PicoCoreMX8MP(r2), armStoneMX8MP,

    efusmx8mp or SMARCMX8MP (FSSMMX8MP). 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.


    The release consists of the following files and directories:


    Readme-yocto-f+s.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

    binaries/ Precompiled images (full names)

    sdcard/ Precompiled images (names as expected by

    install script)

    doc/ Hardware and software manuals, schematics


    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    ! Attention !

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    This is a pre-release and not suitable for production!

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    ! Attention !

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


    This pre release is based on NXP lf-6.6.52-2.2.0 release.


    Here are some highlights of this release.


    1. New Linux Kernel based on lf-6.6.52-2.2.0 with patchleve 6.6.69

    The F&S Kernel is now based on the linux-fslc kernel.

    https://github.com/Freescale/linux-fslc/

    The fslc kernel has LTS updates for the NXP release versions, so security

    fixes can be applied more easily.


    2. Old bootloader U-Boot 2021.04


    In the final release, the bootloader will be based on version 2024.04.


    3. New Yocto version 5.0 Scarthgap


    Updating Yocto to Version 5.0.4 Scarthgap.


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


    git clone -b fsimx8mp-Y2025.03-pre 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.


    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.


    ./setup-yocto --docker



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


    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-fs0.1-pre

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

    Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP

    efusmx8mp SMARCMX8MP





    linux-v6.6.69-fs0.4-pre

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

    Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP

    efusmx8mp SMARCMX8MP


    - Update fsimx8 boards to Kernel 6.6




    meta-fus-yocto-5.0.4-fs0.3-pre

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

    Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP

    efusmx8mp SMARCMX8MP


    - Update fsimx8 boards to Yocto 5.0

    - Use Kernel and U-Boot version specific recipes




    atf-5.15.71-fsimx8mp-2024.07

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

    Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP

    efusmx8mp SMARCMX8MP


    (no changes)


    firmware-imx-8.10.1 ddr synopsys

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


    (no changes)


    Examples

    --------


    (no changes)


    Documentation

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


    - Update to version 1.6 of FSiMX8MP_FirstSteps_eng.pdf

    - Update to version 0.19 of LinuxOnFSBoards_eng.pdf


    Please download the hardware documentation directly from our website.

    Then you always have the newest version.

    Hello,


    we are currently working on a pre-release for fsimx8mm and fsimx8mp, which we are aiming to upload in the next two weeks.


    A pre-release for fsimx6/ul/sx will take more time and is currently not in progress.


    However, the Kernel from the fsimx93 pre-release should at least build with all fsimx defconfigs, so you could try to compile it four your boards.

    https://github.com/FSEmbedded/…tree/fsimx93-Y2025.02-pre


    Your F&S Support Team