WEC T20 / T30 BSP Release Details

The following table contains known issues, scheduled bug fixes, and feature improvements for the Tegra Windows CE BSPs and images.

Any schedules are not guaranteed, but reflect the current planning. The planning could be shifted due to priority changes.Issues which are scheduled for a specific version (e.g. V1.3beta1) will be integrated in the mentioned version of the BSP.

We will update this table continuously in order to always provide the latest state of our development plan.

System might freeze when closing OpenGL application that was running for long time

Apalis T30, Colibri T20, Colibri T30

Graphics

CE6, WEC2013, WEC7

No

Description: When trying to close a OpenGL application that was running for a long time (depending on the complexity of the 3d rendering this can vary from a few days to weeks) the system might freeze.

Description: The bootloader checks the CRC of a WinCE image and provides various options to proceed if a wring CRC is found.
By default CRC is checked but on failure only a warning is output and system will try to boot anyway. The behavior can be changed by setting boot.imgcrcaction to 1 (Halt system boot on CRC errors) or to 2 (try booting another image partition)

Fullscreen OpenGL application starts flickering after a running for very long time

Apalis T30, Colibri T20, Colibri T30

Graphics

CE6, WEC2013, WEC7

No

Description: Running a fullscreen OpenGL or Silverlight application with OpenGL support for very long time (~100 days) can lead to screen repainting out of sync which can result in a flickering screen.

Description: WPA2 802.1x WiFi Profile is persisted across reboots, but User Credential are asked again each time. This seems to be a MS related BUG in the Connection Manager.
We implemented a patch that can be activated by setting the following registry settings:
[HKEY_LOCAL_MACHINE\Software\Toradex\FileSystemFilter]
"WLAN_Patch"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsdspy]
"Dll"="fsdspy.dll"

Description: Added a dummy battery driver to the image. This driver does not access any HW, it just reflects the state of a memory mapped file, so the battery HW can be read out by a customer application or driver and written into this memory mapped file. There is a sample code available here:
https://docs.toradex.com/106587-battery.c?v=1

Description: So far only CableDetectPin (which needs to be connected to VBUS) could be defined to detect the presence of USB Function or USB Host. Now if "UseIDPin"=1 you can define "IDPin" and "IDPol" and you can have 3 states: No driver loaded, USB Function driver loaded or USB Host driver loaded

Description: BusEnum2 allows to load drivers in parallel, shortening the boot time. This is now the default way of loading drivers, to revert to old behavior edit following registry entry:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn]
"Dll"="BusEnum.dll"

