mcus (eclipse ide) as shown in figure 1. um11325 special ... · 8 / 22 figure 4. connection between...

UM11325Installing and using CodeWarrior IDE for TPMS for FXTH87,FXTH87E and NTM88Rev. 1 — 9 January 2020 User guide

1 Installing CodeWarrior v11.1 or above

NXP offers a variety of CodeWarrior (CW) development tools on NXP.com. NXP'stire pressure monitoring system (TPMS) solutions for FXTH87, FXTH87E and NTM88use CodeWarrior for MCUs, the Eclipse integrated development environment (IDE).To download a free, no time limit version of the IDE, visit CodeWarrior Downloads onNXP.com or navigate to NXP.com, Support > All Developer Resources > Software >CodeWarrior Development Tools > Evaluation Software. From the CW downloads page,select the Special button to download the Special Edition version of CodeWarrior forMCUs (Eclipse IDE) as shown in Figure 1.

Figure 1. CodeWarrior Downloads page on NXP.com

The special edition is code-size limited, but the limit is 64 kB, more than the 16 kB TPMSflash size, so the limitation does not apply to TPMS products. On the download page, ifthe “offline” installer is selected, the whole suite will be downloaded with the installer, andaccess to the internet will not be required during the installation process. If the “online”installer is selected, only the core tools will be downloaded with the installer, and the restof the necessary components will be downloaded during the installation process; thelatter thus requires access to the internet during the installation process.

Note: During CodeWarrior software installation retain, do not change the defaultinstallation path proposed by the installer application. The TPMS patch installationdescribed in Section 2 depends on the default installation path. Changing the defaultinstallation path will prevent the proper installation of the TPMS patches. For CW v11.1,the default installation path is “C:\Freescale\CW MCU v11.1”.

Note: The software installation prompts the user to select components as part of theinstallation as shown in Figure 2. For TPMS applications, S08/RS08 is the only requiredcomponent.

https://www.nxp.com/support/developer-resources/software-development-tools/codewarrior-development-tools/downloads:CW_DOWNLOADShttps://www.nxp.com

NXP Semiconductors UM11325Installing and using CodeWarrior IDE for TPMS for FXTH87, FXTH87E and NTM88

UM11325 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2020. All rights reserved.

User guide Rev. 1 — 9 January 20202 / 22

Figure 2. Component selection window

2 Installing the FXTH870000_LIB and NTM88_LIB targets

In the CodeWarrior IDE, after installation the default target “FXTH870000” is the onlyavailable target. This target is used with firmware-based FXTH applications, applicationsthat use the embedded firmware provided by NXP.

FXTH and NTM88 library-based applications, which erase and reload the embeddedfirmware functions from a library, use the targets "FXTH870000_LIB” and NTM88_LIB",respectively. The targets “FXTH870000_LIB” and “NTM88_LIB” are available inCodeWarrior IDE after installing specific patches. These patches are provided with thestarter demo projects that can be downloaded from NXP website. See NXP applicationnote AN12523[1] for additional information on the differences between firmware-basedand library-based applications.

FXTH870000_LIB and NTM88_LIB Patches1:

• The patch com.freescale.mcu11_1.HCS08_FXTH870000_LIB.win.sp.v1.0.4.zipinstalls the target “FXTH870000_LIB”, for library-based FXTH87/87E applications. Thepatch is available in the FXTH Starter Package. Download this package from https://www.nxp.com/design/sensor-developer-resources/tpms-software:TPMS-SOFTWARE.

• The patch com.freescale.mcu11_1.HCS08_NTM88_LIB.win.sp.v1.0.2.zip installs thetarget “NTM88_LIB”, for library-based NTM882 applications. The patch is available inthe NTM88 Starter Package. Download this package from https://www.nxp.com/design/sensor-developer-resources/tpms-software:TPMS-SOFTWARE.

Do not unzip the patch files, the installation uses the files in zip format.

Checking the installed software version for CodeWarrior:

1. Open the CW IDE.2. Select Help > About CodeWarrior Development Studio.3. Verify CW version 11.1 or higher is installed.

CodeWarrior patch installation for FXTH and NTM library-based applications:

1. Ensure CW version 11.1 or higher has been installed, see Checking the installedsoftware version for CodeWarrior.

1 Compatible with CW version 11.1 or above2 NTM88 supports only library-based applications.

