| WC-2708||Feature Request||Add suspend support for Ethernet||Colibri VF50, Colibri VF61||Ethernet||CE6, WEC7, WEC2013|
Description: Suspend/Resume isn't supported. Due to a silicon errata of the Ethernet PHY, it wouldn't be possible to go to the lowest power mode anyway. Currently, Ethernet doesn't work anymore after resuming from suspend.
Workaround: Don't use suspend/resume if you need Ethernet.
| WC-2695||Feature Request||Add support for TOUCH wakeup||Colibri VF50, Colibri VF61||Power Management||CE6, WEC7, WEC2013|
Description: Currently using touch as wakeup source is not possible because of hardware limitations.
| WC-2675||Feature Request||Implement support for PWM outputs||Colibri VF50, Colibri VF61||PWM||CE6, WEC7, WEC2013|
Description: A PWM driver will be implemented and supported by the Toradex libraries, providing the same API interface available on other modules inside the Colibri family.
| WC-2655||Feature Request||IPv6 Issues on Vybrid WinCE6||Colibri VF50, Colibri VF61||CE6|
Description: If you try to PING Vybrid from another PC it is not responding. To make it work, Vybrid should do successful PING once. After that both ways PING works.
Workaround: Use IPv4
| WC-2653||Known Issue||USB devices not detected at boot||Colibri VF50, Colibri VF61||USB||CE6, WEC7, WEC2013|
Description: When a 2nd level USB hub is connected and has some devices attached to it, other devices connected to 1st level hub may not be detected correctly at boot.
Workaround: Detaching and re-attaching the device generates a successful detection, also attaching them to the 2nd level hub instead of the 1st level one seems to work in most cases.
| WC-2648||Known Issue||Small memory leak when using console (WEC2013)||Colibri VF50, Colibri VF61||WinCE Feature||WEC2013|
Description: When using a console under WEC2013 there seem to be a memory leak somewhere.
Workaround: Don't use the console if not really required.
| WC-2643||Feature Request||Implement support for multi-core communications||Colibri VF61||CE6, WEC7, WEC2013|
Description: Support for asymmetric multi-core on the VF61 module will include porting of the Freescale MCC library (message-based interprocessor communication) and support for loading M4 firmware from Windows CE/or the bootloader.
| WC-2642||Feature Request||Implement support for video capture||Colibri VF50, Colibri VF61||Camera Parallel Interface, Video Codecs||CE6, WEC7, WEC2013|
Description: Currently video capture is not supported on the Vybrid. Support will include analog video capture that is a feature specific for Vybrid-based modules and not present in other modules of the Colibri family that require and external video-converted to capture analog video.
| WC-2611||Feature Request||Add support for OS Image compression||Colibri VF50, Colibri VF61||Bootloader||CE6, WEC7, WEC2013|
Description: The bootloader stores the image on flash memory in uncompressed format. Supporting image compression allows usage of the Win CE Image Compressor Tool to reduce image size and increase the flash area available for file storage. Compression may also improve boot times, but this has not been tested yet on the Vybrid modules.
| WC-2610||Feature Request||Optimize USB driver||Colibri VF50, Colibri VF61||DMA, USB||CE6, WEC7, WEC2013|
Description: USB host is supported in the current release, but the driver does not use DMA for data transfer and this may impact transfer speed and increase CPU usage in some scenarios. DMA support requires an additional layer in the operating system to manage DMA channel and share the completion interrupt.
As an effect, USB cameras might not work correctly as the throughput might be too low now.
| WC-2608||Feature Request||Optimize Ethernet driver||Colibri VF50, Colibri VF61||DMA, Ethernet||CE6, WEC7, WEC2013|
Description: Ethernet works in general, but the driver does not use DMA to transfer packet to and from the controller. This may impact transfer speed and increase CPU usage in some scenarios. DMA support requires an additional layer in the operating system to manage DMA channel and share the completion interrupt.
| WC-2607||Feature Request||Optimize SDIO driver||Colibri VF50, Colibri VF61||DMA, SDIO/SD/MMC||CE6, WEC7, WEC2013|
Description: SD bus is supported in the current release but the driver does not use DMA for data transfer and this may impact transfer speed and increase CPU usage in some scenarios. DMA support requires an additional layer in the operating system to manage DMA channel and share the completion interrupt.
| WC-2599||Feature Request||Optimise NAND flash driver||Colibri VF50, Colibri VF61||Bootloader, Flash||CE6, WEC7, WEC2013|
Description: Currently the NAND flash driver is not using DMA nor multi-block reads. Implementing those features will speed-up filesystem access in the operating system and reduce boot time.
| WC-2576||Known Issue||UART minimum baud rates||Colibri VF50, Colibri VF61||UART||CE6, WEC7, WEC2013|
Description: Due to an hardware limitation in the internal controller Vybrid UARTS minimum bsp is limited to 1200bps (VF61) or 600bps (VF50). The divisor registers don't allow configuration of lower clock speeds.
Workaround: Low baud rate UARTs can be implemented using GPIO pins (bit-banging) or by connecting an external UART controller to the module as described in this article: http://developer.toradex.com/knowledge-base/usb2serial
| WC-2563||Feature Request||Redirecting the CMD processor to the serial port causes problems when opening CMD windows||Colibri VF50, Colibri VF61||WinCE Feature|
Description: Only 1 CMD windows can be open while redirecting data to serial port.
| WC-2546||Feature Request||The SD card generated by writing the image has a data partition of 256MB||Colibri VF50, Colibri VF61||CE6, WEC7, WEC2013|
Description: This is only needed if you need to recover the old non-fused module. New modules don't have this limitation any more.
| WC-2545||Feature Request||VGA output does not work with some external VGA monitors on EVB 2.1.||Colibri VF50, Colibri VF61||VGA||CE6, WEC7, WEC2013|
Description: VGA output does not work on some VGA monitors on EVB 2.1 due to the missing level shifters on the vertical and horizontal synchronization signals. Newer versions of EVB have level shifters.
| WC-2523||Feature Request||Copy/Paste and Drag and Drop doesn't work on WEC2013||Colibri VF50, Colibri VF61||WinCE Feature||WEC2013|
Description: Copy/Paste and Drag and Drop doesn't work on with the Explorer on WEC2013.
Workaround: Use command line to copy files.
| WC-2514||Known Issue||Break Detection on UARTs is not supported by the Vybrid processor||Colibri VF50, Colibri VF61||UART||CE6, WEC7, WEC2013|
Description: The Vybrid UART controller is not able to detect breaks while doing data transfers.
A workaround should be implemented, allowing application to enable break detection or regular data transfers.
| WC-2511||Known Issue||I2C Clock Frequency Too Low on VF50||Colibri VF50||I2C||CE6, WEC7, WEC2013|
Description: The I2C frequencies on VF50 are too low.
Should: 100kHz, is: 86kHz
Should: 400kHz, is: 320kHz
| WC-2485||Known Issue||Bootloader Splashscreen Size Setting Corrupts Display||Colibri VF50, Colibri VF61||Bootloader||CE6, WEC7, WEC2013|
Description: Bootloader Splash-screen Size Setting Corrupts Display. It leads to strange effects on the display.
| WC-2476||Known Issue||Add support for USB devices with special descriptor length. Some USB storage devices don't get recognized||Colibri VF50, Colibri VF61||USB||CE6, WEC7, WEC2013|
Description: Some USB Storage devices don't get recognized.
| WC-2469||Known Issue||Binary BSP: Files Are Not Copied When Building a Custom BSP||Colibri VF50, Colibri VF61||Buildsystem||CE6, WEC7, WEC2013|
Description: Building of a custom image fails with an error about missing files files.bib, toradexcommon.bib, ...
Workaround: Copy the files manually to the release folder.
| WC-2450||Known Issue||Setting USB device as "USBSER_class" does not work||Colibri VF50, Colibri VF61||WEC7, WEC2013|
Description: Using USB Client as USBSER_class does not work with all the applications.
| WC-2445||Known Issue||Reading/Writing from NAND when entering suspend will crash device||Colibri VF50, Colibri VF61||Flash||CE6, WEC7, WEC2013|
Description: Writing to NAND flash at the same time as suspending may prevent device from wake-up
Workaround: Synchronize writing to NAND with suspend on application level. This means, make sure NAND access is done and then go to suspend.
| WC-2433||Known Issue||Only English(United States) region can be used||Colibri VF50, Colibri VF61||WinCE Feature||CE6, WEC7, WEC2013|
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.
| WC-2428||Known Issue||Sometimes Colibri VF50/VF61 has no Ethernet connection under WinCE||Colibri VF50, Colibri VF61||Ethernet||CE6, WEC7, WEC2013|
Description: Colibri VF50/VF61 has no Ethernet connection under WinCE
| WC-2427||Known Issue||Gpio boot settings are not accepted||Colibri VF50, Colibri VF61||CE6, WEC7, WEC2013|
Description: GPIO settings cannot be configured in the bootloader as described
| WC-2421||Known Issue||User Credentials for WPA2 Enterprise WiFi connections are not persisted across reboots||Colibri VF50, Colibri VF61||Wi-Fi||WEC7, WEC2013|
Description: Issue was identified as problem with Microsoft code. As WEC7 and WEC2013 are in extended support ( https://support.microsoft.com/en-us/lifecycle/search?alpha=Windows%20Embedded%20Compact%202013 ) this is not going to be fixed by Microsoft updates.
| WC-2414||Known Issue||No IP assigned after enabling/disabling ethernet adapter||Colibri VF50, Colibri VF61||Ethernet||CE6, WEC7, WEC2013|
Description: When disabling and enabling Ethernet adapter, PHY may not resume properly. See related issue #45294
| WC-2413||Known Issue||WinCe OS update fails when image source is a particular USB drive||Colibri VF50, Colibri VF61||Update System, USB||CE6, WEC7, WEC2013|
Description: Update Tool hangs while updating the OS image from particular USB drives.
Workaround: Use a different USB drive or an SD card to store your source image.
| WC-2412||Known Issue||.NET CF V3.9 bug when comparing to (constant) 0L||Colibri VF50, Colibri VF61||WinCE Feature||WEC2013|
Description: Comparing 0L and 0L in .NET Compact Framework 3.9 leads to wrong result.
Workaround: You can find a workaround from Microsoft here
| WC-2411||Known Issue||Ethernet standby is only enabled after entering/leaving standby|
Description: Enable/disable workaround for PHY only takes effect after entering standby mode
| WC-2410||Known Issue||Sometimes Colibri VF50/VF61 has no Ethernet connection under WinCE||Colibri VF50, Colibri VF61||Ethernet||CE6, WEC7, WEC2013|
Description: Colibri VF50/VF61 has no Ethernet connection under WinCE
| WC-2408||Known Issue||USB CableDetectPolarity=0 not working properly, CableDetectPin also not working||Colibri VF50, Colibri VF61||USB||CE6, WEC7, WEC2013|
Description: If driver is using SODIMM 137 as cable detect pin, polarity has to be fixed to 1. If driver is using any other pin as cable detect polarity can be reversed.
| WC-2404||Known Issue||Memory Leak in COM Open related to FTDI USB to Serial controller||Colibri VF50, Colibri VF61||UART, USB||CE6, WEC7, WEC2013|
Description: There is a small memory leak when opening and closing a COM port on a USB to Serial FTDI controller.
| WC-2395||Known Issue||Setting PIN 137 to 1 causes USBFN driver to keep reconnecting||Colibri VF50, Colibri VF61||CE6, WEC7, WEC2013|
Description: Pin 137 is on module connected to VBUS. If USB OTG is disabled and Pin 137 is set to 1 when USB cable is not connected USB stack will try to connect USB.
Workaround: We do not recommend using PIN 137 as GPIO. You can use it but you need to disable USB Device driver. To do this change this registry
[HKLM\Drivers\Builtin\UFN] change DLL to "_usbfn.dll"
[HKLM\Drivers\Builtin\USBOTG\UsbFn] change DLL to "_usbfn.dll"
| WC-2385||Known Issue||Memory Leak When Connecting ActiveSync/WMDC||Colibri VF50, Colibri VF61||WinCE Feature||WEC7|
Description: Minor memory leak when repeatedly connecting / disconnecting the USB cable between module and a PC.
| WC-2383||Known Issue||RtcSync Fails on VF50||Colibri VF50||RTC||CE6, WEC7, WEC2013|
Description: RtcSync does not save / restore time correctly to external RTC.
| WC-2367||Feature Request||Drag and Drop of files doesn't work on WEC2013||Colibri VF50, Colibri VF61||WinCE Feature||WEC2013|
Description: Drag and Drop of files doesn't work in the explorer/desktop on WEC2013.
| WC-2366||Known Issue||Can't save more then 396 files to SD Card||Colibri VF50, Colibri VF61||CE6, WEC7, WEC2013|
Description: If SD Card is using FAT you can not create more than 396 files with long names. This is the limitation of FAT on Windows CE
Workaround: Using exFAT fixes the issue
| WC-2358||Feature Request||Add battery driver||Colibri VF50, Colibri VF61||Power Management||CE6, WEC7, WEC2013|
Description: Currently we support only dummy battery driver. We will add support for a real one.
| WC-2354||Known Issue||Timer interrupt doesn't work||Colibri VF50, Colibri VF61||CE6, WEC7, WEC2013|
Description: There is no interrupt generated when a timer event occurs.
Workaround: The interrupt mask needs to be enabled. This can be done by using the interrupt library API Int_InterruptInitialize().
A sample can be found on our community website: https://www.toradex.com/community/questions/2325/after-issue-9134-bsp-v13beta1-pit-interruput-stop.html
| WC-2334||Known Issue||TCP DHCP settings "Lease Expires" date is wrong||Colibri VF50, Colibri VF61||Ethernet||WEC7|
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.
| WC-2328||Feature Request||Copy/Paste of files doesn't work on WEC2013||Apalis iMX6, Colibri iMX6||WinCE Feature||WEC2013|
Description: Copy/Paste of files doesn't work in the explorer/desktop on WEC2013.
Workaround: Use command line to copy files.
| WC-2322||Known Issue||Wake-up from suspend does not work if wake-up is generated before suspending is finished||Colibri VF50, Colibri VF61||Power Management||CE6, WEC7, WEC2013|
Description: Generating a wakeup event at the same time as module is going to suspend mode may lead to not waking up the module correctly.
Workaround: Prevent wake up events from happening when going into suspend. We saw problems when using a button which was putting the device to suspend but also was able to wake it up w/o proper de-bouncing.
| WC-2314||Known Issue||"Block 158 is bad." message in the production tester log-file|
| WC-2298||Feature Request||Provide a bootloader kit so customers can build their own bootloader||Colibri VF50, Colibri VF61|
Description: Add bootloader kit support to the bootloader.
| WC-2290||Known Issue||CeGetVolumeInfo does not report flag CE_VOLUME_TRANSACTION_SAFE for FAT32||Colibri VF50, Colibri VF61||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-2285||Known Issue||System time does not behave correctly when DST is not activated||Colibri VF50, Colibri VF61||RTC||WEC7, WEC2013|
Description: When DST is not active the current date/time reported by the system is not precise and lags few minutes per hours during runtime.
Workaround: If you have issues with DST not running correctly 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.
| WC-2280||Feature Request||V1.4 release||Colibri VF50, Colibri VF61|
Description: Contains all changes of the V1.4beta versions.
| WC-2279||Known Issue||System time runs slow if DST is not activated.||Colibri VF50, Colibri VF61||WEC7, WEC2013|
Description: When daylight saving option is unchecked from Date/Time properties then system time runs slow.
| WC-2818||Known Issue||ThreadPriority registry key not used by the UART Driver||Colibri VF50, Colibri VF61||UART||CE6, WEC7, WEC2013|
Description: ThreadPriority registry key not used by the UART Driver
Workaround: It is using the slightly wrong spelling keyword shown below:
| WC-2420||Known Issue||SD card cannot be accessed after being used as USB mass storage||Colibri VF50, Colibri VF61||SDIO/SD/MMC||WEC7|
Description: Accessing the SD card in parallel from the application and as a USB mass storage device can prevent the re-mounting of the SD-card.
Workaround: Copy the shared data to a ram drive, and use the ram drive as a USB mass storage