CodeWarrior Development Studio for StarCore DSP v10.5.1

CodeWarrior Development Studio for StarCore DSP v10.5.1 

Release Notes 

CodeWarrior Development Studio for 

StarCore DSP v10.5.1 

Table of Contents 

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

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

1.2 Important Notes ................................................................................................ 2 

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

2.1 User Forum and FAQ ........................................................................................ 3 

2.2 Contacting Freescale concerning CodeWarrior Development Tools ................. 3 

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

3.1 SmartDSP OS................................................................................................... 4 

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

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

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

7 Errata – Known Issues for this Release ................................................................. 6 

8 Errata – Fixed in this Release ............................................................................... 10 

1


1 About This Release 

The 10.5.1 release of CodeWarrior for StarCore Development tools introduces an updated 

SmartDSP OS version and address couple of bug fixes for Star Core compiler and IDE. 

1.1 Version Information 

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

for StarCore DSP v10.5.1. 

Users looking for productized solutions for the StarCore 3850 core and the BSC913x processors 

are encouraged to use CodeWarrior for StarCore 10.5.1 product. 

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

targets, errata with workarounds, and other useful information. 

1.2 Important Notes 

Please check Chapter 3 for the full list of features. 

Note! New Eclipse 3.7.1 feature, Code Analysis: Depending on your settings in the Code 

Analysis panel, you might get unexpected syntax errors. You can customize these settings by 

going to Window->Preferences->C/C++->Code Analysis. 

2


2 Getting Help 

2.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 check: 

- 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.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. 

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. 

10. Click Done. 

The Service Request Confirmation page appears. 

Your service request is submitted. 

3


3 New in this Release 

3.1 SmartDSP OS 

New SmartDSP OS version R04.07.00. All libraries and demos are now built with CW10.5.1 and 

bring the following features: 

- Kernel features 

o Introduces support for a new memory management module: 

• Added the option to control the memory segment memory management structures 

will be placed on. This is controlled by defines in os_config.h; 

• Compilation warnings will be issued in case management size is not defined, 

notifying that default values are used. 

• Memory manager management size default values reduced to 1000 bytes (both local 

and shared). 

- Drivers features 

o BSC9132 eSPI which enables to send and receive data using 2 eSPI controllers on the 

device. This driver API is based on CIO abstraction layer; 

o MAPLE eFTPE Trace - introduces an API for usage of the MAPLE eFTPE Trace 

functionality. This API enables the user to register events to be logged by the eFTPE and 

to extract the logged events from the MAPLE buffer. This feature should be used in 

debug time only (due to performance impact on MAPLE). An example for the usage of 

this API can be found in the MAPLE eFTPE demo, by modifying the demo configuration. 

o BSC9132 debug print multicore - introduces BSC9132 debug print multicore support. A 

demo for this new feature was added; 

- Demos features 

o BSC9132 eSPI demo - This demo demonstrates usage of the eSPI SmartDSP OS driver 

for sending and receiving data in internal loopback mode. The demo is running in 

multicore scenario. Each core is handling a single eSPI unit; 

o BSC9132 CPRI multicore demo - This demo demonstrates usage of CPRI in multicore 

scenario (internal loopback). Each core is handling a single CPRI unit. 

o MAPLE eFTPE Added MAPLE eFTPE Trace demonstration to the demo. This option is 

turned off by default. Instructions on how to set it on are found in readme.txt. 

o BSC9132 debug print multicore Added multicore scenario demonstration to debug print 

demo. Note: current BSP package to use “913x_WUSDK_REL_1.3” – does not have the 

updated Engine & host application. Use the copies from the “debug_print_apps.zip” file 

(Please follow the guide). 

Note! For more details about the SmartDSP OS R04.07.00 please refers to SmartDSP 

OS_release_note. 

4


4 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. 

Note: The users need Windows Administrator rights when installing the CodeWarrior within 

Program Files location. Otherwise CodeWarrior internal processes might fail to start during 

run time execution. 

5 Who Should Use this Release? 

Users developing for the BSC9131, BSC9132 devices 

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

willing to tune their code for performance 

6 Who Should NOT Use this Release? 

Users developing for StarCore MSC8157/8, MSC8154/6/2/1, MSC8256/4/2/1, MSC8144, 

MSC8122/26, MSC8113/12, MSC8101/3, or MSC711x DSPs. 

5


7 Errata – Known Issues for this Release 

This list includes only P1 and P2 issues that are not fixed in this release. 

ENGR00235607 

ENGR00225771 

ENGR00236407 

ENGR00234330 

ENGR00220108 

ENGR00186856 

ENGR00236922 

ENGR00202735 

ENGR00236912 

ENGR00199263 

ENGR00192655 

ENGR00190261 

ENGR00187044 

ENGR00186546 

ENGR00210174 

