• TI Thinks Resolved

CCS/UCD3138A64OEVM-662: UCD138A64 and code composer studio validation id doubt.

Part Number: UCD3138A64OEVM-662

Tool/software: Code Composer Studio

We are using UCD3138A64 along with the XDS100V2 debug probe. 

As suggested in the earlier thread,

When we load the .x0 file while the box is checked, we get the following output

When we load the .out file , we get the following output. 

The console displays "Device ID Validation option not selected."

The above two outputs are not similar to the one's shown in the TI UCD3138 training video series.

Also, the USB to GPIO probe is not used instead we have powered the board externally and we are using XDS100V2 JTAG to program the board.

So is that JTAG sufficient for all the necessary operations we will be performing? 

  • The interface has changed since the training video was made. It looks like you can program from the .x0 file, and you are not asking how to use the .out file. If you want help with that, please ask. I will answer the main question that I see, which is "is that JTAG sufficient for all the necessary operations we will be performing? ". I would highly recommend using the PMBus interface with the memory debugger if you plan to debug code. The UCD3138 family requires that you stop the processor to read the RAM using JTAG. For PFC, that can be disastrous very easily, since the software is controlling the current loop to match the input AC voltage. You need to keep it running. There is also a fair amount of dynamic software running on the various DC to DC EVMs. And generally the most debugging is needed for the dynamic issues. So we tend to primarily use the PMBus interface with the memory debugger. If you're an experienced program, there won't be that many logic errors in the code, it will be more necessary to look at dynamic issues. So we use the memory debugger, as well as using spare I/O lines to put software events out on pins so you can use a scope to compare the timing of the software events to the events on the power supply analog side.

    Happy Debugging,

    Ian Bower

  • In reply to Ian Bower:

    Thank you for your previous answer.

    We are not yet clear on how to proceed with the .x0 file and the .out file too. Because since the video exists for .out we have no way to know what further steps need to be taken for the .x0 file too.

    We have to at least run a blinky code on the UCD3138A64 board and our final aim is to use it for functioning but the resources available are very technical for us since we are final year graduation students. Could you at least help us with the exact steps we need to take for the blinky code to run.  

  • In reply to Shoeb ahmed:

    hello Shoeb
    Which version of CCS are you using? I will replicate here and advise.
    Best Regards
    Cormac
  • In reply to Cormac Harrington:

    We are using CCSV8.

  • In reply to Shoeb ahmed:

    hello again
    I would recommend just using the .out file and not selecting "Validate against Device ID..." and ignoring the message.
    Or else, you can use the .x0 file and select the option "Validate against Device ID...".
    To be honest it doesn't really matter that much. The main thing is that the device is being programmed successfully.
    As Ian mentioned, the PMBus based GUI is also good, as well as all of the positives that Ian mentioned, it is more mature than the JTAG solution.
    As a first step, I would recommend using the PMBus GUI to program the device. Then move onto Uniflash / CCS.
    Send me some screenshots of your Uniflash configuration if you would like me to review.
    Best regards
    Cormac