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.

Template projects for digital power library

Part Number: F280025
Other Parts Discussed in Thread: CONTROLSUITE, C2000WARE, C2000WARE-DIGITALPOWER-SDK, TIDM-1001, TIDM-02000, TIDA-01606, TIDA-010062, POWERSUITE

Dear Champs,

I am asking this for our customer.

In legacy controlSUITE, we have template projects for digital power library, and the projects are equipped with some software framework like state machines.

Template projects for digital power library like below.

C:\TI\controlSUITE\development_kits\TemplateProjects\DPLibv3_4Template-F2803x

C:\TI\controlSUITE\development_kits\TemplateProjects\DPLibv3_4Template-F2802x

The user has experience on it using F2802x/3x and wants to migrate onto F28002x.

Would you please show us if we have similar projects/templates on F28002x?

If not, do you have any suggestion for us to do similar software framework with state machine and for the newer digital power library on F28002x?

Wayne Huang

  • Wayne,

    Did you check C2000Ware and DP SDK? I will ask Ozino to help on this.

    rgds

    Shamim

  • Wayne,

    Did you check C2000Ware and DP SDK? I will ask Ozino to help on this.

    rgds

    Shamim

  • Dear Shamim,

    I do not find similar template/starting projects in C2000ware/DigitalPowerSDK.

    Would you please show us explicitly if any?

    When you start a new digital power reference design on F28004x/2x, how do you start the software framework?

    Wayne Huang

  • Wayne, 

    There are currently no templates available in the C2000Ware-DigitalPower-SDK. Is there an existing solution available in the SDK that the customer would like to port? I would recommend using the TIDM-1001 project as reference project for an F28002x based project. This project contains the code and directory structure framework. Please let me know if you have anymore questions.

    Regards,

    Ozino

  • Dear Ozino,

    Their purpose is to build their housekeeping/communication like I2C/PMBus on top of our template project first as a generic software framework for secondary side development.

    Then, they are planning to port the LLC part (HB LLC) of TIDA-10062 and then PSFB DCDC of TIDM-02000.

    We understand to start it from an existing reference design, but it takes time to study which part should be removed, especially they are new to our newer reference design on F28004x/2x (compared to those on F2802x/3x).

    May we know how you start a new reference design?

    Did you always use an arbitrary reference design and then remove the power control part and unnecessary part?

    Is there a systematic way and cleaner way for you to start a new reference design?

    Wayne Huang

  • Wayne,

    Typically we start new reference designs by using an existing reference design. At this point, we do not have a very good reference to get you started for new designs.

    For your information, our new SW distribution is now C2000Ware-DigitalPower-SDK, we have moved away from the assembly macro based digital power library because unlike the F2802x and F2803x , F28004x is a floating point device. 

    And the use of template projects is limited, rather we are focusing on providing a good starting point from a topology perspective. You can look at the new SW framework in the SDK. 

    Since you have plans to include two existing designs, I would recommend starting with the TIDM-02000 and TIDA-010062 examples. Use the TIDA-01606/010039 software example for steps on how to incorporate two designs together. Once you have your topology based code, I would then add your new logic, I2C/PMBus.

    For your reference, here is a description of the software stack for a typical solution, following files are considered part of a solution, 

    1. solution.c/h files, or commonly called the solution/application files (device agnostic software; reusable across different devices)
    2. solution_hal.c/h file or commonly called board/hal/device files (code specific to a device e.g. ADC/PWM drivers, board protection schemes)
    3. main.c / main.cla that consists of the main function of the C project and also the CLA tasks. This file consists of the ISR framework and calls routines in other files. 
    4. solution-settings.h file, or the powerSUITE generated file which consists of all the settings required for the solution to work, main, solution and board files use settings described in this file. 

    Regards,

    Ozino