Description: On WEC7 and WEC2013 there is no way to open NETUI using code.
We fixed NETUI by naming a window. Users can now use
HWND handle = FindWindow(NULL, L"NETRTWLANU1”);
PostMessage(handle, WM_WZCSYSTRAYICON, 1, WM_LBUTTONDBCLK);
To get handle to a window and send message.
Window name depends on network interface name.

Workaround: The image has to be re-built with additional codepages: 936 (Simplified Chinese) and 949 (Korean) in the OSDesign file nlscpg.txt (c:\Wince700\OSDesigns\ColibriTegra_Core\ToradexFiles\Misc\CE7\nlscpg.txt).

LVDS Converter Freezes After Switching From Splashscreen to WinCE Desktop

Colibri T20, Colibri T30

LVDS

CE6, WEC7

No

Description: In some cases LVDS signals are not toggling any longer after switching from splash screen to the main WinCE desktop. This is due to some problems in the LVDS converter chip.
Fixed by not disable/enable display controller between splashscreen and windows ce desktop.
NOTE: This can only be done if the Splashscreen resolution matches the desktop resolution. In that case the complete display timings will stay as configured in Splashscreen.
To revert to previous behavior set "UseSplashSettings"=0 [HKLM\SOFTWARE\NVIDIA Corporation\NVDDI]

Workaround: Either disable the splash screen or toggle backlight pin in a user space application, to disable/enable the LVDS converter.

Description: If you applied a backup of a config block (CFG) it happened that the serial number / MAC address and hardware ID got lost. This did not happen if you applied a backup by using the CFG file but only if only the config block was restored.
This issue was fixed in Update Tool 6.0.15 which is part of this image.

Description: The module freezes under following circumstances:
- Device gets out of the user idle mode (D2)
- Device does not draw anything new on the screen (at least not hardware accelerated)
- Device has workload on the GMI Data bus

Description: All BSP Features (Drivers, Multimedia, OpenGL, Video, Tools) can be now selected via PlatformBuilder Catalog. No need to edit nvap.bat anymore. This also means that a new Workspace file (defining all standard Features) is needed for customers that build their own Image form the BSP using PlatformBuilder.

Description: Custom images can now be as large as 512 MB without modifying the config.bib file. Please be aware that the limitation is the module: If you have a module that only has 256MB RAM, you will not be able to flash an image with a size larger than 256 MB. Remark: On the Colibri T20 it will be less, the max size is computed like this: RAM Size of the module - Carveout Size (64MB by default).

Description: The FlashDisk disappears on clicking "Backup" in the UpdateTool. This is due the fact, that the update Tool needs exclusive access to the FlashDisk. Reboot the system after that to get the FlashDisk back. Add a note about this in the backup dialogue.

Description: When the device is configured to use a static IP and a DNS is also configured sometimes the NTP client (time synchronization) crashes at boot, and this may impact other networking services. This issue was introduces with the Microsoft March 2017 updates.

Workaround: If you don't need NTP client you can disable it by changing the registry configuration.

Description: The download bundle contains a config file that does not force the RAM to 533MHz any longer. If you flash the device with the Update Tool and you apply the CFG file or you use NVFlash the device will be setup with a RAM timing of 800MHz. If you only upgrade the image (NB0 file), the RAM timing will not change from the previous setting.

Workaround: Higher RAM timing can lead to some thermal issues. Add the following line to the CFG file in order to force the device running at 533Mhz RAM Timing (t30_emc_clk=533000).

Description: Device does not boot if it is reset
while a I2C transaction is going on on the internal I2C bus. This can potentially happen during DFS activity, Touch interaction, Temperature read out or Audio codec access

Description: This feature was not enabled by default in previous images. RAM DFS will be enabeled from now on. It can be disabled by setting the registry key [HKLM\Drivers\BuiltIn\nvrm] DfsEMCLowCornerKHz to 330000.

Description: VSDebugger.exe uses the default ethernet devices of the different modules. This new release supports also the VMINI adapter, allowing debugging of OS using Platform Builder and application using Visual Studio debugger.
If the device does not use the ethernet interface but has a different kind of connection supporting TCP/IP (wi-fi, modem etc.), adding the CheckAdapterName DWORD parameter under HKLM\SOFTWARE\Toradex\Debugger and setting it to zero will allow the debugger to run without checking the adapter used.

Description: Allow reading of config block parameters from static and/or dynamic config block. If critical data gets lost (MAC or Hardware information) in the config block, this increases the chance it can be recovered, also it got overwritten by the user.

Description: Due to an issue in a Microsoft QFE update we had to revert the afd.dll to a previous version. The issue itself is documented under 29048. We use the following version of afd.dll
CE6: 2016M10
WEC7: 2016M09
WEC2103: 2016M11

Boot with default registry in case of missing registry section in flashdisk.

Apalis T30, Colibri T20, Colibri T30

WinCE Feature

CE6, WEC2013, WEC7

No

Description: If there was no registry section in the flashdisk the device did not boot properly (i.e. keyboard was not loaded). In order to prevent this, we let the device boot and output an message on the debug port. Nevertheless you will not be able to store registry changes.

Workaround: Flash the device using *.cfg files or NVFlash in order to support the create a registry section in the internal storage.

Description: Due to some differences in power management in WEC2013 and CE 7 we have to modify the PowerCap registry setting for the display driver in order to make the backlight enable / disable working.

Workaround: Manually set PowerCaps key in [HLKM/Software/Nvidia Corporation/NVDDI] from 0x11 to 0xFF for WEC2013

Description: Due to some communication issue between the CPU and Ethernet chip it can happen, that the Ethernet chip disappears. This only happens if a lot of peripheral interfaces are used as well as there is some traffic on the Ethernet device.
Increase the Transmission FiFo Threshold by setting the registry key TxFifoThreshold in [HKLM\Drivers\Builtin\USBEHCI]. Default value is 0x10, max value 0x3f.

Description: In the image there is a registry key forcePLLD to increase clock accuracy. So far this does not exists in the bootloader. We enabled the PLLD (higher clock accuracy) in the bootloader by default, this does not affect the image itself.

Description: At the moment we print warnings even with one ECC failure bit. We increase the threshold: If we reach half of the max correctable bit errors the an "Ecc.Corrected(x)..." message will be shown.

Description: Since WEC2013 the web-server seems to have an additional timeout after loading a certain amount of resources. The timeout is set according to registry setting ConnectionTimeout, it looks as if the connections on WEC2013 are not closed as it was on CE 7.

Description: If you type "c" in the bootloader menu to clear the registry, this has only an impact the following boot cycle. After rebooting, the old registry is there again. The registry should be cleared persistently instead. This issue affects images from 2.0beta 1 on.

Description: After a suspend resume cycle, the second core of the Colibri T20 the gets not resumed. It will be shown as 100% used in the Colibri Monitor Tool. The Colibri Monitor Tool shows active CPUs as well as allows to disable single CPU. Dynamic CPU power off can be

In this release only the *.CFG files of the download bundle have been changed. Everything else (Images, BSP, Bootloader) remained the same as in the V2.0 release. The change in the *.CFG files affects only Apalis and Colibri T30 modules.
See more details in the issue description.

Description: Due to some customer feedback we downgrade the default RAM clock from 800 MHz to 533 MHz.
Higher RAM clocks caused higher power consumption. Depending on the use case this results in thermal issues. We will set the timing up to 800MHz again once we have implemented the RAM clock dynamic frequency switching (DFS) on the T30 RAM.
If you still want to use the previous 800 MHz RAM timings remove the following lines from the *.CFG files:
[general]
t30_emc_clk=533000

Description: The CE Test kit did not pass the registry tests due to size limitations of the registry partition. The wize for registry partition was increased from 1 to 3 MB. This change was done in the *.CFG files. The image was not touched.

Description: This issue was introduced with 2.0 beta 4. After booting the device had an increased CPU workload (around 10% in idle) and sometimes can not be reset with the reset button. Setting an internal pull state on a interrupt pin solved this issue.
This change was in the bootloader only. Image was not affected.

Description: When TX DMA is Enabled (DMASetting=2 or 3) and a non multiple of 4 Transfer is done followed by a second big transfer, some bytes could be lost on the second transfer.
This problem was introduced with 2.0b4.

Description: Users can now use menu inside registry editor to save or clear registry. There are also command line switches avalible ->
/F to save
/C to clear
They can be used in combination with /S for silent.

Description: Some pin configurations are touched in a generic part of the source code. We migrate that configuration to the boot.bootconf config string.
Affected Pins on T20: GPIOsV0 to V7, T30: GPIOs S2 - S7

Description: If you change Regional Settings (Start -> Settings -> Control Panel: Regionsl Settings), the modifications are lost after reboot also you save the registry. This is an issue since image 2.0 beta 1.

100mW power saving by changing default setting of multiplexed pins of camera input

Apalis T30, Colibri T30

Bootloader, GPIO

CE6, WEC2013, WEC7

No

Description: Adapted default pin settings in order reduce power consumption. On the following GPIOs a internal pull up is set: V2, V3, CC7, DDD6 and DD5.
Configuration is done in the gpio.bootconf, see also issue 7823.

Description: If you update the splash screen using the Update Tool, the buffer strength (ss.bsTeg in Config Block) is set wrong (0) in the bootloader. This leads to a bad image quality. This is fixed in UpdateTool 6.0.8.

Description: GPIO A6 (SODIMM 30) and GPIO B4 (SODIMM 59) are tristated during booting. This is also happens if you configure them as GPIO Output in the bootloader (for example if you use them as ss.bl_gpio).
This will be handled with a default config for bootloader gpio settings feature (7823).

Description: There are some pins on the Colibri / Apalis T30 module which have multiple signals multiplexed on it. The following pins are tristeded in the Bootloader: 136, 138, 95 (GPIO 71 and 69).
Configuration is done in the gpio.bootconf, see also issue 7823.

Workaround: Reconfigure the signals on these pins after boot-up through the GPIOLib or directly in the GPIO registers.

Reading T20 Fuse Registers, While a DMA Transfer is Going on, Freezes the System

Colibri T20

DMA

CE5, CE6, WEC2013, WEC7

No

Description: Reading fuse registers while a DMA transfer is going on freezes the system. Freezes often happend during restoring images using Update Tool 6.0 and later but in rare cases also during boot.

Description: Earlier image download packages contained nvflash.exe and update batch files to program modules using recovery mode. In order to provide a separate NVFlash / Recovery mode bundle we remove these files from the image release bundle.
All NVFlash Files can be bound here: https://docs.toradex.com/103464-nvflash-recovery-toolset.zip

Description: Currently MAC gets loaded from the configblock once and is then stored in the registry. This leads to issues when Backup/ Restore registry in production programming in images 2.0b1 and onward.
Since 2.0b2 the MAC address is always loaded from the config block other than you saved the "NetworkAddress" in the device registry.

Description: The RNDIS driver which is used for platform debugging is not working properly on Windows 10.
The identifier will change to the following:
Class 0xEF
Subclass 0x04
Protocoll 0x01
For platform debugging a new RNDIS device will be installed. Make sure you update the RNDIS connector IP after upgrading to this Image / Bootloader version.

Ethernet adapter sometimes not detected after boot or connection lost during runtime

Colibri T20, Colibri T30

Ethernet

CE6, WEC2013, WEC7

No

Description: On some modules the Ethernet controller sometimes is not detected during the boot process or the link drops during run time.
Most often this happened if there was activity on the GPIO Y0 to Y3 pins (i.e. SPI).

Description: Currently only one PCIe channel is supported. This channel is already used by the internal Ethernet interface on the Apalis module. Toradex has to modify the Microsoft PCI driver to add support for multiple PCIe devices at the same time.

Workaround: Disable the internal Ethernet Controller in order to use your own PCIe device.

Description: RTS Signal toggled during boot phase. This can be an issue for external devices.
We also introduced a registry Key, that allows to change the RTS thread priority for users that can not do that in their code. See also https://developer1.toradex.com/knowledge-base/rs485.

Description: Up to image 1.4 the a hive based registry was stored in \FlashDisk . From this release on, the registry is stored in a new section of the persistent memory, which can not be accessed over the normal storage manager layer. In case you have been using the updatelib to save and clear the registry, you need to use an updated version of the updatelib.
In order to support the new registry location you need to do the upgrade with the latest Update Tool and use the "Layout Config File" to do the re-partitioning of the Flash Disk.

Description: Pins of the serial port are reconfigured with every open and close of the serial port. This is an issue for customer using some UART pins as GPIO Pin. To solve this issue set up a PinMux configuration (Registry key PinMuxConfig) that matches your requirements: See all possible configurations here: http://developer.toradex.com/knowledge-base/serial-ports

Description: Since image V1.4 a improved ECC handling has been introduced (issue 10351). To make use of that you had to upgrade to 1.4 using NVFlash.
From now on you can also use the UpdateTool 6.0.1, which now supports migrating to new ECC handling with image V1.4 and newer. You can also upgrade from Images before 1.4 with the new Update Tool and you will also get the new ECC handling.

Description: Updating certain modules from images 1.1 and older to images 1.3 and newer is not working properly. After updating the image and bootloader the module does not boot any longer. This is solved with Update Tool 6.0: https://docs.toradex.com/103231-tegra-update-tool.zip. First flash an emtpy .bct file and without rebooting do an image update using a .cfg file.

Description: Some displays pixel clock with a higher accuracy. By default the display drivers uses the most efficient clock source. In issue 9528 we have introduced a registry key registry key forcePLLD in [HKLM\Software\Nvidia Corporation\NVDDI\LCD] that allows you to optimize in accuracy. We further optimized the accuracy of the clock in case you are using the forcePLLD key.

Description: Due to power management optimization in image V1.3 and later audio loopback is not working any longer on the T20. Registry Key PowerDownTimeout was introduced to control the power down behavior. Set PowerDownTimeout = -1 in order to prevent the codec being powered down.

Description: Possible lockout of 2D and 3D Hardware interface leads to screen freeze. The module itself is still running the screen gets not refreshed any longer. This mainly happens if you do only read operations of a DC where you previous have been painting on with the 3D and 2D HW unit.

Workaround: Periodically do some write access on surfaces (i.e. background pictures) you only read from.

Description: On Windows Embedded Compact 7 with certain screen resolutions you see vertical lines when the mouse cursor is bellow the bottom screen edge during a mouse click. The lines are shown when the mouse button is released.

Description: RAM timings for Colibri and Apalis T30 are improved. If you ever flashed a custom bct before either flash latest image using nvflash or flash default.bct before flashing new image with the Update Tool.

Description: Prevent the update tool setting negative disp on delays in the bootloader. The bootloader does not support negative disp on delays yet. After updating the splash screen with a module configured a negative disp on delays in the registry it will not boot any longer.

Description: In previous beta release default value of pex.cpus was the maximal number of CPUs for the target CPU. This leads to problems if using an old bootloader with an actual image. Default is set to 0 in this release.

Description: In case you set WaitForTXcomplete=0 and RTS_CONTROL_TOGGLE it happed, that the RTS signal was released before transmit was finished. This was fixed by ignoring the WaitForTXcomplete = 0 in case RTS_CONTROL_TOGGLE was set.

Workaround: Do not change WaitForTXcomplete in case you use RTS_CONTROL_TOGGLE or set it to 1.

Description: To improve durability of NAND Flash on Colibri T20 we add additional ECC bits. With this more read errors per block can be corrected, so blocks are marked as bad later.
Note: To make use of the improved error correction you have to update your image with NVFlash or with the Update Tool > 6.0.0. You also have to use NVFlash or the the Update Tool to downgrade to image before 1.4beta2.

Description: The Silverlight references in the Toradex SDK do not match the Windows CE image 1.3b2 and later. See workaround for more information.

Workaround: Applications running on Images before 1.3 have to be rebuilt with SDK v0.2, applications running on 1.3 and later on have to be rebuilt with SDK v2.0. You get the SDKs from here: https://docs.toradex.com/102481

Description: Accessing files on a SMB server over Ethernet can cause the application to hang.
The CE7 Update 2014M11 triggered this problem. It is fixed with the 2015M02 update which is part of this image.

Workaround: If you build your own image, make sure you have installed the MS QFE Update 2015M02.

Description: Users that need to intercept IOCTLs have now the chance to intercept IOCTLs to implement their own functionality. Please get in contact with the support team to get more information about that.

Description: Some SD memory cards are not working reliable. When they are getting full and/or you do heavy write access, they stop working (error 19 or error 31).
This can be fixed by increasing the read command timeout from 1sec to 2sec.

Workaround: Remove and insert SD Card or get in contact with the support team to get a driver that fixes this issue.

Description: Some SD Memory cards are not shown in the file explorer, the initialization of the cards fails. This is due to the fact, that some cards need some longer to power up before the first communication can take place. To prevent this we have introduced a key "PowerUpDelay" in the SDIO driver. Default value is set to 200ms.

Workaround: After inserting the card toggle the Card Detect Pin manually or using the GPIOlib, after that card is mounted correctly. To get an updated version of the driver that fixes this issue already, get in contact with the support team.

Description: There was a dependency between the Touch, Audio and Analog Input Library. They could not be used independently. Please use the latest ADCLib from the library package 1.9. As long as the package is not availabe, please contact the support to get the latest version.

Description: Power consumption has been reduced by up to 0.3 W in the latest image.
- With DFS on EMC enabled power consumption can be reduced by up to 0.5 W (See issue 9380).
- HDMI is disabled by default (Issue 9395).
- Bootupstyle changed (Issue 9396).

Description: We have seen, that it does not make any difference in the power consumption if we use 40MHz or 216MHz as minimum DFS frequency. On the other side we have a improved interrupt handling by not going bellow 216MHz. For this reason we set the default minimum frequency for DFS to 216MHz.

Description: Some USB devices, i.e. UVC USB Cameras, are not shown in the system, when they are plugged into a running system (Hotplug). This can now be fixed by adding a key "HotPlugDelayMS" with the count of milliseconds the system should wait for the device. Add the key to the appropriate USB Host registry settings (i.e. HKEY_LOCAL_MACHINE\Drivers\BuiltIn\USBEHCI1]).
For UVC Cameras 100ms should be fine.
More Details here: http://developer.toradex.com/knowledge-base/colibri-t20-usb-host-driver-registry-settings#Hotplug_Delay .

