CodeWarrior Development Studio for StarCore DSP v10.2.9

CodeWarrior Development Studio for StarCore DSP v10.2.9 

Release Notes 

CodeWarrior Development Studio for 

StarCore DSP v10.2.9 

Table of Contents 

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

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

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

2.1.1 User Forum and FAQ ................................................................................. 2 

2.1.2 Contacting Freescale concerning CodeWarrior Development Tools ........... 2 

3 New in this Release ................................................................................................. 3 

4 PSC9131 RDB board configuration ........................................................................ 4 

5 System Requirements ............................................................................................. 4 

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

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

8 Errata – Known Issues for this Release ................................................................. 5 

9 Errata – Fixed in this release .................................................................................. 8 

1


1 About This Release 

The 10.2.9 release of CodeWarrior for StarCore Development tools introduces preliminary 

support for PSC9132. The preliminary support means the product was designed for PSC9132 but 

lightly tested. With this release we provide an updated Build Tools component, with an updated 

Linker release. 

1.1 Version Information 

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

for StarCore DSP v10.2.9. This product continues to support MSC815x family and PSC9131, and 

introduces PSC9132. The support for PSC9132 is preliminary, lightly testing was performed. You 

are encouraged to read this document to become familiar with this release’s supported targets, 

errata with workarounds, and other useful information. 

2 Getting Help 

2.1.1 User Forum and FAQ 

After looking through these release notes, and the documentation that comes with the installation 

of CodeWarrior, the next best place to look for answers to your questions is the online user 

forums located at 

http://forums.freescale.com 

Please see the: 

• CodeWarrior for StarCore DSPs forum for issues related to CodeWarrior 

development tools. The Frequently Asked Questions about CodeWarrior for 

StarCore DSP are posted here. 

• StarCore DSPs forum for issues related to the silicon and hardware platforms. 

The forums provide a great way to learn by seeing the questions and answers posted by 

other users. Of course, you can post your own questions and responses as well. 

2.1.2 Contacting Freescale concerning CodeWarrior Development 

Tools 

Finally, if you still have questions not addressed in the release notes, 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 Create 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. 

2


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, 

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. 

The Service Request Confirmation page appears. 

10. Click Done. 

Your service request is submitted. 

3 New in this Release 

Product Level Features 

• Preliminary support for PSC9132 

• Updated Build Tools 

Build Tools 

• StarCore compiler v23.11.6.38 

Debugger 

• DE 7.17.11010 + StarCore plugins 10.17.842 

• Support for PSC9132 

PSC 9132 verified features 

• Basic single-core run control – reset, run, stop, step, attach, kill 

• Multi-core run control (see note below) 

• Software and hardware breakpoints 

• Access to memory and registers 

• Integration of the latest 9132 XML register drop from PEx team 

• Board configuration file including DDR initialization 

• Disassembly view. 

• Symbolic debugging. 

• Standard File I/O. 

PSC 9132 known issues 

- Register displays for TDM, ACU, PEX, TSEC, DDR1 and possibly other groups 

are known to have incorrect data. 

3


Workaround: Use a memory rendering at the base address documented in the 

specs. 

4 PSC9131 RDB board configuration 

The PSC9131 RDB board has dedicated switches controlling whether the StarCore and Power 

Architecture cores are exposed as separate JTAG chains, or through a single unified chain. 

CodeWarrior provides separate configuration sets for SC only versus SC+PA chains. Matching 

the configured and actual JTAG chains is essential to ensure connectivity with the platform. 

Full SC+PA JTAG chain mode requirements: 

- Configure on-board dipswitch SW6[3:4] = OFF/OFF (CFG_JTAG_MODE_0:1 = 00). This 

is the factory default for the RDB board. 

- Use a single UTAP unit with COP header 

- Use the PSC9131 RSE system 

Single TAP mode through primary JTAG header: 

- Configure SW6[3:4] = OFF / ON. Power core is inaccessible. 

- Use a single UTAP unit with COP header 

- Use the PSC9131_SC RSE system 

Single TAP mode through secondary JTAG header: 

- Configure SW6[3:4] = ON / ON 

- Use a single UTAP unit with ONCE header for SC connectivity, and the secondary JTAG. 

