• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 83 subscribers
  • Views 351 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Compiler/TMS320F28388D: General Configurations for C2000 Compiler

user6114104
Intellectual 720 points
Part Number: TMS320F28388D
Other Parts Discussed in Thread: C2000WARE

Tool/software: TI C/C++ Compiler

Hi all,

According to the demo projects supported by C2000Ware (C2000Ware_2_01_00_00) and SYS/BIOS (bios_6_76_01_12), I found different configurations of startup models between them.

In detail, there are two startup models for C2000Ware projects, i.e. RAM model and ROM model, refer to the snapshot below:

Contrastly, there are also two diferent configuration selections ( Debug vs. Release) for SYS/BIOS projects, refer to the snapshot below:

So what's the reasons for the diferences between TI-RTOS projects and Non-RTOS projects?

Thanks.

QL

  • 0
    TI__Guru**** 249260 points

    I'll explain the general concepts behind RAM and ROM model, and build configurations like Debug and Release.  You'll see they are independent configuration parameters. 

    General background on RAM and ROM model ... Consider this C code fragment ...

    int global_variable = 156;

    Where does the value 156 reside?  How it is copied into the memory location for global_variable before main starts?  There are two different ways to do it.  One is called ROM model and the other is called RAM model.  This choice is implemented by a command line option to the linker.  There is much more to it than that, but this is enough detail for now.

    General background on build configurations ... Please see the article on Build Configurations.  Note how this is a choice made at the level of a CCS project.  That is, a higher level than the choice between RAM and ROM model.  

     Given this background, it probably now makes sense to say a non-RTOS project and a different RTOS project could make the same, or different, choices for each configuration parameter.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 720 points

    Dear George,

    Thanks for your information!

    I still have a question of Build Configuration Management.

    Is there a standalone file to save build configurations? When I try to new a Debug Configuration in C2000Ware project just like below,

    I don't know how to do the settings just like what have been done in a RTOS project. As the picture above, I can only copy settings from existing configuration,like CPU1_RAM and CPU1_FLASH. However, I think they are different between RTOS and the original C2000Ware project. So what could I do now? It could be better to have a standalone file for build configuration settings.

    Thanks!

    QL

  • 0 in reply to user6114104
    TI__Guru**** 173310 points

    There isn't a direct way to save the build configuration options to a text file. However, you could take a look at the .cproject file in the project folder, which will contain all the tool options, and extract the necessary details from there.

    A TI-RTOS project is very different from a non RTOS project (like the ones in C2000Ware). It includes a RTOS configuration file and XDCtools settings and options to build the configuration file, and the system configuration and initialization is also done differently. I would suggest starting with either a RTOS or non-RTOS example project and building upon it.

    If you are asking about starting with C2000Ware and then porting the project to TI-RTOS, then I would suggest posting a new question to the C2000 forum as the experts there would be in a better position to provide advise on that topic.