Description: Small issues with audio playback on T20 and T30. When playing two waves the same time or playing one wave immediately after the other sometimes parts of the wave get lost are are played twice. Some wave files had no output at all, only silence was played.

Description: The RTCSync Tool is normally called as part of the boot-up of WinCE (part of init in registry). The SignalStarted API should be called when done if the tool was started as part of the init tools in the Registry. This allows customers to use the dependency feature of the registry init process.

Description: Since image version 1.3 beta 1 it could happen that OpenGL applications do not run any more. This is due to an updated shader compiler. This only happens if there already some precompiled shaders that have been used in a image before 1.3 beta 1.

Description: The Bootloader and Image can now be backed up with the Updatetool. For production programming please still use the workarround described bellow as the Flashfile System, Registry and the Confiblock are not backed up.

Description: The system was hanging when power supply dropped below 3.08V but did not go below 2.0V.

Workaround: A full power cycle is necessary to get the module out of this state.
In Image 1.3beta1 and later we have implemented a software option to either trigger a reset as soon as the voltage drops below 3.08V, or ignore that low-voltage condition at all. See http://developer.toradex.com/wiki-articles/resource-manager-registry-settings#Undervoltage_Lockout for more details.
Both options are not effective during the system boot phase, from the time when the power supply rises above 3.2V, until the power management IC has been configured by the WinCE driver.