Additional access to Power core requires a separate UTAP unit with COP header. 

- Use the PSC9131_SC RSE system 

In addition, the state of Reset and Execute Initialization File options must be adjusted in 

accordance with application requirements. In particular: 

- An environment that does not require the PA core to be operational should have Reset, 

and have the supplied SC-side debugger initialization file enabled. 

- An environment that assumes system initialization is done by PA should have Reset and 

Execute Initialization File turned off from SC side. 

5 System Requirements 

Recommended Configuration 

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

- Microsoft® Windows XP, Windows Vista, Windows 7 

- 2GB RAM (Experience on machines with 1GB RAM is significantly reduced) 

- 2.3 GB free disk space 

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

on the destination drive. 

6 Who Should Use this Release? 

- Users developing for the G1110, PSC9131, MSC8157, MSC8156, MSC8154, MSC8152, 

MSC8151, MSC8256, MSC8254, MSC8252 and MSC8251 devices 

- Developers seeking better performance from code not previously hand-optimized or 

developers willing to tune their code for performance. 

4


7 Who Should NOT Use this Release? 

- Users developing for StarCore MSC8144, MSC8122/26, MSC8113/12, MSC8101/3, or 

MSC711x DSPs. 

8 Errata – Known Issues for this Release 

Issue Abstract 

IDE 

Issue: Problem with CodeWarrior generated folders when project directory and 

project files are located on a UNIX server 

Workaround: Change configuration name and make sure there are only lower 

MTWX35467 

cases in configuration name. 

make sure name from all folders within the project are specified using lower cases 

character only 

Issue: Include path order not correctly handled by the IDE for C++ projects 

MTWX36953 

Workaround: none 

Issue: Problem pane in CW cuts off error message 

MTWX37727 


Issue: Build failed when main project has a reference to sub projects, and the 

reference is not on the Active configuration for the sub-project 

MTWX38435 

Workaround: in the sub project make sure the referenced configuration is the 

active configuration 

Issue: RSE conversion dialog is shown every time CW is Opened when the .launch 

files are left read-only by Clearcase 

Workaround: 

Depending on which exact build that you are using, either: Configure the RSE 

Merge settings (in the "Remote Systems | Merge" section of the "Preferences" 

dialog) so that the setting for "Select how to handle differing RSE Systems" isn't set 

to "Display a dialog to manually resolve the conflict" anymore. 

MTWX46592 

MTWX48965 

MTWX51518 

Or, if this preference panel isn't present, edit the eclipse\cwide.properties file so it 

contains the following line: 

com.freescale.core.ide.rseSettingsCache/stringDefaultMergeOption=latest 

The “latest” setting by one of the following: 

prompt, latest, cached, discard, createNew 

That match the respective options in the setting. 

Issue: Incremental project build does not work 


Issue: Linked resources get broken when the project is RENAMED 

Workaround: After renaming a project change the value of the 

"copy_PROJECT_LOC" variable to point to the correct location (${PROJECT_LOC}). 

5

MTWX51947 

MTWX52105 

MTWX45024 

MTWX45025 

MTWX45026 

MTWX48902 

MTWX47875 

MTWX48065 

MTWX22664 

MTWX49792 

MTWX51205 

MTWX51523 

MTWX52088 

MTWX44090 


Issue: Workspace becomes corrupted somehow and CW will no longer be able to 

use it. 

Workaround: 

delete {workspace}/.metadata/.plugins/org.eclipse.core.resources/.snap file 

This issue seems to occur when the workspace is moved to a different location in 

the file system or on another computer, or shared between users either through 

the network or through a source control repository. 

To avoid this issue, only use an eclipse workspace in a single location for a single 

user on a local machine only. 

Issue: Specifying a batch file name in pre-build steps forces a full rebuild of the 

application. 


Software Analysis 

Issue: Cannot take VTB trace two times in a row without restarting CW 

Workaround: None 

Issue: Obtaining trace in overwrite mode requires terminating the session. 


Issue: CW gives false and unreliable profiling result 


Issue: Analysis plugins call File.exists() too often. 


Simulator 

Issue: MMU exception generated when application using huge number of scanf 


Issue: The SW Pfetch performance shown by simulator is wrong 


