Posts by fs-support_PG

  • New F&S Development Machine - Fedora36-arm32

    F&S Development Machine with Fedora 36 for arm32 V1.5

    There is a new Virtual Machine with Fedora36 in your download section available (My F&S / Tools-Linux /VirtualMachines/Fedora36/32-bit (i.MX6)/ F_S_Development_Machine-Fedora_36-arm32_V1.5.ova). The structure of the virtual machine is listed below.


    Content:

    • fsimx6ul-B2023.12 (/home/developer/fsimx6ul-B2023.12)
    • fsimx6sx-B2024.01 (/home/developer/fsimx6sx-B2024.01)
    • fsimx6ul-Y2024.03 (/home/developer/fsimx6ul-Y2024.03)
    • fsimx6-B2024.04 (/home/developer/fsimx6-B2024.04)
    • fsimx6-Y2024.04 (/home/developer/fsimx6-Y2024.04)
    • fsimx6sx-Y2024.12 (/home/developer/fsimx6sx-Y2024.12)

    New Content:

    • fsimx6sx-Y2024.12 (/home/developer/fsimx6sx-Y2024.12)

    Your F&S Support Team

  • New Yocto Release fsimx6sx-Y2024.12

    F&S i.MX6SX Yocto Release 2024.12 (fsimx6sx-Y2024.12)


    Please see the file


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


    This is a major release for all F&S boards and modules based on the i.MX6-SoloX CPUs from NXP.


    Currently these are the modules efusA9X, efusA9Xr2, PicoCOMA9X, PicoCoreMX6SX.


    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.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. New Linux Kernel 5.15.160


    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


    2. New bootloader U-Boot 2021.04


    The U-Boot is now based on 2021.04.

    Additional to the security and feature updates of the mainline U-Boot,

    there have been many updates on the fsimage command and the general layout

    of the bootloaders in the flash memory.


    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


    4. Improved Image versioning


    The exact versions of Nboot, U-Boot and Linux Kernel will now be printed during the boot process.

    If the image is build with an tagged commit the tag name will be printed.

    If the commit is not tagged, the git commits hash will be printed.

    If the image is based on an uncommitted git, the flag "-dirty" will be added to the last commits name.


    We use an own Linux version string that will be printed additionally to the mainline Linux version. This way modules that are built for the same Linux

    version with just some slight changes, can still be loaded without rebuilding the whole rootfile system.


    Linux device trees are also versioned with the current version of the linux git.


    You can check the versions of the different components at runtime at /sys/bdinfo/


    5. New Release concept over github


    We now provide our Linux gits over github at https://github.com/FSEmbedded.

    All release and pre-release states will be pushed here.

    For now, we will not push each single commit to github.


    Also the release sources are not added to the release tar anymore, but will be downloaded from github during the setup process.


    The versions of the different gits of a release can be looked up in the fs-release-manifest.xml file in the release tar directory.


    6. Support Silex WLAN Chip on the efusA9X(r2)


    The new driver version is based on version 4.5.25.38 of the original Qualcomm driver which is available in branch CNSS.LEA.NRT_3.1 on repository (tag v4.5.25.38)

    There is also a Silex-specific version available on request that improves roaming, adds bang radar and other improvements. Ask F&S if interested.



    Knwon Issues:


    1. The Slilex Bluetooth Chip on the efusmxA9X(r2) is not supported.


    There is currently no driver available for the Linux Kernel 5.15.

    For Silex Bluetooth chip support, please use the release fsimx6sx-B2019.11.1 for basic Bluetooth evaluation.



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


    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.


    nbootimx6sx_51.bin (VN51)

    Supported boards: efusA9X, efusA9Xr2, PicoCOMA9X, PicoCoreMX6SX


    [VN49]

    - 0005378: [NBoot] Ad9 support for new boards efusA9Xr2, armStoneA9R3,

    armStoneA9r4, PicoCoreMX6SXr2


    [VN50]

    - 0005541: [NBoot] NAND dump does not work

    - 0005540: [NBoot] Memory errors on armStoneA9

    - 0005542: [NBoot] Board revision is wrong on armStoneA9


    [VN51]

    - 0005951: [NBoot] Add new board NetDCUA7

    - 0005950: [NBoot] Add secure boot for UL with MMC




    u-boot-2021.04-fsimx6sx-2024.12

    Supported boards: efusA9X, efusA9Xr2, PicoCOMA9X, PicoCoreMX6SX


    - Update to NXP u-boot-201.04

    - Improve Uboot versioning

    - Fix bootaux command

    - Fix fat_size for files bigger than 2GB

    - Drop board revision from BOARD-CFG names

    - addfsheader.sh: Check for crc32 and xxd before using them

    - Remove sha256 support




    linux-5.15.160-fsimx6sx-2024.12

    Supported boards: efusA9X, efusA9Xr2, PicoCOMA9X, PicoCoreMX6SX


    - Update to NXP Linux Version lf-5.15.71-2.2.1

    - Switch to FSL_ASOC_CARD sound driver for sgtl5000

    - Add F&S Versioning for kernel and device tree

    - Improve uart dma support

    - Add leds-pca963x-fus driver and revert the original to

    the mainline driver

    - Enable power key support for PicoCore boards

    - Improve SDIO stability for Azurewave wlan chips

    - Add support to disable pin controls nodes in the device tree

    - Fix Realtek Ethernet Phy Bug in Low Power Mode

    - Fix backlight flicker for inverted pwm

    - Improve auxiliary_core driver

    - Fix picocoma9x rtscts pad settings

    - PCOMA9X: Increase CMA size to 200MB

    - Apply patches from mainline linux-5.15.160

    - Apply patches for Silex-Wlan Chip




    meta-fus-fsimx6sx-2024.12

    Supported boards: efusA9X, efusA9Xr2, PicoCOMA9X, PicoCoreMX6SX


    - Remove weston G2D default support for fsimx6sx




    meta-silex-fus-fsimx6sx-2024.12

    Supported boards: efusA9X, efusA9Xr2


    - Create layer



    examples-V1


    (no changes)



    Documentation


    - Update to version 2.3 of FSiMX6SX_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.

  • Ethernet issue

    Hello,


    we run the iper3 test over the weekend and did not encounter any issues.

    Could you please contact us via our support mail address so we can schedule a meeting?



    Your F&S Support Team

  • Ethernet issue

    Hello,


    gpioset gpiochip0 5=0 pulls the RESET pad if the Atheros to 0. It is not connected to the base board unless you have a version without Ethernet PHY, then it is connected to ETH_B_D4P.


    We will setup an iperf3 test like yours over the weekend.


    Can you make sure that the power connection of your board is stable and provides enough power? At least 5W to make sure that it is not an power connection issue.


    How many boards are affected by this?

    Could you connect 2 PicocoreMX8MM Starter Kits and run the iperf3 test? This way we could make sure to use the same setup.


    Your F&S Support Team

  • Ethernet issue

    Hello,


    yes you will have to add


    Code
    1. BR2_PACKAGE_LIBGPIOD=y


    to your buildroot config.


    There should not be any device tree changes needed.


    Could you describe your test setup in more detail or send it to us?


    Your F&S Support Team

  • Ethernet issue

    Hello,


    did you find a way to reproduce the issue faster? Maybe with high loads?


    We do not configure the HW-PHY-RESET pin in linux to keep the settings from U-Boot while booting.

    Could you try to reset the PHY "by hand" an see if it starts again in case of the error?


    Code
    1. ifconfig eth0 down
    2. gpioset gpiochip0 5=0
    3. sleep 0.1
    4. gpioset gpiochip0 5=1
    5. ifconfig eth0 up



    Your F&S Support Team

  • New F&S Development Machine - Fedora36

    F&S Development Machine with Fedora 36 V1.7 (11.09.2024)

    There is a new Virtual Machine with Fedora36 in your download section available

    My F&S / Tools-Linux /VirtualMachines/Fedora36/64-bit (i.MX8)/ F_S_Development_Machine-Fedora_36_V1.7.ova


    The structure of the virtual machine is listed below.

    Content:

    • fsimx8mm-Y2023.10 (/home/developer/fsimx8mm-Y2023.10)
    • fsimx8mm-B2023.11 (/home/developer/fsimx8mm-B2023.11)
    • fsimx8mn-Y2024.02 (/home/developer/fsimx8mn-B2024.02)
    • fsimx8mp-Y2024.07 (/home/developer/fsimx8mp-Y2024.07)

    New Content:

    • armstonemx8mp-Y2024.07.1 (/home/developer/armstonemx8mp-Y2024.07.1)

    Removed Content:



    Your F&S Support Team

  • armStoneMX8M-Plus Linux Maintenance Release Y2024.07.1 (Yocto 4.0)

    F&S armStoneMX8MP Yocto Release 2024.07.1 (armstonemx8mp-Y2024.07.1)


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


    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.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. Add support for armStoneMX8MP revision 1.10


    It feature an optional RS485 transceiver, an EEPROM, a new audio codec and several smaller bug fixes and improvements.


    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-fsimx8mp-2024.07.1 ()

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

    Supported boards: armStonemx8MP


    - Add support for armStoneMX8MP Rev 110

    - Support output of checksum in fsimage

    - Improve boottime for fastboot




    linux-5.15.160-fsimx8mp-2024.07.1 ()

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

    Supported boards: armStonemx8MP

    - Add support for armStoneMX8MP Rev 110

    - Disable SD UHS support by default for

    armstonemx8mp


    meta-fus-fsimx8mp-2024.07 ()

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


    (no changes)



    atf-5.15.71-fsimx8mp-2024.07 ()

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


    (no changes)



    firmware-imx-8.10.1 ddr synopsys ()

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


    (no changes)




    linux-examples-fus-fs1

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


    (no changes)




    Documentation

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


    - Update to version 1.7 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.

  • USBA not initalized in UBOOT

    Hello,


    we have tested this board with this release and it seems to work.

    Some questions:

    • So only the upper connector is failing? The lower one works?
    • Is the error Baseboard or SOM specific? Does the failing SOM work with an different Baseboard?
    • Did you try different USB sticks?
    • Did you test the Uboot from the new release fsimx8mp-Y2024.07?


    Your F&S Support Team

  • imx-sdma: All bds consumed,restart now.

    Hello,


    the reason, why this message is not displayed with mainline kernel 6.11 should be, that the warning does not exist in the imx-sdma driver code there:


    linux mainline 6.11-rc4:

    https://github.com/torvalds/li…ivers/dma/imx-sdma.c#L873


    linux-imx 5.15.y

    https://github.com/nxp-imx/lin…ivers/dma/imx-sdma.c#L988


    It was introduced in kernel 5.10, however, it also disappeared in newer imx-kernel versions:


    linux-imx 6.1.y

    https://github.com/nxp-imx/lin…vers/dma/imx-sdma.c#L1024


    I cannot find any commit, that removed this warning so it seems that it just was not merged into the newer kernel versions.

    This is the commit, which introduced the warning:

    [1] https://github.com/nxp-imx/lin…ce86c47c8cb10c3567a37bad0


    We did not see these kind of messages yet, however we did not do any intense sdma testing so far of the imx6sx.

    The commit message indicates, that is has something to do with high CPU loads. As the imx6sx is a Solo CPU, this might in fact be a problem.

    The fact, that the warnings where added in kernel 5.10 explain, why you did not see them so far.


    Is your CPU load very high, when these warnings occur?


    Could you try to apply the changes from [1] to the mainline kernel and see if they still not occur?


    Your F&S Support Team