NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.
User:OMAP35x Wireless Connectivity WinCE Getting Started Guide
 |
This page is currently under construction. The content of this page is due to change quite frequently and thus the quality and accuracy are not guaranteed until this message has been removed. Please feel free to contribute to this page while construction is in progress. |
Overview[edit]
Accessing Information[edit]
WiKi Page[edit]
Please refer to the WiKi page at OMAP35xx Wireless Connectivity for more information about the connectivity solution.
Build Environment Instructions[edit]
Please refer to the WiKi page at WinCE Build Environment for more information about the build environment instructions.
Demo Application[edit]
Please refer to the WiKi page at WinCE Demo under the Demo section for more information about Bluetooth and WLAN demo applications.
Download Files[edit]
Please refer to the WiKi page at www.ti.com/connectivitywiki under Downloads to download the most update software release.
Videos[edit]
Please refer to the WiKi page at www.ti.com/connectivitywiki under Videos to view video tutorials.
Release Content[edit]
Prerequisites[edit]
- OMAP3 EVM Rev-G Board
- With a Rev C processor module
- WL1271 Daughter card Rev B
Hardware[edit]
- WL1271 Driver for Windows Embedded CE 6.0 v6.x-WL6.1.4.1.exe release file, which includes:
- WLAN and BT binaries
- Sample runtime image
- Sample OSDesigns
- Documentation
Note:This release can be downloaded from the WiKi page at OMAP35xx Wireless Connectivity under Downloads.
Software Installation[edit]
The “WL1271 Driver for Windows Embedded CE 6.0 v.6.x-WL6.1.4.1.exe” file contains the following folders/binaries:
| Content | Description |
|---|---|
| OSDesigns | Contains sample runtime image configuration |
| Images | Contains demonstration runtime images and recovery tool |
| Docs | Contains the driver documentation |
| WL1271 | Contains the driver sources and binaries |
| X86 | Contains additional tools for Windows |
Install Procedure:
- Launch “WL1271 Driver for Windows Embedded CE 6.0 v6.x-WL6.1.4.1.exe” and accept license agreement by clicking on “Next”.
- Select your WINCE600 directory and click “Next”.
- Click on “Install”, and then “Terminate”.
Tools[edit]
The following tools must be downloaded from the web:
- Tera Term (optional): A serial port terminal program should be used to communicate with the OMAP35x EVM board’s serial port console. This tool is required for running the WLAN and BT demos. TeraTerm is the recommended terminal emulator for Windows.
- It can be downloaded from Download Teraterm
Setting up the System[edit]
Setting Up the Host Computer[edit]
The Host computer must be a PC running Linux or Windows that supports telnet client application.
Setting Up the Target System[edit]
The OMAP3 EVM development has a number of possible combinations for a number of hardware interfaces. These combinations are determined by the definitions of the jumper settings and a dip switch.
DIP Switch Settings[edit]
The OMAP3530 processor supports various boot modes. On the OMAP3530 development boards, the boot modes are selected by setting various dip-switch combinations. On the OMAP3 EVM development board, this switch is labeled SW4. The dip switch settings for the various boot modes are as follows:
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | |
|---|---|---|---|---|---|---|---|---|
| OMAP3EVM With Micron NAND | ON | ON | ON | OFF | OFF | ON | OFF | OFF |
Setting Up the WLAN DC Hardware[edit]
To setup the WLAN DC hardware:
1. Mount the daughter card as shown below:
The following shows the picture of the daughter board on its own.
2. Check that jumper J8 is connected between terminal 1 and 2 in order to enable normal use, as shown below:
3. Check that jumper JP2 is connected. This jumper is only used if the board is modified to power up from the USB connectors, as shown below:
4. Verify that jumpers J2 and J3 are not connected, as shown below:
5. Check that jumper JP1 is either not connected or connected between 1-2 for normal use, as shown below:
First platform system formatting[edit]
Due to some incompatibility between Linux and Windows CE NAND Flash content management, the on board Nand Flash should be formatted first before use time with Windows CE. This is also true for first time use of the evaluation kit. This action is required once when switching from Linux runtime image to Windows CE, to clean up the flash content.
To format the on board Nand Flash
1. Install the EVM Flash tool for Micron Flash located in X:\WINCE600\3rdParty\TI_ECS\Images\Recovery\EVMFlashTool_vEVM2MicronNAND 2. From file explorer :
a. Go to : X:\Program Files\Texas Instruments\EVMFlash3530_v2.0\usb_drv_windows
b. Duplicate file evmflashusb.sys into csstusb.sys
3. Set the SW4 to :
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | |
|---|---|---|---|---|---|---|---|---|
| OMAP3EVM With Micron NAND | OFF | OFF | ON | OFF | OFF | OFF | OFF | OFF |
4. Connect the USB cable to your computer using the USB OTG connector located close to the power supply connector.
Note: For OMAP driver installation process please refer to the document EVMFlash User Guide.pdf
Note: binaries (MLO, EBOOTSD.nb0 and NK.BIN) are located in X:\WINCE600\3rdParty\TI_ECS\Images\Recovery
5. Open the EVM Flash application
a. elect the Link type to USB and BOOT ROM
b. Click download in the left tree
c. Erase tab
d. Select NAND and check the Erase entire option
e. Then Erase and follow instructions on the screen
f. Once erase succeeded close the application
Note: The wizard provided in the application is looking for OMAP 3430 and not 3530 so do not get confused.
To load the images to the SD Card
Preparing the SD Card to be bootable on the EVM: Use SD card boot utility Install the TI_SDCard_boot_utility_v1_0.exe that can be found in X:\WINCE600\3rdParty\TI_ECS\Images\SDCard_boot_utility folder in the SW distribution.
Step 1. Run the installed utility
Step 2. Select the SD card drive
Step 3. In the “second step” application area (MLO File), browse and Select the MLO file located in X:\WINCE600\3rdParty\TI_ECS\Images\Recovery
Step 4. In the “third step” application area (OS Files), browse and Select the EBOOTSD.NB0 file
Step 5. Click Proceed.
Click "Start" to format the SD card
Click "OK" for Format Warning
Click "OK" once "Format Complete" window pops up
Click "Close" to close the format window
Click "Quit" once the files are copied
Note: binaries (MLO and EBOOTSD.nb0) are located in X:\WINCE600\3rdParty\TI_ECS\Images\Recovery
Boot from SD Card to automatically format
1. Change the SW4 dip switch configuration for the system to boot from SDCard
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | |
|---|---|---|---|---|---|---|---|---|
| OMAP3EVM With Micron NAND | ON | ON | ON | OFF | OFF | ON | OFF | OFF |
2. Insert the SD Card into the SD Card slot, and power up the board.
3. Wait 1 minute or check the output using the serial port (UART3).
You should see the following on UART3:
Texas Instruments Windows CE SD X-Loader for EVM 3530
Built Apr 16 2010 at 08:46:26
Version 6.13.00
open ebootsd.nb0 file
Init HW: controller RST
read ebootsd.nb0 file
jumping to ebootsd image
Note: After this formatting, the binaries you have on the SD Card could not be used to load a Windows CE runtime image. So make sure to follow carefully the next instructions to replace those binaries with valid one.
Loading the Images[edit]
Setting Up the Hardware for Loading[edit]
To load the images to the SD Card
1. Preparing the SD Card to be bootable on the EVM: Use SD card boot utility Install the TI_SDCard_boot_utility_v1_0.exe that can be found in X:\WINCE600\3rdParty\TI_ECS\Images\SDCard_boot_utility folder in the SW distribution.
Step 1. Run the installed utility
Step 2. Select the SD card drive
Step 3. Browse and Select the MLO file
Step 4. Browse and Select the EBOOTSD.NB0 and NK.BIN files
Step 5. Click Proceed.
Click "Start" to format the SD card
Click "OK" for Format Warning
Click "OK" once "Format Complete" window pops up
Click "Close" to close the format window
Click "Quit" once the files are copied
Note: binaries (MLO, EBOOTSD.nb0 and NK.BIN) are located in X:\WINCE600\3rdParty\TI_ECS\Images\OMAP 35x EVM RevG
2. Connect the EVM with a serial cable and an Ethernet cable, as shown below:
Starting to Load[edit]
The following procedure describes how to start loading the Kernel WLAN and BT images.
To start loading the Kernel (nk.bin):
1. Connect the OMAP35x EVM to the power supply and hit any key in order to boot the device, as shown below:
Texas Instruments Windows CE SD X-Loader for EVM 3530
Built Apr 16 2010 at 08:46:26
Version 6.13.00
open ebootsd.nb0 file
Init HW: controller RST
read ebootsd.nb0 file
jumping to ebootsd image
Microsoft Windows CE Bootloader Common Library Version 1.4 Built Apr 16 2010 08:42:42
Texas Instruments Windows CE EBOOT for Mistral OMAP EVM, Built Apr 16 2010 at 08:46:17
EBOOT Version 1.1, BSP 6.13.00
TI OMAP3530 Version 0x4b7ae02f (ES3.1)
TPS659XX Version 0x10 (Unknown)
System ready!
Preparing for download...
INFO: Predownload....
WARN: Boot config wasn't found, using defaults
INFO: SW4 boot setting: 0x18
Hit space to enter configuration menu 5...
Hit space to enter configuration menu 4...
Hit space to enter configuration menu 3...
Hit space to enter configuration menu 2...
Hit space to enter configuration menu 1...
Init HW: controller RST
BL_IMAGE_TYPE_BIN
Download file information:
[0]: Address=0x84001000 Length=0x025fd9f0 Save=0x80001000
Download file type: 1
2. After wait until the Kernel finishes booting up.
Configure wired network interface[edit]
Finalize the configuration
1. Set the IP address of the PC and the EVM in the same subnet. For example, set the PC address to 192.168.1.100 and the EVM Ethernet IP address to 192.168.1.10.
a. To change the EVM IP Address, open the Start -> Settings -> Network and Dial-up Connections
b. Select the network interface (SMSC91181) in the list and choose File -> Properties menu
c. Enter IP address: 192.168.1.10
Connecting[edit]
This chapter describes from the GUI and command line the way to connect to an access point. The network configuration performed in previous chapter should be correct in order to use the telnet interface.
Calibrate the WLAN interface[edit]
Before performing any test or any connection, it is very important to run the Tx BiP calibration based on the reference points provided in the registry. Calibration data is saved in registry. Using the WL1271 Manager performs the following steps.
1. Launch the WL1271 Manager
2. Open the configuration Window for WLAN interface
3. Perform the calibration
4. Once calibration is done go back to the WL1271 Manager main window, disable the WLAN interface, wait few seconds, and re-enable it. This will force the reload of the firmware and configuration information (including calibration settings) onto the chipset.
Connecting to target with Telnet[edit]
In the next steps you will have the choice to perform the action using the device touch screen, or from a telnet connection. The information below is provided as reference for future use.
Open telnet connection[edit]
To connect to the target through telnet, enter from the command line window on your computer the following command:
telnet 192.168.1.10
Starting the WLAN and Connecting to an Access Point[edit]
To start the WLAN and connect to an access point using CLI:
1. From the telnet shell launch ticon.exe
\> ticon
user_main, start
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/,
Wer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
Connecting to an Unsecured WLAN Network[edit]
To connect to an unsecured WLAN network GUI: 1. Display the list of the available Access Point. If window doesn’t show up, click on the network icon located in the task bar.
2. Select the desired network and hit the connect button.
Note: If the open network is protected with a WEP passphrase, then the application will ask you for providing the login and password for the selected network.
To connect to an unsecured WLAN network from ZeroConfig Tool:
1. In the telnet window, connect to the target 2. Use ZeroConfig Tool or wzctool application to connect to the unsecured network named AP-SSID, with key 1 set to 0x1234567890
Wzctool -ssid AP-SSID -auth open -encr wep -key 1/0x1234567890
To connect to an unsecured WLAN network from CLI:
Note: Before using the CLI you must specify to windows ce ZeroConfig tool to disconnect from the WLAN driver. In the Wireless network list, unselect the “Notify me when new wireless networks are available” check box located on the main window, and the “Use Windows to configure my wireless settings” check box located in the “Advanced Wireless Settings window” accessible by hitting the “Advanced” button on the main window.
1. In the CLI, press a to access the scan menu, as shown below:
a
.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
2. In the Scan menu, press s to start the scan, as shown below:
s
Application scan started
Scanning for access points starts. The scan is completed after a few seconds and no further indication is provided when the scan is completed.
3. Press / to return to the CLI main menu.
/
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/
, dEbug/, biT/, aboUt, Quit
4. Press c to access the Connection menu.
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
5. Press b to display the full Bssid_list. The full Bssid_list shows the list of access points discovered during the scan process, as shown below:
b
BssId List: Num=8
MAC Privacy Rssi Mode Channel SSID
00.1c.f9.2f.c6.32 0 -83 Infra 1 B
00.16.47.93.66.20 1 -74 Infra 1 ****
00.16.47.93.66.21 0 -75 Infra 1 ****
00.50.f1.12.03.38 1 -81 Infra 1 yaelb
00.16.46.c6.2b.90 1 -74 Infra 6 ****
00.15.c6.5f.62.50 0 -72 Infra 6 123
00.14.a8.a0.ec.10 0 -51 Infra 11 theseus
00.12.01.4d.da.70 1 -82 Infra 11 Cat
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs
6. Connect to one of the access points listed in the Bssid_list. The following example connects to an access point named theseus. This access point has 0 in the Privacy field, indicating that this access point is not secured.
c theseus
Trying to associate with SSID 'theseus'
Associated with 00:14:a8:a0:ec:10
************ NEW CONNECTION ************
-- SSID = theseus
-- BSSID = 0-14-a8-a0-ec-10
****************************************
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
The EVM is now connected to the AP.
7. From any submenu, press / q to exit the CLI menu and return to the linux prompt, as shown below:
/ q
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/
, dEbug/, biT/, aboUt, Quit
root@omap3evm:~/DEMO/wlan#
Verifying the Connection to the Access Point[edit]
A simple ping test can be used to verify the connection to the access point.
To verify connection with the access point:
1. Use the hardware setup to run the ping test:
2. In the CLI menu, type /q to exit the CLI and return to the linux prompt, as shown below:
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/
, dEbug/, biT/, aboUt, Quit
\>
3. Configure the EVM WLAN IP address and make sure that the EVM Ethernet port and WLAN port do not share the same IP subnet address.
Note: To change the IP Address of the WLAN interface, follow the instructions for 4.1Setting Up the Hardware for Loading, but select TIWLNAPI1 network interface instead of the SMSC one.
4. Verify that the WLAN interface (tiwlnapI1) IP address is configured correctly, as shown below:
\> ipconfig
Windows IP configuration
Ethernet adapter [TIWLNAPI1]:
IP Address ........ : 192.168.1.70
Subnet Mask ....... : 255.255.255.0
Ethernet adapter [BTPAN1]:
IP Address ........ : 0.0.0.0
Subnet Mask ....... : 0.0.0.0
Ethernet adapter [SMSC91181]:
IP Address ........ : 192.168.1.10
Subnet Mask ....... : 255.255.255.0
5. Configure the IP address of the laptop that is connected to the access point via the Ethernet cable to be in the same subnet as the EVM WLAN port. In this example, it is configured to 192.168.1.100. The gateway IP address is not important for this test.
6. Use the Ping command to ping the PC that is connected to the access point. In the EVM menu, type the following:
\>ping 192.168.1.100
Pinging Host 192.168.1.100
Reply from 192.168.1.100: Echo size=32 time=95ms TTL=128
Reply from 192.168.1.100: Echo size=32 time=48ms TTL=128
Reply from 192.168.1.100: Echo size=32 time=67ms TTL=128
Reply from 192.168.1.100: Echo size=32 time=64ms TTL=128\>
