'How To' Setup TI 44XX Embedded Compact...INC2 21 Nov 2012 Ken Rabold Updated for INC2 INC2.06 8 Jan...

TI Proprietary Information — Strictly Private

OPBU "HOW TO" SETUP TI_44XX EMBEDDED COMPACT

Document Revision: INC2.09

Issue Date: 15 Mar 2013

BSP W24.INC2.09 Windows CE

TI Proprietary Information — Strictly Private

CS_Generic_MgmtDoc_Tmpl_95_00_02_02764

Revision 1.4 – 30 August 2005

ii

“Texas Instruments™” and “TI™” are trademarks of Texas Instruments

The TI logo is a trademark of Texas Instruments

OMAP™ is a trademark of Texas Instruments

OMAP-Vox™ is a Trademark of Texas Instruments

Innovator™ is a Trademark of Texas Instruments

Code Composer Studio™ is a Trademark of Texas Instruments

DSP/BIOS™ is a Trademark of Texas Instruments

eXpressDSP™ is a Trademark of Texas Instruments

TMS320™ is a Trademark of Texas Instruments

TMS320C28x™ is a Trademark of Texas Instruments

TMS320C6000™ is a Trademark of Texas Instruments



All other trademarks are the property of the respective owner.

Copyright © 2005 Texas Instruments Incorporated. All rights reserved.

Information in this document is subject to change without notice. Texas Instruments may have pending

patent applications, trademarks, copyrights, or other intellectual property rights covering matter in this

document. The furnishing of this document is given for usage with Texas Instruments products only and

does not give you any license to the intellectual property that might be contained within this document.

Texas Instruments makes no implied or expressed warranties in this document and is not responsible for the

products based from this document.

iii TI Proprietary Information — Strictly Private

Error! Unknown document property name. Windows CE BSP W24.INC2.09

"How To" Setup TI_44XX Embedded Compact Revision INC2.09 15 Mar 2013

Table of Contents Table of Contents ....................................................................................................................................... iii

List of Figures ........................................................................................................................................... iv List of Tables ............................................................................................................................................ iv

Revision History .......................................................................................................................................... v

Plan Approvals ............................................................................................................................................ v

1 Introduction ......................................................................................................................................... 1 1.1 Purpose .......................................................................................................................................... 1 1.2 Scope ............................................................................................................................................. 1 1.3 File Name ....................................................................................................................................... 1 1.4 File Location ................................................................................................................................... 1

2 Hardware Setup ................................................................................................................................... 2

3 Virtual Serial Port Driver Setup .......................................................................................................... 2

4 Building Bootloader and OS Images ................................................................................................. 3 4.1 Build Bootloader and CEBASE (Minkern) Images ......................................................................... 3 4.2 Build Environment Variables .......................................................................................................... 4

5 Flashing Bootloader and OS Images ................................................................................................ 5 5.1 Bootloader and OS image on SD Card .......................................................................................... 5 5.2 Bootloader and OS image on eMMC module (Blaze/Tablet2) ....................................................... 5

6 Running OS Images ............................................................................................................................ 5 6.1 Selecting bootloader storage media (SDP44XX) ........................................................................... 5 6.2 Selecting bootloader storage media (Blaze) .................................................................................. 6 6.3 Selecting bootloader storage media (Tablet2) ............................................................................... 6 6.4 Run Minkern Image in RAM ........................................................................................................... 7

7 KITL Debugging ................................................................................................................................... 8 7.1 USB SERIAL KITL .......................................................................................................................... 8 7.2 RNDIS KITL .................................................................................................................................... 8 7.3 Ethernet KITL ................................................................................................................................. 9 7.4 Associating PB with the TI_SDP44XX for KITL debugging: ........................................................ 10

8 Tips and Tricks .................................................................................................................................. 11

iv TI Proprietary Information — Strictly Private



List of Figures

No table of figures entries found.

List of Tables

No table of figures entries found.

v TI Proprietary Information — Strictly Private



Revision History

REV DATE AUTHOR NOTES

