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.

TMS320F280049C-Q1: Change order of initialization in sysconfig

Part Number: TMS320F280049C-Q1
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Tool/software:

Hi TI Team,

I use the current CCS 20.3.0.14_1.9.0 to program the 280049 C2000 controller
Is it possible to change the order of initialization in the auto-generated syscfg board.c for Texas Instruments C2000 microcontrollers?

In the (automatically) generated file, the GPIOs (PinMux_init) are first configured and then the PWM module is configured. However, within the PWM driver, the trip zones are last configured. In my case, this will cause a short pulse on the PWM GPIO to occur during start-up. Is there a way, for example, to initialize the trip zones before the dead-band module or to configure the GPIOs (PinMux_init) only after the PWM module without sacrificing the automatic generation of the board.c by syscfg?

I would be very pleased to have suggestions on how to influence the initialization sequence (or other best practices to avoid unwanted glitches at the output during system startup and still use the syscfg automation)!

BR FM

  • FM

    To change the order of initialization in the auto-generated code from SysConfig requires changes in the C2000Ware Sysconfig metadata. 

    One option is to copy the generated code, update it locally , include it and then  exclude the sysconfig file from the project. 

    Best Regards

    Siddharth