WEC VF50 / VF61 BSP Release

Description: Updated UpdateTool to version 8.2.0 (Library version 2.5)

Description: The stable release 1.7 contains all changes up to version 1.7b6

Description: When upgrading from BSP 1.3 to 1.4 or later the content of \Flashdisk is lost. This is because BSP 1.3 was using a different flash layout. This fix will allow to continue to use the old layout if found, so data can be preserved.

Description: After calling IOCTL_HAL_FLASHPARAMREFRESH, reading the configblock might return invalid values until next reboot.

Workaround: Use RegFlushKey to save registry.

Description: A NAND flash block will be marked as bad as soon as a single bit-flip is detected. The error correction can correct up to 24 bit-flips. This can lead to early reduction of the available memory in the flash filesystem, and prevent an application from storing more data.

Workaround: The flash does not really get defective by this error. Low-level formatting and updating the OS to the latest version solves the problem.

Description: If the UpdateTool is running while a file on the flashdisk is accessed, the system can freeze.

Workaround: A system reboot recovers from this condition.

Description: If a config block read or write is done at exactly the same time as reading or writing a file on the flashdisk, data in the flash can get corrupted.

Description: BSP version 1.6 will contain all changes up to 1.6b4

Description: Eboot does not show an asterisk (*) in front of the section 'gpio', which should mark that it has been saved.

Workaround: It's only a display problem, it has no effect on the actual functionality.

Description: On some modules in certain temperature ranges Ethernet might not work after suspend or after bringing down the network interface. The LED constantly blinks and receive/transmit errors might be reported. No frames can be received or sent in this state.

Workaround: If you are using suspend mode you have to disable Ethernet to improve power consumption. Delete "ImagePath" entry under HKLM\Comm\ENET to do so.

Description: - Added 936 (Simplified Chinese), 949 (Korean), 950 (Traditional Chinese) - Removed all Locales except English US (they can be re-added with cab installers) Cab installers can be found here ( https://developer.toradex.com/add-locales-to-an-existing-windows-embedded-compact-image )

Description: If a time beyond 2034 is set, there is kind of an overflow and the year be set back to 2007.

Description: USB Client only works in high-speed mode if the registry is configured as following: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\USBOTG\UsbFn] HighSpeed = dword:0 USB Host only works in high-speed mode if the registry is configured as following: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\USBOTG\Hcd] HighSpeed = dword:0 This is not ideal. We will change it to 1 to work in high-speed mode. By default the registry setting isn't set (not available) which means it works in high-speed mode. We won't change this behavior, so users not having added this registry setting won't see any difference.

Description: The EarlyAutoCopy feature of WaitForFlashDisk driver does not always work.

Description: Backlight BL_ON signal at power-on doesn't wait for stable pixel data which could lead to strange content flashing up on the display while booting. Use ss.dispondelay delay in ms to wait before backlight and display is enabled

Description: Reduce image size by removing sysgen_appdebug. We still support debugging under WEC2013 by adding webservices.dll in to the nk. For debugging it is not required to add any further dlls.

Description: The Key Default Value (the value assigned to the Key, shown as "(default)") cannot be edited

Description: SDBUS patch needed in order to support both WiFi and BT functions on the SDIO8787 card.

Description: Bootenum2 is now available in image. Its disabled by default. To use it enable [HKEY_LOCAL_MACHINE\Drivers\BuiltIn] "Dll"="BusEnum2.dll"

Description: System sounds are not available under WEC2013.

Description: At the end of an audio file some strange sound could occur.

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

Description: "Start Debugger Client" Does Not Start in WEC2013

Workaround: Open a WinCe command line, type the two commands: start conmanclient3.exe cmaccept3.exe

Description: The issue is related to a flash layout change we had to do in image 1.5.

Workaround: Just use the latest update tool, e.g. 7.5.0(2.0) or newer

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: Power consumption is lower after a suspend/resume cycle, compared to initial boot. This happens because Ethernet driver gets disabled after first suspend/resume cycle. We changed the bootloader to disable the Ethernet PHY and clocks. This allows to get to lower power consumption if you just disable the Ethernet driver which would just enable the PHY and clocks again when loaded. So just disable Ethernet if you do not use it. Instructions on how to disable drivers are here: https://developer.toradex.com/knowledge-base/disable-drivers

