CodeWarrior for StarCore DSPs FAQs

[J2MEJediMaster]

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

[nguyentienluc]

Now, I want to reset SC3850 DSP by writting code C in CodeWarrior instead of pressing reset button in board.How to do it?Thanks in advance!

[lunminliang]

Hello Nguyen tien luc,

If you would like to "reset SC3850 DSP by writting code C", you could use Software hard reset or Software soft reset：

Software hard reset------A hard reset sequence can be initialized by writing to a memory mapped register (RCR)

Software soft reset------A soft reset sequence can be initialized by writing to a memory mapped register (RCR)

Also there is "reset" setting in CodeWarrior launch configuration, in the connection configuration. For your information.

Have a great day,
Lunmin

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[billchadwick]

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

If I make no changes (after the wizard runs) and  load the core 0 image, it stalls in osWaitForAllCores at line 406 of smartdsp_init.c

[lunminliang]

Hi, bill chadwick

That's because of the multicore sychronization in SDOS, you also need to remove the Macro "OS_MULTICORE=1" or change it to be false.

[billchadwick]

Setting OS_MULTICORE=0 causes link problems

Error(E2077): In .unit "c0": symbol "_g_mem_heap_shared" undefined in C:/Freescale/CW_SC_v10.8.0/SC/StarCore_Support/SmartDSP/lib/b4860_family/os_b4860_debug.elb(b486x.eln)

Error(E2077): In .unit "c0": symbol "_g_num_of_shared_heaps" undefined in C:/Freescale/CW_SC_v10.8.0/SC/StarCore_Support/SmartDSP/lib/b4860_family/os_b4860_debug.elb(b486x.eln)

Bill

[hdcc001]

Q: I have a zip file that I would like to import into my project.  Can I do this?

A: Yes it is possible to import zip files.  To accomplish this follow steps below:

        1. From the C/C++ perspective, select File > Import.  The Import window appears. 

        2. Expand General Folder. 

        3. Select Archive File. 

        4. Select Next.  The Archive file window appears.

 

        5. Select Browse button.  The Import from Archive File window appears.

 

        6. Select archive file you want to import in. 

        7. Select Open.  The Import window appears.

 

        8. Expand root folder.

        9. Select Finish.  

[J2MEJediMaster]

Q:In CodeWarrior for StarCore 10, why do I get this message when I attempt to build the project? Error: fopen("*.eld","wb") details : Permission denied.

