Posts by fs-support_PJ


    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


    by default ethernet is disabled in linux. So first of all you have to enable ethernet, e.g.

    1. udhcpc -i eth0

    Then the network will be enabled and get dynamically an IP address. Does this work?

    Your F&S Support Team


    sorry for late response.

    The command ".ubivol_std" executes the following commands:

    • ubi part TargetFS
    • ubi create rootfs

    Your error no space left comes from the fact that already a partition with ubi create "name" has been created. But there is already a partition which takes the the whole size. This does not make it possible to create a second partition. If you want to execute the command

    1. .ubivol_std

    then you have to make sure that the partition is empty. The easiest way is to delete the partition

    1. nand erase.part TargetFS

    After that you can run the command

    1. run .ubivol_std

    Your F&S Support Team


    the current GPIO Reference Card has changed, maybe your browser shows the old one. If you are opening the document in the browser, please press shift + F5 to get the current one. In attachment you find also the current one.


    The name GPIO5 has nothing to do with the real GPIO number, the real GPIO is in column GPIO and the number which you have to export is in column /sys/class/gpio/gpio#

    Your F&S Support Team


    we are currently working on our Buildroot releases. After that we will release a new Yocto version. We are planning this release in Q4/2019. The Yocto version will probably be 2.4 (Rocko). In 2.4 the QT version is 5.9.4.

    I think it will take some time to be at QT 5.13 in Yocto. Sorry for inconvenience.

    Your F&S Support Team


    normally the chip is disabled so you have to call

    1. ifconfig -a

    to show all devices even the devices which are disabled.

    Does this fix you issue?

    Your F&S Support Team


    the pin is normally set to GPIO with a PullDown. The Following line is:

    1. MX6QDL_PAD_EIM_A21__GPIO2_IO17    0x400030b0

    To use as PullUp you have to change the line:

    1. MX6QDL_PAD_EIM_A21__GPIO2_IO17    0x4000b0b0

    If you want to use this pin in linux you have to export this pin. You can see in the Code the GPIO is GPIO2_IO17 that means you have to export Pin 49.

    1. echo 49 > /sys/class/gpio/export

    Did you do that and it doesn´t work?

    Your F&S Support Team


    so you want to use this pin as GPIO instead of CTS?

    If you want to use it as GPIO, you have to do the following settings:

    • Disable the UART settings
      1. Either comment out the define CONFIG_PICOCOMA9X_UART_A
      2. Or if you want to use the UART TX/RX then you have to comment out the define CONFIG_PICOCOMA9X_UART_A_RTSCTS and addtionally you have to change something in the pin control. Change the following line:

    MX6SX_PAD_SD3_CLK__UART4_RTS_B 0x1b0b1

    MX6SX_PAD_SD3_DATA2__UART4_CTS_B 0x1b0b1



    MX6SX_PAD_SD3_CLK__UART4_RTS_B 0x1b0b1

    MX6SX_PAD_SD3_DATA2__UART4_CTS_B 0x1b0b1


    • Now you can setup the GPIO in the pin control hog node.
    • Navigate to pinctrl_hog: hoggrp node
    • Add inside node the following line:

    MX6SX_PAD_SD3_DATA2__GPIO7_IO_4 0x0b0b0 //(Pull Up)


    MX6SX_PAD_SD3_DATA2__GPIO7_IO_4 0x030b0 //(Pull Down)


    MX6SX_PAD_SD3_DATA2__GPIO7_IO_4 0x000b0 //(No Pull/Keeper)

    • Now recompile device-tree and install it. Then you should be able to switch the GPIO.

    Your F&S Support Team

    How to use ftpd server from BusBox?

    In this post I will show you an example how you can activate and use the ftpd server from BusyBox. The usage of ftpd shows that we can use the tool tcpsvd. This tool is by default deactivated in BusyBox.

    1. Activate tcpsvd package
      1. Make busybox-menuconfig
      2. Enable Networking Utilities / tcpsvd (14 kb)
      3. Save config and recompile Root-Filesystem
        • make
    2. Activate the networkadapter
    • udhcpc

    The user which connects via ftp to the board, must have a password.Now you can start the ftpd server with a specific folder to share, e.g. /mnt

    • tcpsvd -vE 21 ftpd /mnt

    After that you can use your favorite tool and connect to the board with your IP-Address, Port (21) and the login data.

    Your F&S Support Team

    How to use httpd webserver from BusyBox?

    In this post I will show you an example how you can activate and use the httpd webserver from BusyBox.

    1. First of all you have to start your board and login to Root-Filesystem
    2. Mount the filesystem read-writeable
      • mount -o remount,rw /
    3. Create a folder with any name in any directory
      • mkdir /www
    4. Copy your html file to your directory
      • cp index.html /www
    5. Activate the networkadapter
      • udhcpc
    6. Now you can start the webserver
      • httpd -h /www
    7. After that you can go to your development machine, start your browser and connect to the board

    If you need PHP support you need additional settings. The necessary information can also be found on the following homepage:

    1. In our default configuration php is disabled, so first of all we have to enable php support
      1. Navigate to buildroot folder
      2. call make menuconfig and activate the following packages:
        • Target packages / Interpreter language and scripting / php
        • Target packages / Interpreter language and scripting / php / CGI interface
        • Target packages / Interpreter language and scripting / php / CLI interface
      3. Save and close menuconfig
      4. recompile Root-Filesystem
        • make
    2. After that install the new Root-Filesystem and start the board
    3. Create file httpd.conf in /etc directory. The file need the following line "*.php:/usr/bin/php-cgi"
      • echo *.php:/usr/bin/php-cgi > /etc/httpd.conf
    4. Modify file /etc/php.ini
      • Search after the following line ";cgi.force_redirect = 1" and modify it to "cgi.force_redirect = 0"
      • Search after the following line ";cgi.redirect_status_env = " and modify it to "cgi.redirect_status_env = "yes";"
    5. After that you can repeat the steps 1-7 above

    In attachment you will find an example file index.html for html and an example file index.php for php support. The files are zipped.

    Your F&S Support Team



      (1.22 kB, downloaded 28 times, last: )