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 software writing of UCD 3138

Part Number: UCD3138

Tool/software: Code Composer Studio

Immediate response is highly appreciated.

 

Currently, we were able to scan UCD3138 with the UCD 3xxx desigener GUI.

However, Fusion Digital Power Designer GUI was not able to scan and use it. How do We use Fusion Digital Power Designer GUI?

Do We need to write programs using the UCD 3xxx designer GUI?

 

best regards,

  • You say you can scan it.  Does this mean that you can find the ROM mode part?  I would suggest using the Device GUI to write the initial programs.

    Or you can start with one of the TI EVM codes and work from there.  The Device GUI can start with ROM mode and then download a program.  If the designer GUI finds a part with ROM mode, it will command the part to execute it's program, and then it expects to find a program which supports quite a few messages, some standard PMBus commands, and some TI manufacturer commands.  The design GUI is really intended for power supply design and tuning, not for program development. 

  • Thank you for your reply.

     We say we can scan it. This means that we can scan with Scan Device in ROM Mode.


     

    Our goal is to use the Fusion Studio Online GUI. Please tell me the procedure from ROM mode.

    We saw TI traning video. Do We need to install CCS to write programs in the Device GUI?

    If possible, I would like to use the same program as used in the evaluation model (UCD3138PSFBEVM-027).

    Best regards,

  • If you download the same program as used in the PSFBEVM, you should be able to download the program and interface to it with the Designer GUI.  Please don't program the checksum when you do.  You probably will need to use CCS 6 at some point, because even if your own board is an exact copy of the PSFB EVM, the code is an evaluation code, not really a production ready code.  If your board is not a close copy of the EVM, then you will need to adjust things to work with the changes.  The download format is a .x0 format.  I suspect that you can find an already compiled .x0 file in the downloaded code for the UCD3138, but I'm not sure. 

    I suggest that you try downloading the first lab from the video training first just as a simple way to make sure that the compiling and downloading system is working. 

  • Thank you for your reply.

    we downloaded the same program as used in the PSFBEVM. However, the folloning pulse waves are observed.

    Is there something that is considered to be the cause of that?

    DPWM0A(Yellow) and DPWM0B(Blue)pins

    best regards,

  • If your board isn't exactly the same as the PSFB, there's no easy way to tell what the program will do.

    I would suggest using the Fusion GUI to see if it finds the PSFB and works with it.  that was one of your goals anyway, right, to use the Fusion GUI?

  • Thank you for your reply.

     

    We are using the Fusion GUI. The previous question was solved, PSFB was found.

    However, We have another question.

     

    We scanned and downloaded same program as used in the PSFBEVM .

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

    We tried both codes. as a result, We would like to use the code of the PSFBEVM.

    However, using the code of the PSFBEVM, There is not the command of VIN_OFF and VIN_ON in Fusion GUI.

     

    The following figure is what use code of PSFBEVM and URL.


     

    Is there a way to display the VIN_OFF or VIN_ON command when using the code of PSFBEVM?

    Is it possible in the Fusion GUI? Or do we need to use Code Composer Studio?


    best regards,



  • Hello,

    Ian will help you to address this. Briefly, the GUI will display what the command bitmasks indicate to display. So the bitmask will need to be updated to reflect these commands and secondly you will need to also support those commands in the firmware.
  • Looking at the latest version of the PSFB code, it should be provide vin off and vin_on, and show the commands as supported.  I'm on a business trip right now, so I can't download it and check it.  Are you using the latest version? 

  • Thank you for your reply

    We use PSFBFirmware-1.1-windows-installer and Code Composer Studio 6.2.0 to create the x0 file.

    We attempted to install the latest version 8 of Code Composer Studio but could not install it.  Do we need to use the latest version?

    best regards,

  • I think you are saying that if you use the psfb 1.1, you get the vin on and off? You certainly should, and that is the version you should use. I'm not sure what code comes with the EVM, but it is an older version. It is not a trivial task to add these functions to the PMBus. You will probably also need to add the code which implements vin_on and vin_off into the control code, as well as translation between the ADC value and the actual voltages, Dflash storage and retrieval of the parameters, and, of course, the PMBus commands. In PSFB 1.1, this is all done for you.
    If you want to see what it is, you can start here in pmbus_topology.c:

    #define PMBUS_CMD_35_FUNCTION_POINTER pmbus_read_write_vin_on_limit
    #define PMBUS_CMD_35_QUERY (QUERY_COMMAND_SUPPORTED + QUERY_WRITE_SUPPORTED + QUERY_READ_SUPPORTED + QUERY_LINEAR)

    #define PMBUS_CMD_36_FUNCTION_POINTER pmbus_read_write_vin_off_limit
    #define PMBUS_CMD_36_QUERY (QUERY_COMMAND_SUPPORTED + QUERY_WRITE_SUPPORTED + QUERY_READ_SUPPORTED + QUERY_LINEAR)

    If you look at those functions pointed to above, you can see where some of the data is stored. If you do global searches on the variables, you will see how it is stored in data flash, and how it is translated, and how it is used in the running code.

    If you really want to, then you can try to transfer all those functions to the older version of the code for the EVM, it source is available. Note that the older code probably uses a slightly different way of calling PMBus commands, but that doesn't make a big difference.

    In PSFB 1.1, the enable bits for the commands also need to be set, which they are in the default version on the web.


    #define PMBUS_CMD_35_ENABLE (1)
    #define PMBUS_CMD_36_ENABLE (1)
  • Hello,

    Please use the guidance from this page to set the environment correctly.
    e2e.ti.com/.../2736436
    Thanks,
    Sanatan