Description: The system time get's synced with an RTC running in the PMIC on the module. The PMIC was configured to use an RC-oscillator instead of the crystal. This could lead to inaccurate time reported by the RTC. The system gets synced every 24 hours with the RTC and therefore could see quite a jump of the time. We changed this in order to use the crystal. The time jumps are now limited to a minimum.

Description: Added support for the RTC used in the PMIC on the T20 and T30 modules. However we still recommend to use an external RTC on the carrier board due to lower power consumption of such chips. More details here: http://developer.toradex.com/knowledge-base/rtcsync

Workaround: Use an external RTC on the carrier board as done e.g. on our Colibri Evaluation Board.

Description: Dial-up connections get disconnected immediately after dial-in. Issue was related to some not supported comm event masks. There have also been added some unimodem related keys in the registry.

Description: Sometimes some peaces of a sound are played again at the beginning when a new file was played later. This also lead to audio driver crashes when playing files again and again with a high frequency.

Workaround: Add sleep after playing sound before playing next file to prevent driver crashes.

Description: After adding additional locals through the Toradex .cab installer, still only the regional settings English(United States) can be used. Any other region setting prevents the system from booting correctly.

Description: Currently the UART driver triggers RX events only once. If the event is not handled by the application and the data is not read, there will not be signaled any other RX event, also not if new data arrives on the device. Trigger a manual read data to reenable the RX events.

