This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
We are pleased to annouce that Adeneo Embedded released a Windows Embedded Compact 2013 BSP for the AM335x Starter Kit board embedding TI's ARM Cortex A8 based Sitara AM335x microprocessor. This BSP leverages the first availability of the WEC2013 BSP for Texas Instruments ARM Cortex A8 MPUs and is available for download directly from Adeneo Embedded's website : www.adeneo-embedded.com
Adeneo Embedded Support team Contact us at sales@adeneo-embedded.com
Hi,
I got the BSP as a sample BSP with the installation of WEC2013. Default it support WEC2013 OMAP4470 platform.
Source code seems like it support WEC7 too. Is it support OMAP 4430 platform on WEC7.
To make it work on WEC7 OMAP4430 what we want to do???
Thanks and Regards
1 Introduction
1.1 Purpose
This document is a general “How To” step by step guide for working with the TI_SDP44XX and Blaze platforms and Windows CE BSP. Hardware setup, build steps, bootloader flashing, OS flashing and other helpful information are provided.
1.2 Scope
|
Platform: |
Blaze SEVM4430G-00-40-00 (OMAP4430 ES2.3) (OMAP4470 ES1.0) Tablet2 TEVM4430G-05-10-00 (OMAP4470 ES1.0) SDP4430 (deprecated)
|
|
Software: |
Windows CE (Embedded Compact) |
|
OS Image: |
CEBASE |
|
BSP: |
|
1.3 File Name
The file name of this document is HOWTO_Setup_TI_SDP44XX_EmbeddedCompact.docx.
2 Hardware Setup
Unpack the TI_SDP44XX box and it up in the following manner:
1) Connect the power supply to the TI_SDP44XX board at the “Battery Simulator” connector.
2) Connect USB cable to jack J2 (Debug USART) on main board.
3) Connect an Ethernet cable to jack J5 on main board.
4) Connect HDMI cable to mini HDMI jack on processor board (optional).
5) Power is controlled by the “Batt Power” switch on the main board.
Unpack the Blaze box and it up in the following manner:
1) Connect the power supply to the Blaze board at the Power/Charger Connector.
2) Connect USB cable to USART Terminal (mini-AB).
3) Connect an Ethernet cable to ENET DEBUG jack.
4) Connect HDMI cable to mini HDMI jack on processor board (optional).
5) There is no power toggle switch on the Blaze, so it is recommended to use a power strip for toggling main DC power on and off. The thin power connector can break with repeated plug insertion and removal.
6) Note that UART Configuration DIPSW is indicated incorrectly as S6 in the Blaze Quick Start Guide. This HowTo will refer to this DIPSW as S3 as printed on the main board.
See the release notes for the BSP for the latest on supported hardware and known hardware issues.
3 Virtual Serial Port Driver Setup
1) Power on the TI_SDP44XX/Blaze with the Debug USART USB cable connected to your PC
2) A notification is seen on the Windows PC for new hardware detected (USB Serial Converter A)
3) Follow on-screen instructions and select to install driver “this time only”
4) Windows XP® has the driver by default so, select “Install the software automatically (Recommended)”
5) Let the software be searched, found and installed. Then select Finish.
6) Open the Device Manager and right-click on “USB Serial Converter A”.
7) Select Properties à Advanced Tabà Load VCP
8) Click on Ok to close.
9) Power cycle the TI_SDP44XX/Blaze
10) Now you should see new device detected – “USB Serial port”.
11) Follow on-screen instructions and select to install driver “This time only”
12) Windows XP® has the driver by default so, select “Install the software automatically (Recommended)”
13) Let the software be searched, found and installed. Then select Finish.
14) 4 COM ports are now added in the Device Manager à Com Ports section. (ex. COM9, COM10, COM11, COM12). Use the third USB serial port created.
15) You may have to reboot sometimes to finish the installation (not always required)
4 Building Bootloader and OS Images
4.1 Build Bootloader and CEBASE (Minkern) Images
To build the bootloader and CEBASE image using the TI_SDP44XX BSP:
1) Install Windows CE (Embedded Compact)
2) Copy the folder TI_SDP44XX to the adaptation kit’s platform directory
3) For IMG DDK support:
4) Open a command window and run the following batch file
For Embedded Compact 7 Update 3, Blaze OMAP4470 -
TI_SDP44XX\BATCHFILES\CE7_4470_Retail.bat
For Embedded Compact 7 Update 3, Blaze OMAP4430 -
TI_SDP44XX\BATCHFILES\CE7_4430_Retail.bat
For Embedded Compact 8 (Canby), Blaze OMAP4470 -
TI_SDP44XX\BATCHFILES\CE8_4470_Retail.bat
For Embedded Compact 8 (Canby), Tablet2 OMAP4470 -
TI_SDP44XX\BATCHFILES\CE8_4470_Retail.bat
set BSP_TABLET_PLATFORM=1
set BSP_TOUCH_STREAM=1
5) Within the same command window, run the following command:
Blddemo clean –q
The release directory will contain the following files:
MLO SD Card XLDR image
xldremmc.img eMMC XLDR image
ebootsd.raw SD Card EBOOT image
eboot.bin eMMC EBOOT image
NK.bin RAM based OS image
boot.cfg SD Card boot configuration file
4.2 Build Environment Variables
The following are environment variables that can control build options. In general, build environment variables in Windows CE follow these conventions:
IMGxxxx Changing these variables only requires a makeimg
BSP_xxx Requires a build of the BSP followed by makeimg
SYSGEN_xxx Requires a full blddemo clean –q
Anything else Same as BSP_xxx
Most build environment variables are either not set (eg. set IMGFLASH= ) to disable the feature or are set to 1 (eg. set IMGFLASH=1) to enable.
Environment variables used by the TI_SDP44XX BSP:
BSP_NOxxx Disable the particular driver/feature in the BSP
IMGMPENABLE Enables SMP when set
BSP_OMAP44XX 4470 (Default - Builds for OMAP4470 ES1.0)
4430 (Builds for OMAP4430 ES2.3)
BSP_TABLET_PLATFORM Enable build for Tablet2 platform
BSP_TOUCH_STREAM Enable build for Tablet2 platform
The SYSGEN variables that were used to create the CEBASE image are listed in the TI_MM_DEMO.bat in TI_SDP44XX\BUILDSCRIPTS.
5 Flashing Bootloader and OS Images
5.1 Bootloader and OS image on SD Card
1) Install SP27213.exe (HP USB disk storage format tool) on your desktop
(http://en.kioskea.net/download/download-127-hp-usb-disk-storage-format-tool)
2) Insert SD card into your desktop’s card reader.
3) Run HP format tool and format the SD card: Use the following configuration: FAT32, uncheck Quick Format and Create a DOS startup disk.
4) From build release directory, copy the files: MLO, EBOOTSD.raw, eboot.bin, xldremmc.img, boot.cfg, and NK.bin to the formatted SD card. Be sure to copy the MLO file first to ensure that it is located as one of the first items in the FAT table.
Note: EBOOT works with SD or SDHC cards.
5.2 Bootloader and OS image on eMMC module (Blaze/Tablet2)
EBOOT supports flashing eMMC module’s xloader, EBOOT, and OS images. Copies of the eMMC images (xldremmc.img, eboot.bin, and nk.bin) should first be copied to the SD card. EBOOT also supports clearing the beginning of the data partition used by OS file system. Clearing the start of the data partition affectively clears the file allocation table causing OS to reformat the file system.
To access the eMMC utilities, select “eMMC Utilities” option from the EBOOT main menu.
6 Running OS Images
6.1 Selecting bootloader storage media (SDP44XX)
The bootloader and image can be on either SD card or eMMC module.
To select SD card as the boot media, set the DIP switches as follows: (white box denotes position of switch):
|
|
S9 |
|
S8 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
To select eMMC module as the boot media, set the DIP switches as follows:
|
|
S9 |
|
S8 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
6.2 Selecting bootloader storage media (Blaze)
The bootloader and image can be on either SD card or eMMC module.
To select SD card as the boot media, set the DIP switches as follows: (white box denotes position of switch):
|
|
S3 |
|
S2 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
To select eMMC module as the boot media, set the DIP switches as follows:
|
|
S3 |
|
S2 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
6.3 Selecting bootloader storage media (Tablet2)
The bootloader and image can be on either SD card or eMMC module.
To select SD card as the boot media, set the DIP switches as follows: (white box denotes position of switch):
|
|
S2 |
|
|
|
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
To select eMMC module as the boot media, set the DIP switches as follows:
|
|
S3 |
|
S2 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
6.4 Run Minkern Image in RAM
The bootloader will load and run with the following settings in Eboot:
Main:
Boot device: NK from MMC
Debug device: KSZ8851 Ethernet
Device ID: 0
Network:
KITL state: enabled
KITL type: active
KITL mode: interrupt
DHCP: enabled
IP address: 192.168.2.1
IP mask: 255.255.255.0
IP router: 0.0.0.0
VMINI: disabled
Press 0 from the Eboot Main Menu to boot the NK.bin OS image that is on the SD card.
See the following section for KITL debugging connections.
7 KITL Debugging
In order to use either USB serial or USB RNDIS KITL, prior to powering on the TI_SDP44XX board remove the SD card with xloader and eboot loader binaries from the SD slot. Then, power on the board and wait approximately 3 seconds before inserting the SD card. This allows OMAP4430 boot ROM to initialize USB modules.
7.1 USB SERIAL KITL
Using USB SERIAL to perform image downloads and KITL debugging requires the configuration of both the mobile device and the host PC. Configuration of the host PC requires either Windows XP or Windows 2000. This is the USB ActiveSync type download supported in Platform Builder.
Mobile Device Setup
1) Connect device USB port (HS-USB1 on TI_SDP44XX ; OMAP USB U97 on Blaze) to PC USB port.
2) Start TeraTerm program on PC, and configure the following, 38400 baud, 8 data bits, no parity, 1 stop bit, and no flow control. TeraTerm can be downloaded from http://ttssh2.sourceforge.jp. From testing, TeraTerm works more reliably with TI_SDP44XX than HyperTerminal.
3) Power on device and press space to enter the configuration menu.
4) Configure the device to download a new image via USB SERIAL. In the main menu, press 2 to select “[2] Select Boot Device”. Then press 2 again to select “[2] USB SERIAL”.
5) Configure the device to connect to Platform Builder using KITL via USB SERIAL. In the main menu, press 3 to select “[3] Select Debug Device”. Then press 2 again to select “[2] USB SERIAL”.
6) Press [0] at the main menu to start download image to the device.
Host PC Setup
1) Open ActiveSync and in “Connection Settings” window make sure “Allow USB connections” is not selected.
2) Start Platform Builder, You should be able to use USB connection for image down load. Please note that you should select USB for your download and USB as transport medium.
3) Use “Attach Device” to attach Platform Builder to connect to device. Now the device will start booting. Note that it is not required to reboot the device.
7.2 RNDIS KITL
Using USB RNDIS to perform image downloads and KITL debugging requires the configuration of both the mobile device and the host PC. The mobile device setup will require a serial cable connection and a terminal program running on the PC. Configuration of the host PC requires either Windows XP or Windows 2000 with additional RNDIS USB support, and a basic knowledge of how to configure network connections. Note: USB RNDIS KITL has not been tested extensively
Mobile Device Setup
1) Connect device USB port (HS-USB1 on TI_SDP44XX ; OMAP USB U97 on Blaze) to PC USB port.
2) Start terminal program on PC, and configure the following, 38400 baud, 8 data bits, no parity, 1 stop bit, and no flow control.
3) Power on device and press space to enter the configuration menu.
4) Configure the device to download a new image via USB RNDIS. In the main menu, press 2 to select “[2] Select Boot Device”. Then press 3 again to select “[3] USB RNDIS”.
5) Configure the device to connect to Platform Builder using KITL via USB RNDIS. In the main menu, press 3 to select “[3] Select Debug Device”. Then press 3 again to select “[3] USB RNDIS”.
6) Configure the device’s networking settings. Press 4 at the main menu to select “[4] Network Settings”. From the Network Setting menu, press 5 to select “[5] Enable/disable DHCP”. Press “Y” to disable DHCP. Then press 6 to select “[6] Set IP address”. The device’s IP address should be set to 192.168.254.10, or some other similar private IP address. Press 7 to select “[7] Set IP mask”. The IP mask should be set to 255.255.255.0, in this case. Now press [0] to return to the main menu.
7) Press [0] to continue the boot process on the device.
Host PC Setup
1) The PC should now detect a new USB device. When prompted, select to “Install from a list or specific location (Advanced)”. Click “Next” to continue. Select the following directory WINCE700\platform\common\src\common\kitldrv\usbdbg\usbdbgrndismdd\host and click “OK”. Should a warning screen appears stating that the driver is not signed, just click “Continue anyway”. If you are prompted for a missing file (usb8023.sys), search in the WINDOWS\system32\drivers directory. When the installation has finished, you may be asked to restart your computer. Please restart if necessary.
2) At this point it is likely that the device has timed-out and you will not be able to see the newly created network interface. If this occurs, please restart the device.
3) Once the driver has been successfully installed, there will be a new network interface under your PC’s Network Configurations. Select Network Connections from the Control Panel to view all of your connections. The device will be named Microsoft Windows CE RNDIS virtual adapter. Right click on the RNDIS adapter and select “Properties”. Scroll down and double-click “Internet Protocol (TCP/IP)”. Select “Use the following IP address:” and set the IP address and Subnet mask to 192.168.254.1 and 255.255.255.0 respectively, or another private IP address and mask on the same subnet as the device. Make sure the PC adapter’s IP address is NOT the same as that of the device, but that they are on the same subnet.
4) Start Platform Builder, you should now be able to use the USB RNDIS connection as a normal Ethernet connection for image download and KITL connectivity. Please note that you should select Ethernet as both your download and transport medium. Do NOT select USB
7.3 Ethernet KITL
1) Power on device and press space to enter the configuration menu.
2) Follow the instructions in section 7.4 for associating PB with the TI_SDP44XX for KITL debugging.
3) Configure the device to download a new image via SD/MMC. In the main menu, press 2 to select “[2] Select Boot Device”. Then press 5 to select “[5] NK from MMC”.
4) Configure the device to connect to Platform Builder using KITL via Ethernet. In the main menu, press 3 to select “[3] Select Debug Device”. Then press 1 to select “[1] KSZ8851 Ethernet”.
5) Press [0] at the main menu to start loading image from MMC. There will be a stall of about 10 seconds after the image jumps into the kernel. This is normal as a DHCP address is being obtained for the TI_SDP44XX.
6) If the association between PB and the TI_SDP44XX is established correctly, KITL will connect to the device.
7.4 Associating PB with the TI_SDP44XX for KITL debugging:
The following steps are used to associate Platform Builder with your TI_SDP44XX:
1) Start Platform Builder for CE and open the OS image file NK.bin (FileàOpen… Project/Solution…)
2) Start serial terminal program
3) Power on TI_SDP44XX to start the bootloader.
4) Press the spacebar to break into the bootloader main menu.
5) In Platform Builder, go to ‘TargetàConnectivity Options.’ Select “Add Device” and provide a name for your TI_SDP44XX board (e.g. TI_SDP44XX #XXX)
6) Press the Settings button next to the Download drop menu.
7) In the bootloader menu, select [0] to Exit and Continue which will start the BOOTME requests. Select your TI_SDP44XX board from the Active Devices list (the device name of the TI_SDP44XX is displayed by the bootloader in the terminal emulator window)
8) Select OK to close this window and Apply then Close to close the “Connectivity Options” window.
9) Start the download of the image by selecting Target -> Attach Device in Platform Builder
10) The image will download and launch the OS image then connect via KITL to Platform Builder for debugging.
1 Introduction
1.1 Purpose
This document is a general “How To” step by step guide for working with the TI_SDP44XX and Blaze platforms and Windows CE BSP. Hardware setup, build steps, bootloader flashing, OS flashing and other helpful information are provided.
1.2 Scope
|
Platform: |
Blaze SEVM4430G-00-40-00 (OMAP4430 ES2.3) (OMAP4470 ES1.0) Tablet2 TEVM4430G-05-10-00 (OMAP4470 ES1.0) SDP4430 (deprecated)
|
|
Software: |
Windows CE (Embedded Compact) |
|
OS Image: |
CEBASE |
|
BSP: |
|
1.3 File Name
The file name of this document is HOWTO_Setup_TI_SDP44XX_EmbeddedCompact.docx.
2 Hardware Setup
Unpack the TI_SDP44XX box and it up in the following manner:
1) Connect the power supply to the TI_SDP44XX board at the “Battery Simulator” connector.
2) Connect USB cable to jack J2 (Debug USART) on main board.
3) Connect an Ethernet cable to jack J5 on main board.
4) Connect HDMI cable to mini HDMI jack on processor board (optional).
5) Power is controlled by the “Batt Power” switch on the main board.
Unpack the Blaze box and it up in the following manner:
1) Connect the power supply to the Blaze board at the Power/Charger Connector.
2) Connect USB cable to USART Terminal (mini-AB).
3) Connect an Ethernet cable to ENET DEBUG jack.
4) Connect HDMI cable to mini HDMI jack on processor board (optional).
5) There is no power toggle switch on the Blaze, so it is recommended to use a power strip for toggling main DC power on and off. The thin power connector can break with repeated plug insertion and removal.
6) Note that UART Configuration DIPSW is indicated incorrectly as S6 in the Blaze Quick Start Guide. This HowTo will refer to this DIPSW as S3 as printed on the main board.
See the release notes for the BSP for the latest on supported hardware and known hardware issues.
3 Virtual Serial Port Driver Setup
1) Power on the TI_SDP44XX/Blaze with the Debug USART USB cable connected to your PC
2) A notification is seen on the Windows PC for new hardware detected (USB Serial Converter A)
3) Follow on-screen instructions and select to install driver “this time only”
4) Windows XP® has the driver by default so, select “Install the software automatically (Recommended)”
5) Let the software be searched, found and installed. Then select Finish.
6) Open the Device Manager and right-click on “USB Serial Converter A”.
7) Select Properties à Advanced Tabà Load VCP
8) Click on Ok to close.
9) Power cycle the TI_SDP44XX/Blaze
10) Now you should see new device detected – “USB Serial port”.
11) Follow on-screen instructions and select to install driver “This time only”
12) Windows XP® has the driver by default so, select “Install the software automatically (Recommended)”
13) Let the software be searched, found and installed. Then select Finish.
14) 4 COM ports are now added in the Device Manager à Com Ports section. (ex. COM9, COM10, COM11, COM12). Use the third USB serial port created.
15) You may have to reboot sometimes to finish the installation (not always required)
4 Building Bootloader and OS Images
4.1 Build Bootloader and CEBASE (Minkern) Images
To build the bootloader and CEBASE image using the TI_SDP44XX BSP:
1) Install Windows CE (Embedded Compact)
2) Copy the folder TI_SDP44XX to the adaptation kit’s platform directory
3) For IMG DDK support:
4) Open a command window and run the following batch file
For Embedded Compact 7 Update 3, Blaze OMAP4470 -
TI_SDP44XX\BATCHFILES\CE7_4470_Retail.bat
For Embedded Compact 7 Update 3, Blaze OMAP4430 -
TI_SDP44XX\BATCHFILES\CE7_4430_Retail.bat
For Embedded Compact 8 (Canby), Blaze OMAP4470 -
TI_SDP44XX\BATCHFILES\CE8_4470_Retail.bat
For Embedded Compact 8 (Canby), Tablet2 OMAP4470 -
TI_SDP44XX\BATCHFILES\CE8_4470_Retail.bat
set BSP_TABLET_PLATFORM=1
set BSP_TOUCH_STREAM=1
5) Within the same command window, run the following command:
Blddemo clean –q
The release directory will contain the following files:
MLO SD Card XLDR image
xldremmc.img eMMC XLDR image
ebootsd.raw SD Card EBOOT image
eboot.bin eMMC EBOOT image
NK.bin RAM based OS image
boot.cfg SD Card boot configuration file
4.2 Build Environment Variables
The following are environment variables that can control build options. In general, build environment variables in Windows CE follow these conventions:
IMGxxxx Changing these variables only requires a makeimg
BSP_xxx Requires a build of the BSP followed by makeimg
SYSGEN_xxx Requires a full blddemo clean –q
Anything else Same as BSP_xxx
Most build environment variables are either not set (eg. set IMGFLASH= ) to disable the feature or are set to 1 (eg. set IMGFLASH=1) to enable.
Environment variables used by the TI_SDP44XX BSP:
BSP_NOxxx Disable the particular driver/feature in the BSP
IMGMPENABLE Enables SMP when set
BSP_OMAP44XX 4470 (Default - Builds for OMAP4470 ES1.0)
4430 (Builds for OMAP4430 ES2.3)
BSP_TABLET_PLATFORM Enable build for Tablet2 platform
BSP_TOUCH_STREAM Enable build for Tablet2 platform
The SYSGEN variables that were used to create the CEBASE image are listed in the TI_MM_DEMO.bat in TI_SDP44XX\BUILDSCRIPTS.
5 Flashing Bootloader and OS Images
5.1 Bootloader and OS image on SD Card
1) Install SP27213.exe (HP USB disk storage format tool) on your desktop
(http://en.kioskea.net/download/download-127-hp-usb-disk-storage-format-tool)
2) Insert SD card into your desktop’s card reader.
3) Run HP format tool and format the SD card: Use the following configuration: FAT32, uncheck Quick Format and Create a DOS startup disk.
4) From build release directory, copy the files: MLO, EBOOTSD.raw, eboot.bin, xldremmc.img, boot.cfg, and NK.bin to the formatted SD card. Be sure to copy the MLO file first to ensure that it is located as one of the first items in the FAT table.
Note: EBOOT works with SD or SDHC cards.
5.2 Bootloader and OS image on eMMC module (Blaze/Tablet2)
EBOOT supports flashing eMMC module’s xloader, EBOOT, and OS images. Copies of the eMMC images (xldremmc.img, eboot.bin, and nk.bin) should first be copied to the SD card. EBOOT also supports clearing the beginning of the data partition used by OS file system. Clearing the start of the data partition affectively clears the file allocation table causing OS to reformat the file system.
To access the eMMC utilities, select “eMMC Utilities” option from the EBOOT main menu.
6 Running OS Images
6.1 Selecting bootloader storage media (SDP44XX)
The bootloader and image can be on either SD card or eMMC module.
To select SD card as the boot media, set the DIP switches as follows: (white box denotes position of switch):
|
|
S9 |
|
S8 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
To select eMMC module as the boot media, set the DIP switches as follows:
|
|
S9 |
|
S8 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
6.2 Selecting bootloader storage media (Blaze)
The bootloader and image can be on either SD card or eMMC module.
To select SD card as the boot media, set the DIP switches as follows: (white box denotes position of switch):
|
|
S3 |
|
S2 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
To select eMMC module as the boot media, set the DIP switches as follows:
|
|
S3 |
|
S2 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
6.3 Selecting bootloader storage media (Tablet2)
The bootloader and image can be on either SD card or eMMC module.
To select SD card as the boot media, set the DIP switches as follows: (white box denotes position of switch):
|
|
S2 |
|
|
|
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
To select eMMC module as the boot media, set the DIP switches as follows:
|
|
S3 |
|
S2 |
|
|||||||||||
|
1 |
2 |
3 |
4 |
|
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
6.4 Run Minkern Image in RAM
The bootloader will load and run with the following settings in Eboot:
Main:
Boot device: NK from MMC
Debug device: KSZ8851 Ethernet
Device ID: 0
Network:
KITL state: enabled
KITL type: active
KITL mode: interrupt
DHCP: enabled
IP address: 192.168.2.1
IP mask: 255.255.255.0
IP router: 0.0.0.0
VMINI: disabled
Press 0 from the Eboot Main Menu to boot the NK.bin OS image that is on the SD card.
See the following section for KITL debugging connections.
7 KITL Debugging
In order to use either USB serial or USB RNDIS KITL, prior to powering on the TI_SDP44XX board remove the SD card with xloader and eboot loader binaries from the SD slot. Then, power on the board and wait approximately 3 seconds before inserting the SD card. This allows OMAP4430 boot ROM to initialize USB modules.
7.1 USB SERIAL KITL
Using USB SERIAL to perform image downloads and KITL debugging requires the configuration of both the mobile device and the host PC. Configuration of the host PC requires either Windows XP or Windows 2000. This is the USB ActiveSync type download supported in Platform Builder.
Mobile Device Setup
1) Connect device USB port (HS-USB1 on TI_SDP44XX ; OMAP USB U97 on Blaze) to PC USB port.
2) Start TeraTerm program on PC, and configure the following, 38400 baud, 8 data bits, no parity, 1 stop bit, and no flow control. TeraTerm can be downloaded from http://ttssh2.sourceforge.jp. From testing, TeraTerm works more reliably with TI_SDP44XX than HyperTerminal.
3) Power on device and press space to enter the configuration menu.
4) Configure the device to download a new image via USB SERIAL. In the main menu, press 2 to select “[2] Select Boot Device”. Then press 2 again to select “[2] USB SERIAL”.
5) Configure the device to connect to Platform Builder using KITL via USB SERIAL. In the main menu, press 3 to select “[3] Select Debug Device”. Then press 2 again to select “[2] USB SERIAL”.
6) Press [0] at the main menu to start download image to the device.
Host PC Setup
1) Open ActiveSync and in “Connection Settings” window make sure “Allow USB connections” is not selected.
2) Start Platform Builder, You should be able to use USB connection for image down load. Please note that you should select USB for your download and USB as transport medium.
3) Use “Attach Device” to attach Platform Builder to connect to device. Now the device will start booting. Note that it is not required to reboot the device.
7.2 RNDIS KITL
Using USB RNDIS to perform image downloads and KITL debugging requires the configuration of both the mobile device and the host PC. The mobile device setup will require a serial cable connection and a terminal program running on the PC. Configuration of the host PC requires either Windows XP or Windows 2000 with additional RNDIS USB support, and a basic knowledge of how to configure network connections. Note: USB RNDIS KITL has not been tested extensively
Mobile Device Setup
1) Connect device USB port (HS-USB1 on TI_SDP44XX ; OMAP USB U97 on Blaze) to PC USB port.
2) Start terminal program on PC, and configure the following, 38400 baud, 8 data bits, no parity, 1 stop bit, and no flow control.
3) Power on device and press space to enter the configuration menu.
4) Configure the device to download a new image via USB RNDIS. In the main menu, press 2 to select “[2] Select Boot Device”. Then press 3 again to select “[3] USB RNDIS”.
5) Configure the device to connect to Platform Builder using KITL via USB RNDIS. In the main menu, press 3 to select “[3] Select Debug Device”. Then press 3 again to select “[3] USB RNDIS”.
6) Configure the device’s networking settings. Press 4 at the main menu to select “[4] Network Settings”. From the Network Setting menu, press 5 to select “[5] Enable/disable DHCP”. Press “Y” to disable DHCP. Then press 6 to select “[6] Set IP address”. The device’s IP address should be set to 192.168.254.10, or some other similar private IP address. Press 7 to select “[7] Set IP mask”. The IP mask should be set to 255.255.255.0, in this case. Now press [0] to return to the main menu.
7) Press [0] to continue the boot process on the device.
Host PC Setup
1) The PC should now detect a new USB device. When prompted, select to “Install from a list or specific location (Advanced)”. Click “Next” to continue. Select the following directory WINCE700\platform\common\src\common\kitldrv\usbdbg\usbdbgrndismdd\host and click “OK”. Should a warning screen appears stating that the driver is not signed, just click “Continue anyway”. If you are prompted for a missing file (usb8023.sys), search in the WINDOWS\system32\drivers directory. When the installation has finished, you may be asked to restart your computer. Please restart if necessary.
2) At this point it is likely that the device has timed-out and you will not be able to see the newly created network interface. If this occurs, please restart the device.
3) Once the driver has been successfully installed, there will be a new network interface under your PC’s Network Configurations. Select Network Connections from the Control Panel to view all of your connections. The device will be named Microsoft Windows CE RNDIS virtual adapter. Right click on the RNDIS adapter and select “Properties”. Scroll down and double-click “Internet Protocol (TCP/IP)”. Select “Use the following IP address:” and set the IP address and Subnet mask to 192.168.254.1 and 255.255.255.0 respectively, or another private IP address and mask on the same subnet as the device. Make sure the PC adapter’s IP address is NOT the same as that of the device, but that they are on the same subnet.
4) Start Platform Builder, you should now be able to use the USB RNDIS connection as a normal Ethernet connection for image download and KITL connectivity. Please note that you should select Ethernet as both your download and transport medium. Do NOT select USB
7.3 Ethernet KITL
1) Power on device and press space to enter the configuration menu.
2) Follow the instructions in section 7.4 for associating PB with the TI_SDP44XX for KITL debugging.
3) Configure the device to download a new image via SD/MMC. In the main menu, press 2 to select “[2] Select Boot Device”. Then press 5 to select “[5] NK from MMC”.
4) Configure the device to connect to Platform Builder using KITL via Ethernet. In the main menu, press 3 to select “[3] Select Debug Device”. Then press 1 to select “[1] KSZ8851 Ethernet”.
5) Press [0] at the main menu to start loading image from MMC. There will be a stall of about 10 seconds after the image jumps into the kernel. This is normal as a DHCP address is being obtained for the TI_SDP44XX.
6) If the association between PB and the TI_SDP44XX is established correctly, KITL will connect to the device.
7.4 Associating PB with the TI_SDP44XX for KITL debugging:
The following steps are used to associate Platform Builder with your TI_SDP44XX:
1) Start Platform Builder for CE and open the OS image file NK.bin (FileàOpen… Project/Solution…)
2) Start serial terminal program
3) Power on TI_SDP44XX to start the bootloader.
4) Press the spacebar to break into the bootloader main menu.
5) In Platform Builder, go to ‘TargetàConnectivity Options.’ Select “Add Device” and provide a name for your TI_SDP44XX board (e.g. TI_SDP44XX #XXX)
6) Press the Settings button next to the Download drop menu.
7) In the bootloader menu, select [0] to Exit and Continue which will start the BOOTME requests. Select your TI_SDP44XX board from the Active Devices list (the device name of the TI_SDP44XX is displayed by the bootloader in the terminal emulator window)
8) Select OK to close this window and Apply then Close to close the “Connectivity Options” window.
9) Start the download of the image by selecting Target -> Attach Device in Platform Builder
10) The image will download and launch the OS image then connect via KITL to Platform Builder for debugging.
Hi,
I followed the same procedure as per your reply.
But with the TI-SDP_44xx WEC 2013 BSP image fails to booting from sd card.
I build for OMAP4470 Tablet 2 platform. I didn't change anything and using hp formatting tool.
From Teraterm i choose sd card as booting device and it start to boot from sd card and ON the green lights on switches after showing "Launching WinCE image by jumping to 0x80100000..."
I attaches the tera term logs here,Please suggest any solution for this
Hi adeneo team,
Thanks for replaying..
I download the pre-build binaries that you shared and its booting without any issue through sd card.
When i replaces the NK.Bin from downloaded binaries with mine, its not working...
My batch files are same as that you shared files.
Downloaded Pre-build binaries booting logs is given below..After this i attaches tera term logs with my NK.Bin.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
....................... <> Record [ 303 ] dwRecAddr = 0x83906fd8, ramAddr = 0x82a06fd8, dwRecLen = 0x10a4a4
........ <> Record [ 304 ] dwRecAddr = 0x83a1147c, ramAddr = 0x82b1147c, dwRecLen = 0x15744
<> Record [ 305 ] dwRecAddr = 0x83a26bc0, ramAddr = 0x82b26bc0, dwRecLen = 0x2b0c4
. <> Record [ 306 ] dwRecAddr = 0x83a51c84, ramAddr = 0x82b51c84, dwRecLen = 0x54
<> Record [ 307 ] dwRecAddr = 0x83a51cd8, ramAddr = 0x82b51cd8, dwRecLen = 0x3c80
Setting Launch address = default
+OEMLaunch(0x00000000, 0x00000000, 0x00000000, 0x00000000 - 3/1)
Launch Windows CE image by jumping to 0x80100000...
Windows CE Kernel for ARM (Thumb Enabled)
--- High Performance Frequecy is 32768 khz---
DeviceId................. SDP4470-
pArgs->flags............. 0x2C
pArgs->devLoc.IfcType.... 0
pArgs->devLoc.LogicalLoc. 0x48098000
pArgs->devLoc.PhysicalLoc 0x0
pArgs->devLoc.Pin........ 0
pArgs->ip4address........ 192.168.2.1
pDevice->Name............ K
pDevice->ifcType......... 0
pDevice->id.............. 0x48098000
pDevice->resource........ 0
pDevice->type............ 2
pDevice->pDriver......... 0x83A7A0F0
WARN: OALKitlInit: KITL Disabled
OALEnableSMP(1) AuxCtrl = 0x41
OALEnableSMP: OALVAtoPA(OALSMPStartup)=0x80115201
OALEnableSMP: OALCpuSetIndentityMap returned =0x0
PID:00400002 TID:00570002 OALIoCtlHalInitRTC(): Resetting RTC
PID:00400002 TID:00B60002 +OALIoCtlPrcmSuspend, IOCTL_PRCM_SET_DEFAULT_SYS_PWRSTATE code = 0x1f5206c
PID:00400002 TID:00B60002 frequency=400, floor=0, ceiling=340
PID:00400002 TID:00B60002 frequency=800, floor=340, ceiling=725
PID:00400002 TID:00B60002 frequency=1100, floor=725, ceiling=1020
PID:00400002 TID:00B60002 frequency=1300, floor=1020, ceiling=1220
PID:00400002 TID:00B60002 frequency=1500, floor=1220, ceiling=1500
PID:00400003 TID:01340002 +PMExt_PMBeforeNewSystemState(0x00000001, on, 0x00000000)
PID:00400003 TID:01340002 +PMExt_PMAfterNewSystemState(0x00000001, on, 0x00000000)
PID:00400002 TID:00B60002 +WriteTwlReg failed!!
PID:00400002 TID:00B60002 +WriteTwlReg failed!!
PID:00400002 TID:00B60002 EDISK: Bus handle created
PID:00400002 TID:00B60002 ======== E DISK (SYSTEM) =============================
PID:00400002 TID:00B60002 EDISK: di_bytes_per_sect = 0x200
PID:00400002 TID:00B60002 EDISK: di_cylinders = 0x0
PID:00400002 TID:00B60002 EDISK: di_heads = 0x0
PID:00400002 TID:00B60002 EDISK: di_sectors = 0x0
PID:00400002 TID:00B60002 EDISK: di_flags = 0xb
PID:00400002 TID:00B60002 EDISK: dwStartSect = 0x5a000
PID:00400002 TID:00B60002 EDISK: di_total_sectors = 0x3a6000 (1868MB)
PID:00400002 TID:00B60002 EDISK: dwTotalBlocks = 0x3a6000
PID:00400002 TID:00B60002 ==================================================
PID:00400003 TID:00B60002 EDK_Init: (Skipping init, already done)
PID:00400002 TID:01D60002 FATFS!FormatVolume: Formatting volume. Flags = 0x16.
PID:00400002 TID:00B60002 ======== E DISK (BULK) =============================
PID:00400002 TID:00B60002 EDISK: di_bytes_per_sect = 0x200
PID:00400002 TID:00B60002 EDISK: di_cylinders = 0x0
PID:00400002 TID:00B60002 EDISK: di_heads = 0x0
PID:00400002 TID:00B60002 EDISK: di_sectors = 0x0
PID:00400002 TID:00B60002 EDISK: di_flags = 0xb
PID:00400002 TID:00B60002 EDISK: dwStartSect = 0x400000
PID:00400002 TID:00B60002 EDISK: di_total_sectors = 0x3770000 (28384MB)
PID:00400002 TID:00B60002 EDISK: dwTotalBlocks = 0x3770000
PID:00400002 TID:00B60002 ==================================================
PID:00400002 TID:00C40006 FATFS!FormatVolume: Formatting volume. Flags = 0x16.
PID:00400002 TID:00570002 FATFS!FormatVolume: Formatting volume. Flags = 0x16.
PID:00400002 TID:00B60002 TILER: INIT pPageTablePA = 0xb0186000 pPageTable = 0xb02a0000
PID:00400002 TID:00B60002 TILER: INIT dwRestorePageTablePA = 0xb01a6000 pRestorePageTable = 0xb02c0000
PID:00400002 TID:00B60002 dwRxFifoTriggerLevel: 1 granularity of 1
PID:00400003 TID:00B60002 dwRxFifoTriggerLevel: 60
VBridge:: VB_INITIALIZED returns [0]
PID:00400002 TID:00B60002 TIWLAN: 0.009152: TI WLAN: DLL_PROCESS_ATTACH
PID:00400002 TID:00B60002 TIWLAN: 0.009154: TIWL: DriverEntry In
PID:00400002 TID:00B60002 TIWLAN: 0.009171: TIWL: DriverEntry Out
PID:00400002 TID:00B60002 TIWLAN: 0.009198: TIWL: entryMiniportInitialize In
PID:00400002 TID:00B60002 TIWLAN: 0.009208: TIWL: AllocAdapterMemory In
PID:00400002 TID:00B60002 TIWLAN: 0.009227: TIWL: AllocAdapterMemory Out
PID:00400002 TID:00B60002 TIWLAN: 0.009246: TIWL: SetRegistrationAttributes In
PID:00400002 TID:00B60002 TIWLAN: 0.009267: TIWL: OpenConfigObject In
PID:00400002 TID:00B60002 TIWLAN: 0.009285: TIWL: AllocateNetBufferListPool In
PID:00400002 TID:00B60002 TIWLAN: 0.009306: TIWL: AllocateNetBufferListPool Out
PID:00400002 TID:00B60002 TIWLAN: 0.009331: TIWL: SetNative80211Attributes In
PID:00400002 TID:00B60002 TIWLAN: 0.009347: TIWL: SetNative80211Attributes Out
PID:00400003 TID:00B60002 ****************dwWlanEnLine = 54
PID:00400003 TID:00B60002 ****************dwWlanIRQLine = 53
PID:00400003 TID:00B60002 ****************hPlatform_Wlan_Get_Irq(): system IRQ = 245
PID:00400002 TID:00B60002 TIWLAN: 0.009597: wlanDrvIf_UpdateDriverState(): State = 0
PID:00400002 TID:00B60002 TIWLAN: 0.009615:
os_setDebugOutputToLogger set flag to 0
PID:00400003 TID:00B60002 TIWLAN: 0.009648: TIWL: entryMiniportInitialize wlanDrvIf_Start()
PID:00400003 TID:00B60002 TIWLAN: 0.009661: wlanDrvIf_Start()
PID:00400002 TID:03690006 TIWLAN: 0.009677: TIWL: OID_TI_WILINK_IOCTL: cbInfoBuffer (24) pcbNeeded (-285179343)
PID:00400002 TID:00B60002 SDHC +SHC_Init
PID:00400002 TID:00B60002 SDHC host controller initialize: m_fastPathSDIO:1 m_fastPathSDMEM:0
PID:00400003 TID:00B60002 InitializeCardDetect() - calling TWLInterruptMask interrupt=0x3100b
PID:00400003 TID:00B60002 InitializeCardDetect() - successfully initialized TWL interrupt
PID:00400002 TID:00D80002 SDHC +SHC_Open
PID:00400003 TID:00F60002 SDHC +SHC_Open
PID:00400002 TID:00D80002 SDHC +SHC_Open
PID:00400003 TID:00B60002
InitialzeEHCI USBSTS=0, PORTSC[1]=1803, PORTSC[2]=1000
PID:00400003 TID:00B60002 OALGetKitlType
PID:00400003 TID:00B60002 KITL H/W BASE ADDRESS 0x48098000
PID:00400003 TID:00B60002 Instantiating HSUSBOTGTransceiver
PID:00400003 TID:00B60002 IRQ = 0x7c
PID:00400003 TID:00B60002 Sizeof(OMAP_SYSC_GENERAL_CORE_REGS)=0x500, mapped (0xa1002000)
PID:00400002 TID:00B60002 +StartUSBClock: usage count=1
PID:00400003 TID:00B60002 StartUSBClock: STARTING USBPHY CLOCK
PID:00400003 TID:00B60002 +OMAPMHSUSBOTG::SoftResetMUSBController
PID:00400003 TID:00B60002 OMAPMHSUSBOTG::Init - FAddr = 0x0
PID:00400003 TID:00B60002 OMAPMHSUSBOTG::Init - Power = 0x20
PID:00400003 TID:00B60002 OMAPMHSUSBOTG::Init - IntrTXE = 0xffff
PID:00400003 TID:00B60002 OMAPMHSUSBOTG::Init - IntrRXE = 0xfffe
PID:00400003 TID:04B20002 CHub::AttachDevice
PID:00400002 TID:00B60002 OMAPMHSUSBOTG::Init - OTG_Rev = 0x50
PID:00400003 TID:00B60002 OMAPMHSUSBOTG::Init - HW Ver = 0x800
PID:00400003 TID:00D80002 IOCTL_POWER_CAPABILITIES
PID:00400003 TID:00B60002 +StartUSBClock: usage count=2
PID:00400003 TID:00B60002 +StopUSBClock: usage count=1
PID:00400002 TID:00B60002 USBOTG::Simplified driver UpdateInput called
PID:00400003 TID:00B60002 +StartUSBClock: usage count=2
PID:00400003 TID:00B60002 +StopUSBClock: usage count=1
PID:00400002 TID:00B60002 USBOTG::Simplified driver UpdateInput called
PID:00400002 TID:00B60002 +StartUSBClock: usage count=2
PID:00400002 TID:00B60002 +StopUSBClock: usage count=1
PID:00400003 TID:00B60002 USBOTG::Simplified driver UpdateInput called
PID:00400003 TID:00B60002 +StartUSBClock: usage count=2
PID:00400003 TID:00B60002 +StopUSBClock: usage count=1
PID:00400002 TID:04EF0002 USBOTG::Simplified driver UpdateInput called
PID:00400002 TID:00B60002 DllMain(): DEBUGMSG LLTD dll attach.
PID:00400003 TID:04EF0002 +StartUSBClock: usage count=2
PID:00400003 TID:00B60002 DllMain RETAILMSG RSPNDR_DLL_PROCESS_ATTACH...PID:00400002 TID:04EF0002 +StopUSBClock: usage count=1
PID:00400002 TID:00B60002 RSPNDR_Init... wm7 PID:00400002 TID:04EF0002 InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:04EF0002 InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:04EF0002 InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:00B60002 +++ TopEnableRspndrPolicyCallback: NdisRegisterProtocolDriver Status : 0 PID:00400002 TID:04EF0002 InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:00B60002 RSPNDR_Init: DriverEntry succeeded.PID:00400002 TID:04EF0002 InitializeUSBPlugEventNotificationHandle
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400003 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400003 TID:04FC000A CHub::AttachDevice
PID:01210013 TID:00B60002 DOT11MSM: End Initializing Security with status: !status!
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0xe
PID:00400003 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400003 TID:01100002 ....Voltage: 0x19
PID:00400003 TID:04FC000A CHub::AttachDevice
PID:00400002 TID:05AF001A HDMI driver not loaded
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400002 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400002 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400002 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400002 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04EF0002 OMAPMHSUSBOTG::ThreadRun: WAIT_TIMEOUT reached, stopping USB Clock
PID:00400002 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04EF0002 +StopUSBClock: usage count=0
PID:00400002 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04EF0002 StopUSBClock: REALLY STOPPING USBPHY CLOCK
PID:00400002 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:05AF001A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400002 TID:00570002 SoftRTC disabled
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0x1f
PID:00400002 TID:051A0002 VBUS Event
PID:00400002 TID:051A0002 TWL_USB_VBUS_INT_LATCH_SET is 0xc
PID:00400003 TID:05260002 +StartUSBClock: usage count=1
PID:00400003 TID:05260002 StartUSBClock: STARTING USBPHY CLOCK
PID:00400003 TID:05260002 OMAPMHSUSBIdGnd::Received VBUS_SESS_VLD_EVENT_INDEX event
PID:00400002 TID:04EF0002 Connected to A-Device
PID:00400002 TID:04EF0002 +OMAPMHSUSBOTG::SoftResetMUSBController
PID:00400002 TID:04EF0002 Suspend Interrupt 0x1 Line 2055
PID:00400002 TID:04EF0002 Received Reset Interrupt
PID:00400002 TID:04EF0002 Calling Peripheral Reset Handler INTRUSB_RESET set
PID:00400002 TID:04EF0002 IOCTL_BUS_USBOTG_HNP_DISABLE
PID:00400002 TID:04EF0002 +StartUSBClock: usage count=2
PID:00400002 TID:04EF0002 +StopUSBClock: usage count=1
PID:00400002 TID:04EF0002 Received Reset Interrupt
PID:00400002 TID:04EF0002 Calling Peripheral Reset Handler INTRUSB_RESET set
PID:00400003 TID:04EF0002 IOCTL_BUS_USBOTG_HNP_DISABLE
PID:00400003 TID:04EF0002 +StartUSBClock: usage count=2
PID:00400003 TID:04EF0002 +StopUSBClock: usage count=1
PID:00400002 TID:04EF0002 Device_ProcessEP0: EP0_ST_STATUS_IN...
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x19
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0xe
PID:00400002 TID:01340002 +PMExt_PMBeforeNewSystemState(0x00000001, useridle, 0x00000000)
PID:00400002 TID:01340002 NMD_IOControl IOCTL_POWER_SET 1
PID:00400002 TID:01340002 +PMExt_PMAfterNewSystemState(0x00000001, useridle, 0x00000000)
PID:00400002 TID:01340002 +PMExt_PMBeforeNewSystemState(0x00000001, on, 0x00000000)
PID:00400002 TID:01340002 NMD_IOControl IOCTL_POWER_SET 0
PID:00400002 TID:01340002 +PMExt_PMAfterNewSystemState(0x00000001, on, 0x00000000)
PID:06430006 TID:074C0006 [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0x1f
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:012C0002 SmartReflex_Enable[0] - 0
PID:00400002 TID:012C0002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 1
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 0
PID:00400002 TID:01160002 ....Voltage: 0x9
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:00400002 TID:01340002 +PMExt_PMBeforeNewSystemState(0x00000001, useridle, 0x00000000)
PID:00400002 TID:01340002 NMD_IOControl IOCTL_POWER_SET 1
PID:00400002 TID:01340002 +PMExt_PMAfterNewSystemState(0x00000001, useridle, 0x00000000)
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x19
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0xf
PID:00400002 TID:01340002 +PMExt_PMBeforeNewSystemState(0x00000001, on, 0x00000000)
PID:00400002 TID:01340002 NMD_IOControl IOCTL_POWER_SET 0
PID:00400002 TID:01340002 +PMExt_PMAfterNewSystemState(0x00000001, on, 0x00000000)
PID:06D7000E TID:07BC000E [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:012C0002 SmartReflex_Enable[0] - 0
PID:00400002 TID:012C0002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0x1f
PID:00400002 TID:04AA000A Warn: Enable_BKL Updated TWL_PWM2ON=1 TWL_PWM2OFF=127
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 1
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 0
PID:00400002 TID:01160002 ....Voltage: 0x9
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:00400002 TID:01340002 +PMExt_PMBeforeNewSystemState(0x00000001, useridle, 0x00000000)
PID:00400002 TID:01340002 NMD_IOControl IOCTL_POWER_SET 1
PID:00400002 TID:01340002 +PMExt_PMAfterNewSystemState(0x00000001, useridle, 0x00000000)
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x19
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0xe
PID:00400002 TID:01340002 +PMExt_PMBeforeNewSystemState(0x00000001, on, 0x00000000)
PID:00400002 TID:01340002 NMD_IOControl IOCTL_POWER_SET 0
PID:00400002 TID:01340002 +PMExt_PMAfterNewSystemState(0x00000001, on, 0x00000000)
PID:06430006 TID:074C0006 [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0x1f
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 1
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 0
PID:00400002 TID:01160002 ....Voltage: 0x9
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:00400002 TID:01340002 +PMExt_PMBeforeNewSystemState(0x00000001, useridle, 0x00000000)
PID:00400002 TID:01340002 NMD_IOControl IOCTL_POWER_SET 1
PID:00400002 TID:01340002 +PMExt_PMAfterNewSystemState(0x00000001, useridle, 0x00000000)
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x19
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0xe
PID:00400002 TID:01340002 +PMExt_PMBeforeNewSystemState(0x00000001, on, 0x00000000)
PID:00400002 TID:01340002 NMD_IOControl IOCTL_POWER_SET 0
PID:00400002 TID:01340002 +PMExt_PMAfterNewSystemState(0x00000001, on, 0x00000000)
PID:06430006 TID:074C0006 [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:011C0002 SmartReflex_Enable[2] - 0
PID:00400002 TID:011C0002 ....Voltage: 0x1f
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 1
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 0
PID:00400002 TID:01160002 ....Voltage: 0x9
PID:06B40082 TID:0715005A [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:06430006 TID:074C0006 [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:06430006 TID:074C0006 [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:06430006 TID:074C0006 [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 1
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 0
PID:00400002 TID:01160002 ....Voltage: 0x9
PID:06430006 TID:074C0006 [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:06430006 TID:074C0006 [WLANAPI] Stopped waiting for notification because server returns error (0, 1818)
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 1
PID:00400002 TID:064F0002 SmartReflex_Enable[1] - 0
PID:00400002 TID:064F0002 SmartReflex_Enable[1] - 1
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 0
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 1
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 0
PID:00400002 TID:01160002 ....Voltage: 0x9
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 1
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 0
PID:00400002 TID:01160002 ....Voltage: 0x9
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 1
PID:00400002 TID:01160002 SmartReflex_Enable[1] - 0
PID:00400002 TID:01160002 ....Voltage: 0x9
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 1
PID:00400002 TID:01100002 SmartReflex_Enable[0] - 0
PID:00400002 TID:01100002 ....Voltage: 0x1c
...............................
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
tera term logs of my NK.Bin is given below
--------------------------------------------------------------------------------------------------------------------------------------
Texas Instruments Windows CE X-Loader for OMAP4 SDP4470
Built Dec 23 2014 at 12:45:01
General Purpose processor
ES 1.0
load ebootsd.raw
### high-capacity card
successfully read eboot
Microsoft Windows CE Bootloader Common Library Version 1.4 Built Dec 23 2014 12:30:06
Texas Instruments Windows CE EBOOTSD 1.0 for OMAP4 SDP
Built Dec 23 2014 at 12:44:53
Silicon Type: 0
*** initMMCcontroller initialize SD/MMC host controller slot 0
SDHCSetRate MMC0 - Actual clock rate = 100000
SDHCSetRate MMC0 - Actual clock rate = 93841
SDHCSetRate MMC0 - Actual clock rate = 100000
SDHCIssueIdentify: MMCCommandResponse failed
SDHCSetRate MMC0 - Actual clock rate = 12000000
OEMPreDownload: done SdhcInitialize, calling bFlashDevReadable
*** initMMCcontroller initialize SD/MMC host controller slot 1
SDHCSetRate MMC1 - Actual clock rate = 100000
+BPE_Initialize
SDHCSetRate MMC1 - Actual clock rate = 100000
MMCIssueIdentify: MMCIssueIdentify
SDHCSetRate MMC1 - Actual clock rate = 93841
SDHCSetRate MMC1 - Actual clock rate = 100000
+MMCReturnCardStruct
-MMCReturnCardStruct
Change MMCHS_CON to support 8-bit SDR
SDHCSetRate MMC1 - Actual clock rate = 48000000
---- Bootpart_e Init: Dumping FlashLayout -------
eMMC number of sectors on device, read from extCSD = 3b70000
eMMC WP_GroupSize from extCSD = 10
XLDR Start = 0, Xldr Size(blks) = 400
IPL Start = 400, IPL Size(blks) = 400
EBT Start = 800, EBT Size(blks) = 800
ARGs Start = 1000, Args Size(blks) = 400
IMGFS Start = 28000, IMGFS Size(blks) = 0
Bytes per Block = 200
-BPE_Initialize
System ready!
Preparing for download...
INFO: OEMPreDownload....
### high-capacity card
INFO: Boot configuration found
Hit space to enter configuration menu 5...
--------------------------------------------------------------------------------
Main Menu
--------------------------------------------------------------------------------
[1] Show Current Settings
[2] Select Boot Device
[3] Select Debug Device
[4] Network Settings
[5] eMMC Utilities
[6] Set Device ID
[7] Save Settings
[8] Enable Battery Chargin
[0] Exit and Continue
Selection: 2
--------------------------------------------------------------------------------
Select Boot Device
--------------------------------------------------------------------------------
[1] KSZ8851 Ethernet
[2] USB SERIAL
[3] USB RNDIS
[4] IPL from MMC
[5] NK from eMMC
[6] NK from external SD slot
[0] Exit and Continue
Selection (actual NK from external SD slot): 6
Boot device set to NK from external SD slot
--------------------------------------------------------------------------------
Main Menu
--------------------------------------------------------------------------------
[1] Show Current Settings
[2] Select Boot Device
[3] Select Debug Device
[4] Network Settings
[5] eMMC Utilities
[6] Set Device ID
[7] Save Settings
[8] Enable Battery Chargin
[0] Exit and Continue
Selection: 0
INFO: Invalid (or out of date) args structure, using defaults
*** DownloadNkbin from external SD slot
DownloadNkbin
DownloadBin
### high-capacity card
BL_IMAGE_TYPE_BIN
*** DownloadBin set default g_DownloadManifest
dwImageStart=0x81000000 dwImageLength=0x13ec268
Download file information:
-----------------------------------------------------------
[0]: Address=0x81000000 Length=0x013ec268 Save=0x80100000
-----------------------------------------------------------
<> Record [ 0 ] dwRecAddr = 0x81000000, ramAddr = 0x80100000, dwRecLen = 0x4
<> Record [ 1 ] dwRecAddr = 0x81000040, ramAddr = 0x80100040, dwRecLen = 0x8
<> Record [ 2 ] dwRecAddr = 0x81000048, ramAddr = 0x80100048, dwRecLen = 0x4
<> Record [ 3 ] dwRecAddr = 0x81001000, ramAddr = 0x80101000, dwRecLen = 0x20000
. <> Record [ 4 ] dwRecAddr = 0x81022000, ramAddr = 0x80122000, dwRecLen = 0x33178
. <> Record [ 5 ] dwRecAddr = 0x81056000, ramAddr = 0x80156000, dwRecLen = 0x48a64
.. <> Record [ 6 ] dwRecAddr = 0x8109ea64, ramAddr = 0x8019ea64, dwRecLen = 0x155f4
<> Record [ 7 ] dwRecAddr = 0x810b5000, ramAddr = 0x801b5000, dwRecLen = 0x4581c
.. <> Record [ 8 ] dwRecAddr = 0x810fa81c, ramAddr = 0x801fa81c, dwRecLen = 0x7e4
<> Record [ 9 ] dwRecAddr = 0x810fb000, ramAddr = 0x801fb000, dwRecLen = 0x51e08
.. <> Record [ 10 ] dwRecAddr = 0x8114ce08, ramAddr = 0x8024ce08, dwRecLen = 0x1f8
<> Record [ 11 ] dwRecAddr = 0x8114d000, ramAddr = 0x8024d000, dwRecLen = 0x51e08
.. <> Record [ 12 ] dwRecAddr = 0x8119ee08, ramAddr = 0x8029ee08, dwRecLen = 0x3e1f8
. <> Record [ 13 ] dwRecAddr = 0x811dd000, ramAddr = 0x802dd000, dwRecLen = 0x6f90
<> Record [ 14 ] dwRecAddr = 0x811e4000, ramAddr = 0x802e4000, dwRecLen = 0x5fdc
<> Record [ 15 ] dwRecAddr = 0x811ea000, ramAddr = 0x802ea000, dwRecLen = 0xd30
<> Record [ 16 ] dwRecAddr = 0x811eb000, ramAddr = 0x802eb000, dwRecLen = 0x4260
<> Record [ 17 ] dwRecAddr = 0x811f0000, ramAddr = 0x802f0000, dwRecLen = 0x4260
<> Record [ 18 ] dwRecAddr = 0x811f5000, ramAddr = 0x802f5000, dwRecLen = 0x3afe0
. <> Record [ 19 ] dwRecAddr = 0x81230000, ramAddr = 0x80330000, dwRecLen = 0x2108
<> Record [ 20 ] dwRecAddr = 0x81233000, ramAddr = 0x80333000, dwRecLen = 0x6d954
... <> Record [ 21 ] dwRecAddr = 0x812a0954, ramAddr = 0x803a0954, dwRecLen = 0x3a84c
. <> Record [ 22 ] dwRecAddr = 0x812dc000, ramAddr = 0x803dc000, dwRecLen = 0x1050
<> Record [ 23 ] dwRecAddr = 0x812de000, ramAddr = 0x803de000, dwRecLen = 0x13098
<> Record [ 24 ] dwRecAddr = 0x812f2000, ramAddr = 0x803f2000, dwRecLen = 0x9094
<> Record [ 25 ] dwRecAddr = 0x812fc000, ramAddr = 0x803fc000, dwRecLen = 0x7288
<> Record [ 26 ] dwRecAddr = 0x81304000, ramAddr = 0x80404000, dwRecLen = 0x20f8
<> Record [ 27 ] dwRecAddr = 0x81307000, ramAddr = 0x80407000, dwRecLen = 0x2018
<> Record [ 28 ] dwRecAddr = 0x8130a000, ramAddr = 0x8040a000, dwRecLen = 0x1c324
<> Record [ 29 ] dwRecAddr = 0x81327000, ramAddr = 0x80427000, dwRecLen = 0xa324
<> Record [ 30 ] dwRecAddr = 0x81332000, ramAddr = 0x80432000, dwRecLen = 0x20b8
<> Record [ 31 ] dwRecAddr = 0x81335000, ramAddr = 0x80435000, dwRecLen = 0xc0
<> Record [ 32 ] dwRecAddr = 0x81336000, ramAddr = 0x80436000, dwRecLen = 0x20b8
<> Record [ 33 ] dwRecAddr = 0x81339000, ramAddr = 0x80439000, dwRecLen = 0xc0
<> Record [ 34 ] dwRecAddr = 0x8133a000, ramAddr = 0x8043a000, dwRecLen = 0x5264
<> Record [ 35 ] dwRecAddr = 0x81340000, ramAddr = 0x80440000, dwRecLen = 0x8070
<> Record [ 36 ] dwRecAddr = 0x81349000, ramAddr = 0x80449000, dwRecLen = 0x9108
<> Record [ 37 ] dwRecAddr = 0x81353000, ramAddr = 0x80453000, dwRecLen = 0x1f1d8
<> Record [ 38 ] dwRecAddr = 0x81373000, ramAddr = 0x80473000, dwRecLen = 0x1c208
<> Record [ 39 ] dwRecAddr = 0x81390000, ramAddr = 0x80490000, dwRecLen = 0x6208
<> Record [ 40 ] dwRecAddr = 0x81397000, ramAddr = 0x80497000, dwRecLen = 0x7020
<> Record [ 41 ] dwRecAddr = 0x8139f000, ramAddr = 0x8049f000, dwRecLen = 0x7020
<> Record [ 42 ] dwRecAddr = 0x813a7000, ramAddr = 0x804a7000, dwRecLen = 0x1050
<> Record [ 43 ] dwRecAddr = 0x813a9000, ramAddr = 0x804a9000, dwRecLen = 0x358
<> Record [ 44 ] dwRecAddr = 0x813aa000, ramAddr = 0x804aa000, dwRecLen = 0x3bffc
. <> Record [ 45 ] dwRecAddr = 0x813e6000, ramAddr = 0x804e6000, dwRecLen = 0x100e0
<> Record [ 46 ] dwRecAddr = 0x813f7000, ramAddr = 0x804f7000, dwRecLen = 0x61e8
<> Record [ 47 ] dwRecAddr = 0x813fe000, ramAddr = 0x804fe000, dwRecLen = 0xd8
<> Record [ 48 ] dwRecAddr = 0x813ff000, ramAddr = 0x804ff000, dwRecLen = 0x30d8
<> Record [ 49 ] dwRecAddr = 0x81403000, ramAddr = 0x80503000, dwRecLen = 0x14298
<> Record [ 50 ] dwRecAddr = 0x81418000, ramAddr = 0x80518000, dwRecLen = 0x23000
. <> Record [ 51 ] dwRecAddr = 0x8143b000, ramAddr = 0x8053b000, dwRecLen = 0x3c000
. <> Record [ 52 ] dwRecAddr = 0x81477000, ramAddr = 0x80577000, dwRecLen = 0x4e4c
<> Record [ 53 ] dwRecAddr = 0x8147c000, ramAddr = 0x8057c000, dwRecLen = 0x27000
. <> Record [ 54 ] dwRecAddr = 0x814a3000, ramAddr = 0x805a3000, dwRecLen = 0x7a9e4
... <> Record [ 55 ] dwRecAddr = 0x8151d9e4, ramAddr = 0x8061d9e4, dwRecLen = 0x1a6d4
<> Record [ 56 ] dwRecAddr = 0x81539000, ramAddr = 0x80639000, dwRecLen = 0x5130
<> Record [ 57 ] dwRecAddr = 0x8153f000, ramAddr = 0x8063f000, dwRecLen = 0x3affc
. <> Record [ 58 ] dwRecAddr = 0x8157a000, ramAddr = 0x8067a000, dwRecLen = 0xf0f0
<> Record [ 59 ] dwRecAddr = 0x8158a000, ramAddr = 0x8068a000, dwRecLen = 0x3a000
. <> Record [ 60 ] dwRecAddr = 0x815c4000, ramAddr = 0x806c4000, dwRecLen = 0x39000
. <> Record [ 61 ] dwRecAddr = 0x815fd000, ramAddr = 0x806fd000, dwRecLen = 0x17130
<> Record [ 62 ] dwRecAddr = 0x81615000, ramAddr = 0x80715000, dwRecLen = 0x20d8
<> Record [ 63 ] dwRecAddr = 0x81618000, ramAddr = 0x80718000, dwRecLen = 0x14fdc
<> Record [ 64 ] dwRecAddr = 0x8162d000, ramAddr = 0x8072d000, dwRecLen = 0x2098
<> Record [ 65 ] dwRecAddr = 0x81630000, ramAddr = 0x80730000, dwRecLen = 0x1fe0
<> Record [ 66 ] dwRecAddr = 0x81632000, ramAddr = 0x80732000, dwRecLen = 0x190fc
<> Record [ 67 ] dwRecAddr = 0x8164c000, ramAddr = 0x8074c000, dwRecLen = 0x242ac
. <> Record [ 68 ] dwRecAddr = 0x81671000, ramAddr = 0x80771000, dwRecLen = 0x1dfc8
<> Record [ 69 ] dwRecAddr = 0x8168f000, ramAddr = 0x8078f000, dwRecLen = 0x80
<> Record [ 70 ] dwRecAddr = 0x81690000, ramAddr = 0x80790000, dwRecLen = 0x20b8
<> Record [ 71 ] dwRecAddr = 0x81693000, ramAddr = 0x80793000, dwRecLen = 0x20b8
<> Record [ 72 ] dwRecAddr = 0x81696000, ramAddr = 0x80796000, dwRecLen = 0x1048
<> Record [ 73 ] dwRecAddr = 0x81698000, ramAddr = 0x80798000, dwRecLen = 0x60
<> Record [ 74 ] dwRecAddr = 0x81699000, ramAddr = 0x80799000, dwRecLen = 0x14000
<> Record [ 75 ] dwRecAddr = 0x816ad000, ramAddr = 0x807ad000, dwRecLen = 0x599e0
.. <> Record [ 76 ] dwRecAddr = 0x817069e0, ramAddr = 0x808069e0, dwRecLen = 0x26ac
<> Record [ 77 ] dwRecAddr = 0x8170a000, ramAddr = 0x8080a000, dwRecLen = 0x599e0
.. <> Record [ 78 ] dwRecAddr = 0x817639e0, ramAddr = 0x808639e0, dwRecLen = 0x26ac
<> Record [ 79 ] dwRecAddr = 0x81767000, ramAddr = 0x80867000, dwRecLen = 0x20d0
<> Record [ 80 ] dwRecAddr = 0x8176a000, ramAddr = 0x8086a000, dwRecLen = 0x20d0
<> Record [ 81 ] dwRecAddr = 0x8176d000, ramAddr = 0x8086d000, dwRecLen = 0x11e8
<> Record [ 82 ] dwRecAddr = 0x8176f000, ramAddr = 0x8086f000, dwRecLen = 0x90
<> Record [ 83 ] dwRecAddr = 0x81770000, ramAddr = 0x80870000, dwRecLen = 0x2a000
. <> Record [ 84 ] dwRecAddr = 0x8179a000, ramAddr = 0x8089a000, dwRecLen = 0x22300
. <> Record [ 85 ] dwRecAddr = 0x817bd000, ramAddr = 0x808bd000, dwRecLen = 0x3108
<> Record [ 86 ] dwRecAddr = 0x817c1000, ramAddr = 0x808c1000, dwRecLen = 0x20f8
<> Record [ 87 ] dwRecAddr = 0x817c4000, ramAddr = 0x808c4000, dwRecLen = 0x43d04
.. <> Record [ 88 ] dwRecAddr = 0x81807d04, ramAddr = 0x80907d04, dwRecLen = 0x212e4
. <> Record [ 89 ] dwRecAddr = 0x81829000, ramAddr = 0x80929000, dwRecLen = 0x16000
<> Record [ 90 ] dwRecAddr = 0x8183f000, ramAddr = 0x8093f000, dwRecLen = 0x39050
. <> Record [ 91 ] dwRecAddr = 0x81879000, ramAddr = 0x80979000, dwRecLen = 0x28000
. <> Record [ 92 ] dwRecAddr = 0x818a1000, ramAddr = 0x809a1000, dwRecLen = 0x54270
.. <> Record [ 93 ] dwRecAddr = 0x818f6000, ramAddr = 0x809f6000, dwRecLen = 0xb050
<> Record [ 94 ] dwRecAddr = 0x81902000, ramAddr = 0x80a02000, dwRecLen = 0x5e4c0
.. <> Record [ 95 ] dwRecAddr = 0x819604c0, ramAddr = 0x80a604c0, dwRecLen = 0x1ab90
<> Record [ 96 ] dwRecAddr = 0x8197c000, ramAddr = 0x80a7c000, dwRecLen = 0xa2a08
..... <> Record [ 97 ] dwRecAddr = 0x81a1ea08, ramAddr = 0x80b1ea08, dwRecLen = 0x198a4
<> Record [ 98 ] dwRecAddr = 0x81a39000, ramAddr = 0x80b39000, dwRecLen = 0x1c274
<> Record [ 99 ] dwRecAddr = 0x81a56000, ramAddr = 0x80b56000, dwRecLen = 0x3e214
. <> Record [ 100 ] dwRecAddr = 0x81a95000, ramAddr = 0x80b95000, dwRecLen = 0x80
<> Record [ 101 ] dwRecAddr = 0x81a96000, ramAddr = 0x80b96000, dwRecLen = 0xd0
<> Record [ 102 ] dwRecAddr = 0x81a97000, ramAddr = 0x80b97000, dwRecLen = 0x37368
. <> Record [ 103 ] dwRecAddr = 0x81acf000, ramAddr = 0x80bcf000, dwRecLen = 0x191c4
<> Record [ 104 ] dwRecAddr = 0x81ae9000, ramAddr = 0x80be9000, dwRecLen = 0x1724c
<> Record [ 105 ] dwRecAddr = 0x81b01000, ramAddr = 0x80c01000, dwRecLen = 0x8fc8
<> Record [ 106 ] dwRecAddr = 0x81b0a000, ramAddr = 0x80c0a000, dwRecLen = 0x3cfd0
. <> Record [ 107 ] dwRecAddr = 0x81b47000, ramAddr = 0x80c47000, dwRecLen = 0x20d8
<> Record [ 108 ] dwRecAddr = 0x81b4a000, ramAddr = 0x80c4a000, dwRecLen = 0x36ffc
. <> Record [ 109 ] dwRecAddr = 0x81b81000, ramAddr = 0x80c81000, dwRecLen = 0x3d000
. <> Record [ 110 ] dwRecAddr = 0x81bbe000, ramAddr = 0x80cbe000, dwRecLen = 0x3d000
. <> Record [ 111 ] dwRecAddr = 0x81bfb000, ramAddr = 0x80cfb000, dwRecLen = 0x2b39c
. <> Record [ 112 ] dwRecAddr = 0x81c27000, ramAddr = 0x80d27000, dwRecLen = 0x639c
<> Record [ 113 ] dwRecAddr = 0x81c2e000, ramAddr = 0x80d2e000, dwRecLen = 0x2a0c4
. <> Record [ 114 ] dwRecAddr = 0x81c59000, ramAddr = 0x80d59000, dwRecLen = 0x2efe4
. <> Record [ 115 ] dwRecAddr = 0x81c88000, ramAddr = 0x80d88000, dwRecLen = 0x5fec
<> Record [ 116 ] dwRecAddr = 0x81c8e000, ramAddr = 0x80d8e000, dwRecLen = 0x1050
<> Record [ 117 ] dwRecAddr = 0x81c90000, ramAddr = 0x80d90000, dwRecLen = 0x2050
<> Record [ 118 ] dwRecAddr = 0x81c93000, ramAddr = 0x80d93000, dwRecLen = 0xffc
<> Record [ 119 ] dwRecAddr = 0x81c94000, ramAddr = 0x80d94000, dwRecLen = 0x485e4
.. <> Record [ 120 ] dwRecAddr = 0x81cdc5e4, ramAddr = 0x80ddc5e4, dwRecLen = 0x1778
<> Record [ 121 ] dwRecAddr = 0x81cde000, ramAddr = 0x80dde000, dwRecLen = 0x4ff0
<> Record [ 122 ] dwRecAddr = 0x81ce3000, ramAddr = 0x80de3000, dwRecLen = 0xe120
<> Record [ 123 ] dwRecAddr = 0x81cf2000, ramAddr = 0x80df2000, dwRecLen = 0x2090
<> Record [ 124 ] dwRecAddr = 0x81cf5000, ramAddr = 0x80df5000, dwRecLen = 0x20a0
<> Record [ 125 ] dwRecAddr = 0x81cf8000, ramAddr = 0x80df8000, dwRecLen = 0x20a0
<> Record [ 126 ] dwRecAddr = 0x81cfb000, ramAddr = 0x80dfb000, dwRecLen = 0x13c8
<> Record [ 127 ] dwRecAddr = 0x81cfd000, ramAddr = 0x80dfd000, dwRecLen = 0x80
<> Record [ 128 ] dwRecAddr = 0x81cfe000, ramAddr = 0x80dfe000, dwRecLen = 0x60e8
<> Record [ 129 ] dwRecAddr = 0x81d05000, ramAddr = 0x80e05000, dwRecLen = 0x2088
<> Record [ 130 ] dwRecAddr = 0x81d08000, ramAddr = 0x80e08000, dwRecLen = 0x90e8
<> Record [ 131 ] dwRecAddr = 0x81d12000, ramAddr = 0x80e12000, dwRecLen = 0x130
<> Record [ 132 ] dwRecAddr = 0x81d13000, ramAddr = 0x80e13000, dwRecLen = 0x60c0
<> Record [ 133 ] dwRecAddr = 0x81d1a000, ramAddr = 0x80e1a000, dwRecLen = 0x2150
<> Record [ 134 ] dwRecAddr = 0x81d1d000, ramAddr = 0x80e1d000, dwRecLen = 0xf0
<> Record [ 135 ] dwRecAddr = 0x81d1e000, ramAddr = 0x80e1e000, dwRecLen = 0x20a8
<> Record [ 136 ] dwRecAddr = 0x81d21000, ramAddr = 0x80e21000, dwRecLen = 0x4128
<> Record [ 137 ] dwRecAddr = 0x81d26000, ramAddr = 0x80e26000, dwRecLen = 0x3fdc
<> Record [ 138 ] dwRecAddr = 0x81d2a000, ramAddr = 0x80e2a000, dwRecLen = 0x3100
<> Record [ 139 ] dwRecAddr = 0x81d2e000, ramAddr = 0x80e2e000, dwRecLen = 0x2308
<> Record [ 140 ] dwRecAddr = 0x81d31000, ramAddr = 0x80e31000, dwRecLen = 0x98
<> Record [ 141 ] dwRecAddr = 0x81d32000, ramAddr = 0x80e32000, dwRecLen = 0x5080
<> Record [ 142 ] dwRecAddr = 0x81d38000, ramAddr = 0x80e38000, dwRecLen = 0x2108
<> Record [ 143 ] dwRecAddr = 0x81d3b000, ramAddr = 0x80e3b000, dwRecLen = 0x2088
<> Record [ 144 ] dwRecAddr = 0x81d3e000, ramAddr = 0x80e3e000, dwRecLen = 0x3118
<> Record [ 145 ] dwRecAddr = 0x81d42000, ramAddr = 0x80e42000, dwRecLen = 0x60a0
<> Record [ 146 ] dwRecAddr = 0x81d49000, ramAddr = 0x80e49000, dwRecLen = 0x20b8
<> Record [ 147 ] dwRecAddr = 0x81d4c000, ramAddr = 0x80e4c000, dwRecLen = 0x7060
<> Record [ 148 ] dwRecAddr = 0x81d54000, ramAddr = 0x80e54000, dwRecLen = 0x53b4
<> Record [ 149 ] dwRecAddr = 0x81d5a000, ramAddr = 0x80e5a000, dwRecLen = 0x9ff0
<> Record [ 150 ] dwRecAddr = 0x81d64000, ramAddr = 0x80e64000, dwRecLen = 0xa0d0
<> Record [ 151 ] dwRecAddr = 0x81d6f000, ramAddr = 0x80e6f000, dwRecLen = 0x1a34c
<> Record [ 152 ] dwRecAddr = 0x81d8a000, ramAddr = 0x80e8a000, dwRecLen = 0x9238
<> Record [ 153 ] dwRecAddr = 0x81d94000, ramAddr = 0x80e94000, dwRecLen = 0xfd43c
....... <> Record [ 154 ] dwRecAddr = 0x81e9143c, ramAddr = 0x80f9143c, dwRecLen = 0x22c38
. <> Record [ 155 ] dwRecAddr = 0x81eb5000, ramAddr = 0x80fb5000, dwRecLen = 0x3fec
<> Record [ 156 ] dwRecAddr = 0x81eb9000, ramAddr = 0x80fb9000, dwRecLen = 0x240
<> Record [ 157 ] dwRecAddr = 0x81eba000, ramAddr = 0x80fba000, dwRecLen = 0x619c
<> Record [ 158 ] dwRecAddr = 0x81ec1000, ramAddr = 0x80fc1000, dwRecLen = 0x88
<> Record [ 159 ] dwRecAddr = 0x81ec2000, ramAddr = 0x80fc2000, dwRecLen = 0x2fe8
<> Record [ 160 ] dwRecAddr = 0x81ec5000, ramAddr = 0x80fc5000, dwRecLen = 0xf8
<> Record [ 161 ] dwRecAddr = 0x81ec6000, ramAddr = 0x80fc6000, dwRecLen = 0x30d0
<> Record [ 162 ] dwRecAddr = 0x81eca000, ramAddr = 0x80fca000, dwRecLen = 0x13000
<> Record [ 163 ] dwRecAddr = 0x81edd000, ramAddr = 0x80fdd000, dwRecLen = 0x559d8
.. <> Record [ 164 ] dwRecAddr = 0x81f329d8, ramAddr = 0x810329d8, dwRecLen = 0x3f338
. <> Record [ 165 ] dwRecAddr = 0x81f71d10, ramAddr = 0x81071d10, dwRecLen = 0x374d0
. <> Record [ 166 ] dwRecAddr = 0x81fa91e0, ramAddr = 0x810a91e0, dwRecLen = 0x37ff8
. <> Record [ 167 ] dwRecAddr = 0x81fe11d8, ramAddr = 0x810e11d8, dwRecLen = 0x3f0ec
. <> Record [ 168 ] dwRecAddr = 0x820202c4, ramAddr = 0x811202c4, dwRecLen = 0x2350
<> Record [ 169 ] dwRecAddr = 0x82022614, ramAddr = 0x81122614, dwRecLen = 0xaa674
..... <> Record [ 170 ] dwRecAddr = 0x820ccc88, ramAddr = 0x811ccc88, dwRecLen = 0x7e508
... <> Record [ 171 ] dwRecAddr = 0x8214b190, ramAddr = 0x8124b190, dwRecLen = 0x35054
. <> Record [ 172 ] dwRecAddr = 0x821801e4, ramAddr = 0x812801e4, dwRecLen = 0x12218
<> Record [ 173 ] dwRecAddr = 0x821923fc, ramAddr = 0x812923fc, dwRecLen = 0x9b660
.... <> Record [ 174 ] dwRecAddr = 0x8222da5c, ramAddr = 0x8132da5c, dwRecLen = 0x10820
<> Record [ 175 ] dwRecAddr = 0x8223e27c, ramAddr = 0x8133e27c, dwRecLen = 0x36168
. <> Record [ 176 ] dwRecAddr = 0x822743e4, ramAddr = 0x813743e4, dwRecLen = 0x1a8a0
<> Record [ 177 ] dwRecAddr = 0x8228ec84, ramAddr = 0x8138ec84, dwRecLen = 0x28030
. <> Record [ 178 ] dwRecAddr = 0x822b6cb4, ramAddr = 0x813b6cb4, dwRecLen = 0x381b8
. <> Record [ 179 ] dwRecAddr = 0x822eee6c, ramAddr = 0x813eee6c, dwRecLen = 0x35ff8
. <> Record [ 180 ] dwRecAddr = 0x82324e64, ramAddr = 0x81424e64, dwRecLen = 0xd534
<> Record [ 181 ] dwRecAddr = 0x82332398, ramAddr = 0x81432398, dwRecLen = 0x772b0
... <> Record [ 182 ] dwRecAddr = 0x823a9648, ramAddr = 0x814a9648, dwRecLen = 0x15744
<> Record [ 183 ] dwRecAddr = 0x823bed8c, ramAddr = 0x814bed8c, dwRecLen = 0x2b0c4
. <> Record [ 184 ] dwRecAddr = 0x823e9e50, ramAddr = 0x814e9e50, dwRecLen = 0x54
<> Record [ 185 ] dwRecAddr = 0x823e9ea4, ramAddr = 0x814e9ea4, dwRecLen = 0x23c4
Setting Launch address = default
+OEMLaunch(0x00000000, 0x00000000, 0x00000000, 0x00000000 - 3/1)
Launch Windows CE image by jumping to 0x80100000...
Windows CE Kernel for ARM (Thumb Enabled)
--- High Performance Frequecy is 32768 khz---
OALEnableSMP(1) AuxCtrl = 0x41
OALEnableSMP: OALVAtoPA(OALSMPStartup)=0x80115201
OALEnableSMP: OALCpuSetIndentityMap returned =0x0
PID:00400002 TID:00560002 OALIoCtlHalInitRTC(): Resetting RTC
PID:00400002 TID:00A10002 +WriteTwlReg failed!!
PID:00400002 TID:00A10002 +WriteTwlReg failed!!
PID:00400002 TID:00A10002 EDISK: Bus handle created
PID:00400002 TID:00A10002 ======== E DISK (SYSTEM) =============================
PID:00400002 TID:00A10002 EDISK: di_bytes_per_sect = 0x200
PID:00400002 TID:00A10002 EDISK: di_cylinders = 0x0
PID:00400002 TID:00A10002 EDISK: di_heads = 0x0
PID:00400002 TID:00A10002 EDISK: di_sectors = 0x0
PID:00400002 TID:00A10002 EDISK: di_flags = 0xb
PID:00400002 TID:00A10002 EDISK: dwStartSect = 0x5a000
PID:00400002 TID:00A10002 EDISK: di_total_sectors = 0x3a6000 (1868MB)
PID:00400002 TID:00A10002 EDISK: dwTotalBlocks = 0x3a6000
PID:00400002 TID:00A10002 ==================================================
PID:00400002 TID:00A10002 EDK_Init: (Skipping init, already done)
PID:00400003 TID:00A10002 ======== E DISK (BULK) =============================
PID:00400003 TID:00A10002 EDISK: di_bytes_per_sect = 0x200
PID:00400003 TID:00A10002 EDISK: di_cylinders = 0x0
PID:00400003 TID:00A10002 EDISK: di_heads = 0x0
PID:00400003 TID:00A10002 EDISK: di_sectors = 0x0
PID:00400003 TID:00A10002 EDISK: di_flags = 0xb
PID:00400003 TID:00A10002 EDISK: dwStartSect = 0x400000
PID:00400003 TID:00A10002 EDISK: di_total_sectors = 0x3770000 (28384MB)
PID:00400003 TID:00A10002 EDISK: dwTotalBlocks = 0x3770000
PID:00400003 TID:00A10002 ==================================================
PID:00400003 TID:00A10002 TILER: INIT pPageTablePA = 0xb0182000 pPageTable = 0xaff80000
PID:00400003 TID:00A10002 TILER: INIT dwRestorePageTablePA = 0xb01a2000 pRestorePageTable = 0xaffa0000
PID:00400003 TID:00A10002 ABE_InitPolicy: ERROR: PmxSetConstraintById fails (DVFS).
PID:00400002 TID:00A10002 dwRxFifoTriggerLevel: 1 granularity of 1
PID:00400002 TID:00A10002 dwRxFifoTriggerLevel: 60
PID:00400003 TID:00A10002 TIWLAN: 9.457000: TI WLAN: DLL_PROCESS_ATTACH
PID:00400003 TID:00A10002 TIWLAN: 9.459000: TIWL: DriverEntry In
PID:00400003 TID:00A10002 TIWLAN: 9.476000: TIWL: DriverEntry Out
PID:00400003 TID:00A10002 TIWLAN: 9.497000: TIWL: entryMiniportInitialize In
PID:00400003 TID:00A10002 TIWLAN: 9.514000: TIWL: AllocAdapterMemory In
PID:00400003 TID:00A10002 TIWLAN: 9.533000: TIWL: AllocAdapterMemory Out
PID:00400003 TID:00A10002 TIWLAN: 9.552000: TIWL: SetRegistrationAttributes In
PID:00400003 TID:00A10002 TIWLAN: 9.572000: TIWL: OpenConfigObject In
PID:00400003 TID:00A10002 TIWLAN: 9.591000: TIWL: AllocateNetBufferListPool In
PID:00400003 TID:00A10002 TIWLAN: 9.611000: TIWL: AllocateNetBufferListPool Out
PID:00400003 TID:00A10002 TIWLAN: 9.634000: TIWL: SetNative80211Attributes In
PID:00400003 TID:00A10002 TIWLAN: 9.653000: TIWL: SetNative80211Attributes Out
PID:00400002 TID:00A10002 ****************dwWlanEnLine = 54
PID:00400002 TID:00A10002 ****************dwWlanIRQLine = 53
PID:00400002 TID:00A10002 ****************hPlatform_Wlan_Get_Irq(): system IRQ = 245
PID:00400002 TID:00A10002 TIWLAN: 9.899000: wlanDrvIf_UpdateDriverState(): State = 0
PID:00400002 TID:00A10002 TIWLAN: 9.920000:
os_setDebugOutputToLogger set flag to 0
PID:00400002 TID:00A10002 TIWLAN: 9.953000: TIWL: entryMiniportInitialize wlanDrvIf_Start()
PID:00400002 TID:00A10002 TIWLAN: 9.966000: wlanDrvIf_Start()
PID:00400003 TID:034B0002 TIWLAN: 9.982000: TIWL: OID_TI_WILINK_IOCTL: cbInfoBuffer (24) pcbNeeded (-1249535920)
PID:00400003 TID:034B0002 TIWLAN: 10.012000: TIWL: Reading InitTable parameters
PID:00400002 TID:034B0002 Exception 'Data Abort' (0x4): Thread-Id=034b0002(pth=a3433a00), Proc-Id=00400002(pprc=8240cae0) 'NK.EXE', VM-active=01c1000a(pprc=a3410000) 'udevice.exe'
PID:00400002 TID:034B0002 PC=ef2570c9(tiwlnapi.dll+0x000470c9) RA=ef254b27(tiwlnapi.dll+0x00044b27) SP=b594f340, BVA=00000000
PID:00400003 TID:00A10002 PPM_Init: h_srPolicy == NULL!!!
PID:00400003 TID:00A10002 PPM_Init: h_cpuldPolicy == NULL!!!
PID:00400002 TID:00A10002 SDHC +SHC_Init
PID:00400002 TID:00A10002 SDHC host controller initialize: m_fastPathSDIO:1 m_fastPathSDMEM:0
PID:00400002 TID:00A10002 InitializeCardDetect() - calling TWLInterruptMask interrupt=0x3100b
PID:00400002 TID:00A10002 InitializeCardDetect() - successfully initialized TWL interrupt
PID:00400002 TID:03980002 CSDIOControllerBase::CommandTransferCompleteHandler - Unable to get/lock current request!
PID:00400002 TID:00A10002
InitialzeEHCI USBSTS=0, PORTSC[1]=1803, PORTSC[2]=1000
PID:00400003 TID:00A10002 OALGetKitlType
PID:00400003 TID:00A10002 KITL H/W BASE ADDRESS 0x48098000
PID:00400003 TID:00A10002 Instantiating HSUSBOTGTransceiver
PID:00400003 TID:00A10002 IRQ = 0x7c
PID:00400003 TID:00A10002 Sizeof(OMAP_SYSC_GENERAL_CORE_REGS)=0x500, mapped (0xa1002000)
PID:00400002 TID:00A10002 +StartUSBClock: usage count=1
PID:00400003 TID:00A10002 StartUSBClock: STARTING USBPHY CLOCK
PID:00400003 TID:00A10002 +OMAPMHSUSBOTG::SoftResetMUSBController
PID:00400002 TID:00A10002 OMAPMHSUSBOTG::Init - FAddr = 0x0
PID:00400002 TID:00A10002 OMAPMHSUSBOTG::Init - Power = 0x20
PID:00400003 TID:00A10002 OMAPMHSUSBOTG::Init - IntrTXE = 0xffff
PID:00400003 TID:00A10002 OMAPMHSUSBOTG::Init - IntrRXE = 0xfffe
PID:00400003 TID:00A10002 OMAPMHSUSBOTG::Init - OTG_Rev = 0x50
PID:00400003 TID:033A000E CHub::AttachDevice
PID:00400003 TID:00A10002 OMAPMHSUSBOTG::Init - HW Ver = 0x800
PID:00400003 TID:00A10002 USBOTG::Simplified driver UpdateInput called
PID:00400003 TID:00A10002 +StartUSBClock: usage count=2
PID:00400003 TID:00A10002 +StopUSBClock: usage count=1
PID:00400003 TID:00A10002 USBOTG::Simplified driver UpdateInput called
PID:00400003 TID:00A10002 +StartUSBClock: usage count=2
PID:00400003 TID:00A10002 +StopUSBClock: usage count=1
PID:00400002 TID:039F000E USBOTG::Simplified driver UpdateInput called
PID:00400003 TID:00A10002 Backlight: required registry key UseBattery could not be read.PID:00400002 TID:039F000E +StartUSBClock: usage count=2
PID:00400002 TID:00A10002 Backlight: required registry key UseExt could not be read.PID:00400002 TID:039F000E +StopUSBClock: usage count=1
PID:00400003 TID:00A10002 Backlight: required registry HKEY_CURRENT_USER key could not be read.Using DEFAULT VALUESPID:00400002 TID:039F000E InitializeUSBPlugEventNotificationHandle
PID:00400002 TID:039F000E InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:039F000E InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:039F000E InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:039F000E InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:032A002E CHub::AttachDevice
PID:00400002 TID:00560002 SoftRTC disabled
PID:00400003 TID:04270006 HDMI driver not loaded
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:04270006 TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:032A002E CHub::AttachDevice
PID:00400002 TID:039F000E OMAPMHSUSBOTG::ThreadRun: WAIT_TIMEOUT reached, stopping USB Clock
PID:00400002 TID:039F000E +StopUSBClock: usage count=0
PID:00400002 TID:039F000E StopUSBClock: REALLY STOPPING USBPHY CLOCK
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I am using release build so that image size is less.
I think OS Design have some problem. Can you share the OS Design??
Also with binaries that you shared the display is not fit to screen??
Thanks and Regards
ASWIN PP
Hi
To clarify, the build process for this BSP (included in WEC2013 installer) does not use OS Design to build. The build batch files (that we shared and you probably have them) are used to setup the build environment and then you can use the build commands applicable to this BSP. So we request you to build using the batch files (to setup the env inside command shell) and then build the binaries.
To understand the display issue you identified, we retrieved an older build and found that display works fine. This leads to either a build mistake on our side in the latest build or something different in QFEs since last we built.
To double check, can you please download the bins from https://www.yousendit.com/download/UlRTT216ays4aU5BSXRVag and try them out on your tablet 2 environment?
For now most of the team will be off till Jan 5th so we wont have more updates for sometime. Sorry about that, we request your consideration on this front.
It would be helpful if you can share your learning goals on this platform, i.e., is your goal to learn OMAP4470 or WEC2013 or application development? this will help us present you with supporting information accordingly.
Hi,
Thank you for replaying,
Now i created the binaries using batch files and its booting fine, Previously i created os design and tried building.
How to to enable mini shell with the binaries.
I want to study more about WEC 2013 OS and BSP, So that i preferred this platform.
Thanks and Regards
Hi,
thanks...
The build issue and mini shell issue resolved, But the NK.Bin is not detecting USB Keyboard.
I tried with mini shell binary that you shared, but that also showing same error.
I attaches corresponding logs
Setting Launch address = default
+OEMLaunch(0x00000000, 0x00000000, 0x00000000, 0x00000000 - 3/1)
Launch Windows CE image by jumping to 0x80100000...
Windows CE Kernel for ARM (Thumb Enabled)
--- High Performance Frequecy is 32768 khz---
DeviceId................. SDP4470-
pArgs->flags............. 0x2C
pArgs->devLoc.IfcType.... 0
pArgs->devLoc.LogicalLoc. 0x48098000
pArgs->devLoc.PhysicalLoc 0x0
pArgs->devLoc.Pin........ 0
pArgs->ip4address........ 192.168.2.1
pDevice->Name............ K
pDevice->ifcType......... 0
pDevice->id.............. 0x48098000
pDevice->resource........ 0
pDevice->type............ 2
pDevice->pDriver......... 0x81CBA0F0
WARN: OALKitlInit: KITL Disabled
OALEnableSMP(1) AuxCtrl = 0x41
OALEnableSMP: OALVAtoPA(OALSMPStartup)=0x80115201
OALEnableSMP: OALCpuSetIndentityMap returned =0x0
PID:00400002 TID:00570002 OALIoCtlHalInitRTC(): Getting RTC
PID:00400002 TID:00AE0002 +WriteTwlReg failed!!
PID:00400002 TID:00AE0002 +WriteTwlReg failed!!
PID:00400002 TID:00AE0002 EDISK: Bus handle created
PID:00400002 TID:00AE0002 ======== E DISK (SYSTEM) =============================
PID:00400002 TID:00AE0002 EDISK: di_bytes_per_sect = 0x200
PID:00400002 TID:00AE0002 EDISK: di_cylinders = 0x0
PID:00400002 TID:00AE0002 EDISK: di_heads = 0x0
PID:00400002 TID:00AE0002 EDISK: di_sectors = 0x0
PID:00400002 TID:00AE0002 EDISK: di_flags = 0xb
PID:00400002 TID:00AE0002 EDISK: dwStartSect = 0x5a000
PID:00400002 TID:00AE0002 EDISK: di_total_sectors = 0x3a6000 (1868MB)
PID:00400002 TID:00AE0002 EDISK: dwTotalBlocks = 0x3a6000
PID:00400002 TID:00AE0002 ==================================================
PID:00400002 TID:00AE0002 EDK_Init: (Skipping init, already done)
PID:00400003 TID:00AE0002 ======== E DISK (BULK) =============================
PID:00400003 TID:00AE0002 EDISK: di_bytes_per_sect = 0x200
PID:00400003 TID:00AE0002 EDISK: di_cylinders = 0x0
PID:00400003 TID:00AE0002 EDISK: di_heads = 0x0
PID:00400003 TID:00AE0002 EDISK: di_sectors = 0x0
PID:00400003 TID:00AE0002 EDISK: di_flags = 0xb
PID:00400003 TID:00AE0002 EDISK: dwStartSect = 0x400000
PID:00400003 TID:00AE0002 EDISK: di_total_sectors = 0x3770000 (28384MB)
PID:00400003 TID:00AE0002 EDISK: dwTotalBlocks = 0x3770000
PID:00400003 TID:00AE0002 ==================================================
PID:00400003 TID:00AE0002 TILER: INIT pPageTablePA = 0xb0182000 pPageTable = 0xaff00000
PID:00400003 TID:00AE0002 TILER: INIT dwRestorePageTablePA = 0xb01a2000 pRestorePageTable = 0xaff20000
PID:00400003 TID:00AE0002 ABE_InitPolicy: ERROR: PmxSetConstraintById fails (DVFS).
PID:00400002 TID:00AE0002 dwRxFifoTriggerLevel: 1 granularity of 1
PID:00400002 TID:00AE0002 dwRxFifoTriggerLevel: 60
PID:00400002 TID:00AE0002 WARN: TransactI2CPacket: No ACK from secondary device with address 0x4b, stat = 0x1006
PID:00400003 TID:00AE0002 Read: Attempts = 2 Port 0
VBridge:: VB_INITIALIZED returns [0]
PID:00400003 TID:00AE0002 VMini:: VBridge is not initialized! Bail out..
PID:00400003 TID:00AE0002 PPM_Init: h_srPolicy == NULL!!!
PID:00400003 TID:00AE0002 PPM_Init: h_cpuldPolicy == NULL!!!
PID:00400003 TID:00AE0002 SDHC +SHC_Init
PID:00400002 TID:00AE0002 SDHC host controller initialize: m_fastPathSDIO:1 m_fastPathSDMEM:0
PID:00400002 TID:00AE0002 InitializeCardDetect() - calling TWLInterruptMask interrupt=0x3100b
PID:00400002 TID:00AE0002 InitializeCardDetect() - successfully initialized TWL interrupt
PID:00400002 TID:0056001A CSDIOControllerBase::CommandTransferCompleteHandler - Unable to get/lock current request!
PID:00400003 TID:00AE0002
InitialzeEHCI USBSTS=0, PORTSC[1]=1803, PORTSC[2]=1000
PID:00400003 TID:00AE0002 OALGetKitlType
PID:00400003 TID:00AE0002 KITL H/W BASE ADDRESS 0x48098000
PID:00400003 TID:00AE0002 Instantiating HSUSBOTGTransceiver
PID:00400003 TID:00AE0002 IRQ = 0x7c
PID:00400003 TID:00AE0002 Sizeof(OMAP_SYSC_GENERAL_CORE_REGS)=0x500, mapped (0xa1002000)
PID:00400002 TID:00AE0002 +StartUSBClock: usage count=1
PID:00400003 TID:00AE0002 StartUSBClock: STARTING USBPHY CLOCK
PID:00400003 TID:00AE0002 +OMAPMHSUSBOTG::SoftResetMUSBController
PID:00400003 TID:00AE0002 OMAPMHSUSBOTG::Init - FAddr = 0x0
PID:00400003 TID:00AE0002 OMAPMHSUSBOTG::Init - Power = 0x20
PID:00400003 TID:00AE0002 OMAPMHSUSBOTG::Init - IntrTXE = 0xffff
PID:00400003 TID:00AE0002 OMAPMHSUSBOTG::Init - IntrRXE = 0xfffe
PID:00400003 TID:00AE0002 OMAPMHSUSBOTG::Init - OTG_Rev = 0x50
PID:00400002 TID:03B50002 CHub::AttachDevice
PID:00400003 TID:00AE0002 OMAPMHSUSBOTG::Init - HW Ver = 0x800
PID:00400003 TID:00AE0002 USBOTG::Simplified driver UpdateInput called
PID:00400003 TID:00AE0002 +StartUSBClock: usage count=2
PID:00400003 TID:00AE0002 +StopUSBClock: usage count=1
PID:00400003 TID:00AE0002 USBOTG::Simplified driver UpdateInput called
PID:00400003 TID:00AE0002 +StartUSBClock: usage count=2
PID:00400003 TID:00AE0002 +StopUSBClock: usage count=1
PID:00400002 TID:03C60002 USBOTG::Simplified driver UpdateInput called
PID:00400002 TID:00AE0002 Backlight: required registry key UseBattery could not be read.PID:00400002 TID:03C60002 +StartUSBClock: usage count=2
PID:00400002 TID:00AE0002 Backlight: required registry key UseExt could not be read.PID:00400002 TID:03C60002 +StopUSBClock: usage count=1
PID:00400003 TID:00AE0002 Backlight: required registry HKEY_CURRENT_USER key could not be read.Using DEFAULT VALUESPID:00400002 TID:03C60002 InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:03C60002 InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:03C60002 InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:03C60002 InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:03C60002 InitializeUSBPlugEventNotificationHandle
PID:00400003 TID:02BE0006 CHub::AttachDevice
PID:00400003 TID:0225000A HDMI driver not loaded
PID:00400003 TID:0225000A ERROR: c:\wince800\public\common\oak\drivers\keybd\laymgr\laymgr.cpp line 4341: PID:00400003 TID:0225000A Keyboard: 'DeviceKeypad' did not call KeybdMDDRegisterGUID() in its entry function, all events will be associated with the default keyboard.
PID:00400003 TID:0225000A KeybdDriverInitializeEx: Layout Manager successfully initialized to 1
PID:00400003 TID:0225000A LayoutMgrActivateKeyboardLayout: Called with hkl = 0x00000409
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400003 TID:0225000A TchPdd_Ioctl: IOCTL_TOUCH_GET_CALIBRATION_POINTS
PID:00400002 TID:00570002 SoftRTC disabled
PID:00400003 TID:02BE0006 CHub::AttachDevice
PID:00400003 TID:0390000E CHub::AttachDevice
PID:00400002 TID:03D20002 VBUS Event
PID:00400002 TID:03D20002 TWL_USB_VBUS_INT_LATCH_SET is 0x8c
PID:00400003 TID:03DE0002 OMAPMHSUSBIdGnd::Received VBUS_SESS_VLD_EVENT_INDEX event
PID:00400002 TID:03C60002 OMAPMHSUSBOTG::ThreadRun: WAIT_TIMEOUT reached, stopping USB Clock
PID:00400002 TID:03C60002 +StopUSBClock: usage count=0
PID:00400002 TID:03C60002 StopUSBClock: REALLY STOPPING USBPHY CLOCK
PID:00400002 TID:0399000E !USBD: Could not load driver for attached device
Both NK.Bin shows same behaviour. https://www.yousendit.com/download/UlRTT216ays4aU5BSXRVag is the link you shared.
And WLAN driver (tiwlanapi.dll) is not including to NK.Bin if we build by enabling mini shell using mini shell batch file.
Please check the issue.
Thanks and Regards
ASWIN PP