https://www.nxp.com/design/sensor-developer-resources/tpms-software:TPMS-SOFTWAREhttps://www.nxp.com/design/sensor-developer-resources/tpms-software:TPMS-SOFTWAREhttps://www.nxp.com/design/sensor-developer-resources/tpms-software:TPMS-SOFTWAREhttps://www.nxp.com/design/sensor-developer-resources/tpms-software:TPMS-SOFTWARE




2. Open the CW IDE.3. Select Help >Install New Software....

4. Selecting Install New Software... opens the Available Software window.

5. On the Available Software window, select the Add... button. The Add Repository

window displays.

6. On the Add repository window, select the Archive... button.7. Navigate to the location of the first patch file to install.8. Select the first patch zip file. Do not unzip the file. The file path and file name of the

zip file appears in the location field of the Add Repository... window.




9. Select the OK button on the Add Repository... window. The focus returns to theAvailable Software... window.

10.On the Available Software... window, select the check box for "MCU v11.1 S08Service Packs".

11.At the bottom of the Available Software... window, select the Next > button to finish

the installation.If the Next button is greyed out and cannot be selected, click on the Select All button,as shown:

12.With the CodeWarrior IDE open, repeat Step 3 through Step 11 for any remaining

patches.13.Close and restart CodeWarrior.

Troubleshooting: during the patch installation, if the error “No repository found…”occurs, this means CW IDE was not installed using the default installation path. Resolvethe error by uninstalling CW and reinstalling CW using the default installation pathproposed by the installer. Do not select a different installation path, or it will notbe possible to install the patches. For CW v11.1, the default installation path is “C:\Freescale\CW MCU v11.1”.




3 Using CodeWarrior IDE

3.1 Importing a project1. Start the CodeWarrior IDE.2. Locate and open the Commander tab on the bottom left of the window.3. Select Import project as shown to open the Import window.

4. On the Import project window, select the Browse... button and navigate to the location

of the project to import.




a. Select Copy project into workspace if you want the project copied inside the

workspace folder.b. Select the Finish... button and the project is imported inside the workspace.

3.2 Building a project1. To build a project, select the "Hammer" icon.

If the "Hammer" icon is not available, double click on any source or header file of aproject which will make the icon selectable.

2. In some projects, several targets are available. This is used to compile the same

project with different options. To display the list of available targets, click on the "downarrow" icon next to the "Hammer" icon.

3. If several targets are available, select the appropriate one. A check mark displays next

to the selected target. The target “FLASH_434_2_AXIS” is selected as shown.




Troubleshooting: If the error ‘No rule to make target’ occurs, clean the project beforebuilding it. To clean the project, right click on the project and select Clean Project.

After the project has been built, several files are created in the output folder:

• .abs file: The .abs file contains the executable information and debugging information.The .abs file is used as input by the debugger.

• .s19 file: The .s19 file contains executable information only. The .s19 file is used asinput by the flash programmer tool.

• .map file: The .map file shows the memory location of the objects used by theapplication. The .map file addresses of all global variables, constants and functions areindicated in this file.

3.3 Hardware setup to program a projectTo program the TPMS, a USB Multilink Universal device from P&E Micro3 is required.For more information about this product, visit the project summary page at NXP.com orsearch http://www.nxp.com for "U-MULTILINK".

The USB Multilink Universal device connects to the TPMS EVB via the connector boardas shown in Figure 3, Figure 4 and Figure 5.

Figure 3. Connector board

3 The P&E Micro Multilink Universal Multilink Development Interface is not a production tool. For moreinformation, visit the PE Micro website.

https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools/universal-multilink-development-interface:UMultilinkhttp://www.nxp.comhttp://www.pemicro.com/products/product_viewDetails.cfm?product_id=15320168&productTab=2




Figure 4. Connection between the Multilink and the TPMS EVB

Figure 5. TPMS EVB interfaced with connector board and attached to computer through aUSB connected Multilink device

For 2.4 GHz EVBs, connect as shown in Figure 6 and Figure 7.




Figure 6. Top view of a powered 2.4 GHz EVB, connector board with Multilink cableattached

Figure 7. Side view of a powered 2.4 GHz EVB, connector board with Multilink cableattached

3.4 Programming a projectThe project can be programmed using either the debugger or the Flash Programmer tool.

