Diary of the trouble of building TMS320F28379D project with css6.0

fish001

Diary of the trouble of building TMS320F28379D project with css6.0 [Copy link]

As someone who is familiar with using Keil to develop ST chips, when I first came into contact with TI chips, I found that the development environments of the two are really very different. After struggling for a few days, I finally completed the establishment of the project. In order to prevent later brothers from suffering, I compiled a document as a record.

Software Installation
　　TI chip development mainly uses CCS. Although some chips can be developed with Keil, DSP chips must use CCS. CCS software is available for free download on TI's official website. The installation process of the higher version is fool-proof. If you are not sure when choosing the installation items, it is best to select all, otherwise it will be another hassle.

　　The second thing to install is the chip help document. TMS320F28379D belongs to the c2000 series chip. The help document is c2000ware, which can also be downloaded from the official website. It is a fool-proof installation. Different series of chips have different help document software, so you need to go to the official website to check.

2. Use of c2000ware

　　After installing c2000ware, let's take a look at the file structure

If you are using TI's official development board, there is a schematic diagram corresponding to the PCB in boards, and there are firmware library interface documents and routines for the c2000 series chips in device_support. Take TMS320F28379D as an example.

I personally recommend using the firmware library interface for programming, which is intuitive and less prone to errors. F2837xD_DriverLib_Users_Guide is the firmware library interface document I mainly use. Next, find where the firmware library routine is. We click on F2837xD_DEV_USER_GUIDE, and there is a paragraph of text:

It can be seen that the routines in the firmware library format we want are in the driverlib/f2837xD/example folder under the c2000 directory. Next, we can import the routines from this directory in ccs.

　　3. Use of CCS

The layout of the CCS software is actually similar to that of general development software, with the project directory on the left, the code segment on the right, and the compilation and debugging window at the bottom.

First we need to import an empty routine

Status bar Project->import ccs projects

Select browse to find empty_drivelib_project in the routine directory mentioned above. It is recommended to select Copy projects into workspace, which will copy the source files to your own working directory without directly modifying the source files.

During the actual operation, I encountered a problem that the compiler version was not supported. Here is a recommended website:

http://software-dl.ti.com/codegen/non-esd/downloads/download.htm#C2000

Download the corresponding version of the compiler and install it in the ccs installation directory

After successful import, you can compile

Click the small hammer button to compile. There are two options for compilation, one is RAM and the other is FLASH. Generally, RAM is used during development, which compiles faster. The FLASH format can run offline and will not be lost during power failure.

Click the little spider button to debug, and you can connect to the development board for debugging.

This is the structure of the entire project. If the user adds a directory to the project, the include directory search for the project needs to be set by the user. Right-click the project--->properties--->include Options, add the directory

Sometimes you need to modify the burner, right click the project--->new--->Target Configuration File

Select the device and downloader, and finally click save.

Then you can enjoy programming. It is recommended to refer to F2837xD_DriverLib_Users_Guide.