Posts by fs-support_KM

    Hello and welcome to the forum,


    which release are you currently using? The newest release is the Buildroot Release fsimx6ul-B2022.04 and the Yocto Release fsimx6ul-Y2020.03.1.


    If you take a look at the device tree in the source code of the Linux kernel, you will see some defines at the beginning. These define which devices are enabled (and therefore can not be used as GPIO).


    arch/arm/boot/dts/picocom1.2.dts:

    Code
    1. /* PWM: PWM_A on pin 74, PWM_B on pin 75, PWM_C on pin 76, PWM_D on pin 70 */
    2. #define CONFIG_PICOCOM1_2_PWM_A
    3. #define CONFIG_PICOCOM1_2_PWM_B
    4. #define CONFIG_PICOCOM1_2_PWM_C
    5. #define CONFIG_PICOCOM1_2_PWM_D

    E.g. CONFIG_PICOCOM1_2_PWM_D defines that pin J11_14 is used as PWM_D. To use this pin as a GPIO, you will need to comment out the define CONFIG_PICOCOM1_2_PWM_D:

    Code
    1. /* PWM: PWM_A on pin 74, PWM_B on pin 75, PWM_C on pin 76, PWM_D on pin 70 */
    2. #define CONFIG_PICOCOM1_2_PWM_A
    3. #define CONFIG_PICOCOM1_2_PWM_B
    4. #define CONFIG_PICOCOM1_2_PWM_C
    5. //#define CONFIG_PICOCOM1_2_PWM_D

    This will set the IOMUX pad from the pin to GPIO mode.

    Afterwards, set the correct config

    Code
    1. make fsimx6ul_defconfig

    and build the device-tree.

    Code
    1. make picocom1.2.dtb


    Flash this device-tree onto the board and you should be able to use the pin J11_14 as GPIO.

    For every other pin the process is the same.



    Your F&S Support Team

    Patches to add efusA9r2 with Realtek PHY

    Currently there is no Yocto release supporting the efusA9r2. In the attachements you will find a zip file containing patches and a README. These patches will enable the efusA9r2 board for the Yocto release fsimx6-Y2020.03.


    Please refer to the README for instructions on how to apply the patches.



    Your F&S Support Team

    F&S i.MX6UL Linux Release Y2020.03.1 (Yocto 2.4 Rocko)

    This is a major release for fsimx6ul. fsimx6ul is the software for all boards from F&S that are based on the i.MX6-UltraLite and i.MX6ULL CPUs from NXP (or i.MX6UL and i.MX6ULL for short). Currently these are the modules efusA7UL, PicoCOM1.2, PicoCoreMX6UL and PicoCoreMX6UL100. Further boards may be added to this family in the future. All these boards can work with software that is created from this release package.


    The release consists of two files:


    fsimx6ul-Y2020.03.1.tar.bz2

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


    sdcard-fsimx6ul-Y2020.03.1.tar.bz2

    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 Code


    Code
    1. tar xvf fsimx6ul-Y2020.03.1.tar.bz2


    This will create a directory fsimx6ul-Y2020.03.1 that contains all the files of the release.


    Please read the file


    doc/FSiMX6UL_FirstSteps_eng.pdf


    It describes the first steps when working with the board and gives references to further reading.


    Release Notes for fsimx6ul-Y2020.03.1


    This release brings new versions to all parts of the software stack. Here are some highlights of this release.


    1. New version numbering


    We have changed the way how we name versions. In the past we had a version number made up of a major part m and a minor part n. Then we used Vm.n for Buildroot releases and Ym.n for Yocto releases. Release versions were counted individually for each CPU architecture. But then a "new" CPU type unfortunately had a smaller version number than an "old" CPU, even if the code was coming from the same sources or was even newer. This caused some irritations and misunderstandings of what release is actually the newest.


    So from now on we will use the year and month of the release instead, preceeded by a 'B' for Buildroot releases and a 'Y' for Yocto releases. For example the "B2019.11" of this release indicates a Buildroot based release from November 2019.


    2. Support for new board PicoCoreMX6UL100


    This is the first regular release that supports PicoCoreMX6UL100. The PicoCore is only 40mm x 35mm but is a very powerful System-on-Module with many I/Os.


    3. New U-Boot 2018.03


    We have a considerably newer U-Boot now. One of the main new features is display support, so basically U-Boot can now be used to show a splash screen.


    U-Boot will also show more information about the CPU type now, for example temperature range, possible speed, etc. The command "clocks" will show much more information about internal clock rates. And USB storage devices are detected faster and more reliably than before.


    U-Boot has experienced quite a lot of internal restructuring. For example it now also supports configuration via a Kconfig menu, similar to Linux kernel and Buildroot. After configuration with


    Code
    1. make fsimx6ul_defconfig


    simply call


    Code
    1. make menuconfig


    to show the menu. There you can select and de-select entries or move to sub-menus.


    Moving all configuration options from the previous header file to this menu is a long-term and still on-going process. So not all features are available in the menu, yet.

    U-Boot is now compiled and running in THUMB mode. This saves space that is needed for all the display code.


    4. New Linux kernel 4.9.88


    The Linux kernel is now based on 4.9.88. By default, we are using the zImage format of the kernel now, not the uImage format as before. Here are some of the new features since the previous kernel 4.1.15.

    • Improvements and optimizations in memory management, for example better heap and page management (tmpfs, shmem), better protection against attacks by implementing stack, heap and memory randomization.
    • Performance optimizations for the network stack, like faster TCP connections, quick killing of hanging network links, more features for the packet filter (firewall), smaller latencies on WLAN.
    • Optimizations in block layer, for example better Device Mapper for LVM, improved parallel access to directories, more efficient access to SSDs, parallel access for NFS, kernel support for file copy, server-side copy for CIFS, NFS, XFS, support for hard discs with host-managed SMR (Shingled Magnetic Recording).
    • Optimizations on file systems (NTRFS, EXT4, F2FS, NFS, XFS, Overlayfs, Ceph), new cluster filesystem Orangefs
    • Many improvements in graphics stack, like DRM (Direct Rendering Manager), new open source graphics driver etnaviv for Vivante graphics on i.MX CPUs (etnaviv = vivante backwards)
    • Better load balancing of processes to CPU cores, new cgroups v2, improved power and frequency handling, new cpufreq governor schedutil.
    • New GPIO infrastructure not using sysfs, supposed to be faster.
    • Support for USB SuperSpeedPlus (USB 3.1).
    • Many many new and improved drivers for WLAN chips, touch controllers, audio codecs, cameras, MMC/SD cards, etc.

    Of course there are also many changes for other CPU types (like x86) and other graphics cores (like AMD, Nvidia, Intel) but these are not of interest here.


    4. Yocto 2.4 (Rocko)


    With this release systemd will be the default init system for the example-fus-images.


    Systemd is a init system and service manager for Linux operating systems. It provides a system and service manager that runs as PID 1 and starts the rest of the system. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux control groups, maintains mount and automount points, and implements an elaborate transactional dependency-based service control logic. It is configured via the systemclt application.


    Also the root file system will now be mounted as read-write by default. This can be changed to read-only when setting up the build enviroment via the fus-setup-release.sh script. See LinuxOnFSBoards_eng.pdf for a detailed description.


    5. Default LVDS display replaced


    The ChiMei LVDS display that F&S used to ship with some Starter Kits is not available anymore. We will ship a different display from now on. Therefore we also changed the default settings for LVDS in the Linux device trees so that upcoming customers will have a working display.


    If you still need the previous settings, simply remove the two comment slashes at the beginning of the following line in the device tree and re-build the device tree. Then the old settings will be active again.


    //#define DISPLAY_LVDS_CHIMEI


    6. New driver for Silex WLAN


    In the past, the Silex WLAN driver was only available as a binary package. Now, for Linux 4.9.88, the driver is an open-source version that is built as part of Buildroot. This means you are more flexible with changes of the networking stack or specific configurations of the driver. A second package provides the firmware files. Please use exactly these, they contain modifications that are specifically adapted to our boards.


    Unfortunately we did not get patches for a newer bluez version in time. So Bluetooth is still based on bluez-5.39. Maybe we can improve this with a patch later.


    7. Documentation


    In the past, the documentation that was included in the release package itself was often superseded by newer versions on our website. But people continued to use the outdated version of the release, causing unnecessary complications.


    To avoid this, from now on only the software related documentation is directly included in the release and we have added a chapter to FSiMX6UL_FirstSteps_eng.pdf that contains direct links to the

    appropriate resources on our website. There you can download the newest versions of hardware documentations, schematics, layout files, certificates, accessories, add-ons, adapters and similar things.


    The software documentation is completely reworked. The FSiMX6UL_FirstSteps_eng.pdf document now really only shows a basic introduction to the work with boards of the fsimx6ul architecture. And there is a new document LinuxOnFSBoards_eng.pdf that shows a more in-depth view of a Linux system in general and of the F&S versions of NBoot, U-Boot, Linux and Buildroot in particular. This is still work in progress, some chapters are not fully done yet and will be revised in the future. Check our website from time to time to see if there is a newer version of this document.

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


    The following list shows the most noticable changes in this release in more detail since our last regular i.MX6UL release (not counting the intermediate release for PicoCoremX6UL). 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 changelog.


    nbootimx6_48.bin (VN48) (07.02.2022)

    Supported Boards: efusA9, armStoneA9, armStoneA9r2, PicoMODA9, NetDCUA9, QBlissA9, QBlissA9r2


    NBoot for i.MX6 shares the source code with other i.MX6 CPU variants like i.MX6UL and i.MX6SX, therefore versions are counted consecutively.


    [VN42]

    - 0004288: [NBoot] add support for eMMC

    - 0004289: [NBoot] add support for customer specific board VAND3


    [VN43]

    - 0004399: [NBoot] add eMMC MBR and FAT support

    - 0004400: [NBoot] improve dosfs and fix known bugs

    - 0004401: [NBoot] add support for boardconfig in eMMC boot partition

    - 0004402: [NBoot] add eMMC access from USB MSD

    - 0004398: [NBoot] add eMMC booting from fat in user partition

    - 0004403: [NBoot] warn user if wrong nboot for boot device is downloaded


    [VN44]

    - 0004625: [NBoot] Add support for new board GAR3


    [VN45]

    - 0004735: [NBoot] change version naming for super secure variant

    - 0004734: [NBoot] use built-in randomizer

    - 0004732: [NBoot] correct DDR3 detection routine


    [VN46]

    - 0004803: [NBoot] Improve eMMC boot support

    - 0004802: [NBoot] Add support for new board UL100


    [VN47]

    - 0005164: [NBoot] Add support for new board efusA9r2


    [VN48]

    - 0005263: [NBoot] nboot for eMMC does not start on PicoCoreMX6UL when fuses not set and SD card is inserted




    u-boot-2018.03-fsimx6ul-Y2020.03.1 (15.03.2022)

    Supported boards: efusA7UL, PicoCOM1.2, PicoCoreMX6UL, PicoCoreMX6UL100, PicoCOMA7


    - Add support for picocoremx6ul100

    - Add support for command fsimage

    - Change DACR to client access control to fix cache errors


    linux-4.9.88-fsimx6ul-Y2020.03.1 (15.03.2022)

    Supported boards: efusA7UL, PicoCOM1.2, PicoCoreMX6UL, PicoCoreMX6UL100, PicoCOMA7


    - Add support for RTC PCF85263

    - Improve support for imx6ul-touchscreen controller

    - Add driver for lontium-lt9211 RGB2LVDS converter

    - Add full device-tree support for PicoCOMA7

    - Improve support for picocoremx6ul revision 1.20

    - Add support for picocoremx6ul100 on architecture fsimx6ul

    - Add support for TSC2004 on fsimx6ul

    - Fix i2c frequency entry in device trees


    yocto-2.4-fsimx6ul-Y2020.03.1 (15.03.2022)

    Supported boards: efusA7UL, PicoCOM1.2, PicoCoreMX6UL, PicoCoreMX6UL100, PicoCOMA7


    - Fix download for meta-mono layer

    - Add updated device trees to fsimx6ul.conf

    - Fix core-image-minimal build

    - Add support to build install.scr

    - Add firmware for sd8997

    - Fix passing of ethaddr for Silex WLAN module


    Examples


    (no changes)


    Documentation


    - Update to version 2.4 of FSiMX6UL_FirstSteps_eng.pdf

    - Add new version 0.12 of LinuxOnFSBoards_eng.pdf


    Please download the hardware documentation directly from our website.

    Then you always have the newest version.

    Hello,


    I tried building the uboot.fs image again from Yocto and it successfully booted. Did you build the release fsimx8mn-Y2021.10 without any changes to the UBoot and Yocto first?


    Could you check the setup for Yocto?

    Code
    1. ./setup-yocto /destination/dir
    2. cd /destination/dir/yocto-3.0-fus
    3. ./yocto-download
    4. DISTRO=fus-imx-wayland MACHINE=fsimx8mn source fus-setup-release.sh -b build-fsimx8mn-wayland
    5. bitbake core-image-minimal


    Your F&S Support Team

    Hello,


    the SPL and NBoot are hardware specific and contain configurations, firmware files and dram timings to enable the board to boot. Usually those binaries are flashed one time and shouldn't change in development, so they don't get generated in the standard build.

    The UBoot (uboot.fs) is the first bootloader that can be customized. For why the flashing of the uboot.fs image resulted in an error, I don't know. I'll try it too with the binaries generated from Yocto.

    It should be enough to load the uboot.fs binary to RAM and call the command "fsimage save".


    E.g.:

    Code
    1. tftp uboot.fs
    2. fsimage save


    Your F&S Support Team

    Hello,


    in the attachments you can find the files necessary to recover the board.


    - Get the board into serial download mode. This is achieved by powering up the board while holding the BOOTSEL button (the button next to RESET).

    - Connect your Host-PC to the USB Device port of the board (either USB Mini A or USB Type C, depends on the Starterkit).

    - Unpack the zip file and start MfgTool2.bat.


    After this the UBoot should boot up again.


    Your F&S Support Team

    Files

    • recovery.zip

      (1.07 MB, downloaded 67 times, last: )

    On March 15, 2022 GitHub disabled the unencrypted Git protocol git:// permanently. This change affects packages in Buildroot and Yocto releases that are still using the mentioned protocol for GitHub resulting in the following error message:

    Code
    1. fatal: remote error: The unauthenticated git protocol on port 9418 is no longer supported


    The Git config can be set to globally use the encrypted protocol https:// instead of git://:

    Code
    1. git config --global url."https://".insteadOf git://



    Your F&S Support Team

    Hello,


    usually the USB_OTG port should be able to automatically switch between USB Host and USB Device with checking the ID pin. If the ID pin is not used, the USB_OTG can be switched to function as USB Host or USB Device in the device tree under arch/arm64/boot/F+S/efusmx8x.dtsi by changing dr_mode to "host" or "peripheral".

    Code
    1. &usbotg1 {
    2. pinctrl-names = "default";
    3. pinctrl-0 = <&pinctrl_usbotg1>;
    4. fsl,usbphy = <&usbphy1>;
    5. fsl,usbmisc = <&usbmisc1 0>;
    6. over-current-active-low;
    7. dr_mode = "otg";
    8. status = "okay";
    9. };

    However, in the current kernel release 4.14.98 there seems to be a bug in the initialization of the clocks that prevent the USB phy PLL to be locked.


    The next kernel release will be on version 5.4.70 and should be out at the end of March. I already checked the USB_OTG there and it is fully functional.


    In the meantime you can try to use the USB_HOST port. The following configs should be enabled in arch/arm64/configs/fsimx8x_defconfig:

    Code
    1. CONFIG_USB_CDNS3=y
    2. CONFIG_USB_CDNS3_HOST=y
    3. CONFIG_NOP_USB_XCEIV=y

    as well as the following device tree node in arch/arm64/boot/F+S/efusmx8x.dts:

    Code
    1. &usbotg3 {
    2. dr_mode = "host";
    3. status = "okay";
    4. };


    Your F&S Support Team

    Add error handling for the install script with eMMC


    Currently the UBoot update process does not react to errors in UBoot commands issued in the install and update scripts. So whenever the load command fails, the RAM area will get written to the destination as it is. For boards with a NAND flash this is not as problematic, because the UBoot will not be affected by the update. For eMMC however the UBoot is included in the sysimg file. An error in the load command results in a corrupt UBoot and the board will not be bootable without external flashing software.


    The updated install script checks for errors that might occur in the load command and aborts the update process before actually writing the corrupt data. Also the chunksize for the eMMC update process is reduced to support more USB sticks.


    The attached zip file contains the install script as a text file and precompiled binaries. The folder structure is exactly as in the release directory with binaries/, sdcard/ and sources/, so it is enough to unpack the zip file inside the release directory fsimx8mn-Y2021.10/.


    If the changes should also be comitted to the Yocto source code, download the attached patch, go to the source directory yocto-3.0-fus/, move the patch file there and apply it with the command patch -p1 < 0001-Add-error-handling-for-the-install-script-with-eMMC.patch.



    Your F&S Support Team

    Add error handling for the install script with eMMC


    Currently the UBoot update process does not react to errors in UBoot commands issued in the install and update scripts. So whenever the load command fails, the RAM area will get written to the destination as it is. For boards with a NAND flash this is not as problematic, because the UBoot will not be affected by the update. For eMMC however the UBoot is included in the sysimg file. An error in the load command results in a corrupt UBoot and the board will not be bootable without external flashing software.


    The updated install script checks for errors that might occur in the load command and aborts the update process before actually writing the corrupt data. Also the chunksize for the eMMC update process is reduced to support more USB sticks.


    The attached zip file contains the install script as a text file and precompiled binaries. The folder structure is exactly as in the release directory with binaries/, sdcard/ and sources/, so it is enough to unpack the zip file inside the release directory fsimx8mm-B2021.06/.



    Your F&S Support Team

    Add error handling for the install script with eMMC


    Currently the UBoot update process does not react to errors in UBoot commands issued in the install and update scripts. So whenever the load command fails, the RAM area will get written to the destination as it is. For boards with a NAND flash this is not as problematic, because the UBoot will not be affected by the update. For eMMC however the UBoot is included in the sysimg file. An error in the load command results in a corrupt UBoot and the board will not be bootable without external flashing software.


    The updated install script checks for errors that might occur in the load command and aborts the update process before actually writing the corrupt data. Also the chunksize for the eMMC update process is reduced to support more USB sticks.


    The attached zip file contains the install script as a text file and precompiled binaries. The folder structure is exactly as in the release directory with binaries/, sdcard/ and sources/, so it is enough to unpack the zip file inside the release directory fsimx8mm-Y2021.04/.



    Your F&S Support Team

    The main reason for the busy error to appear is that in the default device tree, we enable SPI_B which claims the gpio pin. In the device tree under arm/boot/dts/efusa9x.dts you will need to make sure CONFIG_EFUSA9X_SPI_B and CONFIG_EFUSA9X_PARALLEL_CAMERA commented out, because they are both using the pin. After that the IOMUX setting is still missing, so you need to add "MX6SX_PAD_QSPI1A_SS0_B__GPIO4_IO_22 0x1b0b0" to the list of "pinctrl_hog: hoggrp".



    Your F&S Support Team

    Hello,


    to use the GPIOs, the IOMUX registers of the pads must first be set to the GPIO. This is done in the device tree of the Linux kernel. Usually we have defines to enable or disable certain devices (e.g. SPI_B), but for the Pre-Release these are not yet prepared. When disabled we set the IOMUX to GPIO.


    For the 8X the following steps need to be done to set the pads to the GPIO in the Linux kernel source:


    - Under include/dt-bindings/pinctrl/pads-imx8qxp.h search for the define including the GPIO you want to use (e.g. search for GPIO0_IO15 and get SC_P_SPI3_SDI_LSIO_GPIO0_IO15)

    - Under arch/arm64/boot/dts/F+S/efusmx8x.dtsi you will find the node "pinctrl_hog: hoggrp". There you need to include the define with the values as in the IOMUX registers. (I included SPI_B_MOSI with "SC_P_SPI3_SDO_LSIO_GPIO0_IO14 0x06000021")

    - Load the right configuration for fsimx8x with "make fsimx8x_defconfig"

    - Build the device tree with "make F+S/efusmx8x.dtb"

    - Flash the new device tree on to the board


    Your F&S Support Team

    The communication with the WLAN chip runs over PCIe. The kernel module does not load because the initialization of the PCIe fails with the message "phy link never came up". Problems with the link is usually a hardware fault. Most likely a wire from the hardware fix loosened and came off or a contact does not fit.

    The best would be to send the board in via our RMA, so we can correct the hardware.

    https://www.fs-net.de/en/support/serial-number-info-and-rma/



    Your F&S support team

    Hello,


    could you post the output of the following command?

    Code
    1. dmesg | grep pcie


    My guess is that either the module does not get loaded or that the imx6q-pcie driver does not get a link up.


    Also, are there manually attached wires around the CPU chip and WLAN chip? Those are the hardware fixes regarding the WLAN / PCIe for the revision 1.00 of the efusMX8X and should be present.



    Your F&S support team

    i.MX8M-Nano Linux Release Y2021.10 (Yocto)


    This is a major release for all F&S boards and modules based on the i.MX8M-Nano CPU (Solo, Dual and Quad), i.e. PicoCoreMX8MN. 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.


    The release consists of two files:


    fsimx8mn-Y2021.10.tar.bz2

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


    sdcard-fsimx8mn-Y2021.10.tar.bz2

    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

    Code
    1. tar xfv fsimx8mn-Y2021.10.tar.bz2

    This will create a directory fsimx8mn-Y2021.10 that contains all the files of the release.


    Please read the file doc/FSiMX8MN_FirstSteps_eng.pdf. It describes the first steps when working with the board and gives references for further information.


    !!!! Important !!!


    Please note that this release is only compatible with PicoCoreMX8MN of Board Revision 1.30. The Board Revision can be found at the top Site of the board, printed in golden letters. (PCoreMX8MN Rev 1.30 TOP) Please contact F&S if you are owning a PicocoreMX8MN revision 1.20 or lower and want to use this release.


    This does not apply for PCBs for DDR3L based PicocoreMX8Mx. (Rev. 1.20 PCoreMX8Mx) Here, the release can be used from revision 1.20 upwards.


    !!!! Important !!!


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


    Here are some highlights of this release.


    1. New Boot concept for i.MX8MN based boards (fsimx8mn-NBoot)


    The fsimx8mn-NBoot is a first stage bootloader preinstalled to the boards, similar to the fsimx6 Nboot.It handles many board-specific configurations like the DRAM initialization or assembly variants so the user does not need to care about it.


    It does not yet offer the full functionality of the fsimx6 NBoot, like an own command line, but will be further developed in this direction.


    NBoot and U-Boot can be easily updated using the new fsimage command, that automatically flashes to the right hardware partitions. For more information on the fsimage command please see the Linux On F&S Boards documentation chapter "Command fsimage To Handle F&S Images".


    2. New Linux kernel 5.4.70


    The Linux kernel is now based on version 5.4.70.


    From https://kernelnewbies.org/Linux_5.4:

    This release includes the kernel lockdown mode, intended to strengthen the boundary between UID 0 and the kernel; virtio-fs, a high-performance virtio driver which allows a virtualized guest to mount a directory that has been exported on the host; fs-verity, for detecting file tampering, like dm-verity, but works on files rather than block devices; dm-clone, which allows live cloning of dm targets; two new madvise() flags for improved app memory management on Android, support for new Intel/AMD GPUs, support for the exfat file system and removing the experimental status of the EROFS file system; a new haltpoll cpuidle driver and governor that greatly improves performance for virtualized guests wanting to do guest-side polling in the idle loop; and blk-iocost, a I/O cgroup controller that attempts to calculate the cost of I/O more accurately. As always, there are many other new drivers and improvements.


    3. New eMMC-Image format sysimage


    We introduce a new image format for eMMC based boards, that contains a raw Uboot partition, a FAT32 Boot partition for Kernel and device trees, and an ext4 partition for the rootfs. This image can be flashed to the eMMC as a whole, allowing an easy update of the system at once. For further information please the Linux On F&S Baords documentation chapter Mass Storage Devices -> eMMC.


    Please note that the sysimage layout of Buildroot and Yocto currently differ so exchanging separate partitions between those two might not work. This will be fixed in future releases.


    4. Usage of KMS output-chain for DRM bridges


    To ensure the usage of different bridges and panels the kernel mode setting (KMS) will now be used for our device trees. The concept behind KMS is to create one or multiple DRM pipelines consisting of an encoder, bridges and a panel with one or more connectors. The idea is that the display driver knows the display modes that each member of the pipeline supports and can configure a valid display mode for the pipeline.

    [Source: https://www.kernel.org/doc/html/latest/gpu/drm-kms.html]


    5. Yocto 3.0 (Zeus)


    With this release systemd will be the default init system for the example-fus-images.


    Systemd is a init system and service manager for Linux operating systems. It provides a system and service manager that runs as PID 1 and starts the rest of the system. Systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux control groups, maintains mount and automount points, and implements an elaborate transactional dependency-based service control logic.

    [Source: https://www.freedesktop.org/wiki/Software/systemd/]


    It is configured via the systemctl application.


    Also the root file system will now be mounted as read-write by default. This can be changed to read-only when setting up the build enviroment via the fus-setup-release.sh script. See LinuxOnFSBoards_eng.pdf for a detailed description.


    6. New toolchain fs-toolchain-9.3-armv8ahf


    It showed that some packages needed newer Kernelheaders to compile. So we have updated the toolchain again. Please use this new toolchain together with the code of this release.


    Remark: When changing the toolchain, you should always clear the compiler cache, e.g.


    rm -r ~/.ccache ~/.ccache-buildroot


    Otherwise the compiler may mix up precompiled code from the cache with newly compiled code, causing strange runtime errors.


    7. Documentation


    In the past, the documentation that was included in the release package itself was often superseded by newer versions on our website. But people continued to use the outdated version of the release, causing unnecessary complications.


    To avoid this, from now on only the software related documentation is directly included in the release and we have added a chapter to FSiMX8MN_FirstSteps_eng.pdf that contains direct links to the appropriate resources on our website. There you can download the newest versions of hardware documentations, schematics, layout files, certificates, accessories, add-ons, adapters and similar things.


    The software documentation is completely reworked. The FSiMX8MN_FirstSteps_eng.pdf document now really only shows a basic introduction to the work with boards of the fsimx8mn architecture. And there is a new document LinuxOnFSBoards_eng.pdf that shows a more in-depth view of a Linux system in general and of the F&S versions of NBoot, U-Boot, Linux and Buildroot/Yocto in particular. This is still work in progress, some chapters are not fully done yet and will be revised in the future. Check our website from time to time to see if there is a newer version of this document.



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


    The following list shows the most noticable changes in this release in more detail since our last pre i.MX8M-Nano 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 changelog.



    u-boot-2018.03-fsimx8mn-Y2021.10 (30.10.2021)

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

    Supported boards: PicoCoreMX8MN


    - Correct boot from ubi environments to create F&S Updater volumes

    - Add env import/export cmd

    - Fix commands to create F&S Updater volumes in fsimx8mn


    u-boot-2018.03-fsimx8mn-Y2021.09 (24.09.2021 - not released)

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

    Supported boards: PicoCoreMX8MN


    - Add support for board GAR3

    - Add support for board vand3

    - Increase NBoot version to 2021.07

    - F&S Update Framework interface fixed

    - Improve environment variables for fsimx8mm F&S Updater

    - Move enum fsimg_mode from fs_image_common.h to fs_image_common.c

    - Change fsimx8mn to use NBoot

    - Add -ddr3l/-lpddr4 to device tree names for fsimx8mm/fsimx8mn

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

    - Allow optional board-fdt in BOARD-CFG files

    - Add correct fuse values for fsimx8mn

    - Increase size for fs_sys_prompt[]

    - Handle new eMMC layout on fsimx8mn

    - On fsimx8mn, disable code to detect if running on secondary SPL

    - In fat_fus.c, handle files > 2GB better

    - Remove unused folder fsimx8mx_nano

    - Fix building process for fsimx8mm

    - Adjust NAND areas for fsimx8mn nboot

    - Add USB Type C OTG functionality

    - Add variant of PCoreMX8MN




    linux-5.4.70-fsimx8mn-Y2021.10 (30.10.2021)

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

    Supported boards: PicoCoreMX8MN


    - Improve tsc200x-core touch driver

    - Improve tsc200x-core touchscreen driver

    - Improve panel-simple driver of drm/panel

    - Improve sec_mipi_dsim-imx.c driver

    - Improve lontium-lt9211.c bridge driver

    - Improve devicetree picocoremx8mm-ddr3l-lcdif-adp-mipi2rgb.dts

    - Add new devicetree picocoremx8mm-ddr3l-lcdif-g050tan01.dts

    - Add tbs2 mipi2rgb device tree

    - Enable adp-mipi2rgb for fsimx8mn

    - Use panel-lvds driver for output of TC358775

    - Enable USB Type-C for picocoremx8mn-lpddr4

    - Enable adp-mipi2lvds1 for fsimx8mn


    linux-5.4.70-fsimx8mn-Y2021.09 (24.09.2021 - not released)

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

    Supported boards: PicoCoreMX8MN


    - Fix ee0350-mipi-disp touch interrupt pin

    - Revert NXP commit MLK-24133 arm64: SAI1_RXD0 and SAI1_MCLK pins only

    - Enable I2S_B for PicoCoreMX8MP

    - Add cpu freq powersave, conservative governor fix to fsimx8mp_defconfig

    - Add mwifiex node to picocoremx8mp device tree

    - Improve picocoremx8mp Cortex-M7 support

    - Improve support for imx6ul-touchscreen controller

    - Add driver for lontium-lt9211 RGB2LVDS converter

    - Add full device-tree support for PicoCOMA7

    - Improve support for picocoremx6ul revision 1.20

    - Add support for picocoremx6ul100 on architecture fsimx6ul

    - Improve support for picocom1.2

    - Improve architecture fsimx6 PCIe setup

    - Improve support for ADP-MIPI2LVDS1 for fsimx8mm

    - Add support for ADP-MIPI2RGB adapter for fsimx8mm

    - LF-3132: dmaengine: imx-sdma: raise up channel0 priority after resume

    - Enable Polling of the status register for USB-C ptn5110

    - Change naming for device trees of PicoCoreMX8MM_MN_Mx

    - Use simple-panel driver for tc358775 with j070wvtc0211

    - Improve device trees for fsimx8mn




    yocto-3.0-fsimx8mn-Y2021.10 (30.10.2021 based on Yocto 3.0 Zeus)

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

    Supported architectures: fsimx8mn


    - Include all weston binaries for fus-image-std

    - Add mipi2rgb for fsimx8mn

    - Add building of install.scr in Yocto

    - Add adp-mipi2lvds for fsimx8mn

    - Add fs-startscript for core-image-minimal


    yocto-3.0-fsimx8mn-Y2021.09 (24.09.2021 based on Yocto 3.0 Zeus - not released)

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

    Supported architectures: fsimx8mn


    - Remove archiving of sysimg

    - Remove unused config fsimx8mx-nano.conf

    - Adjust device tree names in fsimx8mm and fsimx8mn

    - Enable different UBoot offsets in user area of eMMC

    - Enable initramfs for imx-kobs

    - Add touch calibrator for Weston

    - Update .gitignore




    atf-5.4.70-fsimx8mn-Y2021.09 (02.09.2021)

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

    Supported boards: PicoCoreMX8MN


    - Add imx-atf rel_imx_5.4.70_2.3.2

    - Add domain permission for UART2 on M4

    - Add DEBUG_CONSOLE for imx8mn




    firmware-imx-8.10.1 ddr synopsys (02.09.2021)

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




    Examples

    --------


    (no changes)



    Documentation

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


    - Update to version 1.0 of FSiMX8MN_FirstSteps_eng.pdf

    - Update to version 0.11 of LinuxOnFSBoards_eng.pdf


    Please download the hardware documentation directly from our website.

    Then you always have the newest version.


    Your F&S Support Team

    Hello,


    glad that you have it working. The scfw_tcm.bin is located in the release directory under binaries/. It is copied when executing setup-buildroot once to output/images, but gets cleaned with a "make clean". In the next release this binary will be stored at board/f+s/fsimx8x/ and will get copied through the "imx8-bootloader-prepare.sh" script to the output/images location, so it will not get removed when cleaning. Sorry that I did not think of the scfw_tcm.bin. It is a bit of a niche software for the i.MX8/8X series.



    Your F&S support team

    Hello,


    the create_partitions.sh script is outdated. If you build the images with the new BR2_TARGET_ROOTFS_EXT2_SIZE, the size of the RootFS as well as the size for the RootFS in the partition table (MBR) is updated correctly. The partition table (MBR) is stored inside the sdcard.img file under output/images. Because the partition table (MBR) is only one block/sector large, you can just write the first block/sector of sdcard.img to the eMMC to update the partition table (MBR). With that, the expected size for the RootFS partition is updated as well and the kernel panic should not occur.


    If it is still confusing that a partition table needs to be updated for a bigger partition, it may be advisable to do some research about the general idea behind the master boot record (MBR), which is used in the legacy boot mode and which is the predecessor to the GUID partition table (GPT), which is used for the UEFI boot mode.


    If you want a one line instruction to your problem:

    Write the whole sdcard.img to block 0x0 instead of trying to just update the rootfilesystem. Then the MBR should be correct.


    Your F&S support team