3.4.1 Programming a project using the debugger

If the project is programmed with the debugger, a debug session will start afterthe TPMS is programmed. From the debug session, the user can debug theapplication by executing instructions step by step, reading the content of the registers,the content of the memory etc. For more information on how to keep a debugsession active when the application enters STOP1 mode, refer to the documentTPMS_Code_Architecture_for_Debug provided with the demo starter projects.

To program a project with the debugger:

1. Open the Debug Configurations window by selecting the "down arrow" next to thegreen debug icon as shown:




2. On the Debug Configurations window, select the configuration below “CodeWarrior”.

3. If no configuration displays below "CodeWarrior" in the window, double click on

“CodeWarrior” to create one.4. Complete the configuration in the window as shown:




5. Connection configuration:

a. View the existing Connection configuration: To view the configuration of theConnection, select the Edit... button.

b. Or create a new Connection configuration: Select the New... button.c. On the "New Connection" window, select “Hardware or Simulator Connection”.

d. The "Properties for TPMS_BDM" windows appears:




e. Selecting the New... or Edit... button next to the “Target” opens a window to

configure the "Target".

f. Complete the debug configuration window and select the OK button. The window

focus returns to the "Properties for TPMS_BDM" window.g. Apply the configuration and modifications using the Apply button.

6. To start the programming and debug session, click the Debug button.




Note: During programming, the "Power Cycle Dialog" window may display with thefollowing message:

Disconnect the board power supply for a short time (like one second) by turningthe power supply OFF and then ON again, without disconnecting the Multilink fromthe board. On NXP’s evaluation boards, a jumper enables the power supply to bedisconnected.If using the FXTH870000_LIB target or the NTM88_LIB target, one of the followingtwo "CodeWarrior Alert" windows will appear:




The "CodeWarrior Alert" windows are normal for the library in use and simply alertsthe user that trim coefficients are protected and cannot be overwritten. Select the Yesbutton to proceed to programming.

7. When the programming completes, the debug session starts. By default, the programstops at the beginning of the main. Use the buttons shown to perform tasks such asrun or pause the program, step by step debugging, reset the MCU, and terminate thedebug session.

Note: Only one breakpoint can be enabled at a time. By default, the debugger setsone breakpoint, at the beginning of main. It is for this reason the program stops a thebeginning of main after the debug session launches.

8. When the program stops at the beginning of main, another (and only one) breakpointcan be set elsewhere. If several breakpoints are set, only the first breakpoint is takeninto account, the other breakpoints are ignored.




9. With the program paused or stopped at a breakpoint, the user can check the values of

variables, the content of the registers and the content of the memory. Select the greenplus sign (highlighted in red) to indicate the starting address of the section to monitor.

10.On the Memory tab, the content of the memory can be exported. Note that when

using the FXTH870000_LIB or the NTM88_LIB target, the content of the trim sectionis hidden, so the user will see value “0xBA” instead of the actual trim values. Bydefault, the Export memory button is not enabled: enter an address to monitor usingthe green plus sign icon highlighted in the prior image. Select the now active Exportbutton.

Important note: When the program starts after programming, the MCU enters amode that consumes more power than specified in the data sheet. To restart the MCUin normal mode, a Power-On Reset must be completed. After the user terminatesthe debug session, disconnect the Multilink and perform a POR to restart the MCU innormal mode and reach the expected power consumption specified in the data sheet.




3.4.2 Programming a project using the flash programmer

To program a project using the flash programmer without starting a debug session:

1. Start the CodeWarrior IDE.2. Locate and open the Commander tab on the bottom left of the window.3. Select Flash programmer as shown to open the Flash File to Target window.

4. Configure the "Flash File to Target" window as shown:

5. Connection configuration:

a. Select the Edit... button to view the configuration of the connection.b. Or select the New... button to create a new connection.c. When the "New Connection" window opens, select “Hardware or Simulator

Connection”.




d. The "Properties for TPMS_BDM" window opens.

e. Clicking on the Edit... or New... buttons for "Target" opens the target configuration

window.




f. Configure the target as desired

Select the OK button on the target configuration window.g. Select the OK button on the "Properties for TPMS_BDM" window.

