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.

Does UCD3138 / Cyclone can compiled by CCS4 or CCS5?

Other Parts Discussed in Thread: UCD3138

Dear TI,

         My question as title,

         Does UCD3138 / Cyclone can compiled by version CCS4 or above??

  • Yung-Cheng Hong said:
    Does UCD3138 / Cyclone can compiled by version CCS4 or above??

    Sorry. CCS does not support this part.

     

  • Actually, I am using CCS3.3 compiler for UCD3138,

    I am just wanna make sure, if I upgrade my CCS to 4.0 or above.

    Does it still support for UCD3138.

    Becasue I can't find the device Cyclone in eclips environment.

  • Ok, then I may be mistaken, as I am not that familiar with the UCD3138. Which compiler executable do you use with it in CCS 3.3?

  • Sorry for my question is not clear,

    UCD3138 is an ARM7 base contorller for Digital Power application.

    When I use CCS 3.3 compiler, I selected ARM7 device for UCD3138 to compiler C code.

    It comes out a xxx.x0 file for me to load the code to controller by USB-to-GPIO connector.

    I used the same way on CCS 4.0 and CCS 5.0.

    But it can't not produced any xxx.x0 file.

    So, I just wanna to make sure, does CCS 4.0 and CCS 5.0 support Cyclone device.

  • Yung-Cheng Hong said:

    UCD3138 is an ARM7 base contorller for Digital Power application.

    When I use CCS 3.3 compiler, I selected ARM7 device for UCD3138 to compiler C code.

    You can still build for ARM7 in CCSv4 and v5. When creating a new project, you can select as the Device Family as ARM, and Device Variant as Generic ARM7 Device.

    Yung-Cheng Hong said:

    It comes out a xxx.x0 file for me to load the code to controller by USB-to-GPIO connector.

    I assume the .x0 file is a hex output after converting the .out file generated by the compiler tools into hex. The default output from the TI codegen tools is .out but you probably have a step added as a post-build step in CCS 3.3 to convert the .out to .x0. If so, you can do the same in CCSv4/5, by adding a post-build step in the Project Properties->CCS Build->Build Steps tab to convert the .out file to hex.