0.1 4 Dec 2009 Ken Rabold DRAFT version ER1.0

0.2 22 Dec 2009 Ken Rabold DRAFT version ER2.0

0.3 25 Feb 2010 Ken Rabold DRAFT version ER3.0

0.4 25 Feb 2010 Albert Chung Add instructions on flashing eMMC

0.5 30 Mar 2010 Albert Chung Add instructions on using bootloader

1.0 15 Apr 2010 Ken Rabold Version R1

1.1 26 Apr 2010 Ken Rabold Updated with Blaze instructions

2.0 10 Jun 2010 Ken Rabold Updated for R2 release

3.0 8 Jul 2010 Ken Rabold Updated for R3 release

4.0 6 Aug 2010 Ken Rabold Updated for R4 release

5.0 13 Sept 2010 Ken Rabold Updated for R5 release

6.0 1 Oct 2010 Ken Rabold Updated for R6 release

7.0 1 Nov 2010 Ken Rabold Updated for R7 release

8.0 3 Dec 2010 Ken Rabold Updated for R8 release

10.0 26 Jan 2011 Ken Rabold Updated for R10 release

11.0 25 Feb 2011 Ken Rabold Updated for R11 release

12.0 25 Mar 2011 Ken Rabold Updated for R12 release

13.0 25 Apr 2011 Ken Rabold Updated for R13 release

14.0 27 May 2011 Ken Rabold Updated for R14 release

15.0 18 Jun 2011 Ken Rabold Updated for R15 release

16.0 15 Jul 2011 Ken Rabold Updated for R16 release

17.0 13 Aug 2011 Ken Rabold Updated for R17 release

19.0 17 Oct 2011 Ken Rabold Updated for R19 release

21.0 10 Dec 2011 Ken Rabold Updated for R21 release (Beta Release)

INC2 21 Nov 2012 Ken Rabold Updated for INC2

INC2.06 8 Jan 2013 Ken Rabold Updated for INC2.06 R6

Plan Approvals

REV APPROVAL 1 DATE APPROVAL 2 DATE

Please read the “Important Notice” on the next page.

vi TI Proprietary Information — Strictly Private



IMPORTANT NOTICE

Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications,

enhancements, improvements, and other changes to its products and services at any time and to

discontinue any product or service without notice. Customers should obtain the latest relevant information

before placing orders and should verify that such information is current and complete. All products are sold

subject to TI’s terms and conditions of sale supplied at the time of order acknowledgment.

TI warrants performance of its hardware products to the specifications applicable at the time of sale in

accordance with TI’s standard warranty. Testing and other quality control techniques are used to the extent

TI deems necessary to support this warranty. Except where mandated by government requirements, testing

of all parameters of each product is not necessarily performed.

TI assumes no liability for applications assistance or customer product design. Customers are responsible

for their products and applications using TI components. To minimize the risks associated with customer

products and applications, customers should provide adequate design and operating safeguards.

TI does not warrant or represent that any license, either express or implied, is granted under any TI patent

right, copyright, mask work right, or other TI intellectual property right relating to any combination, machine,

or process in which TI products or services are used. Information published by TI regarding third-party

products or services does not constitute a license from TI to use such products or services or a warranty or

endorsement thereof. Use of such information may require a license from a third party under the patents or

other intellectual property of the third party, or a license from TI under the patents or other intellectual

property of TI.

Reproduction of information in TI data books or data sheets is permissible only if reproduction is without

alteration and is accompanied by all associated warranties, conditions, limitations, and notices.

Reproduction of this information with alteration is an unfair and deceptive business practice. TI is not

responsible or liable for such altered documentation.

Resale of TI products or services with statements different from or beyond the parameters stated by TI for

that product or service voids all express and any implied warranties for the associated TI product or service

and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements.

Following are URLs where you can obtain information on other Texas Instruments products and application

solutions:

1 Products 2 Applications

Amplifiers amplifier.ti.com Audio www.ti.com/audio

Data Converters dataconverter.ti.com Automotive www.ti.com/automotive

DSP dsp.ti.com Broadband www.ti.com/broadband

