|The version 4.6 contains only one change in the bootloader, see issue #34332 below for details. The change is related to initial production programming at the factory only and doesn't affect normal usage. The WinCE image and BSP were not changed and therefore not rebuilt for 4.6. They stay at 4.5. Customers can continue to use their tested bootloader and image version as the issue fixed in 4.6 bootloader isn't critical and doesn't have any affect in normal boot mode.|
| WC-1230||Fixed||BadBlock detection during initial production programming takes too long||Colibri PXA320, Colibri PXA310, Colibri PXA300 XT, Colibri PXA300||Bootloader||CE5, CE6|
Description: The bootloader contains code which is used during initial programming at the factory only. In this code there was a bug which could have lead to timeouts during production depending on the content of the flashes coming from the flash manufacturer. This bug was fixed in the bootloader 4.6. This change doesn't have any impact on normal boot behavior and only changed the behavior during a special test mode during initial programming at the manufacturer.
|- WinCE 5 Updates: Installed Microsoft CE5 Updates until 2014M07 |
- WinCE 6 Updates: Installed Microsoft CE6 Updates until 2014M07
| WC-1217||Fixed||MAC Address and HW Version get overwritten by the UpdateTool in BSP V4.4 on Colibri PXA3xx modules||Colibri PXA320, Colibri PXA310, Colibri PXA300 XT, Colibri PXA300||ConfigBlock||CE5, CE6|
Description: A bug in Kernel V4.4 leads to overwritten MAC address and hardware version settings in the config block when using the UpdateTool to restore the config block. This is normally done, if you use a complete Flash backup to clone the Colibri module SW configuration in production process. Having modules with the same MAC address is only a problem if you are using these devices in the same Ethernet network.
Workaround: The following article describes the problem in detail and provides various solutions:
|- WinCE 5 Updates: Installed Microsoft CE5 Updates until 2014M07 |
- WinCE 6 Updates: Installed Microsoft CE6 Updates until 2014M07
| WC-1269||Fixed||Audio playback too fast after suspend/resume||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||Analog Audio, Analog Inputs||CE5, CE6|
Description: The output sampling rate changes to 48KHz after a suspend resume cycle and could only be changed after a sound has been played.
| WC-1268||Fixed||Debug Message Buffer feature causes issues in Suspend/Resume||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||Kernel||CE5, CE6|
Description: When the debug message buffer was enabled, which is the case by default, a freeze was possible after about 10 to 30 suspend/resume cycles.
Workaround: For BSP versions older than V4.4: Disable the debug message buffer in the registry (DbgMsgBufSize=0) see Debug Message Buffer description for details http://developer.toradex.com/knowledge-base/enable-the-debug-messages
| WC-1266||New Feature||RtcSync: Integrate latest RTC Sync Tool||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||RTC||CE5, CE6|
Description: Add support for ST M41T00S RTC chip.
Call SignalStarted API when done.
| WC-1264||New Feature||Add Support for Spansion NAND Flash||Colibri PXA320||Bootloader, Flash, Kernel||CE5, CE6|
Description: Add support for the Spansion 8GBit NAND flash device. This flash could be used in the future as a replacement for the currently used Samsung Flashes. A PCN will be sent out to customers once we need to do this step.
| WC-1263||Fixed||Improve ConfigBlock concept and use a second copy of it in order to avoid config loss||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||Bootloader, ConfigBlock, Kernel||CE5, CE6|
Description: The config block could be lost if extensively used. This issue has only been seen at one customer so far and in special test-setups. We will use a second back-up copy of the config block in order to avoid the loss.
| WC-1260||Fixed||SDHC Card Detect bug with registry setting CardDetectGPIO=-1||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||SDIO/SD/MMC||CE5, CE6|
Description: The SD/SDIO registry setting CardDetectGPIO=-1 (card always inserted) didn't work.
Workaround: For BSPs older thatn V4.4: Use an unused GPIO for CardDetectGPIO and set it to the desired value by software in order to always detect an attached SD/SDIO card.
| WC-1244||New Feature||Use UpdateTool V5.8.0 with Support for new Spansion Flash||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||Flash||CE5, CE6|
Description: Use UpdateTool V5.8.0 which includes support for future Flash types (Spansion Flash).
| WC-1242||New Feature||Publish Release Version V4.4||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||CE5, CE6|
Description: Publish Release Version V4.4 based including all changes from V4.4beta1.
| WC-1223||Fixed||RTCSync causes problems with some custom images||Colibri PXA300 XT, Colibri PXA300||RTC||CE5, CE6|
Description: When using custom images with e.g. removed Active Sync the RTCSync could hang. This problem didn't occur randomly, it was either occurring or not depending on the WinCE image features available in the image.
| WC-1222||New Feature||Add new RAM Drive Strength default settings for Colibri PXA270 V2.4C versions||Colibri PXA270||Bootloader, ConfigBlock||CE5, CE6|
Description: The new RAM used on Colibri PXA270 V2.4C modules needs a different drive-strength setting.
Workaround: For customers using bootloaders older than V4.4, the settings can be adjusted in the config block. Please refer to our knowledge base article about this change:
|This is a collection version for all older Versions|
| WC-1219||New Feature||WinCE Image Release Notes||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||CE5, CE6|
Description: Download the Toradex PXA WinCE BSP, Image, and Workspace Release Notes for V4.3 and older here: https://docs.toradex.cn/102529-pxa-image-release-notes-archive.txt
| WC-1218||New Feature||Bootloader Release Notes||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||CE5, CE6|
Description: Download the Toardex PXA Bootloader Release Notes for V4.3 and older here: https://docs.toradex.cn/102528-pxa-bootloader-release-note.txt
| WC-1342||Known Issue||Turning off hardware mouse cursor freezes display||Colibri PXA320, Colibri PXA310, Colibri PXA300 XT, Colibri PXA300||Graphics||CE5, CE6|
Description: When turning off the cursor when using HW cursor support freezes the display controller.
Workaround: Use SW cursor. Set cursor=1 in the registry:
| WC-1274||Known Issue||Data corruption when directly writing to SDCard over Mobile Device Center from Win 8||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||SDIO/SD/MMC||CE5|
Description: When using Mobile Device Center under Win 8 to directly write to the SDCard attached to a Colibri PXA using Win CE5 corrupts the written file.
Workaround: Copy the data to either the FlashDisk or ObjectStore (a RAM folder e.g. Temp) and copy it then to the SDCard using WinCE 5.
| WC-1265||Known Issue||Delayed Serial Transmit Completion||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||UART||CE5, CE6|
Description: The serial transmit thread can be interrupted by a thread with the same interrupt priority. This could lead to delayed transmit completion. This normally only affects customers which are using e.g. a RTS toggle function for RS-485 communication as the RTS signal may take several 10ms until it toggles back after sending data.
Workaround: Increase the priority of the sending thread.
| WC-1259||Known Issue||UART 3.6Mbps Freezes PXA300/PXA310||Colibri PXA310, Colibri PXA300 XT, Colibri PXA300||UART||CE5, CE6|
Description: 3.6MBaud freezes the PXA300/PXA310 modules. It's not supported on PXA320 and PXA270 modules.
Workaround: Use lower baud-rates.
| WC-1243||Known Issue||Memory Leak in Suspend/Resume Code||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||Kernel||CE5, CE6|
Description: There is a memory leak when using suspend/resume. It's not clear where the leak comes from. It might be one of the drivers. It's not using huge amount of memory, so it's not that critical for most applications.
| WC-1241||Known Issue||When adding additional languages, the new regional settings don't show up in the control panel||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||WinCE Feature||CE6|
Description: Custom build another language image doesn't show the selected locale setting in Regional settings Control panel applet.
Workaround: Remove nlscfg.inf and nlscpg.txt files from our release workspace.
| WC-1240||Known Issue||CeGetVolumeInfo does not report flag CE_VOLUME_TRANSACTION_SAFE for FAT32||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||WinCE Feature||WEC7, WEC2013|
Description: Function CeGetVolumeInfo does not report flag CE_VOLUME_TRANSACTION_SAFE for FAT32 formated disk. This is an issue in the Microsoft part.
| WC-1239||Known Issue||USB RNDIS function driver does not work on Windows 10 by default||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||USB, WinCE Feature||CE6, WEC7, WEC2013|
Description: On Windows 10 by default a Serial (COM) driver gets loaded if you you load the function driver rndisfn.dll .
| WC-1237||Feature Request||Use new naming and versioning convention for Toradex software packages||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||WEC7, WEC2013|
Description: We changed the naming and versioning format slightly in order to have a common approach for Linux, WinCE, and other Toradex software packages.
Details about the versioning can be found here: https://developer.toradex.com/knowledge-base/toradex-software-versioning-convention
| WC-1236||Known Issue||[RemoteAdmin] fails if certain timezones are selected||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||RTC||CE5, CE6|
Description: When certain timezones are selected (e.g.: UTC+9:00 Osaka, Sapporo, Tokio) the page allowing to set time on the RemoteAdmin interface does not work.
Workaround: Change the timezone prior to using RemoteAdmin
| WC-1235||Known Issue||NAND was not formated as TexFAT||Colibri PXA310, Colibri PXA270||WinCE Feature||CE6|
Description: Bug in code prevented system to be auto formatted as TexFAT. This could lead to data loss.
Workaround: Add this registry keys ->
After this user should reformat NAND using settings TFAT and exFAT
| WC-1233||Known Issue||Bitflip in nand spare area will corrupt file system||Colibri PXA320, Colibri PXA310, Colibri PXA300 XT, Colibri PXA300||Flash||CE5, CE6|
Description: The spare area is used to store meta data for the Flash Disk. However, the spare are isn't ECC protected. A bit flip can cause data loss on the Flash Disk. The SLC flash used on Colibri PXA modules is really reliable and we didn't see problems so far.
| WC-1232||Feature Request||Harmonize FlashDisk settings||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||CE6|
Description: We harmonized the registry settings for the FlashDisk driver. The settings will be the same on all our platforms.
| WC-1226||Known Issue||Module hangs sometimes when resuming from suspend triggered over resistive touch||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT||Kernel, Resistive Touch||CE6|
Description: When pressing the resistive touch to wake up the device from suspend it might hang during resume, especially when the pen (finger) keeps pressing during resume.
| WC-1225||Known Issue||Colibri configured as USB Mass Storage Device takes up to 30 seconds to be mounted on the PC||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||USB||CE5|
Description: When configured as USB Mass Storage Device, it takes up to 30 seconds, until the device is recognized by a Windows 7 PC.
This is true for CE5 and CE6.
Workaround: Toradex has a modified dll which solves this problem. Please contact our support for further information.
| WC-1214||Known Issue||Module does not boot after flashing splash screen with latest UpdateTool||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||Bootloader, WinCE Feature||CE5, CE6|
Description: After flashing a splash screen using the UpdateTool V5.11.0 or the UpdateLib V1.10, and if a negative dispondelay was configured in the registry, the module boot is delayed by up to 65 seconds.
Workaround: Negative dispondelay is not supported in the bootloader. Manually set the dispondelay to 0 in the bootloader or get in touch with the support team to get a fixed version of the UpdateTool / Update Lib.
| WC-1213||Known Issue||RTCSync can cause glitches on I2C lines||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||I2C, RTC||CE5, CE6|
Description: The RTCSync Tool used in image V4.4 and V4.5 can cause glitches on the I2C lines which could break further I2C communications. This problem has been seen with certain I2C bus devices only.
Workaround: If you don't need RTCSync, just disable it in the registry:
"Launch48"="rtcsync.exe" // rename it to e.g. _rtcsync.exe
| WC-1212||Known Issue||Unexpected RTS behavior when using RTS_Pol=1 and RTS_ToggleAlwaysOn||Colibri PXA320, Colibri PXA310, Colibri PXA270, Colibri PXA300 XT, Colibri PXA300||UART||CE5, CE6|
Description: When using RTSToggleAlwaysOn = 1 and RTS_Pol = 1 (e.g. for RS485) the RTS signal is active (1) when booting until the first data is sent sent. From then on it behaves as expected (only active when sending).
The behavior is as expected when using RTS_Pol = 0, but of course with inverted levels.
| WC-1211||Known Issue||Config block command line: clearing a section hangs||Colibri PXA320||Bootloader|
Description: clearing a config block section from the bootloader can freeze the bootloader.
Workaround: after clearing the section, wait 3 seconds, then reset the system.
| WC-1199||Known Issue||Using two SD Interfaces WinCE can deadlock the system||Colibri PXA320, Colibri PXA310, Colibri PXA300 XT, Colibri PXA300||SDIO/SD/MMC||CE5, CE6|
Description: Using two SD card interfaces on PXA modules can lead to dead -locks.
Workaround: Set Priority256 in the driver registry settings to the same value for both driver instances in order to avoid the dead lock.