Search Results

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

  • User Avatar

    Yes, that's correct. But the naming is already swapped in our pin lists. We are showing the names as in a DTE device. So our RTS signal is in fact the CTS signal of i.MX6. This name change usually does not appear anywhere, the only place where you have to take care is in the device tree when configuring these pads. (And of course when you are looking at the driver source code.) But we have added CONFIG macros for RTS/CTS in the device tree, so it should not be necessary to modify these settings …

  • 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…

  • User Avatar

    i.MX6-SoloX 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-SoloX CPU to our server, i.e. the fsimx6sx architecture: efusA9X and PicoCOMA9X. 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.MX6-SoloX boards and it will run. This is a major release. The release consists of two fil…

  • User Avatar

    Probably you missed what RSchubert wanted to say. If you really have your configuration in /etc/network/interfaces as you have cited above, then all IP-Addresses are wrong because you used commas instead of dots to separate the bytes. Then it is obvious why it does not work. Your F&S Support Team

  • User Avatar

    A possible explanation would be some non-consistent package modifications. When Buildroot is built for the first time, it builds for the current configuration. At the same time it also creates so-called stamp files for each completed stage, i.e. some dummy files that tell Buildroot that it already has fully done this stage and does not need to do it again at the next make. This works well if you do not change your configuration significantly. However if you do some changes that would also requir…

  • User Avatar

    Just call Source Code (1 line) Here <executable> is the name of the program you want to disassemble. The result is output on stdout, so you might want to pipe it to "more" or redirect it to a file. Instead of the whole program, you can also give a single .o file. This is easier in large programs because you only need to look at the rather small code section of this module and not the whole application. Your F&S Support Team

  • User Avatar

    When using Buildroot, Qt5 can not work together with X11. You have to build a Qt5 environment first without X11, that just uses the framebuffer. We have provided fsimx6_qt5_defconfig to do this. Source Code (3 lines) This takes a while (longer than the fsimx6_std_defconfig), but after that you have a new rootfs for Qt5. When you download this to the board, you will not see any window manager, just a blank screen. But if you start your Qt application, it should show up and work as expected. Now o…