Workaround: Make sure you do not miss any RX event. If not possible, set a timeout after which you will manually trigger a manual read.

Description: If you have a roated screen, videos played in full screen mode are shown correctly. If you still want to get the videos rotated, set the registry key [HKEY_LOCAL_MACHINE\Software\NVIDIA Corporation\NVDSHOW] NV_VIDEO_RENDERER_FULLSCREEN_ORIENTATION to 90 or 270.

System time does not behave correctly when DST is not activated and SoftRTC is disabled

Apalis T30, Colibri T20, Colibri T30

RTC

WEC2013, WEC7

No

Description: When DST is not active and SoftRTC is disabled (default on Tegra Modules is Enabled) the current date/time reported by the system is not precise and lags few minutes per hours during runtime.
This is a bug in the MS code.

Workaround: If you have issues with DST not running correctly there are two ways to fix this.
1. Enable SoftRTC.
2. Go into registry under
HKLM\Time Zones and select your timezone. There is a subkey "Dynamic DST" with entries for each year. To fix it create a new entry for year when you have issues and copy value from previous year.

Description: There is a memory leak in the SDIO driver. When inserting / removing SD Card some memory is not freed. This specially can be an issue for customers having SODIMM 45 floating (Card detect) and still have SD Card driver enabled.

Workaround: Customers not using SDIO interface should disable the driver in order enable a interrupt on the card detect pin.

