Project Migration

In many cases, we need to hand over the project we wrote to others. In order to ensure that the project can be successfully migrated and run in the new environment, we need to follow certain steps to package and migrate. In this section, we will introduce how to migrate the example project in the TI SDK to other platforms or devices, and provide some common precautions.

1. Find the routine to be migrated and copy it

Select the routine you need. Here we use the routine "Empty Project Empty".

2. Paste the copied routine into the root directory of the SDK

Paste the routine file you just copied into the root directory of the SDK.

3. Copy driverlib files

Enter the <SDK root directory>\source\ti\driverlib path in the SDK directory and copy all the files in the driverlib folder (note: only copy the files, not the folder).

4. Create a new ti folder and paste the files

Go back to the path of the example, create a new ti folder, and paste all the files copied previously into the newly created ti folder.

5. Delete unnecessary folders

Delete unnecessary folders in the project to reduce the project size.

Complete project structure:

6. Related configuration under keil

1. Open the keil project file.

2. Open Keil project management.

3. In the Keil project, delete the files in the Driverlib folder (if there is no such folder, you can skip this step).

4. Add the previously copied files to the new Driverlib folder.

5. Click the "magic wand" to update the header file path.

6. Modify the path in User-> Before Build/Rebuild.

The current path is as follows:

cmd.exe /C "$P../../../../../../tools/keil/syscfg.bat '$P' empty.syscfg"

In fact, the modification method is to specify /tools/keil/syscfg.bat under the SDK path. ../ represents returning to the previous folder from the keil startup file location of the project. The tools folder is in the SDK root directory. So the path should be changed to the following:

xxxxxxxxxx
cmd.exe /C "$P../../tools/keil/syscfg.bat '$P' empty.syscfg"

7. Delete the file path in Linker -> Misc controls

8. After the modification, save and compile, there will be no path problem.