CUPID release notes. OS V1.6.0 19.07.2010 Released by Marc-Oliver Westerburg * Minimum needed Redboot version is V1.11r2520. * The following hardware version is supported: 1.0 * Windows CE 6.0 R3, QFEs up to 05/2010 = Notes = Despite the high version number, this is only an early development release intended to allow customers to start application development and platform evaluation. Many drivers, tools and APIs are not yet included and those that are included may contain known bugs and have not been sufficiently tested to consider them stable. = Supported Drivers = * Display * NAND-FlashDisk * SRAM-Disk * Persistent registry in SRAM * Ethernet * RTC * EEPROM * AC97-resistive touch / I2C-capacitive touch (build-time option) * CAN (both ports, when equipped) * RS232 (UART1, UART2) * RS485 (UART3, when equipped; see known restrictions) * SDHC (see known restrictions) * USB-Host on both USB ports (see known restrictions) * I2C (I2C1, I2C2, I2C3) * SPI (SPI1, SPI2) * Matrix Keypad * Digital-I/O * USB Memory Stick, USB Mouse, USB Keyboard (german and englisch layout) = Garz & Fricke APIs = * To access interfaces and functionality not directly supported by Windows-CE Garz & Fricke provides several custom APIs. * Development support is included in both SDK and BSP. Documentation is provided in header files. * Eventhough headers and libraries for more Garz & Fricke APIs may be included in SDKs and BSPs, only the following APIs are supported by the regular OS-image: * CAN (CAN_Api.h, CAN_API.lib) * EEPROM (EepromApi.h, EepromApi.lib) * Digital-I/O (GFDigitalIOApi.h, GFDigitalIO.lib) * GFVersion (GFVersionApi.h, GFVersionApi.lib) * General Purpose Timer (Gpt_Api.h, GptApi.lib) * I2C (I2c_Api.h, I2CApi.lib) * ShowVersion (ShowVersionApi.h, ShowVersionApi.lib) * SPI (SpiApi.h, SpiApi.lib) = Changes since last release = * Fixed AC97 register read/write communication * Fixed touch driver performance and stability problems * Freed GPT timers for application use * Added support for Digital-I/O driver and API (both on dedicated DIO-pins and the Keypad-interface) * Added support for matrix keypad * Fixed performance problems of Matrix-Keyboard driver * Made path for Matrix-Keyboard configuration file configurable via registry * Split DIO- and Keyboard drivers in platform specific parts to support other i.MX35 platforms * Changed DIO driver to dynamic interrupt allocation * Changed "reset.exe" tool and removed IOCTL_HAL_REBOOT support from user space applications for proper SW-reset support * Changed filesystems for NAND flash disk and SRAM disk from exFAT to TexFAT for improved reliability * Fixed clock-gating on serial debug port * Cleaned-up interrupt allocation in drivers * Replaced old ShowVersion tool with separate command-line and (updated) GUI versions. * Added RS485-support to UART driver * Added support for binary BSPs * Added support for capacitive touches * Fixed problem with occasional RTC 'jumps' (due to a bug in Microsoft's SNTP-server occasionally the realtime clock was to run 30 minutes late) * Fixed I2C thread synchronization occasionally resulting in failing I2C-communiation, data corruption or even I2C bus-hangs. * Made several drivers switchable via registry/XML-configuration files. XML-configuration files are provided for each driver and can be installed like any other XML-configuration file (e.g. display settings). After installation the respective driver will be disabled and can be enabled again via the RedBoot-command "fconfig". By default all drivers are enabled. Drivers that can be turned-on/-off this way: * UART (COM1, COM2, COM3) * I2C (I2C1, I2C2, I2C3) * SPI (SPI1, SPI2) * CAN (CAN1, CAN2) * Matrix Keypad (KPP1) * Touch driver * Touch calibration = Known Restrictions = * USB OTG Port: Currently only host-mode is supported. A device is only recognized if it is already plugged in during boot. IMPORTANT NOTE: The OTG port is currently configured to pure host-mode. DO NOT CONNECT THE SYSTEM TO A PC OR OTHER USB HOST! * SD-Card: Driver occasionally issues error messages. If this may result in data-corruption is currently unknown. * RS-485: On CUPID v1.0 boards pins 13 and 14 of the RS-485 receiver (IC13) must be shortened for RS-485 to work properly. * Currently some error messages are displayed during boot, because the Audio driver is not yet working. These can be ignored: {{{ [ERROR] "InitOutputDMA: DMA buffer page allocation failed" [ERROR] "InitInputDMA: DMA buffer page allocation failed" [ERROR] "Failed to initialize output interrupt thread" }}} * Currently unsupported interfaces / devices: * No audio support * No MDB support * No USB device-mode support on OTG-port OS V1.3.0 25.03.2010 Released by Marc-Oliver Westerburg * Minimum needed Redboot version is V1.11r2520. * The following hardware version is supported: 1.0 * QFE-support up to CE6.0R3, = Notes = Despite the high version number, this is only an early development release intended to allow customers to start application development and platform evaluation. Many drivers, tools and APIs are not yet included and those that are included may contain known bugs and have not been sufficiently tested to consider them stable. = Supported Drivers = * Display * NAND-FlashDisk * SRAM-Disk * Persistent registry in SRAM * Ethernet * RTC * EEPROM * AC97-resistive touch / I2C-capacitive touch (build-time option) * CAN (both ports, when equipped) * RS232 (UART1, UART2) * RS485 (UART3, when equipped; see known restrictions) * SDHC (see known restrictions) * USB-Host on both USB ports (see known restrictions) = Changes since last release = * This is the first public release. = Known Restrictions = * USB Host Port: Device detection only works once. If a device is unplugged and the same or other device is plugged back in, it won't be recognized. * USB OTG Port: Currently only host-mode is supported. A device is only recognized if it is already plugged in during boot. IMPORTANT NOTE: The OTG port is currently configured to pure host-mode. DO NOT CONNECT THE SYSTEM TO A PC OR OTHER USB HOST! * SD-Card: Driver occasionally issues error messages. If this may result in data-corruption is currently unknown. * RS-485: On CUPID v1.0 boards pins 13 and 14 of the RS-485 receiver (IC13) must be shortened for RS-485 to work properly. * The GPT driver and API are currently completely used by the AC97 touch driver and are not available for applications. * Currently some error messages are displayed during boot, because the Audio driver is not yet working. These can be ignored: {{{ [ERROR] "InitOutputDMA: DMA buffer page allocation failed" [ERROR] "InitInputDMA: DMA buffer page allocation failed" [ERROR] "Failed to initialize output interrupt thread" }}} * Currently unsupported interfaces / devices: * No audio support * No Digital-I/O support * No MDB support * No USB device-mode support on OTG-port * No support for Keypad Interface