Posts by fs-support_ZU


    you are right! I checked the code and 10Mbit implementation seems to be faulty for NetDCUA7. I will correct it. How urgent is this feature for you? Think I can provide you an update next week. Can you do the test in your enviroment?


    which kernel version do you use?

    AIN-, Touch- and Audio driver are driven via AC97 driver. We detect some issue here and improve AC97 driver in kernel V3.5 and V3.6. Since this time all issues seems to be resolved. We test touch driver over several thousand reboots without failure.


    COM9 is used by ActiveSync over USB Device. You can configure USB Device also as VPC (VPC Sample), but this was not what you want - I think.

    You can activate UART3 (COM3: at pin 16, 17) by set Registry HKLM/drivers/builtin/picocoma5/uart3/Flags=dword:0. Save Registry and then reboot.


    >>Can I use a device that supports ftdi_ser.dll?

    << Think this is not what you want: "virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC".

    >> Can you confirm that this works for PicoComA5 before I order such a device? And where does the ftdi_ser.dll have to be copied?

    << You have to copy the drivers to ffsdisk and do the corresponding Registry entries.

    >> Can you confirm that this works for PicoComA5 before I order such a device?

    << I can't;) But we can try to support you while installation. FTDI provides a library and programmer guid please check this.


    on PicoCOMA5 we have three COM ports see HW Doc. (one with RX, TX, RTS, CTS and two with RX, TX only). If this is not sufficient or you use the corresponding pins already for other purpose you can use various FTDI chips with D2XX driver. ARM drivers are available for WCE6, WEC7 and WEC2013.

    Hope this helps.


    not it is not possible to use Visual Studio 2023 under WCE/WEC. I answered already your distrubutor, see following quotation: "it is not possible to use every Visual Studio (VS) Version with every WCE/WEC Version. In general following is possible:

    - WCE6 with CF3.0 is supported by VS2005 only.

    - WCE6/WEC7 with CF3.5 is supported by VS2008 only (at least pro version).

    - WEC2013 with CF3.9 is supported by VS2012/2013/2015 (at least pro version) plus installation of Application Builder for Windows Embedded Compact 2013.

    It may be possible to convert your old project to new (above refered) VS by open the project file with it (not solution file). But as the new platform is not in the project as “hack” is required before and you must add the new platform by hand (using a text editor).

    It may be easier to create a new solution/project and add your old files and old settings afterwards."

    You can access older VS versions by purchase a "Visual Studio Subscription".

    Note WEC2013 is EOL in 2028!

    So best way to stay on Windows OS would be to choose a newer platform which supports Windows 10 IOT (e.g. PicoCOREx).


    nice that it works.

    For got boot screen working with 5V too you have to create a new PSD file.

    1. disable boot screen in EBoot by enter: XDE ...

    2. write current display settings (containing the 5V-type-bit set) to PSD, by using ndcucfg command "boot display on"

    3. enable bootscreen in EBoot again by enter: XDE ...

    4. now you have also 5V enabled for boot screen too

    5. to create new PSD file use ndcucfg command "psd read <mynewpsd>.bin". Copy this file to your host and flash it as usual.

    Hope this helps.

    PS: sorry, for sure you need the future EBoot which contains the feature above too. It will be included into Eboot V2.8.


    you can download the new kernel from your custom download area.

    Please rocognize the history file too if any questions please come back.

    PS: your kernel verision is very old (refer change log). Maybe we should think about an update. But then you have to verify your application with the new image.


    you will find XIPIMX6_C8E_V3.7_BETA_231018 in the common FSIMX6 download area, please test.

    For activate 5V for LVDS on efusA9 or efusA9R2 you have to modify your Registry value type as follow:

    newtype = currenttype | 0x0010.


    current value type is 0x4006

    new value type is 0x4016.

    PS: we will release the V3.7 including all Windows Embedded Compact Updates in approx. two weeks.


    assume special rights are not required. I test with a standard commandline template and create folders ffsdisk/111 and ffsdisk/111/222 by console and following works without issues:

    BOOL Res = RemoveDirectory(_T("ffsdisk\\111\\222"));

    Res = RemoveDirectory(_T("ffsdisk\\111"));

    How do you test that the folder still exists?

    Any GetLastError!=0 in spite of Res=1?


    >> />echo "Hallo Welt" >> /exampleOutput.txt

    << In cmd it seems to be solved straightforward they just use _tfopen and write/append the string here.

    >> />echo "I will be send over STDIN" | someProcess.exe

    << In cmd it seems to be a bit more complex (much code anyway). But they use SetStdioPathW as fs-support_HK already told. They create a file "" with the string and set the file as STDIN by SetStdioPathW (instead of TEL1: or CON1:). Then they create (and open(?)) the process as outlined above.