Search by Tags

WEC VF50 / VF61 BSP Release

 

The following table contains known issues, scheduled bug fixes, and feature improvements for the Vybrid 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 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.

Odd beta versions, as 1.0b1 or 1.3b3, are internal releases only for testing. They are omitted from the table.

View All Submitted (open) Released (closed)
Clear Filter
Issue #StatusSubjectModuleSubsystemWinCE OS

V1.1beta1 (Release date: 2015-02-06)
- WinCE 6 Updates: Installed Microsoft CE6 Updates until 2014M11
- WEC 7 Updates: Installed Microsoft CE7 Updates until November 2014
- WEC 2013 Updates: Installed Microsoft CE8 Updates until November 5
WC-2552FixedI2C drivers high CPU load when I2C lines are not pulled-upColibri VF50, Colibri VF61I2CCE6, WEC7, WEC2013

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.