Posts by telerob

    So, with the next windows 10 update to version 1709 we got more troubles. We looked into microsoft forums and fixed so far the problems. But one pc still do not want to install the WMDC. We got the error of a missing DLL during the installation of the WMDC. Are there any ideas what to do?


    we have installed a computer with windows 10 and we want to connect to to the netdcu board "netdcu9". But we get no connection to the board. Neither with windows 10 synchronizing centre nor with the windows mobile device centre.
    Any ideas where to look ?



    I tried under windows 10 (logged in as local administrator) a kernel uodate with the netdcu usb loader 2.4.1
    After connecting the serial and usb cable and starting the kernelupdate process in the bootlader menu with DU, i got following message from the dcuterm shell:
    RNDISFN: UFN_RESET received
    RNDISFN: UFN_RESET received
    RNDISFN: UFN_RESET received

    than it stops

    In the application NetDCU-USB-Loader the red LED don't switch to green.

    After checking the forums i tried to install manually the FSBoardUSB driver with the FSBoardUSB.inf file.
    It returns with the message "Die INF-Datei des Drittanbieters enthält keine Digitalsignaturinformationen".

    Is this the problem?

    Any help is welcome.


    I use fsimx6-V2.1 we also added some packages based on the minimal configuration.

    Network is initialized over the /etc/network/interfaces.conf:

    This is my buildroot configuration:

    This is the code which is used...

    Kernel output.... check first line and last lines

    Limiting the speed in U-Boot works as you suggested. But as soon as the kernel is started it switches back to 1GBits.

    I applied the kernel patch and tested it. Nothing changed.... link speed is still 1000MBit.

    PHY: 1:04 - Link is Up - 1000/Full
    ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

    I didn't change the rate in u-boot.....

    Any ideas?

    I also see a different in U-Boot and C example:
    val &= ~0x0300; vs
    dio write FEC 0 3300

    Yes, after compiling this package in, I have a limits.conf file. But it is still not working. I also added pam to busybox, without success. I'm not sure but as I see, all settings in limits.conf are applied as soon the user logs in. In my case, the process is started by start-stop-daemon which switches to another user and then start the executable. So I don't know if settings are applied... I also don't know if pam is working because I don't know how I would see this.
    Is there any other possibility to give a user the rtprio right? sysctl or something else?


    in our application some threads run with rtprio. If I start the program as root, everything works as expected. If starting as normal user it is not possible to change the priority to rt. I know that this is nothing special, because not all users have the same rights.
    On a "normal" Linux systems I modify the /etc/security/limits.conf file. On the device, there is no such file and also after creating it, it is not used by the system.
    Any ideas?

    Some time ago we did some tests with the imx6 and its hw encoder/decoder capabilities. We are very happy with the performance but we need to integrate it into an "old" system.

    One device should act as an encoder for fbas/composite PAL signal to h.264 and on the other side backwards from h.264 to fbas/composite PAL.
    Is there an "easy" solution to get fbas into the system and fbas out?


    is there any reason why you don't build the compilers/gdb with buildroot?
    We have some issues running gdb from the toolchain because we have a 64bit system and there are missing dependencies (python2.7 386).

    Compiling Buildroot with its own toolchain seems to work with the minimal configuration. After installing the libpython2:i386 package the toolchain provided by F&S also works fine. Maybe we change over to a newer gcc because of C++11 but at the moment we will use 4.7.

    I tried to update my efusA9 to the new release (V2.1) over a SD-Card. Therefore I renamed install.scr to update.scr.
    If I insert the card into the micro-sd slot, U-Boot doesn't start the update. If I insert it into to std sd slot the update starts and everything is fine.
    Our current design only uses the micro-sd connector (SD_A_xx signals) do we need to modify U-boot (in source) or is it easier to change our design? Are there any other restrictions if we only use the micro-sd signals?