Search Results

Search results 1-20 of 1,000. There are more results available, please enhance your search parameters.

  • User Avatar

    wrong date

    fs-support_HK - - PicoCOM4

    Post

    The Real Time Clock must be buffered with a battery, for example a coin cell. Your F&S Support Team

  • User Avatar

    VADC is something different, this is the analog video input (Video A/D Converter). So [2] is not relevant in this case. The device tree setting in [1] is actually all that needs to be set for ADC to work. There are two channels (ADC_A, ADC_B) on adc1 and two channels (ADC_C, ADC_D) on adc2. You will find the analog values in /sys/bus/iio/devices/iio\:device0 and /sys/bus/iio/devices/iio\:device1 respectively. BUT: On a regular efusA9X, the ADC channels are not connected. For some reason I also d…

  • User Avatar

    The USB protocol has a 16 bit value for the count of data blocks that can be transferred in one go. In other words up to 65535 data blocks with 512 bytes each, which is nearly 32MB. From the protocol, there are no restrictions given for this 16 bit value. However in real life, some USB sticks seem to have problems when the maximum value 65535 is used. Then they simply don't answer anymore, which results in USB protocol timeouts. From my point of view these USB sticks do not implement the protoco…

  • User Avatar

    Just a question, how do you enter commands if ttymxc3 is not working in both directions? What I did: Connect (loop-back) pins 3 and 5 of connector J6. Then Source Code (3 lines) The "Hello" appears. Then I did the same for ttymxc3. However as this is the input line for commands, I used telnet to connect to the board instead. Source Code (2 lines) Then I started telnet on the PC: Source Code (1 line) After logging in, I unplugged the PC from connector J7 and looped back pins 3 and 5 instead. On t…

  • User Avatar

    Then I'm out of ideas. Maybe there is a hardware malfunction. Please use RMA and send us the board (incl. PicoCOMA9X) and we will check this. Your F&S Support Team

  • User Avatar

    We are working on the next release with newer kernel, newer Buildroot and newer U-Boot. But this will still take a few weeks. We will of course also have a look on Wayland again, so in the next release this should work out of the box. Your F&S Support Team

  • User Avatar

    OK, let's check something else. If you remove the PicoCOMA9X module from the baseboard, then you'll see two soldering jumper places on the baseboard itself, i.e. two semi-circle shaped pads close to each other so that they can be connected by putting some solder on them. Here the jumper next to the two capacities should be open and the jumper in direction to the PicoCOM connector should be closed (connected). There are also pads for a small 8-pin IC next to this second jumper, this IC should not…

  • User Avatar

    The next release will use a newer Yocto version (most probably 2.4) which also contains a newer Chromium. However it will still take a few weeks until release. Your F&S Support Team

  • User Avatar

    Just to be sure: Terminal input (like ttymxc in this case) is line buffered. so you will not see the input data until you press Return on the PC side. If you do not want this, you have to change the tty settings on the board side to raw mode using stty. And also note that each character is echoed, which may have funny effects if you connect two ttys together: one character is sent, the other side echoes the character, the local side echoes the character again, and so on, resulting in an endless …

  • User Avatar

    In our standard configuration, we do not install any timezone information. If you need this, you have to add this in Buildroot (under topic "System configuration"). Your F&S Support Team

  • User Avatar

    Do you use the serial adapter and null-modem cable that was provided in the starter kit? Did you configure the serial connection in the terminal program on the PC side correctly? 115200 baud, 8 data bits, 1 stop bit, no flow control. For example using flow control on the PC side when RTS/CTS is not active on the PicoCOM side may cause such behavior. Then the PC may think that the board is not ready to receive data due to the uninitialized and therefore incorrect state of the RTS line of the boar…

  • User Avatar

    Ok, we have checked this. Actually Buildroot and Yocto use a different CAN utilities package. Buildroot uses the can-utils package from linux-can on github, Yocto is using the canutils package (without dash) from Pengutronix. Both packages provide commands candump and cansend, but they use a different syntax. can-utils (Buildroot): Source Code (1 line) <n> number of can port <id> either 3 or 8 hex digits for short or extended ID <bytesequence> 2 to 16 hex digits representing the data bytes of th…

  • User Avatar

    I have tried to verify this issue. I extracted Buildroot, called make fsimx6_qt5_defconfig and then called make menuconfig to add the extra packages that you mentioned. Finally I called make. If I look into my rootfs now, I do find the plugin as /usr/lib/qt/plugins/sqldrivers/libqsqlpsql.so. So here it works fine. This PostgreSQL Plugin is part of qt5-base. So if you had Qt5 already built, before you enabled the plugin, then you need to call Source Code (1 line) before the next build. Alternativ…

  • User Avatar

    Thanks for the feedback. Your F&S Support Team

  • User Avatar

    NBoot source code

    fs-support_HK - - efusA9 NXP i.MX6

    Post

    No, usually not. NBoot is closed source. Why would you need this? Your F&S Support Team

  • User Avatar

    I do not understand this. if you configure your Buildroot with fsimx6_qt5_defconfig and build this environment, then Qt5 is already active and you can see the "PostgreSQL Plugin" in "Target packages" -> "Graphic libraries and applications (graphic/text)" -> "Qt5". In other words if you did not see this, then you most probably have configured Qt5 in a wrong way anyway. So please make sure that your environment is actually based on fsimx6_qt5_defconfig if you use Qt5, not on fsimx6_std_defconfig. …

  • User Avatar

    Preparing a working release is rather difficult. In our Buildroot releases we always used the script based boot environment from Busybox, which is basically a simplified System V approach. So it was a logical step to use System V on Yocto, which is also script based. By doing this we could re-use the scripts from Buildroot. Besides that, NXP also used this environment up to Yocto 2.1 and only recently switched to systemd. Switching to systemd is actually on our Todo list. Maybe we will do the sw…

  • User Avatar

    Sorry, but this is application development and thus beyond the support for technical questions. So F&S can not help here. But maybe other customers. Your F&S Support Team

  • User Avatar

    USB Printer Support is not enabled in our Linux default configuration. So in Buildroot call make linux-menuconfig, go to "Device Drivers" -> "USB support" and activate entry "USB printer support". Then recompile the kernel and download it to the board. Now the printer should be detected. Changes in the device tree should not be necessary. Your F&S Support Team

  • User Avatar

    i.MX6-UltraLite Linux Release Y1.0 (Yocto) We have uploaded a new Linux version based on Yocto for all boards and modules based on the i.MX6-UltraLite CPU (UL and ULL) to our server, i.e. the fsimx6ul architecture: efusA7UL and PicoCOM1.2. This release is running on all platforms of this architecture at the same time. So you can download the same binaries for NBoot, U-Boot, Linux kernel and Yocto root filesystem to any of the i.MX6UL/ULL boards and it will run. This is a major release. The relea…