• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 240 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.

Original question:

TIDM-DC-DC-BUCK: Adapting solution to F28P55x

TIDM-DC-DC-BUCK: F28P55x migration: compensation design

Zachary Miles
Prodigy 60 points

Part Number: TIDM-DC-DC-BUCK
Other Parts Discussed in Thread: POWERSUITE, SYSCONFIG

Hi,

I have been working on migrating the TIDM-DC-DC-BUCK reference design from the F28004x to the F28P55x. I started with a F28P55x 'Universal Project', copied over files from F28004x, and made various edits to get it to work. This new project is entirely independent from the powerSUITE structure. 

I am mostly done, but still a bit stuck implementing changes in the buck converter parameters (Celec, ESRelec, etc). In the original project, you would update the sysconfig file, which would populate 'Kit.json' and I believe something in the background would implement the changes with the Solution Adapter and Compensation Designer. 

On this new Universal Project, the best idea I have is to code up my own Compensation Designer in Python/MATLAB, but even then I am not super confident how I should implement changes in the buck converter parameters. 

  • 0
    TI__Expert 4665 points

    In the powersuite integrated project when you select the hardware parameters and build the project a new header file called settings .h is generated. This file has all the values in the form of #defines which corresponds to values entered in syscfg. Please copy paste this file and modify the hardware parameters.

  • 0 in reply to Pawan Nayak
    Prodigy 60 points

    It appears that the buck_settings.h file (inserted in this message) in this project does not contain buck converter power stage parameters, like resistances, inductance, capacitances, etc. I believe these reside in 'Kit.json'. It does contain nominal operating points and control law coefficients, sure. The bottom line is that it isn't clear to me how the buck converter power stage parameters impact the project.

    I want to be able to change just a specific capacitance because the newer version of the buck converter design has a single updated output capacitor and the default coefficients don't reflect that. Furthermore, I am curious as to how the parameters spelled out in 'Kit.json' impact the project. I believe it impacts the compensator design for closed loop by somehow playing a role in the calculation of DCL DF22 coefficients, but I am not sure. I would value your feedback on this.

    buck_settings.h

  • 0 in reply to Zachary Miles
    TI__Expert 4665 points

    Hi Zachary, I will request the design expert to help you on this.

  • 0 in reply to Pawan Nayak
    TI__Expert 7410 points

    Hello Zach,

    I will take a look and give initial feedback by end of this week.

  • 0
    TI__Expert 7410 points

    Zach,

    In powerSUITE-based projects, buck_settings.h is auto-generated at build time from selections made in main.syscfg. It intentionally contains only the results of the compensation design (coefficients and operating points), not the underlying power stage parameters. The power stage parameters live in Kit.json because they serve as inputs to the coefficient calculation, not runtime configuration.

    For non-powerSUITE projects, buck_settings.h is a normal editable project file where you define global configuration settings. Either way, the buck.c and buck.h files implement the DCL compensator support variables that consume these coefficients.

    Please refer to page 52 of TIDM-DC-DC-BUCK solution user's guide for better code structure understanding: C2000Tm Digital Power Buck Converter BoosterPackTm Design Guide (Rev. A)