Hello,
>> The overall size of the OS image (xip.bin) seems to be not the problem. ...
I have not modified the memory mapping in config.bib.
<< I assume you have to modify the config.bib. Especially chinese locals increase the image size essentially (10...20MB)!
Hello,
I please you to order it via our homepage -> products -> accessories -> custom kernel.
Your custom settings can you send direct to me or to our sales office.
Thanks.
Hello,
yes this works! In the worst case some headers/libs missed*). SDK contains only contains only stuff about APIs. API is the same for all our boards (else you can't built). Processor dependend stuff is in the "OS". Take a look to the SDK folder.
>>Means this, i can build 100% working binary compatible exe-Files for NetDCUA9 by using the SDK for the NetDCUA5?
<< Concerning the SDK yes. But it depends also on your code, e.g. if you use hard code registry paths or DLL names it won't work.
>> Why then different SDKs?
<< *)To be sure all headers and libs for the modules include into the image are available. But this is a minor issus and i rarely saw it.
Hello,
sorry i just debug on a NetDCUA9 using FSVYBRID_WEC7_SDK and MS Visual Studio 2008 but i cannot reproduce the problem.
Hello,
unfortunately the is not configurable in WEC! It come with SYSGEN_XPSKIN and is active in all standard images.
We can offer you a custom image without SYSGEN_XPSKIN or you use the BSP to build your own image.
Hello,
>>After installation the standard look&feel is set to WinXP
<< You are talk about your applikation or the WEC applets (SYSGEN_XPSKIN)?
Have you a sample picture?
Hello,
which SDK, Visual Studio and OS you are using?
Any additional messages from Vsiual Studio?
Hello,
the link above is obsolete. You will find the tool under "MyF&S" in the "Tools" section at our hompage.
Hello,
using HW revision 1.30 automatically "[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\EFUSA9X\USDHC4_REV120]" is activated.
Hello,
if the touch works you can ignore this output. it has definetly nothing to do with the origin problem. Maybe it is caused by the amount of debug output which takes some more time.
You can increase the timeout under HKLM\System\gwe\touchproxi\driverloadtimeoutms=DWORD:<timeout in ms>.
Hello,
thanks for this information. Would be intersting to compare the SX default register settings with the one loaded by the driver.
Hello,
and sorry, you are right! I saw that this debug feature and also debug zones are disabled in the current driver. So please try the attached one. It is the latest version. Copy it to ffsdisk and change register value "DLL" to "ffsdisk\...".
Hello,
keep in mind - if you use a board with multiple cores you have to do the measurement above for each CPU!
You can use the SMP functions to do this, like:
CeGetTotalProcessors():
CeSetThreadAffinity();
Refer SMP Functions documentation on MS Windows Dev Center.
Hello,
use latest device dirver document "play around" with the values, ZXMin/MaxBound(, PNDTPullUp, SetDelay, AdcReadHoldoffHns, ...) . Use also the SX data sheet. Assume a touch dection while low pressure delivers wrong values.
PS: check also if these values are already implemented in your resent touch driver version ("debug=4" should output the settings during boot on the debug line).
Hope this helps.
Hello,
to get an event from an ordinary button a WM_DOWN and WM_UP from inside the buttom area is required. It would be also interesting which events fail and how far is the distance from the buttons border in this case.
I do not await that the driver does any mistakes because it gets ready-made values from the SX controler.
Does recalibration helps?
Any EMV sources near the touch or SX chip?
I will also check if there are any registers inside the SX which may bring improvments and come back here.
Just an update about which OS requires which Visual Studio:
WEC6R3 WEC7:
Visual Studio 2005 Standard (c++, .NET CF2.0)
Visual Studio 2008 Professional (c++, .NET CF3.5)
WEC2013
Visual Studio 2012/13/15 Professional (c++, .NETCF3.9)
Windows 10 IoT Core
Visual Studio 2019 Professional
To get access to older Visual Studio versions you need a "Microsoft MSDN Subscriptions" license.
You can use CERHost to connect to your Windows Embedded Compact terminal over Ethernet and display its screens in a window. You can also use the mouse and keyboard on the desktop to remote control the device the same way as if you were using the UI on the device.
In general device side component is already available on the device. Just launch is by enter "start CERDisp -c". Now launch cerhost on your desktop and select the device you want to conncet.
Hi Hans Kessel,
step into the bootloader enter "XDS", enter your desired video memory size, reboot - thats all.
Example:
Hello t4science,
sorry no other relevant command line options or Registry settings in our case.
So use "cerdisp -c"
Hello t4science,
you have to launch "cerdisp" with a command line. This is not possible under HKLM/init! Launch "cerdisp -c" will broadcast the ip-address. Use startup feature (refer DeviceDriverDoc) with cmd or lnk file for do this *or* write an onw program which launches "cerdisp -c".
As far as i remenber you can also adjust ip-adresse via registry. I will check it and come back.