Interface interface.ti.com Digital Control www.ti.com/digitalcontrol

Logic logic.ti.com Military www.ti.com/military

Power Mgmt power.ti.com Optical Networking www.ti.com/opticalnetwork

Microcontrollers microcontroller.ti.com Security www.ti.com/security

Telephony www.ti.com/telephony

Video & Imaging www.ti.com/video

Wireless www.ti.com/wireless

Mailing Address: Texas Instruments Post Office Box 655303 Dallas, Texas 75265

Copyright © 2005, Texas Instruments Incorporated



TI Proprietary Information —Strictly Private1.4 Page 1

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: TI_SDP44XX W24.INC2.09 (same BSP source for both Blaze and Tablet2)

1.3 File Name

The file name of this document is HOWTO_Setup_TI_SDP44XX_EmbeddedCompact.docx.

1.4 File Location

This document shall be captured in ClearCase® path defined in the project CM Plan:

OMAPSW_wince\WINCEROOT\docs\Releases\WinCE_24.x




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:

a. Copy the folder PowerVR to the adaptation kit’s public directory

b. set SYSGEN_POWERVR=1

c. set BSP_MODIFY_DDI=%_PUBLICROOT%\powervr\oak\lib\%_TGTCPU%\%WINCEDEBUG%\ddi_powervr.lib

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 -


For Embedded Compact 8 (Canby), Blaze OMAP4470 -


For Embedded Compact 8 (Canby), Tablet2 OMAP4470 -


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

http://en.kioskea.net/download/download-127-hp-usb-disk-storage-format-tool




6.2 Selecting bootloader storage media (Blaze)



S3 S2

1 2 3 4 1 2 3 4 5 6 7 8


S3 S2

1 2 3 4 1 2 3 4 5 6 7 8

6.3 Selecting bootloader storage media (Tablet2)



S2

1 2 3 4 1 2 3 4 5 6 7 8


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

http://ttssh2.sourceforge.jp/




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 (FileOpen… 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 ‘TargetConnectivity 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.




8 Tips and Tricks

Leave the debugger “off” until you need it:

Setting IMGNODEBUGGER=1 and running makeimg will remove the kernel debugger from the image. This will eliminate the symbol loading and DLL checking during bootup which will help speed up boot times on Windows CE images. KITL is still active and the Windows CE> shell interface can still be used. After the OS is fully running, you can load the debugger using the Windows CE> s loaddbg command. The debugger will load and you will have fully debugging capabilities again.

Override DLLs/EXEs in the OS image from the release directory:

Platform Builder has a mechanism to load specific DLLs and/or EXEs from the release directory instead of the OS image. Select Target->Release Directory Modules to select which DLLs/EXEs to load from the release directory. This allows for quicker turnaround time when changing source code for a module as a full makeimg and flashing of the OS is not needed. Once a full OS image is flashed to the SDP, you can reboot and select in the bootloader Boot from IPL to load the OS from flash directly.

Booting an OS image standalone (no PB or KITL connection)

To boot the OS in standalone mode, set the bootloader options in the following manner:

1) Select the Boot Device to be “NK from eMMC”

2) Select the Network Settings to Disable KITL

3) Select the Network Settings to Disable DHCP

4) Save the settings

The OS will boot in standalone mode every time the device is powered up with these bootloader settings.

Use DISABLE_OPTIMIZER=1 for debugging

The DISABLE_OPTIMIZER environment variable is useful for creating DLLs and EXEs that are easier to debug with using Platform Builder. This variable disables all the compiler optimizations which can cause the PB debugger to not resolve variables or breakpoints. Do not use this option when compiling the bootloader as it will expand the size of bootloader binary and it will not fit in the allotted flash size.

'How To' Setup TI 44XX Embedded Compact...INC2 21 Nov 2012 Ken Rabold Updated for INC2 INC2.06 8 Jan...

Documents

Transcript of 'How To' Setup TI 44XX Embedded Compact...INC2 21 Nov 2012 Ken Rabold Updated for INC2 INC2.06 8 Jan...