Posts by detwese

    Ok, I tried it now and it works. Thank you very much.

    I'm going to add some code snipets if anyone else will have the Problem someday.

    First create a file and add some commands to it:

    And then simply start the "shell like" process:

    2. startInfo;
    4. processInfo;
    5. int createRet = CreateProcessW( L"<shell like process>", NULL, NULL, NULL, FALSE, NULL, NULL, NULL, &startInfo, &processInfo);

    Thanks again.

    As far as I understood, in the code above the STDIN / STDOUT of the parent is used.

    What about writing to files? The cmd process must somehow be able to redirect it to a file when calling:

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

    and also a redirection to input should be managed when

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

    is called.

    At this point also a huge thank you that you really try to give me an understanding about that. :thumbup:

    Thanks for the reply.

    Unfortunatly we don't have access to change the other process.

    Currently we are starting the process in da cmd environment which can handle the redirection.

    I only wonder how cmd does it...

    As far as I understood the concept, STDIN and STDOUT are always linked to a certain driver (e.g. telnet does it).

    But cmd can redirect things to files. You see, I haven't grabed the whole idea how WEC does it, yet.

    Also the link you send seems to be brocken and incomplete.


    now that codeaurora is offline (See Here.) for many releases there were replies how to update to new repo.

    For rocko those are missing for now. And when I tried just to adapte the URL to github, I receive the error:

    1. error: Cannot checkout meta-freescale-distro
    2. error: Cannot checkout meta-fsl-bsp-release: ManifestInvalidRevisionError: revision refs/tags/rocko-4.9.88-2.0.0_ga_gh in meta-fsl-bsp-release not found
    3. error: in `sync`: revision refs/tags/rocko-4.9.88-2.0.0_ga_gh in meta-fsl-bsp-release not found

    That makes sense, becaue I'm also not able to locate that tag.

    Is it planed to also provide a patch to fix the Y2020.03 release?

    Thank you in advance and greetings.


    I think I can see where the misunderstanding comes from. I'm comming from a Linux environment, where it is possible to just open a pipe and connect it to the STDIN and STDOUT of the newly created process. That way the process starting the new one can send and receive data from it.

    In the example posted, I would like to add something ( I can't be more specific due to missing knowledge :smile: ) inside the wmain function, which receives the output of ndcucfg.exe so I can work with that. Further it would be great to even send commands from wmain function to the running nducfg and then read the output.


    we are running an Armstonea9r2 with WinCE and facing a task we need help for.

    We would like to create a process of a shell-like application which takes it command via STDIN and prints out the results via STDOUT.

    To interact with that application the "parent process" needs to access the STDIN and STDOUT of the specific child process.

    There are multiple approaches around the internet, but none of them seems to work on WinCE, for example:

    • Here is a way to pass pipes in the CreateProcess function, but we cannot do that as makros are missing and the documentations states its desktop only.
    • Here the setting of the stdio via pipes is used. But there dont seem to be pipes on WinCE.

    Interestingly, the Pocket CMD v 8.00 seems to allow those operations, as pipes and redirections can be used there.

    I hope there is a simple answer to that problem I overlooked for now.


    wir betreiben ein Custom Board (VAND3), welches an die efus A9X Plattform angelehnt ist.

    Beim Versuch NBoot mit dem MFGTool2 zu überspielen zeigte sich jedoch kein Effekt und das Programm bleibt in dem Status "Starting NBoot" hängen (nach 15min wurde der Vorgang dann abgebrochen).

    Kurz das Vorgehen:

    1. Es der Jumber wurde auf bootselect gelegt.

    2. Das USB Kabel wurde angeschlossen.

    3. Es wurde sich seriell mit DCU Term Verbunden.

    4. Eine ausgeschaltete Spannungsquelle wurde angeschlossen.

    5. Das MFG Tool wurde gestarten. Wie erwartet stand dort "No Device Connected".

    Nachdem die Spannungsquelle eingeschaltet wurde, zeigte das MFG Tool den Status "HID-compliant vendor-defined device" und nicht wie in der Anleitung angegeben "HID-conform device".

    Nachdem dann auf start gedrückt wurde, stand dort erst "Loading NBoot", gefolgt von "Starting NBoot".

    Weiter passiert nichts und auch die DCUTerm Ausgabe bleibt leer (bis auf eine "0" beim Einschalten des Boards).

    Wo könnte da ein Problem liegen, welches wir noch zu betrachten haben?

    Problem solved.

    Setting up the initial Baudrate as mentioned in section 6.2 of the CAN Doc solved the problem.

    Now the freshly started board can be attached to the CAN bus without any incidents.

    Thank you very much for the quick help.

    Hallo and thank you for your fast reply!

    How can i figure out the versions of the kernel and bootloaders?

    Also i couldn't find the registry entry to set up the initial baudrate. Where can I find it?


    every time we connect a freshly restarted device on an existing and running CAN bus, the existing bus stops working correctly.

    Only after the CAN bus is open and initialized programatically, etherything works.

    After a reboot of the system the problem occours again.

    Now the question arises, what exactly happens on the CAN Interface after restart.

    Is there a way to let the CAN bus be disabled after restart, so it doesn't interfere with the existing bus and after connecting the board to the CAN bus the bus keeps working?

    Addendum: The cabeling should be fine, we tried different ones.

    The board runs on WindowsCE.