TMS320F28377S: Scheme for creating a fresh ELF project

Lukasz Przenioslo

Part Number: TMS320F28377S
Other Parts Discussed in Thread: C2000WARE

Hello there,

I am new to the C2000 world and CCS. I would like to create a new project for the TMS320F28377S launchpad with the most modern approach available, that is driverlib and EABI approach.

I have chosen to create a new project in CCS for the given MCU with the given binary interface. I get the following warning from the linker when building a basic main.c application:

warning #10440-D: creating output section ".bss" without a SECTIONS specification.  For additional information on this section, please see the 'C2000 Migration from COFF to EABI' guide at https://software-dl.ti.com/ccs/esd/documents/C2000_c28x_migration_from_coff_to_eabi.html
warning #10440-D: creating output section ".const" without a SECTIONS specification.  For additional information on this section, please see the 'C2000 Migration from COFF to EABI' guide at https://software-dl.ti.com/ccs/esd/documents/C2000_c28x_migration_from_coff_to_eabi.html
warning #10440-D: creating output section ".sysmem" without a SECTIONS specification.  For additional information on this section, please see the 'C2000 Migration from COFF to EABI' guide at https://software-dl.ti.com/ccs/esd/documents/C2000_c28x_migration_from_coff_to_eabi.html
warning #10440-D: creating output section ".init_array" without a SECTIONS specification.  For additional information on this section, please see the 'C2000 Migration from COFF to EABI' guide at https://software-dl.ti.com/ccs/esd/documents/C2000_c28x_migration_from_coff_to_eabi.html
warning #10247-D: creating output section ".data" without a SECTIONS specification

So I go to the proposed page. But then, I am not migrating anything... I just want to create a new project. Do I really need to edit some linker files (given memory section names) manually? I am not even sure how from the given page.

As a test I edited the proposed names in the 28377S_FLASH_lnk.cmd file, but then the warning was still complaining about the .data section, which is not defined there.

What is the right approach here? I would appreciate all help.

over 2 years ago

0 Santosh Jha over 2 years ago

TI__Guru 50611 points

Hi,

Please start with empty project project with C2000Ware SDK.

It will automatically have include path, linker path, device type set for you.

C:9/ti/c2000/C2000Ware_4_03_00_00/driverlib/f2837xd/examples/c28x/empty_projects

Please refer to C2000 Academy to learn more details:

https://dev.ti.com/tirex/explore/node?node=A__Abxz11dQxsbltUNf1sAMlg__c2000Academy__jEBbtmC__LATEST&placeholder=true

Regards, Santosh

0 Lukasz Przenioslo over 2 years ago in reply to Santosh Jha

Expert 2630 points

Hi Santosh Jha, thank you for the answer.

So, are you saying that the "by design" approach for creating new projects in CCS is to import existing "empty" projects with some predefined paths?

0 Santosh Jha over 2 years ago in reply to Lukasz Przenioslo

TI__Guru 50611 points

Hi Lukasz,

Starting with empty_project is best approach. You have all the setup needed for the device are already taken care for you. Just rename the project and .c file after you import the project.

Regards, Santosh

0 Santosh Jha over 2 years ago in reply to Santosh Jha

TI__Guru 50611 points

Just to add on to what I said earlier, you can import the project to any workspace, and there is no hardcoding for the path. It is using environment variables for CCS install folder, and C2000Ware install folder.

Regards, Santosh

0 Lukasz Przenioslo over 2 years ago in reply to Santosh Jha

Expert 2630 points

Hi, thanks again for the answer. So there exists an "empty_project" for every si gle MCU that one can export?

Also, depending on the version of c2000ware, each person using the project (i.e., if its version controlled) will have potentially different libs when building?

+1 Santosh Jha over 2 years ago in reply to Lukasz Przenioslo

TI__Guru 50611 points

Hi,

Lukasz Przenioslo said:
So there exists an "empty_project" for every si gle MCU that one can export?

Yes, there is a empty_project for each device.

Lukasz Przenioslo said:
Also, depending on the version of c2000ware, each person using the project (i.e., if its version controlled) will have potentially different libs when building?

Once you import the project, you can add your custom libraries in your project and manage the version control. It is completely independent of the original project.

Regards, Santosh

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F28377S: Scheme for creating a fresh ELF project