CodeWarrior Development Studio for Power Architecture Netcomm

CodeWarrior Development Studio for Power Architecture Netcomm v10.0.1 

Release Note 

CodeWarrior Development Studio for 

Power Architecture Netcomm v10.0.1 

Table of Contents 

1 About This Release ................................................................................................. 2 

1.1 Version Information ........................................................................................... 2 

1.2 Getting Help ...................................................................................................... 2 

1.2.1 Documentation ........................................................................................... 2 

1.3 New in this Release .......................................................................................... 4 

1.3.1 Product Level Features .............................................................................. 4 

1.3.2 Documentation ........................................................................................... 4 

1.3.3 Debugger ................................................................................................... 4 

1.3.4 Software Analysis ...................................................................................... 5 

2 Important Usage Notes and Known Limitations .................................................... 5 

2.1 General ............................................................................................................. 5 

2.1.1 In the event of a Crash of CodeWarrior in Linux ......................................... 5 

2.1.2 Using CodeWarrior on 64-bit Linux Hosts .................................................. 6 

2.2 Debugger .......................................................................................................... 6 

2.2.1 Trace/Profiling Effects on Debugging Function ........................................... 6 

2.2.2 Supported GTAP connections: ................................................................... 6 

2.2.3 Aurora initialization ..................................................................................... 6 

2.2.4 Import Elf Wizard ....................................................................................... 6 

2.2.5 Cache support P2020 ................................................................................ 6 

2.2.6 Cache support P4080 ................................................................................ 7 

2.2.7 Multi-core reset .......................................................................................... 7 

2.3 Software Analysis ............................................................................................. 7 

2.3.1 General ...................................................................................................... 7 

2.3.2 Trace Collection ......................................................................................... 7 

2.3.3 Performance Analysis Tools ....................................................................... 8 

3 System Requirements ............................................................................................. 8 

4 Who Should Use this Release? .............................................................................. 8 

5 Who Should NOT Use this Release? ...................................................................... 8 

6 Errata ........................................................................................................................ 9 

6.1 Known Errata in this Release ............................................................................ 9 

Freescale Confidential Proprietary 

1


1 About This Release 

The 10.0.1 release of CodeWarrior for Power Architecture Development Studio is the first release 

that is generally available. 

1.1 Version Information 

This release note provides important information for users of CodeWarrior Development Studio 

for Power Architecture Netcomm, 10.0.1. This product targets the P4080 (rev’s 1 and 2), P4040, 

P2020 and P2010 processors. You are encouraged to read this document to become familiar with 

this release’s supported targets, new features, errata with workarounds, and other useful 

information. 

1.2 Getting Help 

1.2.1 Documentation 

Please be aware of the abundant documentation available for CodeWarrior for Power 

Architecture. 

1.2.1.1 Quick Starts 

CodeWarrior for Power Architecture Processors 

Explains how to install CodeWarrior Development Studio and how to create and debug a 

simple project that targets a simulator. 

Targeting the P4080DS Board 

Explains how to set up the P4080DS board, install CodeWarrior Development Studio, and 

use this software to create, build, and debug a simple P4080DS project. 

Debugging a Linux Application 

Explains how to configure your system for Linux application debugging, how to create a 

project that generates a Linux application, and how to debug this application. 

Debugging U-Boot 

Explains how to configure and build U-Boot on a Linux machine, how to configure Simics to 

use the new U-Boot image, and how to use the CodeWarrior tools to debug this image. 

Debugging Under the Hypervisor 

Explains how to configure and build hypervisor support on a Linux machine and how to 

debug bareboard applications under the hypervisor. 

Debugging the Linux Kernel Under the Hypervisor 

Explains how to configure and build hypervisor support on a Linux machine and how to 

debug the Linux kernel under the hypervisor. 

Using Ethernet TAP Probe 

Explains how to set up and use the Ethernet TAP probe. 

