Posts by fs-support_PJ

    Can you please confirm if this bug also occurs with the new release fsimx6-B2020.04?


    What CPU variant do you using? Do you checken the temperature, maybe it´s related to this.


    Your F&S Support Team

    Update to F_S_Development_Machine-Fedora_27_V1.2 (06.05.2020)


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



    New Content:

    • freertos-fsimx7ulp-V2020.03.1 (/home/developer/freertos-fsimx7ulp-V2020.03.1)
    • fsimx6-Y2020.03 (/home/developer/fsimx6-Y2020.03)
    • fsimx6sx-Y2020.03 (/home/developer/fsimx6sx-Y2020.03)
    • fsimx6ul-Y2020.03 (/home/developer/fsimx6ul-Y2020.03)
    • fsimx7ulp-Y2020.03 (/home/developer/fsimx7ulp-Y2020.03)
    • fsimx6-B2020.04 (/home/developer/fsimx6-B2020.04)


    Removed Content:

    • 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.0-armv7ahf)



    Your F&S Support Team

    Hi,


    for ft5x06 driver you can control the treshhold parameter via device-tree or at runtime.


    Device-Tree:

    1. Open arch/arm/boot/dts/efusa9qdl.dtsi
    2. I guess you are using ft5x06 driver so search for line ft5x06_ts@38
    3. Then you can change the threshold entry
    4. Afterwards recompile your device-tree and install it


    Runtime:

    1. I also guess you are using ft5x06 driver
    2. I don´t know the exact path to variable but you can search it by typing the following command in your RootFS
      1. find / -iname "threshold"
    3. Then you should find the file "threshold" which you have to modify
    4. To modify the threshold at runtime type in
      1. echo 80 > .../threshold


    Your F&S Support Team

    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