|Issues in this section are not planned to be addressed. Please get in touch with our support if you need to have any of these issues addressed.
| 29029||Feature Request||Harmonize FlashDisk settings||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||CE6||No|
Description: We harmonized the registry settings for the FlashDisk driver. The settings will be the same on all our platforms.
| 28616||Known Issue||Bitflip in nand spare area will corrupt file system||Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||Flash||CE5, CE6||No|
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.
| 28291||Known Issue||NAND was not formated as TexFAT||Colibri PXA270, Colibri PXA310||WinCE Feature||CE6||No|
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
| 27613||Known Issue||[RemoteAdmin] fails if certain timezones are selected||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||RTC||CE5, CE6||No|
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
| 25592||Feature Request||Use new naming and versioning convention for Toradex software packages||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||WEC2013, WEC7||No|
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
| 19913||Known Issue||USB RNDIS function driver does not work on Windows 10 by default||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||USB, WinCE Feature||CE6, WEC2013, WEC7||No|
Description: On Windows 10 by default a Serial (COM) driver gets loaded if you you load the function driver rndisfn.dll .
| 19910||Known Issue||CeGetVolumeInfo does not report flag CE_VOLUME_TRANSACTION_SAFE for FAT32||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||WinCE Feature||WEC2013, WEC7||No|
Description: Function CeGetVolumeInfo does not report flag CE_VOLUME_TRANSACTION_SAFE for FAT32 formated disk. This is an issue in the Microsoft part.
| 18182||Known Issue||When adding additional languages, the new regional settings don't show up in the control panel||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||WinCE Feature||CE6||No|
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.
| 17202||Known Issue||Module hangs sometimes when resuming from suspend triggered over resistive touch||Colibri PXA270, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||Kernel, Resistive Touch||CE6||No|
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.
| 14175||Known Issue||Unexpected RTS behavior when using RTS_Pol=1 and RTS_ToggleAlwaysOn||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||UART||CE5, CE6||No|
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.
| 13865||Known Issue||RTCSync can cause glitches on I2C lines||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||I2C, RTC||CE5, CE6||No|
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
| 11886||Known Issue||Module does not boot after flashing splash screen with latest UpdateTool||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||Bootloader, WinCE Feature||CE5, CE6||No|
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.
| 10088||Known Issue||Colibri configured as USB Mass Storage Device takes up to 30 seconds to be mounted on the PC||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||USB||CE5||No|
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.
| 8088||Known Issue||Delayed Serial Transmit Completion||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||UART||CE5, CE6||No|
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.
| 6068||Known Issue||Data corruption when directly writing to SDCard over Mobile Device Center from Win 8||Colibri PXA270, Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||SDIO/SD/MMC||CE5||No|
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.
| 5756||Known Issue||UART 3.6Mbps Freezes PXA300/PXA310||Colibri PXA300, Colibri PXA300 XT, Colibri PXA310||UART||CE5, CE6||No|
Description: 3.6MBaud freezes the PXA300/PXA310 modules. It's not supported on PXA320 and PXA270 modules.
Workaround: Use lower baud-rates.
| 3380||Known Issue||Using two SD Interfaces WinCE can deadlock the system||Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||SDIO/SD/MMC||CE5, CE6||No|
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.
| 1866||Known Issue||Turning off hardware mouse cursor freezes display||Colibri PXA300, Colibri PXA300 XT, Colibri PXA310, Colibri PXA320||Graphics||CE5, CE6||No|
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: