Posts by tr_bef


    I would like to use the RS485 with serial port C (ttymxc3) on the demo board.

    However, I can not set the flag SER_RS485_ENABLED in the configuration!

    In Buildroot's menuconfig I activated the RS485 with BR2_PACKAGE_RS485CONF = y

    rs485conf.flags = SER_RS485_ENABLED;

    ioctl(fd, TIOCSRS485, &rs485conf); // write config

    ioctl(fd, TIOCGRS485, &rs485conf) ; // read config again

    printf ("\nflags: %x", rs485conf.flags); // output -> flags: 0

    What else is to be done?

    Best regards



    the additions to the .pro file are already in the documentation. After restarting QT Creator, the executable was finally in the list of deployment files!

    I use your Fedora 23 Development machine, picocoremx6sx-B2019.03 and QT Creator 4.0.3.

    Do you recommend a newer version of QT Creator?

    Best regards


    Sorry, I searched for the document in the wrong tab.

    The example for the desktop works now.

    But there are some issues with the target device.

    - The list of files to be deployed is empty.

    I added to the .pro file:

    linux-* {

    target.path = /root

    INSTALLS += target


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

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

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

    Best regards



    I can not find the mentioned document "Application Development with QT5" in the Linux folder.

    So far I only know the short description about QT in the document "Quick Start with F & S Development Machine"

    Best regards


    Hello F&S-Team,

    could you provide a QT project file for a non-QT C application (settings for compiler, CMake tool, CMake Generator)?




    I want to transfer a file from the VM to the board with scp.

    In the VM-shell I tried this command:

    scp hello.txt root@

    root@'s password:

    Permission denied, please try again.

    I can't log in, why?

    Best regards



    the board is connected to a ethernet-switch.

    The SOM is the PicoCoreMX6SX-V3-LIN with two ethernet ports.

    I don't know what the previos (delivery) Image-version was.I have done a reverse update to uImage-fsimx6sx-V2.0 found on the Fedora-VM.

    Now the ping is working in both directions again!


    Starting network...

    RTNETLINK answers: File exists

    Starting telnetd: OK

    yes, eth0 exists

    eth0 Link encap:Ethernet HWaddr 00:05:51:0D:59:22
    inet addr: Bcast: Mask:
    inet6 addr: fe80::205:51ff:fe0d:5922/64 Scope:Link
    RX packets:14777 errors:0 dropped:1663 overruns:0 frame:0
    TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1956171 (1.8 MiB) TX bytes:168 (168.0 B)


    after updating to Image B2019.3 the network doesn't work.

    The boot-message shows the error:

    Starting network: RTNETLINK answers: File exists


    a ping from/to the board fails.

    What can be the reason?


    Thanks, it worked!

    I think the command "nand erase.part TargetFS" is missing in the document "i.MX6-SoloX Linux First Steps" under point 3.3.6 Load and Save Root Filesystem.


    i want to flash a new root filesystem, but in U-Boot the command run .ubivol_std fails:

    PicoCoreMX6SX # run .ubivol_std

    ubi0: attaching mtd1

    ubi0: scanning is finished

    ubi0: attached mtd1 (name "mtd=7", size 500 MiB)

    ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes

    ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048

    ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096

    ubi0: good PEBs: 4000, bad PEBs: 0, corrupted PEBs: 0

    ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128

    ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 0

    ubi0: available PEBs: 0, total reserved PEBs: 4000, PEBs reserved for bad PEB handling: 80

    No size specified -> Using max size (0)

    No space left in UBI device!

    verify_mkvol_req failed 12

    What can be the reason?