ENGR00208009 

IDE 

Issue: CORBA Connection Error 

Workaround: Split test suit to run less then 300 tests in a batch run and restart 

CodeWarrior between batch runs (this can be configured from the scripts) 

Issue: Breakpoints hit not correct after executed "Mulitcore Resume" 

Workaround: the user can enable/disable the breakpoint instances individually for each 

core, from the breakpoint view. 

debug_print project fails to build with CW10.5.0 for multicore 

Workaround: Set correct path towards linked libraries. 

GUI locks when Product Licenses dialog appears over another modal dialog 

Workaround: hit Enter to dismiss the error dialog first before closing the warning dialog for 

expiring licenses. 

Additionally pressing the ESC key might close the dialog in the background. 

Issue: RSE sytem persistence uses too long directory names 

Workaround: Use a workspace at the top level hierarchy of a windows drives (e.g. 

c:\workspace). 

Software Analysis 

SA reports function calls "not covered" in some cases 

Workaround: none 

Cannot enable trace for G1110/G1110SC in the Debug Configuration 


Issue: "Trace and Profile" Support for G1110 was enable in Creation wizard but not in 

Debug launch Configurations window 


Issue: Cannot build SDOS project with Trace enable support HSST as Trace offload 

method 


Issue: Cannot build the imported project successful 


Issue: Export trace window is not able to closed/disappeared if you don't want to replace 

an existed csv file 

Workaround: open location of existed csv file by window exploer and rename this file. now 

back to 'Export Trace Data to CSV' window of CodeWarrior and you can export with your 

desired name 

Issue: No Trace is collected after removing all Trace points when debug session started. 

Workaround: If you want to remove all tracepoints, do this offline (not when you are 

debugging the project). If you don't want to remove all tracepoints, you can do this in both 

online and offline mode. 

Issue: CW behaves abnormal when ETH get disconnected 


Issue: TP is disable when set an external source code. 


Issue: Error connecting to simulator when Debug and Resume profilerdemo_SC3x50 

project 


Simulator 

Issue: Profiler module ver 1.1.12 for simulator outputs empty results 

Workaround: None 

6


ENGR00231532 

ENGR00236725 

ENGR00262393 

SmartDSP OS 

Issue: CPRI auto-negotiation fail for 4.9G. when using os_msc8x57_drivers.elb 


Issue: Trace was not collected for 9131 SDOS stationary project due to wrong VTB 

addresses 

Workaround:none 

SDOS R4.7.0 - cpri_hdlc demo is not functional 

Workaround:none 

CCS 

Issue: CWTAP: Starcore 8156 board tested with temporary flying leads 

probe. Found that register write failed after step core operation during 

ENGR00193932 

step test. 


Issue: ccs::reset_to_debug generates "core not responding" error with 

ENGR00207767 QDS + DSP core access by DSP JTAG port 


Issue: CCS drivers do not pass WinLogo verification (on Win XP) 

ENGR00231737 


Build tools 

Issue: It takes more than 8 minutes to build the attached project. 

ENGR00183307 Workaround: Use lower optimization level –O0, -O1, -O2 

Issue: Fatal Error while using Map(STL) of int and class object. 

ENGR00184584 Workaround: use additional argument to shell: -Xicode --exception_support=false 

Issue: C_L_conj gives wrong result when input parameter is -1 

ENGR00185514 Workaround: none 

Issue: Error: Can't find mapping (2-1), for IL2986 in extract_mapping_solutions 

ENGR00185626 Workaround: -Xicode --disable_standard_op to disable standard optimizations in icode. 

Issue: EVRC Codec is not bit-exact anymore 

ENGR00186055 Workaround: - use -Xicode --achieve_cross_compo=FALSE for file evrc_bqiir.c 

Issue: Incorrect code generated in function pexInitialize 

Workaround: Add following lines in file msc8156_drivers_smartdsp_os.appli 

module "pex_init" 

[ 

function _pexInitialize [ 

active_sequential_access = FALSE 

] 

ENGR00186389 ] 

Issue: Complier does not recognize Front End option "-optimize_single_and_or" states 

"unknown option" 


Issue: Profiler module ver 1.1.09 for simulator outputs wrong statistics 


Issue: Dissembler returns: ERROR: an invalid codification was found at pc=0x1007F80 


Issue: HwdrvGetGainOffset works abnormal when O3 is used 

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

Issue: Some strange code generated for function 

cif_ue_context_config_processing_action() 

ENGR00192872 Workaround: use -O3 optimization level for the whole file 

Issue: Icode internal error on EDM_GMSK_ACS kernel 

Workaround: use fewer modulo registers in loops, as it is not efficient for the compiler to 

ENGR00192893 spill them 

ENGR00194567 Issue: ICODE crash when tries to perform modulo addressing 