A: This message is generated by the linker, when it is not able to open the corresponding *.eld/*.elb (or any other extension provided for artifact name) file.

In this case, another program or executable is keeping the *.eld file locked. Usually, this other executable is DE.exe, which is the debugger engine.

To solve this problem, make sure that the previous debug session is closed, or that there is not other DE.exe opened in the Task Manager.

[J2MEJediMaster]

Q: I cannot edit my source files in a CodeWarrior project. I am getting an error message that tells me that the file's encoding is different. What can I do?

A: This message often occurs when a project is sent from one platform to another. (For example, the project is moved from a Linux to a Windows system.)

CodeWarrior supports different text file encodings. In order to choose the encoding appropriate for your project, choose Window > Preferences > General > Workspace. Click on the radio buttons in the Text file encoding group to modify the settings.

[J2MEJediMaster]

Q: Can I set a non-intrusive breakpoint at run-time with CodeWarrior?

A: All breakpoints (any of them: regular, software, hardware) used by CodeWarrior are intrusive. In order to set a breakpoint, the target must be stopped/halted to allow CodeWarrior to modify the appropriate setting.

The only method that will not stop the target to perform these settings is to use the OCE Configurator to set a hardware breakpoint.
The OCE Configurator can be found at Window > Show View > Other > Debug > OCE Configurator.

[Irene]

Q: How does the Eclipse IDE open an already existing project created using CodeWarrior for StarCore 10.x.x?  I can not find the ‘Open Project…’ option in the toolbar. 

A:  You can only open projects that are already in your workspace and have been closed.  To bring an external StarCore project(one that is created on another machine or in another workspace) into your workspace you can follow steps below:

1. From the C/C++ Perspective toolbar, select File > Import. The Import window appears.
2. Expand General folder.
3. Under General, select Existing Projects into Workspace.
4. Select Next.  The Import Projects window appears.
5. Select Browse.  The Browse For Folder window appears.
6. Select the project that you would wish to import. 
7. Select OK.  The Browse For Folder window closes.  The imported projects appears under Projects.
8. Select Finish. 

[Irene]

Q: I right-click on the C/C++ perspective and select the Toggle Toolbar Visibility option.  The Icon bar display disappears.  How can I restore it?

A: The way to restore the toolbar is to select Window >Show Toolbar.

[Irene]

Q: Is there a way to customize the icon bar display?  I removed some icons underneath the Shortcut Categories in the Customize Perspective window but the removed icons still appear.

A: The icons and toolbars are enabled from the plug-ins level.  To manage the toolbars follow steps below:

             1.  From the C/C++ perspective toolbar, select Window  > Customize Perspective.  The Customize Perspective –

                  C/C++ window appears.

             2.  Select Commands tab. 

             3.  Under the Available command groups column, select/deselect toolbars you want or do not want on your IDE.  Under

                  the Toolbar details column you can see the icons that will appear in the toolbar.

                            

[Irene]

Q: Does the project name have the same name of the directory that contains the .project file?

A: Yes it has to be located in the folder with the same name as the project.

[Irene]

Q:  If you save your launch configurations as a local file and then you delete the project, all the local configurations get deleted.  Is there a way around this issue?

A:   Yes there is a way around the issue.  To change the default behavior of this setting follow steps below:

           1.  From the C/C++ perspective toolbar, select Window > Preferences. The Preferences window appears.

           2.  Expand the Run/Debug folder.

           3.  Expand Launching folder.

           4.  Under Launching, select Launch Configurations.  The Launch Configurations settings appear.

           5.  On the right hand side, remove the checkmark from the Delete Configurations when associated

                 resource deleted  checkbox.

             

[Irene]

Q:  I encountered a problem when I tried to save changes to my source file basic_demo.c.   The error message that appears is:

          Save could not be completed. 

          Reason:

          Some characters cannot be mapped using "GBK"  character encoding. 

          Either change the encoding or remove the characters which are not supported by the "GBK" character encoding.

     The same problem happened when I tried to save both files msc815x_config.c and os_config.h.  I re-installed the IDE but it still failed.  I changed the workspace but it still failed.   I looked up in the help system and it said that GBK encoding can be changed by selecting Edit > Set Encoding… Even though I changed these three files, the menu is still not available.  Other files, for example, *.lcf in this project, can be changed and saved.  If I do not include the SmartDSP OS, changes to the MSC8156_main.c can be saved successfully. 

A:  In order to be able to save these files follow steps below:

          1.  From C/C++ perspective toolbar, select Preferences.  The Preferences window appears.

          2.  Expand General Folder.

          3.  Expand Workspace Folder.

          4.  On the right hand side under Text file encoding,  select Other radio button. 

          5.  In the Other textbox, insert GB18030.

          6.  Select Apply.

          7.  Select OK.

[Irene]

Q:  How are the PARENT-COUNT-MyVariable definitions defined, and how do we modify these when there is an error?

A   The Linked resource variable PARENT can be used to define path variables relative to a parent directory of another one. For example, a path variable FOO can be set to ${PARENT-2-PROJECT_LOC}/foo, which is equivalent of setting it to  ${PROJECT_LOC}../../foo.

The reason of this strange syntax is for Eclipse compatibility constraints: we can't have the "..." characters inside a path variable value (at the resource level).

[Irene]

Q:  The project file location in a workspace is kept with an absolute path (file .location in {workspace}\.metadata\.plugins\org.eclipse.core.resources\.projects\projectName), which makes it problematic when the workspace has to change physical location on disk by copying it or moving it to another computer, it would be better if relative paths could be used in order to specify project location.

A: When you create the project in the default location which is the workspace directory, no .location file gets created and you just have to zip up the project and the workspace.  Before you create the zip file, make sure that you remove the following:

          1.  The project build directory since there will be absolute paths in the .mk and .args files.

          2.  The workspace .metadata\.plugins\.org.eclipse.ltk.core.refactoring directory.

          3.  The workspace \.metadata\.plugins\org.eclipse.ltk.core.resources\.history directory.

          4.  Remove the .PDOM files from \.metadata\.plugins\org.eclipse.cdt.core directory. 

[Irene]

Q:  What if changes were made to my source code but they are the wrong changes?  Is there a way to revert to the original contents of the source file?

A:   If you made undesired changes to your source file you can revert to the previous file by following steps below:  

          1.  In the CodeWarrior Projects window right-click on source file, a context menu appears.

          2.  From menu, select Replace With > Local History.  A Compare Window appears. 

          3.  Select the Revision Time from under Revision Time tab.  This window shows a list of the multiple times this file

               was saved and lets you replace it with the one you want.  After you have decided which one you want, press the

               Replace button.  The file will be replaced. 

Note Another way to replace the file is to right-click on source file and select Replace With > Previous from Local History from context menu and it will replace it with the last file that you saved. 

[Irene]

Q: How do I convert Line Delimiters to Unix?

A:  The Default is Windows line delimiters, but if you want to change to them UNIX, then select File > Convert Line Delimiters To….. from the toolbar. 

[Irene]

Q:  When I try to edit my source file I get the following error:

 
               “File ‘/../../filename.c’ is read-only.  Do you wish to make it writable?”

 
     Why am I getting this error and how can I change the source file so that I don’t get this error message?

A:  You are getting this error because the file that you are trying to edit is read-only.  If you don’t want to make it writable

     then select No.  If you want to find out the settings for this file follow steps below:

         1.  From the CodeWarrior Projects window, right-click on source file.  A context menu appears.

         2.  From context menu, select Properties.  The Properties for source file window appears. 

         3.  Select Resource.  The file settings appear on right hand side.

         4.  Select Apply.  To save change that you want to make to file.

         5.  Select OK. The properties window closes.