----------------------------------------------------------------------------- - - iMX31-10 SOM-LV Development Image Release Notes [ "Dev Image" ] - - Copyright (c) 2007 Logic Product Development - ----------------------------------------------------------------------------- ============================================================================= This WindowsCE image is a RAM image built for use on the iMX31-10 SOM-LV platform. This image has not been subjected to extensive testing and the user may note other issues that are not listed here. Please feel free to use the technical discussion group at http://www.logicpd.com/support/ to post your observations and to share information with other developers. ============================================================================= ----------------------------------------------------------------------------- * Table of Contents * (0) What is the purpose of this image (1) What standard components are included in the image (2) What custom BSP components are included in the image (3) Known Issues (4) FAQ [Custom displays, touch cabliration, registry sync, .etc] ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- (0) What is the purpose of this image ----------------------------------------------------------------------------- This image ("dev image") is provided, with workspace, to be a starting point for developers with our BSP. It has been built with released BSP components available on our website. (In comparison, the Sample Development Image may be built with unreleased components, this will be refered to as "sample image") It is expected that the user should be able to build this same binary file using the provided worksapce. There are some exceptions to this, as the user may not have all updated QFE updates from Microsoft installed, which can affect how the final compiled image works and performs. Very few 'extra' features are provided in this image, only items that a user would need for writing a application and testing on it. It does not contain Internet Explorer, Windows Media Player, games, or image viewers. If those items are needed, please look for the sample image provided on our website. ----------------------------------------------------------------------------- (1) What standard components are included in the image ----------------------------------------------------------------------------- Display Based Device Features Included (but not limited to) in Image --) Applications - End User - Activesync - WordPad --) Applications and Services Development - .NET Compact Framework 1.0 - .NET Compact Framework 2.0 - C Libraries and Runtimes - Microsoft Foundation Classes - Standard SDK for Windows CE .NET - XML - SOAP - COM --) Core OS Services - USB Host Support (Mouse & Keyboard [HID], printer, storage, remote NDIS) - Serial Port Support --) Communication Services and Networking - Wired Local Area Network ( 802.11 ) - Wireless LAN ( 802.3, 802.5 ) - Dial Up Networking ( RAS/PPP ) - Telephony API ( TAPI 2.0 ) - TCP/IP - Network Utilities (IpConfig, Ping, Route) --) File Systems and Data Store - Bit-Based - RAM-based Registry Note: See information below about registry persistence - RAM and ROM File System - Storage Manager - FAT file system --) Graphics and Multimedia Technologies - Waveform Audio --) Shell and User Interface - Command Shell (Command Processor and Console Window) - Standard Shell - Mouse - Network User Interface - Software Input Panel - Touch Display (Stylus) ----------------------------------------------------------------------------- (2) What custom BSP components are included in the image ----------------------------------------------------------------------------- Kernel Support in the Image --) Kernel lpd_kernel_imx31_50_2_1_9_0 Device Drivers in the Image --) Power Managmenet IC lpd_imx31_mc13783_imx31_50_1_0_0 --) Display Driver lpd_imx31_ipu_imx31_50_1_0_0 --) Touch lpd_imx31_touch_imx31_50_1_0_0 --) USB Funciton lpd_imx31_usbf_imx31_50_1_1_0 --) USB Host lpd_imx31_usb2h_imx31_50_1_0_0 --) Serial (UART) lpd_imx31_uart_imx31_50_1_0_0 --) Audio lpd_imx31_audio_imx31_50_1_0_0 --) SD Host Controller lpd_imx31_sdhc_imx31_50_1_0_0 --) Floating Point lpd_imx31_vfp_imx31_50_1_0_0 --) NAND Flash File System lpd_yaffs_nand_imx31_50_1_4_4 --) Ethernet lpd_smsc_lan911x_imx31_50_0_5_0 --) CF (PCMCIA) lpd_imx31_pcmcia_imx31_50_1_0_0 ----------------------------------------------------------------------------- (3) Known Issues ----------------------------------------------------------------------------- - *Should be used with LogicLoader 2.4.0. If using an earlier version of LogicLoader, please be sure to see iMX31 PCN regarding USB Transceiver (PHY) changes. For LogicLoader 2.3.5p2 and earlier, you must set run this in LogicLoader before booting to WinCE: w /w 0x43FAC008 0x00000000 - The PMIC RTC has an issue when December 31 tries to roll over to Jan 1. - Touch calibration off for early release kits. - If 'coproc:00f00000:' is not included in your boot script, VFP driver will lock up system ----------------------------------------------------------------------------- (4) FAQ ----------------------------------------------------------------------------- Q: How can I build this same NK.bin? A: The .pbxml file provided is the workspace we used with Platform Builder to create this binary. If you would like to build your own, you can create a folder in 'D:\WINCE500\PBWorkspaces\' called 'dev_image_imx31', place this .pbxml file there and then open it with Platform Builder 5.0. You must have installed Logic's latest BSP components prior to opening this workspace. Q: Does this image use the onboard NAND Flash? A: Yes, Logic's YAFFS File System driver is included and uses Blocks 1 through 4096 for one large partition called '/YaffsPart1'. Partition Name: YaffsPart1 Partition Size: 16 KB * 4095 Blocks = ~63 MB Note: Recomendation to note change the partition name and block size via the registry. This image has components that expect /YaffsPart1 to exist as stated above. Note: To access the same YAFFS partition in LogicLoader, you can use the following commands at the 'losh>' prompt. Please read up on LogicLoader YAFFS use in the LogicLoader manual. losh> add-yaffs YaffsPart1 nand B1 B4095; mount yaffs /YaffsPart1; Q: How do I use a custom display? A: Use LogicLoader to set up the display and use 'skiplcdcinit:1:' in the boot string, along with a display mode, e.g. if it was a 320x240 display, choose mode 3 (disp_num:3:skiplcdcinit:1). Note: The display driver will automatically detect the width and height of the settings in the LCD (IPU) controller. Custom displays that do not match a default display mode are ok to use because of this feature. Q: What are the supported display modes for this revision of the sample image? A: 5 - LCD-5.7-VGA-10 (Logic 5.7" Display Kit 320x240) 2 - LCD-12.1-VGA-10 (Logic 12.1" Display Kit 800x600) 3 - LCD-3.6-QVGA-10 (Logic 3.6" Display Kit 320x240) 5 - LCD-6.4-VGA-10 (Logic 6.4" Display Kit 640x480) 7 - LCD-10.4-VGA-10 (Logic 10.4" Display Kit 640x480) 8 - LCD-3.5-VGA-20 (Logic 6.4" Display Kit 240x320) Q: How do I connect to KITL? A: Use the included LogicLoader script "generic_kitl_ram_boot_script.losh" and enter your display number at the end of it. The lpd_smsc_lan911x driver will not load if KITL is used. Q: Is the registry persisted? A: No, this sample image does not provide persistant registry. This is meant for a starting point for testing applications and for building a workspace. Q: I'd like to run the Touch Calibration at boot time, but I can not get to the utility in the control panel. A: Use a USB Mouse to find and open the touch calibration utility from the control panel. Q: I'm using a pre-release beta kit (please see the following PCN for information) and the touch is swapped creating an unusable touch interface, what can I do to correct this? A: If you run the touch calibration, it may work as is. If you have our BSP, you'll want to change the touch driver's registry file to support this early kit. Change: HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch SwapXY dword 0 To: HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch SwapXY dword 1 Q: Does this image allow use of the iMX31's floating point unit (VFP)? A: Yes. Be sure to include 'coproc:00f00000:' in the boot string, which enables this floating point unit. Q: I'd like to automatically launch my application when Windows CE boots, is this possible? A: Not with this image as is. This can be added to a custom NK.bin you build. Please search Microsoft's help for instructions on how to automatically launch an application. The "Sample Image" on our website includes support for launching an app at boot, if you need to do a demo. Q: Is there Real Time Clock support? A: Yes, the kernel supports both the RTC internal to the iMX31 processor and in the Atlas Power Management IC (PMIC). The provided boot strings contain the entry (rtc:rtc_imx31_pmic:)to enable the Kernel to use the PMIC's RTC, which can be preserved through reset of the system. Since no battery is provided on the kit, it will not however hold the RTC contents through a power cycle. -----------------------------------------------------------------------------