6. After configuring the fields, select the Erase and Program button.Do NOT select the Erase Whole Device button. Selecting this button erases allflash, including the trim coefficients. If the trim coefficients are erased, the sensorswill be permanently rendered non-functional.

7. The "Save Resource" windows opens.• To store the settings in the workplace, select the "Save to framework only" radio

button.• To store the settings in a file, select the "Save to file " radio button. Storing the

settings in a file enables the user to import these settings into other workspaces.

During programming, the following Power Cycle dialog message may appear:




Disconnect the board power supply for a short time (like one second) by turningthe power supply OFF and then ON again, without disconnecting the Multilink fromthe board. On NXP’s evaluation boards, a jumper enables the power supply to bedisconnected.

8. When programming completes, perform a Power On Reset to restart the MCU innormal mode in order to reach the expected power consumption specified in the datasheet.

4 AbbreviationsTable 1. AbbreviationsAbbreviations Description

TPMS Tire pressure monitoring system

IDE Integrated development environment

MCU Microcontroller unit

CW CodeWarrior

.abs Executable and debugging information file used as input by the debugger.

.s19 Executable information file used as input by the flash programmer tool.

.map Memory location file of all objects (global variable addresses, constants and functions) used by theapplication.

P&E P&E Microcomputer Systems, Inc.

EVB Evaluation board

POR Power on reset

5 References

[1] AN12523 — Firmware versus Library model applications, application notehttps://www.nxp.com/docs/en/application-note/AN12523.pdf

6 Revision historyTable 2. Revision historyRev Date Description

v.1 20200109 Initial version

https://www.nxp.com/docs/en/application-note/AN12523.pdf




7 Legal information

7.1 DefinitionsDraft — The document is a draft version only. The content is still underinternal review and subject to formal approval, which may result inmodifications or additions. NXP Semiconductors does not give anyrepresentations or warranties as to the accuracy or completeness ofinformation included herein and shall have no liability for the consequencesof use of such information.

7.2 DisclaimersLimited warranty and liability — Information in this document is believedto be accurate and reliable. However, NXP Semiconductors does notgive any representations or warranties, expressed or implied, as to theaccuracy or completeness of such information and shall have no liabilityfor the consequences of use of such information. NXP Semiconductorstakes no responsibility for the content in this document if provided by aninformation source outside of NXP Semiconductors. In no event shall NXPSemiconductors be liable for any indirect, incidental, punitive, special orconsequential damages (including - without limitation - lost profits, lostsavings, business interruption, costs related to the removal or replacementof any products or rework charges) whether or not such damages are basedon tort (including negligence), warranty, breach of contract or any otherlegal theory. Notwithstanding any damages that customer might incur forany reason whatsoever, NXP Semiconductors’ aggregate and cumulativeliability towards customer for the products described herein shall be limitedin accordance with the Terms and conditions of commercial sale of NXPSemiconductors.

Right to make changes — NXP Semiconductors reserves the right tomake changes to information published in this document, including withoutlimitation specifications and product descriptions, at any time and withoutnotice. This document supersedes and replaces all information supplied priorto the publication hereof.

Suitability for use — NXP Semiconductors products are not designed,authorized or warranted to be suitable for use in life support, life-critical orsafety-critical systems or equipment, nor in applications where failure ormalfunction of an NXP Semiconductors product can reasonably be expectedto result in personal injury, death or severe property or environmentaldamage. NXP Semiconductors and its suppliers accept no liability forinclusion and/or use of NXP Semiconductors products in such equipment orapplications and therefore such inclusion and/or use is at the customer’s ownrisk.

Applications — Applications that are described herein for any of theseproducts are for illustrative purposes only. NXP Semiconductors makesno representation or warranty that such applications will be suitablefor the specified use without further testing or modification. Customersare responsible for the design and operation of their applications andproducts using NXP Semiconductors products, and NXP Semiconductorsaccepts no liability for any assistance with applications or customer productdesign. It is customer’s sole responsibility to determine whether the NXPSemiconductors product is suitable and fit for the customer’s applicationsand products planned, as well as for the planned application and use ofcustomer’s third party customer(s). Customers should provide appropriate

design and operating safeguards to minimize the risks associated withtheir applications and products. NXP Semiconductors does not accept anyliability related to any default, damage, costs or problem which is basedon any weakness or default in the customer’s applications or products, orthe application or use by customer’s third party customer(s). Customer isresponsible for doing all necessary testing for the customer’s applicationsand products using NXP Semiconductors products in order to avoid adefault of the applications and the products or of the application or use bycustomer’s third party customer(s). NXP does not accept any liability in thisrespect.