CodeWarrior IDE - Quick Reference Card 

Lists keyboard shortcuts and defines the purpose of major CodeWarrior IDE user interface 

elements. 


2


1.2.1.2 Cheat Sheets 

Making C/C++ the IDE's Default Perspective 

Shows you how to make the C/C++ perspective the default IDE perspective. 

Using the Flash Programmer 

Shows you how to use the flash programmer to manipulate flash memory. 

Importing Resources Using the Import Wizard 

A set of cheat sheets that shows you how to import various resources into the IDE: 

o Importing Archive Files 

o Importing Breakpoints 

o Importing Classic CodeWarrior Projects 

o Importing Existing Projects into Workspace 

o Importing Preferences 

o Importing Resources from Local File System 

o Importing Team Project Set 

Creating and Debugging a Power Architecture Project 

Shows you how to create and debug a Power Architecture project using the New Project wizard. 

Modifying Build Properties 

Guides you through the process of modifying build properties to better suit your needs. 

Burning U-Boot to Flash for P4080DS 

Guides you through the process of burning U-Boot to Flash for P4080DS. 

1.2.1.3 Further Help 

If you have questions, issues, or want to provide feedback, please use the Freescale online 

support web page. To use this page, follow these steps: 

1. In a web browser, go to http://www.freescale.com/TechSupport. 

Freescale’s Technical Support web page appears. 

2. On this page, click the Submit a service request online link. 

The New Service Request — Category/Topic page appears. 

3. From the Category dropdown menu, select Technical Request. 

4. From the Topic dropdown menu, select CodeWarrior (or other appropriate topic). 

5. Click Next. 

The New Service Request — SR Details page appears. 

6. In this page, enter the requested information. 

At a minimum, enter information in each field marked by an *. 

7. Click Submit. 

If you are already logged in, the Service Request Confirmation page appears. Go to 

the last step. 

If you are not already logged in, the Log-in page appears. 

8. If you are a registered member, login with your user name and password. 

The Service Request Confirmation page appears. Go to the last step. 

9. If you have not yet registered, 


3


a. If you want to become registered member, click Register Now and complete the 

registration process. 

The Service Request Confirmation page appears. 

b. If you do not want to register, supply your contact information in the I do not want 

to register - Provide contact information form and click Submit. 

10. Click Done. 

The Service Request Confirmation page appears. 

Your service request is submitted. 

1.3 New in this Release 

1.3.1 Product Level Features 

Improved Linux host support including 

Extensive testing on Ubuntu 9.10, 32-bit host 

Win 7, 32-bit tested 

1.3.2 Documentation 

1.3.2.1 Tracing and Profiling User Guide 

Added description for OceaN, EPU, RCPM, NXC Trace Profile configurations 

Added description for Hardware Tracepoints 

1.3.2.2 Application note, AN4212 – Using LTTng UST on P4080DS Development Board 

Explains how to enable LTTng UST in the P4080 Board Support Package (BSP). 

1.3.2.3 CheatSheets: 

Creating and Configuring Performance Analysis Project 

Shows how to create and configure a Performance Analysis project 

Creating, Debugging, Collecting, and Viewing Trace Data 

Shows how to create, debug, collect, and view trace data on the P4080/P4040 target 

1.3.2.4 CodeWarrior for Power Architecture Processors 10 Targeting Manual 

Explained the build settings in detail in a separate chapter 

Updates to the Working with Projects chapter based on the new targets introduced with this 

release 

Made updates to the import wizard both in targeting manual and quick starts 

Updated Quick Starts 

1.3.3 Debugger 

P2010 DS bare-board and Linux support 

P2010 RDB bare-board and Linux support 


4


P4040: Linux kernel and Hypervisor debug support 

Support for P4080/P4040 Linux BSP release 2.2 

Support for P4080/ P4040 Linux BSP Fail-over release 