Description: The CE7 exception handler seems to have a problem if the exception happens in thumb mode (instead of the normal arm32 mode). This also happens if not explicitly using Thumb mode. This is an issue if the exception handling is triggered by any uninitialized function pointer with an odd value.

Workaround: None. This is a Microsoft code issue. Microsoft is aware of it but currently doesn't plan to fix it.

Description: Sharing USB memory device or SD Memory Device using the "Mass Storage Class" with an external PC does not work properly. The device is not shared after booting neither when insert remove the storage. The only thing that solves the issue is plug / unplug the USB function cable. Sharing the internal flash storage works fine.

Workaround: Remove [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\USBFN\] "Order" key. This will force the USBFN driver to be loaded with the lowest order and gives the SDIO driver some more time to get loaded.

Description: The "Lease Expires" date is always set to 1/1/1970 initially. This seems to be WEC7 related issue. This is not an issue on CE6.

Workaround: Do a ip renew (ipconfig /release, ipconfig /renew) to get a correct "Lease Expires" date. If you build your own Image, you can also use a legacy dhcp.dll that was in a release before November 2014, where this issue was not present.

Description: The default timeout for write operations to a COM port is (10ms * numberOfBytes + 100ms).
At baud rates below 1000bps this might not be sufficient, causing a premature abort of the transfer.

