Posts by fs-support_PJ

    F&S i.MX7ULP FreeRTOS Release (31.03.2020)

    Please see the file


    doc/FreeRTOS_on_FSiMX7ULP_Boards_eng.pdf


    for a description of how everything is installed and used.



    This is a bugfix FreeRTOS release for fsimx7ulp. This bugfix release includes the patch above and some small changes in the documentation. Fsimx7ulp is the software for all boards from F&S that are based on the i.MX 7ULP CPU from NXP. Currently this is the module PicoCoreMX7ULP. 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 following list shows the most noticable changes in this release in more detail since our last regular i.MX 7ULP FreeRTOS-BSP 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.



    freertos-sdk-2.5.1-fsimx7ulp-V2020.03.1 (31.03.2020)

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

    Supported boards: PicoCoreMX7ULP

    not tested: efusA9X, PicoCOMA9X, PicoCoreMX6SX


    - Improve naming of supported boards




    Toolchain


    new toolchain gcc-arm-none-eabi-8-2019-q3-update




    Documentation


    - Update to version 1.2 of FreeRTOS_on_FSiMX7ULP_Boards_eng.pdf


    Your F&S Support Team

    F&S i.MX7ULP FreeRTOS Release (24.03.2020)

    Please see the file


    doc/FreeRTOS_on_FSiMX7ULP_Boards_eng.pdf


    for a description of how everything is installed and used.



    This is a major FreeRTOS release for fsimx7ulp. Fsimx7ulp is the software for all boards from F&S that are based on the i.MX 7ULP CPU from NXP. Currently this is the module PicoCoreMX7ULP. 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.


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



    1. Update to NXP MCUXpresso SDK 2.5.1


    Update to NXP MCUXpresso SDK 2.5.1 software.



    2. Add audio support


    Audio chip sgtl5000 is now supported.


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


    The following list shows the most noticable changes in this release in more detail since our last regular i.MX 7ULP FreeRTOS-BSP 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.



    freertos-sdk-2.5.1-fsimx7ulp-V2020.03 (24.03.2020)

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

    Supported boards: PicoCoreMX7ULP

    not tested: efusA9X, PicoCOMA9X, PicoCoreMX6SX


    - Update all working examples to current NXP MCUXpresso SDK 2.5.1

    - Update not tested examples to current NXP MCUXpresso SDK 2.5.1

    - Add new examples from NXP MCUXpresso SDK 2.5.1

    - Switch input UART clock from 80 MHz to 24 MHz

    - Improve print message of prepare script

    - Add AUD_POW_EN and M4_PER_EN pins to the pin-mux and enable them on start up

    - Improve the power off state on the 7ULP of the A7 by turning of the power

    supply of the LPDDR

    - Add sai driver examples and sgtl5000 codec

    - Add SGTL codec support too the power_mode_switch example

    - Fix linkerfile for hello_world_dram depending on ram size

    - Fix memory addresses of different memory types for the imx6sx examples

    - Fix the placement of the vring-buffers for the imx6sx

    - Move fs_func_gen and fs_gpio_toggle to not_tested

    - Fix compiler warnings for fsimx7ulp

    - Fix power_mode_switch example: Disable GPIO_PAD_LOW_POWER define again

    - Move some examples to not_tested folder

    - Fix compiler warnings for fsimx7ulp

    - Improve sema42 example print message

    - [fsimx7ulp][freertos_tickless]: Modify button

    - Improve naming of supported boards




    Toolchain


    new toolchain gcc-arm-none-eabi-8-2019-q3-update




    Documentation


    - Update to version 1.1 of FreeRTOS_on_FSiMX7ULP_Boards_eng.pdf


    Your F&S Support Team

    Hi,


    we don´t have an own documentation about the backlight driver. We are using the default backlight driver from drivers/video/pwm_bl.c of the kernel (nothing special). The default documentation of the backlight driver is located in the Kernel directory: Documentation/ABI/stable/sysfs-class-backlight.


    I can not tell how to control backlight using Chromium but the kernel provide the default interface for backlight driver. So Chromium must just use the default backlight interface (if supported in Chormium). In my opinion it is a Chromium specific setup.


    Your F&S Support Team

    F&S Secure Boot Release V2020.02


    we have uploaded a new F&S Secure Boot version for all supported boards with an i.MX6 CPU to our server, i.e. i.MX6S/DL/D/Q, i.MX6SX, i.MX6UL/ULL.


    This is a major release. The release consists of one file:


    fs-secure-boot-V2020.02.tar.bz2


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


    This tar archiv is compressed with bzip2. So to see the files, you first have to unpack the archives


    Code
    1. 1. tar xvf fs-secure-boot-V2020.02.tar.bz2

    This will create a directory fs-secure-boot-V2020.02 that contains all the files of the release.


    Please read the file doc/FS_Secure_Boot.pdf. It lists the meaning of all files and shows how to install and use everything.


    The release consists of the following files and directories:


    • Readme.txt (Release notes)
    • setup-fs-secure-boot (Script to unpack fs-secure-boot release)
    • binaries/ (Precompiled secure images)
    • doc/ (software manual)
    • sources/ (source code packages)


    Release Notes for F&S Secure Boot V2020.02


    Here are some highlights of this release.


    1. Support signing and encrypting of zImages


    This is the first regular release that supports the kernel type zImage.



    2. Support signing and encrypting of FIT-Images


    This is the first regular release that supports the image type FIT-Images.



    3. Add possibility to setup CST via an environment variable


    Now it´s possible to setup the CST directory via an environment variable.



    Your F&S Support Team




    Note:

    You are only able to purchase our F&S Secure Boot release, if you have ordered it. For further information, see https://www.fs-net.de/en/support/secureboot/

    Hi,


    if you have connected the display to the backlight PWM then you should be able to setup the brightness. You can change it from display off to fully brightness. There is a driver which handle this. It´s located under

    Code
    1. cd /sys/class/backlight/


    So in my opinion you can create a time-controlled program by your own, which are controlls the backlight and also recognize the touch. I´m not sure if there is any driver which can handle that for you. Maybe there are programs which helps you to implement that (e.g. Cron).


    Your F&S Support Team

    Hi,


    you´re welcome. Yes this is correct, first you have to transfer the image to the RAM and after that you can write it to the emmc.


    Yes if the image size is bigger than the RAM size, you are not able to transfer and write it in one piece. But normally it should work if you split the image in different parts and write it with the correct offsets.


    Your F&S Support Team

    Update to F_S_Development_Machine-Fedora_27_V1.1 (07.01.2020)


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


    Content:

    • fsimx7ulp-B2019.12 (/home/developer/fsimx7ulp-B2019.12)
    • freertos-fsimx6sx-V2019.12 (/home/developer/freertos-fsimx6sx-V2019.12)
    • gcc-arm-none-eabi-8-2019-q3-update (/usr/local/arm/gcc-arm-none-eabi-8-2019-q3-update )


    Environment Variables:


    The file "/home/developer/.bashrc" has been set up.

    • export variable "ARMGCC_DIR=/usr/local/arm/gcc-arm-none-eabi-8-2019-q3-update"


    Your F&S Support Team

    Hi,


    yes it is possible to write an yocto image to emmc. Yes you can use the mmc write command. The syntax of this command is:


    Code
    1. mmc write addr blk# cnt


    If you use the command mmc write you have to convert the byte size of the image to block size. Every block has 512 bytes. So if you have an image with the length of 1048576 bytes, the blocksize is 1048576/512 = 2048 blocks in hex 0x800.


    For example you want to write the image with the length 1048576 bytes to mmc device 0 at offset 0. The image is available at $loadaddr. The command is

    Code
    1. mmc write $loadaddr 0x0 0x800


    Here are the following steps which you have to do:


    1. Transfer image to your Board
      1. tftp minimal.img
    2. Switch to emmc (I guess device 0)
      1. mmc dev 0 0
    3. Write to emmc (I assume length is 10 MB (10485760 Bytes = 20480 Block / 0x5000 block)
      1. mmc write $loadaddr 0x0 0x5000
    4. Now you should be able to read this partitions
      1. ls mmc 0:1 and ls mmc 0:2


    Your F&S Support Team

    F&S i.MX6SX FreeRTOS Release (20.12.2019)

    Please see the file


    doc/FreeRTOS_on_FSiMX6SX_Boards_eng.pdf


    for a description of how everything is installed and used.



    This is a major FreeRTOS release for fsimx6sx. fsimx6sx is the software for all boards from F&S that are based on the i.MX6-SoloX CPU from NXP. Currently these are the modules efusA9X, PicoCOMA9X and PicoCoreMX6SX. 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.


    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 FreeRTOS-BSP 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. For example the "2019.12" of this release indicates a FreeRTOS-BSP based release from December 2019.



    2. Add support for rpmsg-lite


    Now NXP´s rpmsg-lite is used instead of openAMP RPMsg. This makes the size of the images significant smaller.



    3. Rework of the directory layout


    Change directory layout but the examples can be built with the same commands as before.



    4. Merge fsimx6sx and fsimx7ulp git repositories


    The two git repositories fsimx6sx and fsimx7ulp are merged together so it´s easier to handle.


    5. Add hello_world_split example


    The hello_world_split example shows the user how to split an example in different memory regions like DDR, OCRAM and TCM.


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


    The following list shows the most noticable changes in this release in more detail since our last regular i.MX6SX FreeRTOS-BSP 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.



    freertos-bsp-1.0.1-fsimx6sx-V2019.12 (20.12.2019)

    Supported boards: efusA9X, PicoCOMA9X, PicoCoreMX6SX,

    Not tested: PicoCoreMX7ULP


    - Add hello_world_split_example

    - Merge branch 'temp'

    - Remove example folder

    - Move not portet examples

    - Add cmake build alls upport for 7ulp

    - Improve 7ulp make all function

    - Remove unnecessary files

    - Move board specific files for better sdk layout (imx6sx + 7ulp)

    - Improve prepare.sh and install7ulp.sh script to support new SDK layout

    - Add imx6sx nxp documentary move linux_app/ to not tested

    - Add picocoremx6sx support

    - Rename boards directory to examples

    - Remove readme.txt and xml files from the examples

    - Add and modify examples, which did not work because of Soc revision A

    - Improve binary to image conversion

    - Remove nxp evk

    - Add cmmsis examples to not tested

    - Fix qspi examples

    - Add power_mode_switch example

    - Add shell_mem example

    - Fix picocore adc build bug

    - Remove some unnecessary files

    - Add not_tested readme.txt

    - Update all working examples to current NXP MCUXpresso SDK 2.5.1

    - Update not tested examples to current NXP MCUXpresso SDK 2.5.1

    - Add new examples from NXP MCUXpresso SDK 2.5.1

    - Switch input UART clock from 80 MHz to 24 MHz

    - Improve print message of prepare script

    - Add AUD_PW_EN and M4_PER_EN pins to the pin-mux and enable them on start up

    - Improve the power off state on the 7ULP of the A7 by turning of the power supply of the LPDDR

    - Add sai driver examples and sgtl5000 codec

    - Add SGTL codec support to the power_mode_switch example

    - Fix linkerfile for hello_world_dram depending on ram size

    - Fix memory addresses of different memory types for the imx6sx examples

    - Fix the placement of the vring-buffers for the imx6sx

    - Move fs_func_gen and fs_gpio_toggle to not_tested

    - fix compiler warnings for fsimx6sx




    Toolchain


    new toolchain gcc-arm-none-eabi-8-2019-q3-update




    Documentation


    - Update to version 3.1 of FreeRTOS_on_FSiMX6SX_Boards_eng.pdf


    Your F&S Support Team

    F&S i.MX7ULP Buildroot Release (18.12.2019)

    Please see the file


    doc/FSiMX7ULP_FirstSteps_eng.pdf


    for a description of how everything is installed and used.



    This is a major release for fsimx7ulp. fsimx7ulp is the software for all boards from F&S that are based on the i.MX 7ULP CPU from NXP. Currently these are the modules PicoCoreMX7ULP. 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.


    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.13" of this release indicates a Buildroot based release from November 2019.



    2. Support for board PicoCoreMX7ULP revision 1.20


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


    3. Buildroot 2019.05.1


    Buildroot 2019.05 has many many updated packages, for example Qt-5.12, busybox-1.30.1, xserver-1.20.5 and gstreamer-1.16.0. We actually use buildroot-2019.05.1, which is a newer version that already has some more fixes.


    4. New toolchain fs-toolchain-8.3-armv7ahf


    Our new toolchain is now based on gcc-8.3 that fully supports C++14 and has basic support for C++17 and even some experimental support for C++2a.


    This toolchain is now a 64-bit toolchain, i.e. it will not run on PCs (or VMs) with a 32-bit Linux anymore. The default output of the toolchain is of course still ARMv7 code for 32 bit ARM CPUs like Cortex-A7 or Cortex-A9, as in i.MX6UL or i.MX6SX.


    This toolchain also fixes a bug in the calling convention for ARM CPUs that was introduced in gcc-5.x and prevented some code optimizations. Many software packages now depend on a compiler that has this bug fixed. For example our new u-boot-2018.03 will produce bad code if compiled with a toolchain before gcc-6.0. Qt5-webengine will not compile with a toolchain before gcc-8.0. So please use this new toolchain together with the code of this release.


    5. New WLAN module Azurewave CM276NF


    In the past, the WLAN module Laird Sterling-LWB5 was mounted. In the current HW revision 1.20 the new module Azurewave CM276NF is mounted.


    6. 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 FSiMX7ULP_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 FSiMX7ULP_FirstSteps_eng.pdf document now really only shows a basic introduction to the work with boards of the fsimx7ulp 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 i.MX7ULP release (not counting the intermedieate release for PicoCoremX7ULP). Please note that the source code may 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-2017.03-fsimx7ulp-B2019.12 (18.12.2019)

    Supported boards: PicoCoreMX7ULP

    Not tested: efusA9X, PicoCOMA9X, PicoCoreMX6SX, CONT1, efusA7UL, PicoCOM1.2, PicoCoreMX6UL, GAR1, GAR2, CubeA7UL, Cube2.0, armStoneA9, armStoneA9r2, efusA9, PicoMODA9, NetDCUA9,

    QBlissA9, QBlissA9r2, CUBEA5, armStoneA5, NetDCUA5, PicoCOMA5, AGATEWAY, HGATEWAY


    • Improve fsimx7ulp defconfig - otg pwr polarity
    • Add support for PicoCoreMX7ULP rev. 1.20
    • Add support for Gigadevice SPI flashes
    • Add option for monlitic LPDDR3 RAM in DCD
    • Improve fsimx7ulp environment size
    • Improve fsimx7ulp RNDIS configuration
    • Fix some compiler warnings and remove some unnecessary entrys in imx7ulp.dtsi
    • Inlcude: update log2 header from the Linux kernel
    • Add support for SPI NOR flash gd25lq80c



    linux-4.9.88-fsimx7ulp-B2019.12 (18.12.2019)

    Supported boards: PicoCoreMX7ULP

    Not tested: efusA9X, PicoCOMA9X, PicoCoreMX6SX, CONT1, efusA7UL, PicoCOM1.2, PicoCoreMX6UL, GAR1, GAR2, CubeA7UL, Cube2.0, armStoneA9, armStoneA9r2, efusA9, PicoMODA9, NetDCUA9,

    QBlissA9, QBlissA9r2, CUBEA5, armStoneA5, NetDCUA5, PicoCOMA5, AGATEWAY, HGATEWAY


    • Add SD1_VSEL to picocoremx6ull.dts to support UHS SD cards
    • Improve picocoremx6sx device-tree - rework
    • Improve picocoremx6ul device-tree usb otg1 support
    • New merge for rel_imx_4.9.11_1.0.0_ga
    • Handle flexcan names in a common way in device trees
    • New merge for rel_imx_4.9.88_2.0.0_ga
    • Have new minimal defconfigs for fsimx6/sx/ul
    • Improve mipi_dsi_northwest driver flag interpretation
    • Improve picocoremx7ulp device-tree - add mipi-dsi display support
    • Add i.MX6 PCIe driver to defconfig
    • Add PCIe support for all F&S i.MX6 boards
    • Add Marvell WIFI PCIe driver to fsimx6_defconfig
    • Improve PCI_IMX6 driver activation for fsimx6sx_defconfig
    • Add property lrclk-strength to SGTL5000 device tree node
    • fsimx6: Fix audio clock rates, set lrclk-strength for SGTL5000
    • fsimx6: HDMI: Use DVI mode, do not overwrite pixel format
    • Add support for 3rd and 4th camera for ISL7998x on fsimx6
    • Add CMSPAR option to IMX UART
    • Improve focaltech ft5x06 driver - support reverse coordinates
    • Support Azurewave-CM276NF for fsimx7ulp_defconfig
    • Add support for picocoremx7ulp rev. 1.20 and remove old revisions
    • Fix Ethernet clock in mach-imx6sx.c
    • Add 12.5pF setting for RTC PCF85063TP, fix two bugs
    • Handle USB over-current polarity
    • Split picocoremx6ull.dts into UL and ULL version
    • Re-factor driver for PCA963X (leds-pca963x.c)
    • Change F&S device trees to use new leds-pca963x driver
    • Update to newest Atmel MXT touch driver
    • Add cube2.0ull.dts
    • Clarify F&S device tree settings (LVDS, Ilitek, audio clock)
    • Fix default touches for PicoCoreMX6UL/SX
    • Replace deprecated fsl,uart-has-rtscts in F&S device trees
    • Add new default LVDS display FS-J070WVTC0211 to F&S devicetrees
    • Improve PicoModA9 device-tree settings for LCD supply regulator
    • Revert RTC PCF8563 driver to previous version
    • Speed up firmware download in btmrvl_sdio.c
    • Add UART_C for board revision 1.40 of GAR1
    • Add config file for atmel mxt224e version 2 touch
    • Add disable-over-current flag to picocoremx7ulp device-tree
    • Add support for crypto unit in picocoremx7ulp
    • Turn off -Wattribute-alias to support GCC 8
    • Backport minimal compiler_attributes.h to support GCC 9
    • Disable user space firmware loader helper from F&S defconfigs
    • Remove support for BT-AMP on Marvell SD8787 Bluetooth
    • Add support for mipi display YTC310KLAA
    • Add YTC310KLAA mipi display to fsimx7ulp
    • imx6ull: VDD_SOC_CAP -> changed voltage from 1.175V to 1.25V
    • Add PWM_A to PicoCoreMX6SX device-tree
    • Improve picocoremx6ul.dts - add defines for HW units
    • Improve picocoremx6sx.dts - increment board revision
    • Improve F&S i.MX6SX/UL device-trees - Update Copyright
    • fec_main: Do not init MII bus in case of fixed link
    • Add DP83848 Ethernet PHY to fsimx6ul_defconfig
    • Add devicetree for GAR2
    • Improve fsimx7ulp VLLS state by turning of LPDDR-IOs correctly
    • Add audio support for imx7ULP via rpmsg-audio
    • Fix DT for efusA9, QBlissA9 and QBlissA9r2 for ft5x06_ts.c
    • Add mainline patches to remove compiler warnings with gcc-8
    • Remove compiler warnings with gcc-8 in F&S specific files
    • Fix clock enabling in pxp_dma_v3.c, add to fsimx6ul
    • Support gstreamer imxv4l2sink with PXP on fsimx6sx
    • Add RTC IRQ settings on efusA9 and efusA9X
    • Add check for valid memory-region to auxcore-driver
    • Improve cont1 device tree - update board revision
    • Improve fsimx6sx/fsimx6ul device-trees
    • Improve picocoremx6sx device tree - fix bl_pwm
    • Improve PicoCoreMX6SX/UL device-tree - VLCD_ON pin
    • Remove rpmsg message from efusa9x.dts
    • Add missing RTS/CTS for UART_C on PicoCoreMX6SX
    • Fix Ubifs crashes after resume from suspend
    • Fix ov564x_mipi devicetree entry
    • Improve mxs-dma driver by adding runtime_suspend support
    • Improve picocoremx7ulp device-tree
    • Add support for mipi display TM050JDHG33
    • Improve picocoremx7ulp devicetree, set new default MIPI display
    • Improve picocoremx7ulp lpi2c5 node



    buildroot-2019.05.1-fsimx7ulp-B2019.12 (18.12.2019)

    Supported boards: PicoCoreMX7ULP

    Not tested: efusA9X, PicoCOMA9X, PicoCoreMX6SX, CONT1, efusA7UL, PicoCOM1.2, PicoCoreMX6UL, GAR1, GAR2, CubeA7UL, Cube2.0, armStoneA9, armStoneA9r2, efusA9, PicoMODA9, NetDCUA9,

    QBlissA9, QBlissA9r2, CUBEA5, armStoneA5, NetDCUA5, PicoCOMA5, AGATEWAY, HGATEWAY


    • Drop support for PicoCOM4
    • Drop support for fss5pv210 (armStoneA8, NetDCU14, PicoMOD7A)
    • Switch to fs-toolchain-7.4-armv7ahf for F&S boards
    • Switch F&S boards to zImage
    • Update xdriver_xf86-video-fbdev to version 0.5.0
    • Rebase to buildroot-2019.02
    • Correct picocoremx6ull dts name in qt5_defconfig
    • Fix qt5webengine compilation
    • Add firmware Marvell 88W8997
    • fsimx7ulp_std_defconfig set xserver to current version
    • Fix dependencies and macro names in gstreamer1
    • Add package imx-gstreamer1 for NXP based gstreamer1 version
    • Use NXP version of libdrm
    • Make IMX codecs and parsers work with imx-gstreamer1
    • Use imx-gstreamer1 on fsimx6x/fsimx6sx/fsimx6ul
    • Add support for MWIFIEX_SDSD8997 WLAN/BT
    • Add Azurewave-CM276NF support for fsimx7ulp
    • Do not use GL and GLES at the same time in fsimx6_std_defconfig
    • Rebase to buildroot-2019.05
    • Always use (host-)gettext-gnu on F&S configurations
    • Rebase to buildroot-2019.05.1
    • Update weston package for F&S boards to rel_imx_4.9.88_2.0.0_ga
    • Activate similar set of Qt5 modules in all F&S defconfigs
    • Update F&S busybox defconfig to 1.30.1
    • Add cube2.0ull device tree to cube defconfig and finalscript-cube
    • Optimize ALSA configuration file (asound.state)
    • Add Mesa3D and Weston demos to F&S wayland_defconfig
    • Add support for libglfw on Wayland
    • Fix Qt5 webengine build
    • Switch to fs-toolchain-8.3-armv7ahf for F&S boards
    • Add GAR2 devicetree to fsimx6ul defconfigs
    • Add rpmsg-audio alsamixer config
    • Add fsimx6sx/fsimx6ul wayland defconfig
    • Add startup script for weston
    • Replace package silex-wlan-fs with newer version
    • Keep bluez5_utils-headers on same version as bluez5_utils
    • Do not install S50telnet by default, only if requested
    • Add spi-tools to F&S defconfigs
    • Add support for device-tree gar2 in fsimx6ul_wayland_defconfig
    • Rework of fsimx7ulp_std_defconfig
    • Add fsimx7ulp_wayland_defconfig
    • Improve rootfs_ext2_size of fsimx7ulp configs
    • Rework of fsimx7ulp_qt5_defconfig



    Examples


    (no changes)



    Toolchain


    fs-toolchain-8.3-armv7ahf.tar.bz2 for Linux


    • Based on gcc-8.3
    • Support for C and C++
    • Includes glibc-2.29 (compiled for ARM code)
    • With binutils-2.32
    • Hardware floating point
    • Native Posix Thread Library (NPTL)
    • Full support for C++14 and OpenMP 4.5
    • Basic support for C++17
    • Experimental support for C++2a



    Documentation


    - Update to version 2.0 of FSiMX7ULP_FirstSteps_eng.pdf

    - Add new version 0.3 of LinuxOnFSBoards_eng.pdf


    Please download the hardware documentation and GPIO Reference Cards directly from our website. Then you always have the newest version.


    Your F&S Support Team

    Hi,


    just for clarification, if you want to write to the NAND flash you should write the filesystem with the extension .ubifs. I think the minimal image is smaller then the NAND flash size.

    If you want to to write the filesystem to the eMMC then you should use the filesystem with the extension .ext4.


    UBoot only supports raw write commands, e.g. mmc wirte (block wise).


    I know i can perform this from linux using dd command, I simply put the image on the usb, mount the usb and use dd to flash the image on /dev/mmcblk2 which represents the emmc card. However, I need to use u-boot to detect the USB and if it finds an image file, then it flashes it on the emmc.


    In linux you can either write the filesystem with dd to eMMC or you can mount the rootfs.ext4 and copy the files high level to the eMMC ext4 partition.


    We recommend to use NAND flash if the ubifs filesize fits.


    Your F&S Support Team

    Dear Mr. Schubert,


    RS485 works on kernel 4.9.88. You can open the device in rootfs and set the necessary RS485 flags.


    The changes to enable rs485 while booting are not implemented yet. We have noticed that and we will add this in the future to the uart driver.


    We made some changes in the driver to support RS485 9 bit mode.


    Your F&S Support Team

    F&S Development Machine with Fedora 27 (10.12.2019)


    There is a new Virtual Machine with Fedora27 in your download section available (My F&S / Tools-Linux / F_S_Development_Machine-Fedora_27_V1.0.ova). The structure of the virtual machine is listed below.


    Content:

    • fsimx6-B2019.08 (/home/developer/fsimx6-B2019.08)
    • fsimx6sx-B2019.11 (/home/developer/fsimx6sx-B2019.11)
    • fsimx6ul-B2019.11 (/home/developer/fsimx6sx-B2019.11)
    • fs-toolchain-5.2.0-armv7ahf (/usr/local/arm/fs-toolchain-5.2.0-armv7ahf)
    • fs-toolchain-7.4.0-armv7ahf (/usr/local/arm/fs-toolchain-7.4-armv7ahf)
    • fs-toolchain-8.3.0-armv7ahf (/usr/local/arm/fs-toolchain-8.3-armv7ahf)


    Packages:


    The following packages are installed:


    gawk tar gzip python3 unzip perl lbzip2 bzip2 lzop findutils bc wget putty bless tigervnc cifs-utils meld emacs kate cmake make gcc git git-cola eclipse-cdt qt-creator glibc glibc.i686 glibc-devel.i686 zlib zlib.i686 zlib-devel.i686 zlib-static.i686 libstdc++.i686 libgcc.i686 ncurses ncurses-base ncurses-devel ncurses-libs bison bison-devel bison-runtime perl-ExtUtils-MakeMaker perl-Data-Dumper perl-Thread-Queue perl-bignum socat diffutils diffstat cpp gcc-c++ patch python3-pexpect automake chrpath ccache which file cpio python autoconf qt5-devel htop texinfo python3-pip xz dtc libatomic qtcreator



    User:


    The default user ist "developer" and the corresponding password is also "developer". This user has root privileges.



    Set up programs:


    The following programs have been set up.

    • NFS Server
    • TFTP Server



    Tools:

    • setup_toolchain (/etc/profile.d) - easily switch between toolchains. Just call "settoolchain" in terminal
    • mkimage (/usr/bin)



    Environment Variables:


    The file "/home/developer/.bashrc" has been set up.

    • export variable "ARCH=arm"
    • export variable "CROSS_COMPILE=arm-linux-"
    • export variable "BUILDROOT_DL_DIR=$HOME/releases/dl"
    • export variable "BR2_DL_DIR=$BUILDROOT_DL_DIR"



    Others:


    Setup F&S wallpaper for home screen and login screen.



    Documentation:

    • Quickstart with F_S Development Maschine.pdf

    The document can be downloaded either at "My F&S / Tools-Linux / Quickstart with F_S Development Maschine.pdf" or "select your specific Board / Documents / Quickstart with FS Development Machine".


    Your F&S Support Team

    Hi,


    - The list of files to be deployed is empty.

    I added to the .pro file:

    linux-* {

    target.path = /root

    INSTALLS += target

    }


    Thanks for the hints, we will check our documentation and change it.


    - Is the configuration for the CMake Tool in Figure 13 correct?

    Would not it have to be CMake (for ARM Cross Compile)?


    Yes you are right there is something wrong in the Figure, we will fix it.


    - The "general message" window shows an error:

    /home/developer/picocoremx6sx-B2019.03/build/buildroot-2018.11-fsimx6sx-B2019.03/output/host/mkspecs/features/qmake_use.prf(6): 'take_first' is not a recognized replace function.

    Project ERROR: Library '' is not defined.


    Do you use your own virtual machine or do you use our Fedora 23 Development machine?

    And you are using the release picocoremx6sx-B2019.03?



    Your F&S Support Team

    Hi,


    by default we have preinstalled the tftp server/client on the VM/Board. So you can use this protocol to transfer data. If you want to use scp you have to setup the ssh server on the board. Therefore you have to do the following steps.

    1. Activate network connections
      1. e.g. udhcpc
    2. Setup a date
      1. date "2019-11-07 10:00"
    3. Modify sshd_config (/etc/ssh/sshd_config) if you want to login as root. Before you can modify the file be sure your rootfs is mounted writeable.
      1. In the file you have to insert the line PermitRootLogin=yes
      2. If you want to allow to connect with empty password, then you also have to set PermitEmptyPasswords=yes
    4. After that you can start the ssh server
      1. /etc/init.d/S50sshd start if it´s already started /etc/init.d/S50sshd restart
    5. Now you should be able to use the scp command.


    Your F&S Support Team