CodeWarrior for StarCore DSPs FAQs

[J2MEJediMaster]

This thread contains the Frequently Asked Questions (FAQs) for the StarCore for CodeWarrior DSPs development tools.

[levengli]

The err variable reflects accurately what the MMU Configurator window contained prior to calling osMmuDataErrorDetect

[Irene]

Q:  Customer wants to build the CW project in the DOS command line. They don't want to write makefile themselves because they think makefile is a little complicated. Is there any method to build the CW project in DOS command line?

A:  There is only one way to do this currently in the CodeWarrior for StarCore 10.1.X tools.  To create an Eclipse build from the ecd command line follow steps below:

1.  Copy ecd.exe file from the <CWInstallDir>\eclipse\plugins\com.freescale.core.ide.commandLineDriver_2.0.0.FSL_  {build_number} folder to the <CWInstallDir>\eclipse\ folder.

2.  Invoke the ecd command line.

3.  In the ecd command line, type the following command: ecd -build -data my_workspace_path -project my_project_path

4.  Click <Enter>.

5.  After a few seconds the Automated Builds window appears.  After the build is completew you will see the following appear in the DOS window - Build succeeded for project <"project_name">

Note: Please make sure that the project that you going to build has been imported into the workspace.

[J2MEJediMaster]

Q: I created a project for the StarCore MSC8156 with SmartDSP OS support using the wizard. What should I modify to get a project that I can run/test on one core only?

A: First edit the file os_config.h and set OS_NUM_OF_CORES to 1.

Next, edit the file os_msc815x_link.l3k and change
   number_of_cores(6);
to
   number_of_cores(1);

Finally, rebuild the application and you get a single .eld file, and you can run that application on one core only. 

[J2MEJediMaster]

Q: How can I view my SDOS tasks stack frames in the CodeWarrior Debug view?

I have created my application with SmartDSP OS support using the wizard and I do not see all my active tasks in the debugger.

A: In this case, you need to do the following:

Edit the file os_msc815x_link.l3k.
  1) Set USING_USER_KA_STACK to 1.
  2) Save the file.

Edit the file os_config.h.
  1) Make sure that you have following lines in there:

/* Kernel Awareness************************************************************/
#define USER_KERNEL_AWARENESS_STACK ON
#define KERNEL_AWARENESS_ADDR &KernelAwareness_b
#define KERNEL_AWARENESS_STACK_SIZE (uint32_t)&KernelAwareness_size

  2) Save the file if you did change something.
  3) Make sure to link against the library os_msc8156_debug_log.elb (instead of os_msc8156_debug.elb) in the StarCore C/C++ Linker -> Libraries panel.

Edit the file smartdsp_init.c.
  1) Make sure you have the following lines in there:

extern unsigned long int KernelAwareness_b;
extern unsigned long int KernelAwareness_size;

  2) Rebuild the application.

Set the OS type in the Launch Configuration.
  1) Open the Debug Configuration dialog.
  2) Go to the Debugger Tab.
  3) Switch to the OS Awareness panel and set Target OS to SmartDSP OS.
  4) Make sure the Log task Awareness option is checked.
  5) Save the changes. This should be repeated for each core, where you want to see the different tasks.

Start debugging.
  1) Once in the Debug Perspective, open the System Browser view (Select Windows > Show View > Others and open System Browser from the Debug group).
  2) Start execution of the application.
  3) When the application stops, you see the different threads available in the system browser.
  4) Double-click on one of the threads and the corresponding stack Frame will be shown in the Debug view.

For information on how to collect and see kernel Awareness Logs, please refer to SmartDSP OS Concepts Guide.pdf chapter Kernel Awareness.