7


ENGR00195487 

ENGR00196023 

ENGR00197523 

ENGR00197639 

ENGR00198461 

ENGR00199029 

ENGR00199341 

ENGR00201338 

ENGR00203863 

ENGR00204177 

ENGR00204856 

ENGR00205346 

ENGR00206943 

ENGR00207002 

ENGR00207176 

ENGR00207335 

ENGR00218415 

ENGR00230286 

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

Issue: Performance degradation afetr "unroll & jam" 


Issue: Loop issue in NSN kernel 


Issue: Compilation time is too long: ALU excepts less than 60 seconds compilation time 

per file 


Issue: Unsigned 64 bit value misinterpreted as signed 32 bit 

Workaround: –Xicode --achieve_induction=false 

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

Workaround: 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: Compiler generates incorrect code with optimization 

Workaround: Following work around seems to cure the problem: 

1- Define the function extract_command as non static and disable inlining of taht 

function. 

2- Remove initialization of *pActualLength to 0 at line 148 

3- Build with ICODE option --scalarization=FALSE 

Issue: Wrong input parameter to memset function 


Issue: Linker reports error when moving global definition from one file to another 


Issue: Can’t generate code based on MACRO from command line with newer linux 

compilers 

Workaround: A workaround is to use -Xcfe "-D..." to bypass SCC's -D handler, e.g.; 

something like this: 

scc -v -arch sc3850 -be -Xcfe "-DMACRO=\"Hello World\"" test.c 

Issue: ICODE runs out of memory 

Workaround: -FsO0 

2nd workaround: -Xicode --codegen_no_lookahead 

Issue: Execution result is incorrect in case of opt level 1 or higher 

Workaround: Build function ImageConvert within module test.c with ICODE option 

achieve_composition = FALSE 

Issue: Performance degradation in WCDMA function ArkFilterAlfaBeta (Test case 29) for 

about 14.5% between 23.11.1.27D and 23.11.3.26 


Issue: Switch_To_Rom=TRUE generated jump-to table is not suitable for multi-core 

Workaround: Do NOT use Switch_To_Rom=TRUE. 

Issue: Internal error in choose_spill_register 

Workaround: compile in O3 or O0 

Issue: Compiler is stuck when compiling c file "LramVarialbe_DDR.c" 


Issue: sc100-elf2xx.exe in post-build failed 


Issue: move.l d3,(sp-45) is generated for a byte access 


Issue: wrong instruction flow after inline 

Workaround: 

-Xicode --codegen_simplify_in_valid_reg 

OR -Xicode --codegen_simplify_move 

8


ENGR00231347 

ENGR00235146 

ENGR00235314 

ENGR00235392 

ENGR00235609 

OR -Xicode --codegen_simplify_loop_reshape (I am no sure for the last one). 

Issue: Long compilation time, llt - CW for StarCore 

Workaround: With -Xllt -c_mem0 the compilation is very short in llt. 

Issue: segments overlap after building 


Issue: segment is not aligned 


Issue: Internal compiler error with statement like if ((modulatorSettings[i].symbol_rate > 0) 

== (0) ) 

Workaround: 1- Change the line 12631 from 

if ((modulatorSettings[i].symbol_rate > 0) == (0) ) 

to 

if (!(modulatorSettings[i].symbol_rate > 0)) 

2- add following pragma prior to the implementation of function init_modulator 

#pragma fspeephole off 

You can then add following pragma at the end of the function implementation 

#pragma fspeephole on 

Issue: wrong ifa tfrf combination 

Workaround: -Xicode --codegen_simplify_loop_reshape 

9


8 Errata – Fixed in this Release 

This list includes the issues reported by external customers and additional issues that were 

marked as exceptions in CW10.5.0 and that are now fixed 

IDE 

ENGR00240802 Build error on new CW10.5.0 (RT21) 

ENGR00221778 CW for SC3850 does not put warning in problems window 

Compiler 

ENGR00236874 wrong stack write/read for local parameter with -o3 

ENGR00239981 Optimization propagation level issue 

ENGR00229215 Incorrect code generated for bitfield assignment 

ENGR00236897 Compiler bug - 64-bits alignment not correctly computed 

ENGR00234427 Improve message generated when a range overflow is generated 

ENGR00239225 Compiler generates incorrect stack manipulation 

SmartDSP OS 

ENGR00257207 SmartDSP OS Recovery solution disabled Non Maskable Interrupts up until background 

task. 

ENGR00257864 Maple_crcpe demo should have launch group configuration for 9132 

ENGR00257956 Maple_pusch cannot run successfully with 9131 target 

ENGR00257968 "Maple_Pusch PSC9132 External Ctrl - Release" got fail result 

10

CodeWarrior Development Studio for StarCore DSP v10.5.1

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

Delete template?

Save as template?