CodeWarrior Development Studio for Power Architecture Netcomm

More documents

Recommendations

Info

$Set of General Math and Motor Control Functions for ARM Cortex ...$

CodeWarrior Development Studio for Power Architecture Netcomm v10.0.1 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. Freescale Confidential Proprietary 6
CodeWarrior Development Studio for Power Architecture Netcomm v10.0.1 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 Freescale Confidential Proprietary 7
Page 1 and 2: CodeWarrior Development Studio for
Page 3 and 4: CodeWarrior Development Studio for
Page 5: CodeWarrior Development Studio for
Page 9: CodeWarrior Development Studio for

CodeWarrior Development Studio for Power Architecture Netcomm

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?