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.

CCS5 TMS570 project properties

Other Parts Discussed in Thread: TMS570LS20216

Hi,

I'm using Code Composer Studio 5 and TMS570LS20216, in the project properties, under 'Build - Run Time Model Options', there is the options "Designate Code State 16 bit or 32 bit". I want to know:

1. What is the difference between 16 and 32 bit?

2. What should I set for the micro TMS570LS20216?

3. If I set 32 bit, Why does the the CCS compiler gives the error "program will not fit into available memory" (error #10099-D).? Note that, the size of flash memory utilised by the program is higher than that of bank FLASH0 but lower of the sum of banks FLASH0+FLASH1 +FLASH2 +FLASH3.

Thanks

 

 

  • ARM processors support 16 bit (Thumb/Thumb2) and 32 bit (ARM) instruction sets. This option which code state you want to set for your project. For the Cortex M3/R4/A8, the --code_state=16 option generates Thumb-2 code. More details on these instruction sets are best found on ARM Ltd's web site: http://www.arm.com

    Regarding how these options are set/supported by our compiler, please refer to the ARM Compiler Users Guide.

    TMS570LS20216 is a Cortex R4 so should support both ARM(32-bit) and Thumb2 (16-bit) so you can set to either depending on your requirements.

    enrico terraneo said:
    If I set 32 bit, Why does the the CCS compiler gives the error "program will not fit into available memory" (error #10099-D).? Note that, the size of flash memory utilised by the program is higher than that of bank FLASH0 but lower of the sum of banks FLASH0+FLASH1 +FLASH2 +FLASH3.

    If you get the error "program will not fit into available memory" then the code size must be too large to fit into the available Flash memory. The allocation of code to memory region is dependent on the specifications in your linker command file, and you may be able to modify it to get the code to fit. Before jumping into customizing linker command files, it is best to have some understanding of the syntax and specifications of the linker command file, and I would suggest taking a look at Chapter 7, and specifically sections 7.5.4.6 and 7.5.4.7 of the Assembly Language Tools Users Guide.