ActiveSync Requirements (Windows Embedded Compact 7)
ActiveSync is an application that Windows Embedded Compact 7-based devices can use to synchronize data with Exchange (email) servers and share files with a desktop computer running Windows. Windows Embedded Compact 7 devices must meet certain hardware and software requirements to ensure that they work correctly with ActiveSync.
In this article:
- Microsoft Windows Versions That Support ActiveSync with Windows Embedded Compact 7
- ActiveSync and Silverlight-Based Sample Home Screen Incompatibilities
- BSP OAL Requirements
- Device-Specific Requirements
Windows Versions That Support ActiveSync with Windows Embedded Compact 7
The following versions of Windows support synchronization with Windows Embedded Compact 7 devices by using ActiveSync:
- Windows XP with ActiveSync version 4.5
- Windows Vista with Windows Mobile Device Center version 6.1
- Windows 7 with Windows Mobile Device Center version 6.1
ActiveSync and Silverlight-Based Sample Home Screen Incompatibilities
You cannot add ActiveSync components to an OS that is configured to use the Silverlight-based Sample Home Screen. (The Sysgen variable SYSGEN_AS_BASE adds ActiveSync features to an OS, and the Sysgen variable SYSGEN_XRSHELL adds the Sample Home Screen.) This restriction exists because ActiveSync requires features that are implemented in the standard shell but not in XRShell, the shell containing the Sample Home Screen. If you combine both modules in the same OS, the shell will stop responding during boot time.
BSP OAL Requirements
For ActiveSync to work correctly with a board support package (BSP), you must implement a handler for the IOCTL_HAL_GET_DEVICE_INFO input-output control (IOCTL). This handler appears in the OALIoCtlHalGetDeviceInfo function of the OEM Adaptation Layer (OAL). The handler must correctly handle the SPI_GETPROJECTNAME system parameter information code. In addition, handling the SPI_GETOEMINFO and SPI_GETPLATFORMVERSION codes is considered good programming practice, although the handler is not strictly required to handle them. For more information, see “Best Practices” in OEMIoControl in the Windows Embedded Compact 7 reference documentation on MSDN.
Device-Specific Requirements
Specific device types require software settings and certain hardware to make the device work correctly with ActiveSync.
TI OMAP 3530 EVM2 (ti_evm_3530) Hardware Platform and the Handheld Design Template
Sysgen Variables
- SYSGEN_USBFN_SERIAL
Hardware
- USB cable, Type-A to Type-B (standard)
Instructions
- On the device, use the port labeled "HSUSB_OTG".
NetChip NET2280 (CEPC) Hardware Platform and the Handheld Design Template
Sysgen Variables
- SYSGEN_USBFN_NET2280
- SYSGEN_USBFN_SERIAL (depends on SYSGEN_USBFN_NET2280)
Hardware
- USB NET 2280 PCI card (http://www.plxtech.com/products/2280.htm)
- USB cable, Type-A to Type-B (standard)
Sigma Designs SMP865X Hardware Platform and the Handheld Design Template
Sysgen Variables
- SYSGEN_USBFN_NET2280
- SYSGEN_USBFN_SERIAL (depends on SYSGEN_USBFN_NET2280)
Hardware
- USB NET 2280 PCI card (http://www.plxtech.com/products/2280.htm)
- USB cable, Type-A to Type-B (standard)
Instructions
To check ActiveSync functionality on iMX27 and Sigma platforms
- Download the Handheld Design Template image to the device, but do not yet attach the USB cable to the computer running Windows 7.
- Using a Command Prompt window on the device or Target Control in Platform Builder, load the appropriate serial USB driver by using a command such as the following:
s ufnloader load serial_class - Make sure that Windows Mobile Device Center is installed on the computer that is running Windows 7.
- Attach the USB serial cable to the computer running Windows 7.
- Windows Mobile Device Center is activated automatically.
If you use only SYSGEN_USBFN_SERIAL, the serial USB driver does not need to be explicitly loaded before you connect the USB cable.
See Also
- [[articles:Windows Embedded Compact]]
- [[articles:Windows Embedded Compact Survival Guide]]