• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 414 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.

TMS320F28379D: Vienna Kit issue in compiling project

Colombo Carlo
Mastermind 24620 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: CONTROLSUITE, SFRA

Hello everybody , 

for legacy I m using Controlsuite .  I am on the latest and using CCS8.2 ( again for legacy ) .

now  if I run the Vienna Kit project and compile for 377D  everything works .  If in project I change to 28379D  it fails plenty of errors .

Now I  found the issue is related to differnet  command file in use :

 

F2837x_Headers_nonBIOS_cpu1.cmd is used in defualt   project  by f28377D

 

2837x_FLASH_lnk_cpu1.cmd  this is the one  used when I change to f28379D 

why this ?  if I change file  for 379D it works fine .

coudl you give me more details on why this file is in use ?

thank you veyr much

best regards

Carlo

 

 

  • 0
    TI__Guru 54175 points

    When you update the device in CCS, it tries to be helpful and replace the cmd files the project is using with cmd files that CCS has set as its default for the device. Since it's just a default though, it's not customized for your project and that can cause errors.

    In this case, just removing 2837x_FLASH_lnk_cpu1.cmd and adding the original cmd files back into the project is fine. I believe F28377D and F28379D have the same RAM/FLASH size and addresses.

    Whitney

  • 0 in reply to Whitney Dewey
    TI__Mastermind 24620 points

    Hi Whitney ,

    OK   but why the Vienna project is  by default using a differnet  cmd than standard one ?  any extra care to take in account for doing this ?

    regards
    Carlo

  • 0 in reply to Colombo Carlo
    TI__Guru 54175 points

    The CCS provided default cmd file is just a starting point. Applications are going to have their own section definitions, placements, and sizes. In the case of this Vienna project for example, there are some application specific variables that need to be placed into specific RAM sections (see SFRA_Data, FPUmathTables, cntl_coeff_RAM, etc...), so the custom pfc3phvienna_ram/flash_cpu1_f2837x.cmd file was created.

    Whitney