• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 80 subscribers
  • Views 84 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TIDM-02014: Porting Reference code to TMS320F280049C

Eui-Heon Jung
Expert 1105 points
Part Number: TIDM-02014
Other Parts Discussed in Thread: TMS320F280039C, SYSCONFIG, C2000WARE, TMS320F280049C, TMS320F280039

Dear Experts,

I am porting the TIDM-02014 code coded in TMS320F280039C to TMS320280049C. As a result of the overall investigation, it appears that TIDM-02014 supports only TMS320F28003x and 2x peripheral device settings using sysconfig. If I'm porting that reference design to the TMS320F280049C, how can I use sysconfig to automatically configure the peripherals or how can I modify the xx.js, xx.json and xx.projectspec files?

Sincerely,

Eui-heon

  • 0
    Expert 1105 points

    Dear Expert,

    I modified the files below for porting, and also modify the path to necessary files, cmd file and traction_inv_f28004x_cpu1.projectspec. and make 28004x folder.

     C:\ti\c2000\C2000Ware_MotorControl_SDK_5_01_00_00\.metadata\ sdk.json

     C:\ti\c2000\C2000Ware_MotorControl_SDK_5_01_00_00\.metadata\.tirex\ macros.tirex.json

     C:\ti\c2000\C2000Ware_MotorControl_SDK_5_01_00_00\.metadata\.tirex\ MotorControlSDK.content.tirex.json

     C:\ti\c2000\C2000Ware_MotorControl_SDK_5_01_00_00\.metadata\.tirex\.dependencies\ dependency-mapping.json

     C:\ti\c2000\C2000Ware_MotorControl_SDK_5_01_00_00\.metadata\.tirex\.dependencies\ traction_inv_f28003x_cpu1_0.dependency.tirex.json

    In my opinion, The remaining work appears to be setting up peripheral devices and creating related files. There seem to be two ways to do this.

    (Method 1) Modify the existing hal.syscfg using the sysconfig file. : From TMS320F280039 to TMS320F280049C

    (Method 2) Modify hal related files, directly. 

    It seems desirable to work with (method 1) for the next revision, but this task is not easy. As it stands, I would like your advice if I am working with (Method 1)

    Sincerely,

    Eui-heon