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.

CCS/UCD3138: About setting of UCD 3138

Part Number: UCD3138

Tool/software: Code Composer Studio

We downloaded and use the PSFB program of this URL(www.ti.com/tool/ucd3138fw-psfb ).

We have four questions related to this program.

(1) About software diagrams

We want Software diagrams of PSFB program.

Are there software diagrams?

(2) About configure of Fusion Studio

What part of software diagrams does command of Limits act?

We would like to know command overview.

(3) About monitor of fusion studio

What part of software diagrams does monitor of fusion studio display?

We also would like to know the relationship between the value that are displayed and the control.

(4) About protection function

What kind of protection does the software provide for PWM control?

If the protection is provided, how can it be known?

best regards,



  • By software diagrams, I presume you mean flow charts?  We do not provide flow charts for most of our firmware.  There is a general consensus among programmers that using flow charts leads to bad code and bad documentation for complex programs.  Starting in the 1980s, pseudo code has been preferred, with more advanced techniques emerging later. 

    For the PSFB, the main documentation is the code itself, which is available on the web.  It's relatively well structured and commented. 

    I've already told you where to find the software fault detection.  

    If you look at the initialization of the various peripherals, and study the UCD3138 Technical Reference manual, you can see the initialization of the hardware protections. 

    If you look at the values which are used for software fault protection, and the values which are loaded into the DACs for the analog comparators, you will see the end point of the limit settings.  You can follow the equations back through the code to see how the values come from initialization settings, and from PMBus commands.