• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 252 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28377S: Upgrading to SysConfig 1.17 giving lot of warnings for previous EPWM settings

Asad Hameed
Intellectual 705 points
Part Number: TMS320F28377S
Other Parts Discussed in Thread: SYSCONFIG

We have upgraded to SysConfig tool version 1.17 some time ago. After this update we are getting new warnings with the existing EPWM settings.

We don't understand the above warnings and the resolution as we are already assigning a non-zero counter compare values.

Similarly the following warning is coming:

We had assign a value 0 as we don't want any phase shift between the Sync input EPWM and the EPWM for which the setting is applied. 

These warnings come during the build process. I know we can suppress these warnings but we want to better understand if these warnings actually require some modification/changes from our side for proper resolution.

  • 0
    TI__Mastermind 36055 points

    Hi, 

    Will check and get back to you in couple of  days.

    Best Regards

    Siddharth

  • 0 in reply to Siddharth Deshpande
    TI__Mastermind 36055 points

    Hi,

    Is it possible to share the sysconfig file that you are using? 

    Looks like these warning can be suppressed since you are already providing valid values.

    Best Regards

    Siddharth

  • 0 in reply to Siddharth Deshpande
    TI__Mastermind 26636 points

    This warning is related to run time, within the TRM we have a note under Configuration Requirements for Common Waveforms that talk more about this. Depending on what counter mode you're running in, setting CMPA/CMPB to a value will depend on loading condition. Since you're running in up/down count mode and loading on ZRO, you should use CMPA/B values greater than or equal to 1. If you load on TBPRD, you can use CMPA/B values less than or equal to TBPRD -1.

    This warning you can suppress, we need to update this because it is referring to clearing the TBCTL[PHSEN] bit, not the TBPHS value. I have filed a ticket for this to have this fixed. 

    Best regards,

    Ryan Ma