Limiting values — Stress above one or more limiting values (as defined inthe Absolute Maximum Ratings System of IEC 60134) will cause permanentdamage to the device. Limiting values are stress ratings only and (proper)operation of the device at these or any other conditions above thosegiven in the Recommended operating conditions section (if present) or theCharacteristics sections of this document is not warranted. Constant orrepeated exposure to limiting values will permanently and irreversibly affectthe quality and reliability of the device.

Terms and conditions of commercial sale — NXP Semiconductorsproducts are sold subject to the general terms and conditions of commercialsale, as published at http://www.nxp.com/profile/terms, unless otherwiseagreed in a valid written individual agreement. In case an individualagreement is concluded only the terms and conditions of the respectiveagreement shall apply. NXP Semiconductors hereby expressly objects toapplying the customer’s general terms and conditions with regard to thepurchase of NXP Semiconductors products by customer.

No offer to sell or license — Nothing in this document may be interpretedor construed as an offer to sell products that is open for acceptance orthe grant, conveyance or implication of any license under any copyrights,patents or other industrial or intellectual property rights.

Export control — This document as well as the item(s) described hereinmay be subject to export control regulations. Export might require a priorauthorization from competent authorities.

Translations — A non-English (translated) version of a document is forreference only. The English version shall prevail in case of any discrepancybetween the translated and English versions.

Security — While NXP Semiconductors has implemented advancedsecurity features, all products may be subject to unidentified vulnerabilities.Customers are responsible for the design and operation of their applicationsand products to reduce the effect of these vulnerabilities on customer’sapplications and products, and NXP Semiconductors accepts no liability forany vulnerability that is discovered. Customers should implement appropriatedesign and operating safeguards to minimize the risks associated with theirapplications and products.

7.3 TrademarksNotice: All referenced brands, product names, service names andtrademarks are the property of their respective owners.

CodeWarrior — is a trademark of NXP B.V.NXP — is a trademark of NXP B.V.




TablesTab. 1. Abbreviations ...................................................19 Tab. 2. Revision history ...............................................19

FiguresFig. 1. CodeWarrior Downloads page on NXP.com ..... 1Fig. 2. Component selection window ............................2Fig. 3. Connector board ............................................... 7Fig. 4. Connection between the Multilink and the

TPMS EVB ........................................................ 8Fig. 5. TPMS EVB interfaced with connector board

and attached to computer through a USBconnected Multilink device ................................ 8

Fig. 6. Top view of a powered 2.4 GHz EVB,connector board with Multilink cableattached .............................................................9

Fig. 7. Side view of a powered 2.4 GHzEVB, connector board with Multilink cableattached .............................................................9


Please be aware that important notices concerning this document and the product(s)described herein, have been included in section 'Legal information'.

© NXP B.V. 2020. All rights reserved.For more information, please visit: http://www.nxp.comFor sales office addresses, please send an email to: [email protected]

Date of release: 9 January 2020Document identifier: UM11325

Contents1 Installing CodeWarrior v11.1 or above ..............12 Installing the FXTH870000_LIB and NTM88_

LIB targets ........................................................... 23 Using CodeWarrior IDE ...................................... 53.1 Importing a project .............................................53.2 Building a project ...............................................63.3 Hardware setup to program a project ................ 73.4 Programming a project ...................................... 93.4.1 Programming a project using the debugger .......93.4.2 Programming a project using the flash

programmer ..................................................... 164 Abbreviations .................................................... 195 References ......................................................... 196 Revision history ................................................ 197 Legal information ..............................................20

1 Installing CodeWarrior v11.1 or above2 Installing the FXTH870000_LIB and NTM88_LIB targets3 Using CodeWarrior IDE3.1 Importing a project3.2 Building a project3.3 Hardware setup to program a project3.4 Programming a project3.4.1 Programming a project using the debugger3.4.2 Programming a project using the flash programmer

4 Abbreviations5 References6 Revision history7 Legal informationTablesFiguresContents

mcus (eclipse ide) as shown in figure 1. um11325 special ... · 8 / 22 figure 4. connection between...

Documents