Posts by fs-support_PG

    Hello,

    We can reproduce the issue. The system seems to hang when initializing the GPU.

    A quick workaround would be to disable the GPU in the qblissa9r2q device tree:

    Add the following lines to the bottom of arch/arm/boot/dts/qblissa9r2q.dts:


    Code
    1. &gpu_3d{
    2.     status = "disbaled";
    3. };

    Recompile and install the new qblissa9r2q.dtb to the board.


    We will further investigate this issue and come back to you.


    Your F&S Support Team

    There seems to be a config file at /etc/alsa/conf.d/ missing.


    Please try the following:

    Code
    1. mount -o remount,rw /
    2. mkdir -p /etc/alsa/conf.d
    3. cp /usr/share/alsa/20-bluealsa.conf /etc/alsa/conf.d/


    Your F&S Support Team

    Did you try to set the bluetooth device directly?

    Code
    1. aplay -D bluealsa:DEV=XX:XX:XX:XX:XX:XX test.wav

    Also, can you run this command?

    Code
    1. bluealsa-aplay -L


    Your F&S Support Team

    Hello Michele ,


    interesting project.

    Did you try to activate Target packages -> Networking applications -> bluez-tools in the menuconfig for bluethoothd ?

    It should get installed to /usr/libexec/bluetooth/bluetoothd

    Your F&S Support Team

    Hello,


    the SNVS_HPRTC and the SNVS_LPRTC seem to be two different RTCs. However, chapter

    58.4.2 Non-secure real-time counter of the imx6sx reference manual states, that they can be synchronized but does not explain how...

    The linux driver at drivers/rtc/snvs-rtc.c seems to read and write directly from/to the LPRTC but the access should be only possible with activated HPRTC, so maybe you could try to read from the LPRTC registers from the Cortex-M4 side.


    For more information please read 58.4 SNVS structure of the

    i.MX 6SoloX Applications Processor Reference Manual Rev. 4, 05/2020


    Your F&S Support Team

    Hello,


    it is a know issue that some USB memory devices cause problems in Uboot.


    Here is a quote from an other discussion:

    Compatible USB Sticks


    Which release are you using?


    Your F&S Support Team

    Hello Stefan,


    the PicoCOM9X uses an extern RTC connected via I2C by default, as it is more precise.

    If you set the RTC time to the system-time with the hwclock -w command, it will set the extern RTC, not the intern RTC.

    If both RTCs are activated in your system you should see multiple RTCs at /dev/rtcX.

    You can set a specific RTC by using the command hwclock -w --rtc=/dev/rtcX.


    Please make sure to protect shared peripherals from simultaneous access by using e.g. Semaphores.

    Unfortunately, NXP did not implement RDC_Sema42 in the Linux Kernel, but you can use the normal Sema4.

    The driver drivers/char/imx_amp/imx_sema4.c can be used on Linux side, while the example

    freertos/examples/fsimx6sx/demo_apps/sema4_demo can be used on Cortex-M4 side.


    Your F&S Support Team

    Hello,


    we have reuploaded the OVA image. Please try to import it again.


    We have also uploaded a MD5SUM. You can check if your download was correct by computing your local MD5SUM with the PowerShell commend


    certutil.exe -hashfile <PATH\TO\YOUR\OVA> MD5


    We have also noticed that the error Result Code: E_INVALIDARG (0x80070057 also can occur, if there is not enough disc space left, so please make sure that you have at least 30GB available.


    If it still does not work please send a mail to sales@fs-net.de and you will recive a alternative download link.


    Your F&S Support Team

    Hello,

    Yes it should be also available in fsimx6-V3.0., but you should update if you can afford it, as the new release offers a lot of bug fixes and performance improvements and is better supported.


    Your F&S Support Team

    Hello,


    Which release are you using?


    In fsimx6-B2020.06 the TUN/TAP driver can be activated in the Linux kernel menuconfig at


    Device Drivers -> Network device support -> Network core driver support -> Universial TUN/TAP device support


    You can either add CONFIG_TUN=y to arch/arm/configs/fsimx6_defconfig to your linux-fsimx6 kernel


    or run make linux-menuconfig in your buildroot directory and select it by hand.


    Either way, you have to run make linux-reconfigure to rebuild the kernel and use the new kernel on your board. You should get the device /dev/net/tun


    Your F&S Support Team

    Hello,


    did you copy the content of install.scr or install.txt?


    Also, did you try to use the install.txt file from the source/ directory of the release directly to create the install.scr?


    There might be some special characters in your test.txt that lead to this behavior.


    Your F&S Support Team

    Touchscreen Fix for 3.5" MIPI-DSI Display mit PCAP Touch ( B.LCD.22)


    The Touchscreen of the 3.5" MIPI-DSI Display mit PCAP Touch ( B.LCD.22) is not working with the following combination:


    Boards: PcoreMX8MM-V1-LIN, PcoreMX8MM-V13-LIN [Rev1.3]

    Adapter: ADP-MIPI2MIPI1 [Rev 1.2]

    Display: 3.5" MIPI-DSI Display mit PCAP Touch ( B.LCD.22)

    Releases: Y2021.04, B2021.06


    To fix this, you can either apply the attached patch to the Linux Kernel and rebuild the device tree or make the following U-boot settings:


    Run the following command in the U-boot console:

    Code
    1. setenv fix_EE0350_touch 'fdt addr $fdtaddr; fdt set i2c1/mxt336u interrupt-parent <0x00000036>; fdt set i2c1/mxt336u interrupts <0x00000000 0x00000002>;'

    Edit the $fdt variable and add the command run fix_EE0350_touch befor the booti command. For example

    Code
    1. editenv fdt
    2. mmc rescan; load mmc 2 0x43000000 picocoremx8mm-lcdif-adp-mipi2mipi1-ee0350et-2cp.dtb;run fix_EE0350_touch;booti 40480000 - 0x43000000
    3. saveenv

    ( The $fdt variable may look different, depending on where the device tree is loaded from)


    Boot, the board. The touchscreen should work now.


    Your F&S Support Team

    Touchscreen Fix for 3.5" MIPI-DSI Display mit PCAP Touch ( B.LCD.22)


    The Touchscreen of the 3.5" MIPI-DSI Display mit PCAP Touch ( B.LCD.22) is not working with the following combination:


    Boards: PcoreMX8MM-V1-LIN, PcoreMX8MM-V13-LIN [Rev1.3]

    Adapter: ADP-MIPI2MIPI1 [Rev 1.2]

    Display: 3.5" MIPI-DSI Display mit PCAP Touch ( B.LCD.22)

    Releases: Y2021.04, B2021.06


    To fix this, you can either apply the attached patch to the Linux Kernel and rebuild the device tree or make the following U-boot settings:


    Run the following command in the U-boot console:

    Code
    1. setenv fix_EE0350_touch 'fdt addr $fdtaddr; fdt set i2c1/mxt336u interrupt-parent <0x00000036>; fdt set i2c1/mxt336u interrupts <0x00000000 0x00000002>;'

    Edit the $fdt variable and add the command run fix_EE0350_touch befor the booti command. For example

    Code
    1. editenv fdt
    2. mmc rescan; load mmc 2 0x43000000 picocoremx8mm-lcdif-adp-mipi2mipi1-ee0350et-2cp.dtb;run fix_EE0350_touch;booti 40480000 - 0x43000000
    3. saveenv

    ( The $fdt variable may look different, depending on where the device tree is loaded from)


    Boot the board. The touchscreen should work now.


    Your F&S Support Team