Debugger 

Issue: Registers View resets when stepping or running to BP 

Workaround: 

1) Create a new registers group and add the registers of interest to this group. 

Remove the other groups. 

2) Add the registers of interest to the expressions view (remember to put a $ before 

the register name when adding the expression) 

Issue: Register read causing CCS protocol error 

Workaround: Use CCS to read registers directly 

Issue: CW 10.2.5 crashes during development work 


Issue: Download performance degrades significantly on subsequent download 

attempts after first 

Workaround: merge the attached TCL script with debugger initialization file 

Issue: When two ISS for msc8156 are running, usually some IDE crash will happen. 


Build tools 

Issue: Illegal data spill in address register 

Workaround: Please try "-Xicode --codegen_simplify_oper" or "-Xicode -- 

6

MTWX44371 

MTWX45859 

MTWX46146 

MTWX46148 

MTWX46361 

MTWX46492 

MTWX47332 

MTWX47369 

MTWX47767 

MTWX47920 

MTWX48126 

MTWX48214 

MTWX49471 

MTWX49989 

MTWX49994 

MTWX50749 


codegen_no_lookahead". On the sl file it looks like either one of then solves the 

problem. 

Issue: Switch_To_Rom=TRUE generated jump-to table is not 

suitable for multi-core 

Workaround: Do NOT use Switch_To_Rom=TRUE 

Issue: Performance degradation when -FsO0 is removed from scc 

shell 


Issue: function gets stuck with -O3 

Workaround: 

Workaround #1: disable first scheduling step -Xllt -s0 

Workaround #2: 

Change the type of the parameters of asm function FAST_D_FLE from DOUBLE to 

INT64 + when the FAST_D_FLE is called add a Db_to_LL conversion for each 

argument. 

Issue: function executes redundant FAST_D_FLE 


Issue: Problem with paralell compilation 

Workaround: Restart project build 

Issue: 20% performance degradation in LTE-PRACH function 

when running with CW10.1.11 compared with CW10.1.8 

Workaround: Add "-Xcfe -fl=fscastopts" to the compiler 

command. 

Issue: EDMGMSK_LowTriInv_SC3850C fails with -O0 but passes 

with -O3 


Issue: Icode internal error on function 


Issue: Cannot generate code based on MACRO from command 

line with newer linux compilers 


Issue: Compilation time is too long 


Issue: HwdrvGetGainOffset works abnormal when O3 is used 

Workaround: Add "-e0 -ee0" to the LLT options 

Issue: Profiler module ver 1.1.09 for simulator outputs wrong 

statistics 


Issue: Generated asm code in a loop is not optimal for -O3 


Issue: In the muReadThread() function not getting the right value 

for "data" by call macro "muGetRxMessage". 


Issue: ICODE runs out of memory 


Issue: FATAL ERROR: Internal compiler error 11.. Aborting... 

Workaround: 

7

MTWX50938 

MTWX51357 

MTWX51474 

MTWX51805 

MTWX51858 

MTWX52188 


Remove #pragma align dio_chunk 0x10000000 and replace with 

struct dio_mem_area dio_chunk 

__attribute__((section("dio_chunk_seg"))) ; 

This way the variable is in a separate section which can be 

aligned from the linker command file to any desired value. 

Issue: Performance degradation after "unroll & jam" 


Issue: Under Windows 7, sc3000-ld exit without throwing out any 

error message in console. 

Workaround: Run linker in Windows XP compatibility mode. 

Issue: Output error with O3 optimization 


Issue: ICODE crash when tries to perform modulo addressing 

Workaround: don't use #pragma safe_mod for the 2 loops. 

Issue: The file test_maple_ftpe.c in 

SC\StarCore_Support\SmartDSP\demos\starcore\msc815x\mapl 

eb2_ftpe can't pass building when optimization level>=1 

Workaround: use -Xicode --achieve_induction=FALSE 

Issue: Virtual and physical address mismatch although map11 

exists 


9 Errata – Fixed in this release 

Issue Abstract 

Build tools 

MTWX52753 Issue: DSP Image size much too large 

8

CodeWarrior Development Studio for StarCore DSP v10.2.9

Create successful ePaper yourself

Delete template?

Save as template?