Posts by YoMas

    This is really bad news and brings us back to (very) old MFC Design like in ancient NETDCU8 days. In times customers are used to control touch screens with gestures on modern styled GUIs this is not up to date.

    Do you have any idea what Microsoft means with “production ready controls”? ActiveX Controls? DLLs?

    Concerning dll’s: They don’t work neither I already tried it – they are shaded out as well.

    My example shows my effort in writing pure C# Code without using XAML. With XAML I gave up. So this is a Device Application using Visual C# (which I hope is possible since it is offered when starting a new project). In this Windows Form project I just add a new class I call "MeinSteuerelement" and deviate it (using (I think) something like: "public class MeinSteuerelement : Control") from a Control. After compiling the new Control is available in the toolbox - but in the WCE it's shaded out, in a normal Windows application it is not. And this is what I don't understand: Why can't I deviate classes / override classes?

    Hello,


    I have a problem designing custom made buttons. After a lot of effort with (not working) XAML tools I tried overwriting the Control class to design own controls / buttons. While it works very fine with a Windows Application it does not with the Windows Embedded Compact SDK. Everything is similar and there is no problem to register the "MeinSteuerelement" class, but only in the Win App it's usable while in the WCE environment the class is shaded.
    Where could be my mistake? Isn't it possible in WCE to override classes?


    Greetings Sören

    OK. Thank you for your support, basicly it's working... But:


    To tell the truth, we hoped to decrease work on the NETDCU in the series, but it seems to increase. The reason for that is, that we have to start the *.bat file for the setup. Therefore we must see something on the display, which means that we have to connect it to the DCU Terminal load the display text file start the batch file and after that the same procedure as before. So work nearly doubles.


    Here are my questions:
    1. Do you have an idea how to start the update program automatically, so that we are not forced to see anything on the screen?
    2. Is it possible to update the kernel including the txt file for the display?

    An answer on my question really is urgent, since we want to use your kernelupdate software from next week on. So I really would appreciate some comment.

    The point why I use the Kernel update program is, that I do not like to use the bootloader. Since this is the test for the series there should be another way to solve this.

    Trying a Kernel update with your "KernelUpdate_NDCU8_V104.exe" the program aborts with "Kernel partition to small". Platform used is a NETDCU 8. The Kernel Version I would like to use is "NK82_CF2_070525.bin".


    What shall I do?

    Well, I am still interested in this, so maybe anyone has an idea in between?


    The problem for me is that I have to shuffle something like 60k from an ARM7 Chip to the NETDCU. The WCE "overhead" for serial communication is slowing this extremly down when each transfere action must not exceed 2k. At the moment I have to separate my data to around 30 pieces and send them one after the other always waiting for an acknowlage that the 2k buffer is read before sending the next package. So this operation takes during the start of the program around 8 seconds.


    May there is a way to accelerate this?

    To minimize "handwork" for the serial production I make as much initialisation as possible with my Software. Since I need another color scheme I use the following code:


    Code
    1. cKey.Open (HKEY_CURRENT_USER, _T("ControlPanel\\Appearance"));
    2. cKey.SetValue (_T("Current"), (CString) "High Contrast White");
    3. RegFlushKey(cKey);


    Having a view to the registry the value is set but the scheme has not changed (yes, I restarted the NETDCU). When I'm looking directly under the settings in WCE the new color scheme is standing in its field, but to apply it I have to press "Apply". Then it is changed permanently.
    Can I "press" apply via Software, too?

    The display key should be already generated. Since I am not sitting at my developing environment right now I cannot simulate generating a new key.
    Nevertheless there is another chance to get access to the registry by using the "Remote Registry editor" in the menue "Tools" of the evc4. Have a look to folder "HKEY_LOCAL_MACHINE" and there "Drivers\\Display\\Samsung\\mode100" or wathever display you use. Inside there you can change the value by hand.
    I do not know exactly if the value is saved "forever" in the registry, therefore I use the DcuTerm to reg save the value after that.


    Then restart NETDCU. To control the setting (is it really present in the registry) use the Registry editor again (i.e. when display is not rotated).


    By the way: FSTN Displays as far as I tried it are not rotable, at least I only got stripes after rotation.

    Ever tried to rotate the display using registry settings?
    Try i.e.:

    Code
    1. CRegKey cKey;
    2. cKey.Open (HKEY_LOCAL_MACHINE, _T("Drivers\\Display\\Samsung\\mode100")); //Cursor key
    3. cKey.SetValue (_T("Rotate"), (DWORD) 0); //Rotation in degrees
    4. RegFlushKey(cKey); //Save Registry


    After a restart it should be rotated depending on your DWORD value.

    After writing the application it should stay 'forever' on the NETDCU8. Clearly I have to flash the .exe, but libraries are demanded, too. How can I get the information which pieces of code I also have to flash?

    Just to give a final answer:
    The mistake lies in fOutxCtsFlow = TRUE and in fOutxDsrFlow = TRUE. Changing both parameters to FALSE solves the probblem.


    Generally the RS232 is extremly bad documented in WCE, also the microsoft webpage is no help at all. So for a lot of settings, which could be made it is not obvious what hardware settings correspond to them.