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 Build Environment Instructions

From Texas Instruments Wiki
Jump to: navigation, search
Construction Icon small.png 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.

Getting Started Guide[edit]

Please refer to the WiKi page at WinCE Getting Started under the Getting Started section for more information about the build environment and about loading the images on the EVM.

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.

Build Environment Instructions[edit]

Please refer to the WiKi page at WinCE Build Environment for more information about the build environment instructions.

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.

Build Image009.jpg

Release Content[edit]

Prerequisites[edit]

Hardware[edit]

  • OMA3EVM Rev-G Board
    • With a Rev C processor module
  • WL1271 Daughter card

Software[edit]

  • Visual Studio 2005
  • Windows Embedded CE 6.0 R3
  • TI OMAP 3530 BSP v6.13 for Windows Embedded CE 6.0
  • WL1271 Driver for Windows Embedded CE 6.0 v.6.x-WL6.1.4.1, which includes:
    • WLAN and BT binaries
    • Sample runtime image
    • Sample OSDesigns
    • Documentation

Note: This release can be downloaded from the WiKi page at www.ti.com/connectivitywiki under Downloads.

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.

Setting up the Build environment[edit]

Setting Up the development Computer[edit]

Before starting anything, the driver package should be installed on the development machine. Install Procedure:

  • Launch “WL1271 Driver for Windows Embedded CE 6.0 v.6.x-WL6.1.4.1.exe” and accept license agreement by clicking on “Next”.
  • Select your WINCE600 directory and click “Next”.

Build Image011.jpg

  • Click on “Install”, and then “Terminate”.

Build Image013.jpg

Build Image015.jpg

Note: After checking the destination folder displayed in this dialog box, you should answer Yes to the question. This will then install the driver files in the appropriate folders without erasing any existing of your project or files. Except if you already installed a previous version of the WL1271 driver

Folders organization and content[edit]

The root folder is the installation path specified during the installation (c:\WINCE600) and will be named $(_WINCEROOT) in the next document instructions.

The installation creates two folders where sources, binaries and configuration files are located: $(_WINCEROOT)\ OSDesigns $(_WINCEROOT)\ 3rdParty

Sample OS Design[edit]

The sample OS Designs folder contains the configuration files that will allow you to build a pre configured runtime image.

  • WL1271_For_Testing : This OS Design is the most appropriate for testing of the driver
  • WL1271_For_TI_EVM_3530: This OSDesign is the most appropriate for demonstration of the WL1271 chipset capabilities like web browsing, A2DP audio streaming…

For more details on the way to build those samples, have a look to Chapter 4

Third Party folder[edit]

The 3rdParty folder contains all the drivers and source code, including some sample applications.

  • AdeneoEmbedded : All the software is provided as evaluation version to illustrate the Bluetooth capabilities of Windows Embedded CE 6.0 R3
  • TI_ECS : WL1271 driver and related source code
AdeneoEmbedded[edit]

The Bluetooth Manager from Adeneo Embedded provides a way to exploit the Bluetooth capabilities of Windows Embedded CE.

Note: For more details about this product check out the BTHMGR-CE60-02J-US User Manual.pdf located in the Doc folder.


TI_ECS[edit]

The TI_ECS folder contains all the files and binaries for the WL1271 chipset:

  • Docs : All the documentation including this document
  • Images : Sample run time images
  • X86 : Windows desktop binaries for testing purposes
  • WL1271 : driver and sample source code for WL1271 configuration

Configuring the TI EVM 35xx BSP[edit]

The TI EVM 35xx BSP comes with different configuration batch files corresponding to the different version of the EVM Hardware revisions. The latest hardware revision is revision G and named EVM 2.

Generic batch file customization for TI EVM 35xx Rev G[edit]

First the generic file should be renamed in order to get the basic set of configuration for the EVM2 board. In folder $(_WINCEROOT)\PLATFORM\TI_EVM_3530,

1. remove file named ti_evm_3530.bat
2. rename evm2_ti_evm_3530.bat into ti_evm_3530.bat
3. In ti_evm_3530.bat file
   a. Line 182 : 
               Is: set BSP_EVM2_VIDEO_CAPTURE=1
               Should be: REM set BSP_EVM2_VIDEO_CAPTURE=1
   b. Line 364 :
               Is: set BSP_NONLED=
               Should be: set BSP_NONLED=1
   c. Line 417 :
               Is: set BSP_NO_CUSTOM_SDMEMORY=1
               Should be: REM set BSP_NO_CUSTOM_SDMEMORY=1

Building provided OS Designs[edit]

Open the sample OS Design[edit]

From Visual Studio 2005, Open the solution file (.sln) located in the $(_WINCEROOT)\OSDesigns sub folders. Those OSDesigns integrate the driver with WLAN and Bluetooth support and the mandatory component to get an On The Shelves runtime image ready for testing.

Build Image017.jpg

Build the sample OS Design[edit]

1. Select a Release build from the Configuration Manager accessible through the Build Menu.

Build Image019.jpg

Build Image022.jpg

2. Launch the build using the Build menu and Build Solution or by pressing F7.

Uild Image024.jpg

The build process is a long process and could take approximately 25 to 40 minutes depending on the performance of your development machine.

Run the sample OS Design Runtime image[edit]

Using the SDCard prepared following the Getting Started Guide document instructions, copy on it the nk.bin file located in the build folder. For example for the WL1271_For_Testing sample OSDesign the file is in following folder: $(_WINCEROOT)\OSDesigns\WL1271_For_Testing\WL1271_For_Testing\RelDir\TI_EVM_3530_ARMV4I_Release

Integrating driver in an OS Design[edit]

Catalog Item[edit]

To access the catalog items view, there are 2 possibilities:

  • By clicking on “Catalog Items View” tab
  • By clicking on “View -> Other Windows -> Catalog Items View” on Platform Builder Menu.

Build Image026.jpg

The driver installation includes into the catalog of Windows Embedded CE plug-in for Visual Studio different items that could be selected to include features into your Runtime image.

Build Image027.jpg

TI – WL1271

  • Bluetooth
    • Bluetooth Support : Bluetooth driver and all mandatory dependencies
  • WL1271 Tools
    • Serial Test Application : Allow SPP demonstration
    • WL1271 Logger : driver debug logger application server
    • WL1271 Manager Applet : control panel applet for driver configuration
    • WL1271 Manager Standalone : configuration application
  • WLAN
    • Security Support
      • WPA Encryption : include support for WPA protected networks
      • WPA2 Encryption : include support for WPA2 protected networks
  • WLAN Support : WLAN driver and all the mandatory dependencies

Note: The support for Open and WEP networks are by defatult enabled in the OS. So no needs to choose those options in your catalog.

Select the features that you would like to enable in the runtime image and build the OS Design using the Build Solution entry of the Build menu