Description: Print serial debug message when registry is saved

Description: USB device connectivity is not reliable and seen especially when using USBSER class.

Description: Printout serial number in bootloader

Description: USB Mass Storage Class may take up to few minutes to mount. It may also fail to mount

Description: On some modules display may not work sometimes. This was due to a floating pin. Bootloader now pulls SODIMM 59 down to make sure display is working.

Workaround: Configure SODIMM 59 as level 0. To do this in bootloader use commands set ss.disp_gpio 59 set ss.disp_pol 0 save ss

Description: Investigate Use system files from FlashDisk or overwrite to Windows folder while loading Wait4FlashDisk driver.

Description: Using recovery mode will delete the config block. This is not ideal and we will remove this "feature"

Description: Bug in code prevented system to be auto formatted as TexFAT. This could lead to data loss

Workaround: Add this registry keys -> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\EXFAT] "FormatExFat"=dword:1 "FormatTFat"=dword:1 "DisableAutoScan"=dword:1 And use command "eraseflash filesystem" in bootloader to autoformat on next boot

Description: Explorer.exe no longer outputs debug messages

Description: .

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

Description: Some of the time servers configured in the standard image are no longer active. We replace the NTP servers with the ones from the NTP Pool Project (See also: http://www.pool.ntp.org )

Workaround: Add additional time servers and remove the non-valid ones as described here: https://msdn.microsoft.com/en-us/library/ms884926.aspx?f=255&MSPPError=-2147217396

Description: Exception will be occur when doing export registry.

Description: When importing reg file some keys get shown twice. Key is still created only one but view is wrong.

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: Users can now right click on the listview and get context menu where they can add values to the current key.

Description: Importing registry keys under HKEY_CURRENT_USER would fail.

Workaround: Contact support to get new version of registry editor.

Description: Using the debugger over an ethernet or wi-fi connection does not work reliably. On some PCs you get an error about runtime versions, on others connections works just sporadically. ActiveSync seems to work, but it's also not 100% reliable on all PCs.

Workaround: Issue has been fixed in release 1.1, it impacts only release 1.1 beta 4.

Description: When going to sleep mode, the CPU now uses less power

Description: All binaries have a built-in version number now.

Description: Generating to many framing errors could lead to full system crash.

Description: User can now configure time between re-connection attempts and number of times re-connection will be performed. Instructions can be found here: http://developer.toradex.com/knowledge-base/netui-additional-settings

Description: Using update tool to open files from sub-folders may fail.

Workaround: Move files to root directory

Description: Transmit messages could get lost, especially at higher baud rates.

Workaround: Use lower baud rate for now or use protocol to detect lost messages.

Description: Copy/Paste of files doesn't work in the explorer/desktop on WEC2013.

Workaround: Use command line to copy files.

Description: Provide support for the built-in watchdog feature in the kernel. This feature will be used by the watchdog library.

Description: When doing clean sysgen using our workspace some files did not get copied to release directory.

Workaround: Rebuild ToradexFiles subproject manually.

Description: SYSGEN_CONNMGR2 is missing in the workspace we provide

Workaround: Add SYSGEN_CONNMGR2 by selecting it in catalog view

Description: If external USB hard drive takes a long time to start it is not detected by the system.

Description: Calling TransmitCommChar does not transmit any charachers.

Description: If UART driver is not in use it does not work after resuming from suspend

Description: Added filesystem restore feature to Update Tool

Description: Rotating screen after image is booted lead to wrong rotation.

Description: When using .NET and RTSToggleAlwaysOn RTS will now toggle as soon as it finishes sending last byte.

Description: For fast UART communication please add "usingisr":1 inside HKLM\Drivers\Builtin\UARTA (or UARTB,UARTC,UARTD,UARTE ). This will be set to 1 by default in future releases.

Description: Add support for NETUI messages suppression.

Description: Added IOCTL (CAN_IOCTL_GET_STATUS) to driver. Users can now ready status registers and get more information about the CAN status. This will also be included in our libraries.

Description: Added the suspend mode feature

Description: We implemented suspend/resume now. Users need modules version 1.2 or newer to use this feature.

Description: Add an IO control which returns a Unique ID which can be used for security features. It might be one of these two: IOCTL_HAL_GET_DEVICE_INFO IOCTL_HAL_GET_UUID or both.

Description: We improved Vybrid graphics performance in some cases.

Description: SODIMM43 is configured as default wakeup pin

Description: Sometimes when connecting a device over RNDIS it would not get recognized.

Description: Debug output for Windows did not work on UART B and C but worked in bootloader

Workaround: None

Description: When shorting RX and TX of the port that is used for boot loader messages, UART driver would crash on opening.

Workaround: Use boot.silent in the bootloader

Description: Bootloader now supports set patch command

Description: Suspend option in start menu should only show if module supports it

Description: Adding synchronization to driver, to prevent wrong order of access to NAND

Description: When installing CAB files it did not show any GUI but it still worked.

Description: Serial port driver will be modified to be more in line with other drivers we use. We also hope this will help us fix some performance issues.

Description: I2C did set some pin as I2C pins even if users disabled I2C driver. We did not notice any side effect from this but we will fix it in next release.

Description: Add registry settings to configure the pin and polarity for the SD card detect signal.

Workaround: Currently there is not way to reconfigure the detect pin.

Description: Windows CE targets the ARMv4i architecture and does not support the ARMv7 architecture. ARMv4 did not provide a standard implementation for FPU and the OS relies on SW emulation. To support HW floating point the BSP must save the state of FPU at every task switch and the OS image should contain an additional DLL, implementing floating point operations that will replace the SW emulated ones. The same apply to NEON registers that are supported by the processor but not by the OS.

Description: CAN ID over 200000 did not work.

Workaround: Write to support for workaround.

Description: Added support for backlight. Users can use control panel to set when display will turn off after inactivity. By default backlight control is disabled so backlight will not automatically power off.

Description: Windows Embedded Compact 2013 currently does not support the Update Tool.

Description: Vybrid currently reports it's battery powered. Adding the battery driver will change this to AC powered by default.

Description: QueryPerformanceCounter Returns Wrong Value After 16 Seconds

Description: When framing error occurred on UART lines, the UART buffer got shifted by number of bytes.

Description: The recovery files (recovery utility) is missing in the image package V1.2beta1

Workaround: Use the recovery utility form download package V1.1 https://docs.toradex.cn/102563-vybrid-wince-image.zip

Description: In .NET 3.9 if HwGetCommProperties does not return all the baud rates, .NET 3.9 won't work properly.

Description: Using CAN IDs higher than 7 is currently not supported by the CAN driver.

Workaround: Use IDs below 7.

Description: Currently the drivers use FIFO mode to send/receive data. This may impact performances and increase CPU load in some scenarios. A common layer to support DMA will allow integration of DMA access in the drivers and also allow applications to used DMA for specific transfers.

Description: This is implemented now same as on our other modules, see instructions how to use it here: http://developer.toradex.com/knowledge-base/mouse-cursor

Description: Function returns correct values for Vybrid BSP now.

Description: UARTC was not enabled by default. We now fixed that and new images have UARTC enabled by default.

Description: I2C2 can be enabled in registry

Description: We changed driver indexing to match all other Toradex devices. Some users may need to fix their applications. Example: ADC0 is now changed to ADC1, and ADC1 is changed to ADC2

Description: Setting default state of SODIMM PINs at boot now works for all GPIOs

Description: Update tool is now included in the image. Update Tool is supported on WinCE 6 and WEC 7 only at the moment.

Description: Interface the existing ADC driver to the Toradex libraries to provide the same feature set provided on other modules.

Description: Provide functions to configure pull-up and pull-down, speed and other Vybrid-specific parameters related to each GPIO pin.

Description: The bootloader displays a wrong MAC address. This is only a displaying issue.

Description: When using certain functions of the serial port driver, the receiving interrupt was temporarily disabled which could lead to data loss on the receive side.

Description: The Silverlight references in the Toradex SDK do not match the Windows CE image 1.1b1 and later. Workaround for more information.

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

Description: Users can now set GPIO as input during boot time. How to do this is described here http://developer.toradex.com/knowledge-base/gpio-config-block-settings#Vybrid

Description: When using Windows CE6 or Windows embedded compact 7, there was some issues with the image is using screen rotation. Here are instructions on how to rotate the screen: http://developer.toradex.com/knowledge-base/display-rotation

Description: We changed port name from I2C0 to I2C1, so we can keep naming convention for all our devices.

Workaround: The port name can be configured in the registry settings.

Description: On Windows CE6 there ware sometimes issues with saving registry. Now functions described on this page http://developer.toradex.com/knowledge-base/save-registry work correctly

Description: IOCTL_HAL_REBOOT is now supported on Vybrid. This allows the capability of resetting the device via software as described in this article: http://developer.toradex.com/knowledge-base/ioctl-hal-reboot A "restart" command has been added on the bootloader console to perform the same operation.

Workaround: Version 1.1Beta1 has an issue that prevents users from using IOCTL_HAL_REBOOT directly. Users can use SetSystemPowerState(NULL, POWER_STATE_RESET, NULL); to reboot the system. This is anyway the recommended way.

Description: Currently the BSP supports only USB client operations on the 2nd integrated USB controller. This controller supports also host mode using USB OTG, but the software does not currently support this.

Description: Add support for more ECC to VF61. Bootloader will automatically migrate config block. But flash disk data will be lost. The user must backup the data before migrating to V1.1beta2 and restore it after the update.

Description: Horizontal Sync Width and Vertical Sync Width values can now be above 255 in bootloader.

Description: The bootloader supports a splash screen and also configuration of display parameters directly from the command prompt using the same format used for PXAxxx BSP. Customization of splash screen isn't possible at the moment, but you can disable splash screen. Splash screen parameters can be re-used by display driver as described here: http://developer.toradex.com/knowledge-base/display-driver-registry-settings

Description: Add the PS/2 feature for mouse and keyboard to the BSP. The implementation will allow to use any GPIO for SDA and SCL.

Workaround: Use a USB mouse or keyboard

Description: The hardware controller can support up to two additional bits after each byte of data. One bit is always used as stop bit, the other one may be used as additional stop bit or parity. Now the driver supports also 2 stop bits, but only with no parity. When selecting 8 data bits + parity the parity is now sent as 8th bit, driver can support 7 or 8 data bits, parity and 1 or 2 stop bits. The maximum number of bits is 10. So it's possible to have 8+parity+1 stop, 8 + 2 stop, but not 8+parity+2 stop bits This means that the serial controller supports the following combinations: - 8 data bits + 1 stop bit - 8 data bits + 1 parity bit + 1 stop bit - 8 data bits + 2 stop bits - 7 data bits + 1 partity bit + 1 stop bit Currently only the first and last combinations are supported by the driver

Description: When the I2C_SDA and I2C_SCL lines are not pulled-up (not used for I2C), as soon as an application tries to communicate on the bus CPU usage rises to 100%. The I2C drivers checks if the SDA line is high, if it isn't it generates some clock pulses on SCL to allow devices that are keeping the bus busy to finish their operations (devices like RTCs have no reset signals and if the board is reset in the middle of an I2C communication they may lock the whole bus) and then sends a STOP to allow all connected devices to expect a new packet. If lines are not pulled-up this leads to an infinite loop that uses 100% of the CPU. Issue is solved in version 1.0. The driver tries to initialize the bus for at most 10 seconds when an application tries to communicate. Is still suggested to disable the I2C driver if no I2C devices are used.

Workaround: Disable I2C driver if no devices are connected to the I2C bus.

Description: The driver doesn't generate this useless output messages anymore.

Description: The behaviour of dbg.serial is now coherent with the one of other Toradex platforms. dbg.fread and dbg.fwrite flags, preventing loading and saving of regitry are also supported.

Description: When new user accounts are created using the management interface or the NTLMSetUserInfo API the accounts work until the system is reset. The registry must be saved to keep accounts persistant, but on reset passwords are no longer recognized. This issue has been solved in release 1.0

Description: When an application is sending/receiving small packets on the serial port (3-7 bytes, depending on the port) the interrupt handling routine will not clear a flag correctly, leading to an unacknowledged interrupt re-entering every 1uS and locking the system.

Description: Resistive touch screen is now supported on VF61. The driver supports the TouchType,MinZValue,Sensivity and Settling time parameters described in this knowledge base article: http://developer.toradex.com/knowledge-base/resistive-touch-screen

Description: The filesystem on flash is mounted asynchronously and this prevents the system from loading drivers that are not part of the image. To avoid this issue a pseudo-driver can be used to delay further driver loadings until the filesystem is mounted. This will allow loading at startup drivers located in the FlashDisk\System folder. Drivers with order less than 128 will be loaded from the image. The driver is included in the image but it's disabled by default to not unnecessarely slow down the boot process. To enable it write the following value in the registry: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Wait4FlashDisk] "Flags"=dword:0 Driver will be activated after a reboot. The driver supports two registry values to configure the internal flash mount point and mount timeout in seconds (here shown with their default values) [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Wait4FlashDisk] "Folder"="\\FlashDisk" "Timeout"=dword:3C See: http://developer.toradex.com/knowledge-base/load-drivers-from-internal-flash

Description: USB Client driver is supported. ActiveSync, Storage or RNDIS drivers can be configured following the instructions of this knowledge base article: http://developer.toradex.com/knowledge-base/usb-function-driver-%28colibri%29 The USB mass-storage profile can't be used to access the internal flash from a PC because this storage is partitioned in a way that is not supported by Windows or Linux. This partitioning system is required to support wear leveling on the filesystems mounted on the internal flash.

Workaround: In order to debug applications without using USB Client, please refer to the following knowledge-base article: http://developer.toradex.com/knowledge-base/colibri-vf50-vf61-wince-bring-up#Application_debugging

Description: The BSP supports persistance of RAM-based registry. The registry is saved on internal NAND, keeping a backup copy until the save operation has been completed successfully. A menu option in the bootloader can be used to clean the registry and reset all configuration parameters to default values.

Description: The "C" option in the e-boot menu can be used to clear the registry, effectively resetting all parameters to their default value. Registry cleanup is suggested after flashing a different version of the operating system on the module.

Description: We are going to ship fused modules with the next production batch. We had to do some adjustments to support these modules too. This also includes recovery mode for the modules through serial port.

Description: The system tick was configured using 50MHz as value for the clock speed used by the timers. The real value is 66MHz for VF50 and 83MHz for VF61. This error impacts the actual lenght of Sleep calls and all the timeouts used for wait functions.

Workaround: The issue has been fixed and tested. The fix will be released in the next update.

Description: Bad block management has been added to the bootloader.

Description: I2C is supported by a driver. Support in the image is limited to I2C0. The driver is interfaced with the Toradex I2C library and provides API compatibility with existing applications.

Description: Savereg.exe has bee added to the OS image, allowing persistant saving of the registry. It is available from the start menu as in other modules.

Description: Currently using touch as wakeup source is not possible because of hardware limitations.

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

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.

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.

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.

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.

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

Description: This is only needed if you need to recover the old non-fused module. New modules don't have this limitation any more.

Description: Copy/Paste and Drag and Drop doesn't work on with the Explorer on WEC2013.

Workaround: Use command line to copy files.

Description: The I2C frequencies on VF50 are too low. Should: 100kHz, is: 86kHz Should: 400kHz, is: 320kHz

Description: Some USB Storage devices don't get recognized.

Description: Using USB Client as USBSER_class does not work with all the applications.

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: GPIO settings cannot be configured in the bootloader as described

Description: When disabling and enabling Ethernet adapter, PHY may not resume properly. See related issue #45294

Description: Comparing 0L and 0L in .NET Compact Framework 3.9 leads to wrong result.

Workaround: You can find a workaround from Microsoft here https://social.msdn.microsoft.com/Forums/en-US/a187a5da-d46f-440c-9e40-e201636c042d/bug-in-net-cf-justintimecompiler-with-roslyn-generated-ilcode-windows-embedded-compact-2013?forum=netfxcompact

Description: Colibri VF50/VF61 has no Ethernet connection under WinCE

Description: There is a small memory leak when opening and closing a COM port on a USB to Serial FTDI controller.

Description: Minor memory leak when repeatedly connecting / disconnecting the USB cable between module and a PC.

Workaround: -

Description: Drag and Drop of files doesn't work in the explorer/desktop on WEC2013.

Description: Currently we support only dummy battery driver. We will add support for a real one.

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: 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.

Description: Add bootloader kit support to the bootloader.

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.

Description: When daylight saving option is unchecked from Date/Time properties then system time runs slow.

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