Multi-board support (Limitation: no support for P4080 due to MTWX43800) 

1.3.4 Software Analysis 

1.3.4.1 Trace Collection 

Nexus Trace collection to DDR, NPC, or Gigabit Tap 

Support Nexus tracing from Core, DDR, QMan, OceaN 

Linux LTTng User Space Trace (Linux host only) - See application note for LTTng UST for 

more detail – AN4212) 

LTTng Linux Trace support updates for latest FSL BSP v2.2 

Support for Gigabit Tap collection via aurora from CW UI. 

Improvements to trace events viewer find/filter capability. 

Additional support for P4040. 

1.3.4.2 Performance Analysis 

Additional UI filters added: 

Metrics Tree, Low Level Events 

Hide Filterer leaf nodes with no information. 

Metrics improvements 

Support for user defined metrics. 

Additional support for P4040. 

2 Important Usage Notes and Known Limitations 

This section describes some issues that are more likely to be encountered, and how to avoid or 

work around them. Additional information on errata and work-arounds can be found in the Errata 

section of this document. 

2.1 General 

2.1.1 In the event of a Crash of CodeWarrior in Linux 

When running CodeWarrior in Linux, in the unlikely event that you have encountered a 

crash of the Debugger Engine in CodeWarrior, you may need to do the following. 

a) Close CodeWarrior and kill any “cwde” processes that may still be left running. (kill 

) 

b) Navigate to the filesystem's /tmp directory. 

c) If any files exist of the form “CWDebuggerEngineSCS-x-” they should 

be deleted. (rm –f /tmp/CWDebuggerEngineSCS*) 


5


2.1.2 Using CodeWarrior on 64-bit Linux Hosts 

For 64-bit Linux hosts CodeWarrior Connection Server (CCS) requires installation of 32bit 

X11 libraries in order to launch. Please ensure libXpm is installed on the system 

prior to use. 

2.2 Debugger 

2.2.1 Trace/Profiling Effects on Debugging Function 

Enabling Trace or Profiling was found, in some cases, to have negative consequences 

for debugging functions. In general, the debugging problems can be avoided if profiling 

and trace are disabled if they are not needed during basic debugging. 

2.2.2 Supported GTAP connections: 

JTAG over JTAG cable and JTAG over Aurora cable are supported. 

Limitation: Debugging using Aurora connection is not supported (Aurora cannot be initialized for 

debug). 

2.2.3 Aurora initialization 

Supported only with Silicon Rev 1 

Limitation: Tracing is supported only when the debugger is connected. The Aurora connection is 

also stopped when the debugger disconnects. 

2.2.4 Import Elf Wizard 

Limitation: A dtb file cannot be imported within the wizard and the user has to do this from GUI. 

Also SMP cores cannot be selected. 

Limitation: No existing RSE can be chosen inside the wizard (a new one will be created every 

time). The RSE can be chosen after project creation from GUI. 

2.2.5 Cache support P2020 

e500v2 core: The memory window is not updated after a write operation in data cache. This 

is by design – no attempt to read data cache is done when reading memory, only the 

instruction cache. It is done this way because data cache is coherent, while instruction cache 

is not. 

e500v2 core: A cache line gets invalidated, when its content has been changed through the 

memory window; this is the expected behavior since when a transaction is produced by SAP 

(as well as any other bus master) the cache snooping mechanism invalidates the appropriate 

line. 

Opening Cache window: Valid lines can appear in Cache Viewer even if the cache is 

enabled or disabled. This is by design, the line status does not depend on whether cache is 

enabled or not. 


6


2.2.6 Cache support P4080 

2.2.6.1 L1 Data Cache for Memory Reads for P4080 

L1 Data cache allocates lines for memory reads of code around the PC; in order not to have that 

code in the cache, a cache inhibited read should be done or SAP should be used. 

2.2.7 Multi-core reset 

MTWX42123 Reset command from debugger shell can only be used to reset the entire system. 