Workaround: Define a different timeout by calling the SetCommTimeouts() function.

Description: Officially Microsoft does not support the webinterface (Remoteadmin) since CE 7. Migrate the interface to WEC2013 in order to provide an easy way to administrate users and remote file access.

Description: After Windows Embedded Compact 7 booted the CPU is 100% loaded for around 10 seconds.
This behavior is normal. It's caused by the kernel cleaning dirty pages in a idle priority background thread.

Description: While the Windows CE device's USB client port is connected to a host (e.g. for debugging), the network connection is not accessible.
Reason: The USB client connection creates a virtual COM port COM0 and an additional network connection through COM0. The Windows CE device's network traffic is then routed to COM0 by default.

Workaround: Use the Windows CE command line to change the routing table:
1. route print com0
Look at the COM0: row in the interface list, and remember the number shown in the first column .
2. route delete 0.0.0.0 IF
Where i is the number taken from step 1.
Repeat these steps each time you disconnect and re-connect the USB cable.

Inconsistent usage of UART Settings Between Bootloader and WinCE Driver may cause problems.

Apalis T30, Colibri T20, Colibri T30

UART

CE6, WEC7

No

Description: If using non default UART Pin muxings in some certain settings it is possible that the UART does not work as multiple PINs with the same alternate function are defined. The reason is that the bootloader may use other pins than the WinCE image.

Workaround: Customers can manually set the duplicated functions to GPIO in their application using the GPIOLib. Or use the same pin muxing in the bootloader as well as in the image (ser.pinmux in the bootloader).

Description: Backlight enabling / disabling is not fully supported as described for the PXA modules: http://developer.toradex.com/knowledge-base/backlight. When back light gets disabled the whole display drivers is disabled. This is a potential issue for some customer hardware (i.e. flickering screen when re enabling the backlight).