Windows Embedded CE 6.0 R3
Functions
novaluefound
Drivers
Name
Status
Comments
Limitations
Links
IrDA
on request
USB Host interfaces
available
The driver support handles "Mass-Storage Devices" and "Human interface devices (HID), keyboard and mouse)". Support for other devices such as serial port adapters are available on request.
USB Function driver
available
The function "Serial Client (MS Mobile Device Service)" and "Mass Storage Client" are included. If another function is needed send a request to emtrion.
Touch driver (resistive touch)
available
Storage Devices: SD-Card
available
Storage Devices: Flash File System (NAND)
available
PWM
on request
SPI
on request
I2C
available
Audio driver for analog audio
available
Serial interfaces (RS232)
available
GPIO driver
on request
Analog In
on request
On-board Ethernet (10/100MBit/s)
available
HW accelerated audio/video codec (MPEG4)
available
Video Out (PAL, NTSC, Display)
available
Video In (PAL, NTSC, Digital)
available
Display Driver (onchip)
available
True
Dienste
novaluefound
Release Notes
29.04.2013
-
Added support for NAND flashes on DIMM-SH7723 hardware revision R6D
19.08.2011
-
BugFix: Now the USB driver supports also BULK transfers which are terminated on the USB bus with a short packet before the requested byte count was reached.
-
BugFix: Now KITL is started again during initialization if this is configured.
21.01.2011
-
added support of new touch controller Microchip AR1020, which is used on DIMM-SH7723 modules starting with module revision 4 (please see remarks in release notes pdf about how to switch between the touch drivers)
-
Fixed bug in Ethernet driver which caused crash of driver on high network traffic
07.07.2010
-
Appliciation package of Version 6 is now available online for Windows embedded CE 6.0 R3
Changes compared with Version 5: BugFix in I²C driver (detection of a no acknowledge in the communication)
07.06.2010
-
Application package of Version 5 is now available online for Windows embedded CE 6.0 R3
02.12.2009
-
Application package of Version 4 is now available online for Windows embedded CE 6.0 R2
Known Issues
Block diagram
Downloads / Documents
Release Notes (DIMM-SH7723DevKitCE6)
WCE 6.0 package for GUI based devices
emtrion Multimedia package for DIMM-SH7723
Windows EC Kernel Description
Description of the latest Windows CE Embedded 6.0 R3 kernel
Developer Kits
Accessories
Supported operating systems
FAQ
Download of Image File
I want to download a new image file to the device but the Kernel Download Tool or the Windows CE Platform Builder doesn't response to the Bootme request. Why can the download not work although I can ping the emtrion...
The device requests a new image from a workstation by sending a bootme message as an ethernet broadcast to the connected network. This ethernet broadcast with the destination FF:FF:FF:FF:FF:FF is a UDP datagram on port 980 (dec.). So if this port 980 is blocked by an active Windows-Firewall, the download doesn't start. Furthermore the download will also not start when a router instead of a network switch or a direct cable is connected between the device and the workstation because ethernet broadcasts are normally not routed between two networks.
Debug C# with Visual Studio 2005
When I want to debug C# applications with Visual Studio 2005, the debugger doesn't stop at breakpoints. What is the problem?
You have to install the .NET Compact Framework 2.0 Service Pack 1 or 2 Redistributable on your development machine.
Otherwise, Visual Studio 2005 doesn't recognize that the C# application is loaded on the Windows CE device and deactivates the breakpoints. The Service Pack of the .NET Compact Framework is not installed automatically with the Visual Studio 2005 or the Service Pack 1 of the Visual Studio 2005. It's also not part of the platform-specific Software Development Kit. You can download Service Pack 2 from the Microsoft download center.
Connect to target plattform (fail)
When I want to connect to the target platform Visual Studio reports Connection failed.0x8973151A. What is the problem?
This means that the CoreCon files executed on the target device have not the same revision as the ones running on the host PC. This can happen when the kernel image contains the files from a Visual Studio 2005 installation while the files on the host PC comes from a Visual Studio 2008 installation or vice versa. Such constallation can occur when Visual Studio 2008 was installed after Visual Studio 2005 because the CoreCon files uses in both revision the same shared folder. You can get hints to solve this issue when you read the HowTo debug C++ or C# applications with Visual Studio 2008.