For per-core reset, the GUI reset dialog should be used. 

2.3 Software Analysis 

2.3.1 General 

The Software Analysis tools only support the P4080 and P4040 processors. 

Enabling Trace and Profiling was found, in some cases, to have negative consequences for 

some debugging functions. In general, the debugging problems can be avoided if profiling 

and trace are disabled in the Trace and Profile tab in the Launch Configuration, if they are not 

needed during basic debugging. 

2.3.2 Trace Collection 

1. Tracing is supported only when the debugger is connected to the target. 

2. Within the Jython console in CodeWarrior there is no standard out being shown when scripts 

are invoked. To workaround this limitation capture the decoded output using “out=” 

argument to GetBufferTrace or GetProbeTrace scripts. 

3. When using the GetBufferTrace.py or GetProbeTrace.py scripts to collect and decode trace 

data, please edit your debug launch configuration and uncheck the 'Enable Trace and Profile' 

setting. 

4. If collecting program trace from a P4080 rev2 processor, edit the file(s) listed below and set the 

value of the 'Trace Predicate Instructions' attribute to '1', for each core that outputs program 

trace data: 

If collecting trace using the graphical user interface: 

\PA\cdde\sasdk\data\fsl.configs.sa.nexusdecoder\NexusDecoderP4080Internal.xml 

If collecting trace using the GetBufferTrace.py or GetProbeTrace.py scripts: 

\PA\cdde\sasdk\data\fsl.configs.sa.nexusdecoder\NexusDecoderP4080.xml 


7


Note: In order to check whether your P4080 processor is rev1 or rev2, check the content 

of the e500mc's special purpose register called SVR, in the CodeWarrior register view. If 

the SVR register's value masked with 0xfff0fff0 is equal to 0x82000010 the processor's 

revision is rev1, otherwise it is rev2. For more details please consult the P4080 

Reference Manual. 

5. The trace settings are applied to the target using the active debug launch configurations. 

Currently the multiple active debug launch configurations associated with different P4080 

boards are not supported, please make sure that all active debug launch configurations are 

using the same P4080 board, when collecting trace data. 

6. U-boot in the FSL BSP (on P4080rev1) disables the aurora lanes used for Nexus trace 

support with the Gigabit TAP. To collect trace to Gigabit TAP probe you must enable at least 

2 lanes for Aurora. 

7. Sometimes, collecting to the NPC Buffer via the CodeWarrior Eclipse environment is not 

currently working. Collecting to the NPC buffer via the scripting environment (GetBufferTrace) 

is working. 

2.3.3 Performance Analysis Tools 

The "Generate a Configuration Access Log" operation, found on the Analyze Tab, requires that 

the "Save configuration with each captured data" options be checked on the Options Tab. 

The Performance Analysis Events viewer will be empty when initially opened. Upon completion 

of each collection operation it will display the collected counter data. 

3 System Requirements 

Recommended Configuration 

3GHz Intel® Pentium® P4 processor or better. Dual-core processor preferable. 

Microsoft® Windows XP 

2GB RAM (Step speed on machines with 1GB RAM is significantly slower) 

1GB free disk space 

Note: 500MB of free space is required on the OS drive, regardless of the free space available 

on the destination drive. 

4 Who Should Use this Release? 

Users developing for the P4080 

5 Who Should NOT Use this Release? 

Users developing for PowerQuicc, 8xxx, 7xxx, 7xx, 6xx or 5xx based processors. These 

developers should use the previous (non-Eclipse based) versions of the tools. 


8


6 Errata 

6.1 Known Errata in this Release 

Please check the Documentation tab in the CodeWarrior for Power Architecture section 

of the Freescale website for updated lists of known errata and addressed errata: 

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=CW_DSPA& 


9

CodeWarrior Development Studio for Power Architecture Netcomm

Create successful ePaper yourself

Delete template?

Save as template?