-------------------------------------------------------------------------------- - Logic PD OMAP35x Windows Embedded CE 6.0 Port - - - - Source drop 2_1_1 - - - - Release Notes - - - - Logic PD, February 2012 - -------------------------------------------------------------------------------- This file contains information pertaining to the usage of Logic PD's Windows Embedded CE 6.0 port on the OMAP35x SOM-LV and OMAP35x Torpedo SOM platforms. It provides information on the contents of the enclosed .zip file. For instructions on how to install and use this package, please refer to the "OMAP35x Windows CE 6.0 BSP User Manual," available on the Logic PD website at: http://support.logicpd.com/downloads/1347/ PACKAGE CONTENTS -------------------------------------------------------------------------------- + \Binaries This folder contains pre-built OS images based on OS Designs also included with this package. The differences are listed below. Each image references the applicable model numbers as well as a .pbxml file associated with the selected catalog items. Please refer to the Model Number of your own device to determine the applicable image. - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-10_SOM-LV/NK-trunk-10D-build-xx-revision-xxxxx.bin RAM-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-10_D_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3530-10-1672JFIR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-10_SOM-LV/NK-trunk-10D_Hive-build-xx-revision-xxxxx.bin Hive-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-10_D_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3530-10-1672JFIR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-11_SOM-LV/NK-trunk-11A-build-xx-revision-xxxxx.bin RAM-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-11_A_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3503-11-1670HFCR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-11_SOM-LV/NK-trunk-11A_Hive-build-xx-revision-xxxxx.bin Hive-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-11_A_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3503-11-1670HFCR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-11_SOM-LV/NK-trunk-11B-build-xx-revision-xxxxx.bin RAM-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-11_B_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3503-11-1672IFCR-A SOMOMAP3530-11-1672IFCR-A SOMOMAP3530-11-1672IFXR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-11_SOM-LV/NK-trunk-11B_Hive-build-xx-revision-xxxxx.bin Hive-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-11_B_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3503-11-1672IFCR-A SOMOMAP3530-11-1672IFCR-A SOMOMAP3530-11-1672IFXR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-11_SOM-LVNK-trunk-11C-build-xx-revision-xxxxx.bin RAM-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. Reference .pbxml file: OMAP35X-11_C_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3530-11-1670EFCR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-11_SOM-LVNK-trunk-11C_Hive-build-xx-revision-xxxxx.bin Hive-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. Reference .pbxml file: OMAP35X-11_C_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3530-11-1670EFCR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-11_SOM-LV/NK-trunk-11D-build-xx-revision-xxxxx.bin RAM-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-11_B_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3530-11-1782JFIR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x-11_SOM-LV/NK-trunk-11D_Hive-build-xx-revision-xxxxx.bin Hive-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-11_B_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3530-11-1782JFIR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x_TORPEDO_SOM/NK-trunk-TORPEDO-build-xx-revision-xxxxx.bin RAM-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-11_C_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3503-20-1670AGCR-A SOMOMAP3530-20-1670AGCR-A SOMOMAP3530-20-1670AGIR-A SOMOMAP3503-21-1670AGCR-A SOMOMAP3530-21-1670AGCR-A SOMOMAP3530-21-1780AGIR-A - LOGIC_SOM_OMAP35X_SHOW/OMAP35x_TORPEDO_SOM/NK-trunk-TORPEDO_Hive-build-xx-revision-xxxxx.bin Hive-based registry storage release build of LOGIC_SOM_OMAP35x_SHOW OS Design. Contains all of the bells and whistles, including multimedia support and Internet Explorer. A very large image; most components are included. For application development, connect the Visual Studio tools using ActiveSync over USB Function (OTG) or an active Ethernet connection. Contains most application support components. Reference .pbxml file: OMAP35X-11_C_NK.pbxml. This image applies to the following Model Numbers: SOMOMAP3503-20-1670AGCR-A SOMOMAP3530-20-1670AGCR-A SOMOMAP3530-20-1670AGIR-A SOMOMAP3503-21-1670AGCR-A SOMOMAP3530-21-1670AGCR-A SOMOMAP3530-21-1780AGIR-A - LogicLoader_Scripts/ Contains example scripts for loading and launching the NK.bin files. + load_from_nand_script.txt Mounts YAFFS partition and loads NK.bin from YAFFS. + load_from_sd_script.txt Mounts SD card and loads NK.bin from SD. + LoLo_bootme_192.168.0.154_NET Sets up static IP address, sends bootme packet to Platform Builder/VS2005, and loads NK.bin from Platform Builder. + LoLo_bootme_dhcp_NET Sets up DHCP address, sends bootme packet to Platform Builder/VS2005, and loads NK.bin from Platform Builder. + WinCE_Launch_after_ram_load_boot_script.losh Command to launch OS after NK.bin is loaded (assumes default 4.3" display is used). + WinCE_Launch_LCD-x.x-xxxx-xx_ram_boot_script.losh Command to launch OS after NK.bin is loaded; sets up specific display kit before launching into OS. + \Documentation This folder contains documents describing the operation and use of the driver components built into the OS Design. + \OSDesigns - LOGIC_SOM_OMAP35x_SHOW LOGIC_SOM_OMAP35x_SHOW OS Design is shared by both the OMAP35x SOM-LV and and Torpedo SOM platforms. This contains most of the drivers, including multimedia and Internet Explorer, plus all application support. + \PLATFORM This folder contains the OMAP35x SOM-LV and Torpedo SOM platform-specific port of the Windows CE 6.0 OS. The BSP can be built for either platform, based on a catalog component choice. There are very few differences in the hardware design and these small differences are handled in software by the building process. SUPPORTED DRIVERS AND FEATURES -------------------------------------------------------------------------------- + Basic kernel functionality - Interrupts, 1ms system timer - Shared access to TWL chip, I2C interface, and GPIO - Performance counter supported - TWL Root Driver - OEMIdle / Suspend support - RTC + Audio Driver - Supports audio playback through audio jack on the baseboard. - Supports audio record through audio jack on baseboard. + CF Memory Map Mode - CF card support available as ATA Memory Mapped device. + YAFFS Driver - Support for YAFFS (Yet Another Flash File System) on the onboard NAND flash. + Bluetooth Driver + Root Power Bus Driver + Power Key Driver + LED Switch Driver - OMAP35x SOM-LV only + Display Driver - Supports Logic PD's 3.6", 4.3", 6.4", and 12.1" displays - Supports custom display initialization in LogicLoader (auto detects settings) - Supports 2D Hardware Acceleration + System DMA Driver + GPIO Driver - Supports GPIO usage from applications and drivers for OMAP35x and PMIC (TPS65950) GPIO. - API header information can be found in \WINCE600\PLATFORM\COMMON\SRC\SOC\OMAP35XX_TPS659XX_TI_V1\inc\gpio.h - Example usage can be found in: \WINCE600\PLATFORM\LOGIC_SOM_OMAP35x\SRC\drivers\sdhc\impl\ SDController.cpp + I2C Driver + Wi-Fi Driver - Supports WiLink6.0 solution using WL1271 module - Provided in binary format only - Texas Instruments does not consider the WL1271 driver to be production ready + NETUI Driver - Custom NETUI driver with modified dialog boxes to support Logic PD's 4.3" display + Ethernet Driver - Boot-time and run-time cable detection - 10/100 MB/s full/half duplex modes support - Auto negotiation support - Static IP and DHCP address support - LAN921x and LAN922x chip support + SDIO Driver - Boot-time and run-time card detection - DMA supported read and write transfers - Write protection support - On-board Wi-Fi chip support + McBSP Driver + SPI Driver - Supports SP13 - Supports DMA operation + UART Driver - Supports 5, 6, 7, 8N1 with standard baud rates up to and including 115200b/s. + Touch Driver - System wake-up capability + USB OTG - OMAP35x USB0 Port - Function - Can function as an ActiveSync device - Can function as a Mass Storage device - Host - Supports Human Interface Devices (HID) e.g., Mouse, Keyboard - Supports Mass Storage devices + USB Host - ISP176x (post PCN400) - Supports HID devices - Supports three USB Host ports from the OMAP35x SOM-LV and Torpedo baseboards + YAFFS, SD, and CF based Hive Registry is supported. YAFFS is the default, as defined in LOGIC_SOM_OMAP35x_SHOW.bat set BSP_HIVE_YAFFS=1 set BSP_HIVE_SDHC= set BSP_HIVE_ATAMEMCF= + KITL (Only in Debug Configuration) - Debugging with break points - Remote tools - Will notify Ethernet driver to not load, preventing conflicts TESTED PLATFORMS -------------------------------------------------------------------------------- + The following modules have been tested: Due to a single customer’s last time buy configuration, only a single OMAP35x SOM-LV -10 has been tested. SOM-LV -10: - Model Number SOMOMAP3530-10-1672JFIR Part Number 1017137 Configuration Description ASSEMBLY, OMAP3530-10 (ROHS), 256MB DDR, 512MB NAND, 8MB NOR, AUDIO, TOUCH , ETHERNET,BT, I-TEMP SOM-LV: Baseboard #1013373 SOM-LV -11: - Model Number SOMOMAP3503-11-1670HFCR-A Part Number 1016383 Configuration Description ASSEMBLY, OMAP3503-11 (ROHS), 128MB DDR, 256MB NAND, 0MB NOR, ETHERNET, AUDIO, TOUCH - Model Number SOMOMAP3530-11-1670EFCR-A Part Number 1016373 Configuration Description ASSEMBLY, OMAP3530-11 (ROHS), 128MB DDR, 256MB NAND, 0MB NOR, AUDIO, TOUCH - Model Number SOMOMAP3530-11-1782JFIR-A Part Number 1016361 Configuration Description ASSEMBLY, OMAP3530-11 (ROHS), 256MB DDR, 512MB NAND, 8MB NOR, ETHERNET, AUDIO, TOUCH, BT, I-TEMP - Model Number SOMOMAP3530-11-1672IFCR-A Part Number 1016346 Configuration Description ASSEMBLY, OMAP3530-11 (ROHS), 128MB DDR, 256MB NAND, 8MB NOR, ETHERNET, AUDIO, TOUCH, BT, 802.11 SOM-LV: Baseboard #1014845 Torpedo SOM -21: 1016185H, 1016185M - Model Number SOMOMAP3530-21-1780AGIR-A Part Number 1016336 --> 1016185M Configuration Description ASSEMBLY, TORPEDO, OMAP3530-21 (ROHS), 256MB DDR, 512MB NAND, I-TEMP - Model Number SOMOMAP3530-21-1670AGCR-A Part Number 1016334 --> 1016185H Configuration Description ASSEMBLY, TORPEDO, OMAP3530-21 (ROHS), 128MB DDR, 256MB NAND Torpedo: Baseboard #1013995, #1014845 BOOTLOADER -------------------------------------------------------------------------------- + LogicLoader (LoLo) 2.4.14 or higher is required + Tested with 2.4.14 OMNIFY -------------------------------------------------------------------------------- + Part Number 1017480 KNOWN ISSUES -------------------------------------------------------------------------------- + Intermittent issue with white screen and no Windows shell at boot When booting and loading image from SD; after running "exec" the LCD sometimes remains at the white screen. Wait for the system to suspend (6 minutes) and then bring the system out of suspend by either touching the LCD screen or pressing the resume button (S2) to display the Windows shell. (Jira # OMAP3WCE600-357) + A pop sound may be heard at the end of an audio file. (Jira # OMAP3WCE600-341) + KITL Auto Negotiation KITL will fail at connecting to a network that does not support auto negotiation. In current release, auto negotiation must be available for KITL to work. (Jira # OMAP3WCE600-444) + The CF card was developed for memory-mode only and does not support runtime hot-swap (insertion/removal); it acts like an internal hard drive. For runtime hot-swap support, contact Logic PD Sales at: http://www.logicpd.com/contact/inquiry/ (Jira # OMAP3WCE600-21) + SDIO multi-block data transfers are limited to 2 blocks/transfer (silicon bug). (Jira # OMAP3WCE600-445) + SDIO "I/O mode on" does not reliably work. (Jira # OMAP3WCE600-446) + SDIO Windows CETK test does not complete and results in the device disconnecting. (Jira # OMAP3WCE600-447) + Debug binary may not return to operation after entering low-power mode. Upon entering low-power mode or being suspended when using the debug binary module, the system may not recover to full operation. The CE screen may or may not return, and if the CE screen does return it may or may not operate normally. This behavior has not been observed on the release binary. (Jira # OMAP3WCE600-448) + Debug tools and debugging via ActiveSync are not supported. Cause: Windows CE 6.0 has no support for Cortex-A8 ARMv7-A; therefore, it falls back to using ARMv4 instead. However, the built-in Microsoft Platform Builder CE Debug Tools support the ARMv4i architecture only. Workaround: Copy x:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\ target\wce600\armV4i into x:\Program Files\Common Files\Microsoft Shared\Windows CE Tools\Platman\ target\wce600\armV4 For further information, please refer to the following URL: http://nicolasbesson.blogspot.com/2007/06/remote-tools-arm-processor-and-windows.html + SPI Test will fail on the first pass on SPI1 interface if Bluetooth is configured in the build. It will pass on the second attempt. If Bluetooth is not configured, the test should pass on the first attempt. (Jira # OMAP3WCE600-449) (see also OMAP3WCE600-154) + Bluetooth driver will generate DEBUGCHK breaks (2 to 3 times) when using a debug build with kernel debugger. Pressing the F5 key (Debug Menu / 'Start') to continue running will properly boot the device. "Unknown: DEBUGCHK failed in file C:\ymzki\private\winceos\comm\bluetooth\pan\.\miniport.cxx at line 5594" (Jira # OMAP3WCE600-59) + UFSDIO/SDHC driver may generate DEBUGCHK breaks (~10 times) when using a debug build with kernel debugger. Pressing the F5 key (Debug Menu / 'Start') to continue running may help; a reboot may be required. "Unknown: DEBUGCHK failed in file C:\WINCE600\PLATFORM\LOGIC_SOM_OMAP35x\SRC\drivers\sdhc\ SDBUS2\sddevice.cpp" (Jira # OMAP3WCE600-450) + USB OTG Host functionality requires adding the following items to the OS build: - USB OTG Function - USB Function - USB Function Client (Jira # OMAP3WCE600-451) + USB OTG may disconnect from USB Host or USB Devices. (Jira # OMAP3WCE600-91) + USB Mass Storage Devices connected to the USB Host interface unexpectedly terminate during read transactions. This issue does not exist when connecting a USB Mass Storage Device to the USB OTG interface. (Jira # OMAP3WCE600-452) + Touch functionality may not work and may require a reboot on OMAP35x SOM-LV boards using OMAP35x silicon revision 2.1 or earlier(see PCN405). This issue does not exisit on SOM-LV boards with OMAP35x Silicon revision 3.0 and higher. (Jira # OMAP3WCE600-33) + Charge current is set to 1.2A; the limit for the OMAP35x Torpedo Development kit is 0.6A (at room temperature less than 30C). To change the charging current, comment the following code from the \WINCE600\PLATFORM\LOGIC_SOM_OMAP35x\SRC\ oal\oallib\oem_pm.c file: // UPDATE MAIN BATTERY CHARGING SETTINGS ON TORPEDO PLATFORM { OALTritonWrite(hTwl, TWL_BOOT_BCI, 0x10); //need to turn off auto-charging OALTritonWrite(hTwl, TWL_BCICTL1, 0x20); //update charging current to 2x OALTritonWrite(hTwl, TWL_BOOT_BCI, 0x11); //turn back on auto-charging // OALTritonWrite(hTwl, TWL_BCIMFKEY, 0xE7); // OALTritonWrite(hTwl, TWL_BCIIREF1, 0xFF); //update charging current // OALTritonWrite(hTwl, TWL_BCIMFKEY, 0xE7); // OALTritonWrite(hTwl, TWL_BCIIREF2, 0x03); //update charging current } (Jira # OMAP3WCE600-39) + For the OMAP35x Torpedo platform, movie or audio files requiring certain codecs will have a warning message saying the codec is not available. Playback of movies continues with no audio. (Jira # OMAP3WCE600-308) + OMAP35x Torpedo suspend button (S3) no longer works. (Jira # OMAP3WCE600-379) An unsupported fix consists in enabling the GPIO associated to the S3 button, CONTROL_PADCONF_SYS_BOOT0, at line 585, in the trunk\PLATFORM\LOGIC_SOM_OMAP35x\SRC\OAL\OALLIB\platform.c file, PinMuxSetup() function: change from //OUTREG16(&pWakeupConfig->CONTROL_PADCONF_SYS_BOOT0, (INPUT_ENABLE | PULL_INACTIVE | MUX_MODE_4)); /*GPIO_2*/ to OUTREG16(&pWakeupConfig->CONTROL_PADCONF_SYS_BOOT0, (INPUT_ENABLE | PULL_INACTIVE | MUX_MODE_4)); /*GPIO_2*/ + The wireless 802.11 driver fails to resume after the system has been resumed. (Jira # OMAP3WCE600-44) + When using the 3.6" or 6.4" display, it can be difficult to calibrate with touch, as the display touch is out of calibration. The user must attach a mouse to navigate to the calibration application. (Jira # OMAP3WCE600-510) + Cannot use touch or USB devices when KITL is enabled on OMAP35x Torpedo SOM. (Jira # OMAP3WCE600-467) + Serial Debug messages appear on UARTA. If you disable the serial debug and enable UARTA to be used as a serial standard UART, you still get serial debug messages from UARTA. (Jira # OMAP3WCE600-464) + Display splash screen fades to white. While loading from an SD card, the Logic PD logo splash screen is displayed but it fades to white, then to white with stripes. (Jira # OMAP3WCE600-425) + CETK Test Failure "RTC_Real-Time_Functions" - December 31st rollover test. This is a Microsoft related issue, due to enabling DST. (Jira # OMAP3WCE600-375) + White screen flashes before shell on wake-up. (Jira # OMAP3WCE600-363) + USB1760 Host may fail to return after suspend and resume. (Jira # OMAP3WCE600-354) + USB OTG HOST USB Powered Hub + 2 devices at run time is non-functional. Keyboard nor mouse will work well with powered hub. (Jira # OMAP3WCE600-350) + Included files are not properly added. SDK build does not include necessary header files. (Jira # OMAP3WCE600-471) + Performance: Poor Object Store File System Performance. The performance of copying a file from \Temp to \Application Data is low. (Jira # OMAP3WCE600-511) HOW TO -------------------------------------------------------------------------------- + How to enable debug messages By default, debug messages get disabled at the end of kernel initialization. The rationale for disabling the debug messages is to avoid conflicts between the debug messages and the user-level UART driver as they use the same physical UART port. In order to enable the debug messages, select the OMAP35X SOM-LV Debug serial option found in the following catalog path: Third Party\BSP\LOGIC LV-SOM OMAP35x BSP\Device Drivers\Serial\UART\UART1 When the debug serial option is enabled, the use of the COM1 UART driver will not be available. The other serial ports are available when receiving debug messages through the debug serial port. NOTE: The recommended method for debug is using KITL. + How to enable KITL - Open Project > LOGIC_SOM_OMAP35x_SHOW properties window - Select active configuration from drop-down menu - Under Configuration Properties > Build Options - check "Enable Kernel debugger" - check "Enable KITL" - Under Configuration Properties > Environment - set environment variable "bsp_share_eth" to 1 + How to disable KITL - Open Project > LOGIC_SOM_OMAP35x_SHOW properties window - Select active configuration from drop-down menu - Under Configuration Properties > Build Options - uncheck "Enable Kernel debugger" - uncheck "Enable KITL" - Under Configuration Properties > Environment - set environment variable "bsp_share_eth" to 0 + How to shorten the delay between removing a storage device and seeing the icon disappear in Explorer window - Adjust the following registry entries in platform.reg. The values shown here are recommended values only. [HKEY_LOCAL_MACHINE\System\StorageManager] "PNPUnloadDelay"=dword:3E8 ; 0.5s - default: dword:1000 (4096ms) "PNPWaitIODelay"=dword:1F4 ; 1.0s - default: dword:1000 (4096ms) + How to set hive registry - The OS Designs included in this BSP use RAM registry. The hive registry component can be selected for custom development. Along with switching to the hive registry component (requires a Rebuild Solution, a.k.a Clean Sysgen), select where the hive is placed using the variables below. - Hive-based registry can be set using BSP Variables. The default variable set is 'BSP_HIVE_YAFFS=1',which will set the proper registry entries for placing the hive on the YAFFS partition in NAND. For use on a memory-mode CF card, set 'BSP_HIVE_ATAMEMCF=1' in LOGIC_SOM_OMAP35x_SHOW.bat and set 'BSP_HIVE_YAFFS='. For use on an SD card, set 'BSP_HIVE_SDHC=1' and the others to nothing. YAFFS HIVE (default if Hive used) In LOGIC_SOM_OMAP35x_SHOW.bat set BSP_HIVE_YAFFS=1 set BSP_HIVE_SDHC= set BSP_HIVE_ATAMEMCF= SD CARD HIVE In LOGIC_SOM_OMAP35x_SHOW.bat set BSP_HIVE_YAFFS= set BSP_HIVE_SDHC=1 set BSP_HIVE_ATAMEMCF= CF CARD HIVE In LOGIC_SOM_OMAP35x_SHOW.bat set BSP_HIVE_YAFFS= set BSP_HIVE_SDHC= set BSP_HIVE_ATAMEMCF=1 - Perform a Rebuild Solution (a.k.a Clean Sysgen) when changing between RAM-based and Hive-based registries. - Refer to Logic PD's "Using a Hive Registry" white paper for more information on Hive Registry at: http://support.logicpd.com/downloads/381/ + How to build when changing between platforms (Torpedo SOM vs SOM-LV) - The BSP can support two platforms: OMAP35x Torpedo SOM or OMAP35x SOM-LV. The platform can be selected in Catalog Items View > Third Party > BSP > LOGIC_SOM_OMAP35x: ARM4VI > Platform Support (choose one) > OMAP35X SOM-LV or OMAP35X Torpedo. - Note that changing the platform requires a Clean Sysgen. This can be accomplished using one of the following options: - Solution Explorer > LOGIC_SOM_OMAP35X_SHOW > C:/WINCE600 > Platform > LOGIC_SOM_OMAP35x_SHOW (right-mouse-click menu) > Rebuild - Menu > Build > Rebuild Solution - Menu > Build > Advance Build Commands > Clean Sysgen - Menu > Build > Advance Build Commands > Rebuild Current BSP and Subprojects + How to suspend/resume OMAP35x Torpedo SOM - When selecting to suspend/resume from Windows CE, the display may return a white screen, rather than the Windows CE desktop. Using the hardware sysboot0 button more than once will restore the Windows CE screen. Based on limited testing, it has been noticed that once the screen is restored, subsequent Windows CE suspend/resume or hardware sysboot0 instances work. REVISION HISTORY -------------------------------------------------------------------------------- + Version 2.0.0 - 08/12/2010 + Version 2.0.1 - 10/07/2010 - Updated the NK.bin images (for both OMAP35x SOM-LV and Torpedo) to include playing a Logic PD startup video (Jira # OMAP3WCE600-381) - Updated BSP Revision to 2.0.1 (Jira # OMAP3WCE600-418) - Added SMSC USB 3320 Host Driver for OMAP35x-11 SOM-LV (Jira # OMAP3WCE600-291) - Resolved an issue related to the USB OTG driver, which crashed the system, generating a 'Data Abort' message. The error was observed upon resuming the system, even though it was generated while suspending the system. (Jira # OMAP3WCE600-378) - Update YAFFS driver to support MLC NAND flash and 4-bit ECC for the OMAP35x-11 SOM-LV and OMAP35x-21 Torpedo SOM (Jira # OMAP3WCE600-320) Background: The OMAP35x-11 SOM-LV and OMAP35x-21 Torpedo hardware can be ordered with a 4 GB Micron NAND flash device. Unlike prior NAND flash, this device requires 4 bits of ECC to maintain the same level of data integrity as previous 1-bit ECC NAND flash devices. NAND flash requiring 4 and 8 bits of ECC correction has become more common with all NAND flash manufacturers. The YAFFS file system tracks how often each block has required ECC correction using a "strike count." When this strike count reaches three, YAFFS marks the block bad, not to be used again. This strike count is maintained in RAM, and the count is reset after any power cycle. Issue: The 4 GB Micron NAND flash device is more susceptible to ECC correction due to the fact that the device requires 4-bit ECC correction instead of the legacy 1-bit ECC NAND flash devices. Because of this, YAFFS will increment the strike count much faster on 4-bit ECC NAND flash devices than on 1-bit ECC NAND flash devices. This results in YAFFS marking blocks as bad at a much higher rate for 4-bit ECC devices than 1-bit ECC devices. It should be noted that YAFFS continues to maintain data integrity. But with prolonged use, the number of blocks available to use for data storage will drop prematurely over the lifetime of the device. Solution: Until YAFFS developers update the YAFFS file system to manage the life expectancy of 4-bit ECC NAND flash devices, Logic PD has devised a work around that can be used to help mitigate the premature retirement of NAND flash blocks. This work around is to allow the user to adjust the strike count limit. Where YAFFS has a fixed value of three strikes causing a block to be marked bad, a user can now modify this limit to any value from 0 (no blocks are retired) to 255. The strike count threshold is made configurable using a registry entry shown below. [HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\YAFFS] "StrikeCount"=dword:80 The "StrikeCount" entry is valid only for the 4 GB Micron NAND parts with 4-bit hardware ECC correction. It has no effect on other NAND brands supported on OMAP35x SOMs. - USB 3320 USB Host Driver does not support Suspend/Resume (Jira # OMAP3WCE600-322) (OMAP3WCE600-423) - Validated USB-RS232 Support (Jira # OMAP3WCE600-395) A patch from TI was included in this release to address an issue that was encountered when using USB-RS232 dongles on the OTG port. This issue can be easily recognized by the inability to receive data at the application level from a USB-RS232 dongle attached to the OTG port. This is caused by a failure of the RX endpoint to be properly setup in the enumeration process. There is a complication in that the issue recorded by TI and the issue reported by Logic PD have different symptoms but the same root cause. More information about this issue can be found in TI's bug tracking database, issue ID SDOCM00069457. This issue can be found at: https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDO- Web&contextid=SDOWP&queryID=34371711&rmsessionid=77dc0f1f-805d-4f59-be30-c0a8f08f4205 After the patch was integrated into the 2.0.1 release it was tested with an FTDI based USB-RS232 dongle connected to the OTG port. CDC Support is not included in the 2.0.1 BSP release, but the required DLL and registry entries to use FTDI USB-RS232 dongles can be downloaded at: http://www.ftdichip.com/Drivers/VCP/WinCE/CE60/ARMv4VCPDriver60.zip - Resolved a problem with the USB OTG driver which prevented devices from being enumerated when already inserted prior to POR (power-on-reset). (Jira # OMAP3WCE600-389) (Jira # OMAP3WCE600-352) (Jira # OMAP3WCE600-102) - Board 1016383 sometimes reboots with a white screen (OMAP3WCE600-435) - Transmitting 8 bytes or more over I2C may cause the system to slow down. (OMAP3WCE600-325) + Version 2.1.0 - 01/15/2011 - OMAP35x Torpedo SOM cannot copy a file from the device to an SD card. (Jira # OMAP3WCE600-362) - USB OTG Host Unpowered Hub + 2 MSDs is not functional. (Jira # OMAP3WCE600-342) - LAN Shared Ethernet is not available. (Jira # OMAP3WCE600-298) - Using Shared Ethernet for KITL breaks normal Ethernet accesses. (Jira # OMAP3WCE600-466) - The display driver shall include a method of skipping display initialization, if already initialized. (Jira # OMAP3WCE600-463) - Issue with wired Ethernet after suspend. (Jira # OMAP3WCE600-315) - Enable Dynamic Voltage and Frequency Scaling (DVFS). (Jira # OMAP3WCE600-296) - The audio volume on -11 boards is reduced, rather than muted. (Jira # OMAP3WCE600-442) + Version 2.1.1 - 02/27/2012 - RTC Date and Time errors with BSP 2.0.1 and BSP 2.1.0. (Jira # OMAP3WCE600-532) - USB OTG Compliance Failure, USB Endpoint Halt Test. (Jira # OMAP3WCE600-533) - OMAP35x Torpedo SOM suspend button (S3) no longer works. (Jira # OMAP3WCE600-379) - Added IOCTLs to the "YAF" stream interface in the YAFFS driver. (Jira # OMAP3WCE600-545) REVISION INFORMATION -------------------------------------------------------------------------------- This is current SVN information for the SRS: $Rev:: 27109 $: Revision of last commit $Author:: stacey.obrien $: Author of last commit $Date:: 2012-03-14 14:59:19 -050#$: Date of last commit -------------------------------------------------------------------------------- Copyright (c) 2012 Logic PD, Inc. www.logicpd.com