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.

TMS320F28075: TMS320F28075

Part Number: TMS320F28075
Other Parts Discussed in Thread: SYSCONFIG, SFRA, C2000WARE

Hi Omer,

We are having issues migrating from 280049 to 2837x and 2807x families within Code Composer Studio.

Context: Manish from TI helped us debug the original Bridgeless TTPFC Project with the 280049 device. We have been successful in bringing the project through all of its phases, up to Full Power. Now we are looking to migrate from 280049 to either the 37x or 07x family.

You have been very helpful in providing us with the link to access the SysConfig tool; however we have been receiving several CLA errors when attempting to migrate from 049 to 37x and 07x (please see attached images with corresponding errors: Exhibit 4).

Due to these CLA errors, the build fails to update the "Generated Files" to the target processor.

Also, the generated files don't seem to include the pin mapping file from the source (049) to the target.

Additionally, we are not able to locate the 075 or 377s devices when using the "Switch" feature. Instead, we used 076 and 378s as targets, as only these were available as switch options.

Could you please advise us on how we can resolve these errors?

Thanks!

  • Hello,

    Could you show the CLA errors you see in the SysConfig GUI after you migrate?

    We will correct the CCS Launch Device options to include the full list of GPNs in the next CCS version. For now you can use the highest part number and refer to the datasheet to determine what peripherals are not present on your specified GPN.

    Thank you,

    Luke

  • Hi Luke, thanks for the prompt response, greatly appreciated.

    We tried loading the spreadsheet with errors but this thread would accept only a bitmap image.

    I'm going to attempt copying and pasting the spreadsheet columns here:

    Description Resource Path Location Type
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 /ttplpfc_F28004x_04032024/libraries/DCL   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 DCL_PI_C1.asm /ttplpfc_F28004x_04032024/libraries/DCL   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 DCL_PI_C4.asm /ttplpfc_F28004x_04032024/libraries/DCL   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 DCL_PI_L1.asm /ttplpfc_F28004x_04032024/libraries/DCL   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 device.c /ttplpfc_F28004x_04032024/device   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 f28004x_codestartbranch.asm /ttplpfc_F28004x_04032024/device   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 sfra_gui_scicomms_driverlib.c /ttplpfc_F28004x_04032024/libraries/sfra   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 ttplpfc.c /ttplpfc_F28004x_04032024   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 ttplpfc_clatask.cla /ttplpfc_F28004x_04032024   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 ttplpfc_hal.c /ttplpfc_F28004x_04032024   C/C++ Problem
    #24018-D Option --cla_background_task=on is not valid without --cla_support=cla2 ttplpfc_main.c /ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [device/device.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [device/f28004x_codestartbranch.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [libraries/DCL/DCL_DF22_C1.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [libraries/DCL/DCL_PI_C1.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [libraries/DCL/DCL_PI_C4.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [libraries/DCL/DCL_PI_L1.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [libraries/sfra/sfra_gui_scicomms_driverlib.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [ttplpfc_clatask.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [ttplpfc_hal.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [ttplpfc_main.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: *** [ttplpfc.obj] Error 1 ttplpfc_F28004x_04032024   C/C++ Problem
    gmake: Target 'all' not remade because of errors. ttplpfc_F28004x_04032024   C/C++ Problem

    Important Note: Please scroll each line horizontally all the way to see all the columns of the errors spreadsheet.

    As you can see, the same item was pasted as a screenshot Exhibit 4 in the previous message.

    Also, following your recommendation, we tried "Switch" to 28379D, the apex device of the 2837x family, with the following message:

    If TI can assign priority to this issue, and guide us in succeeding with the Switch from 28049 to 28377s, it'd be a huge help!

    Best Regards,

    Sundar

  • Hi Sundar,

    Are all of the errors in the CLA module when attempting to migrate to F28379D, or do you see errors in other modules as well? If there are only CLA errors, I will reassign this thread to our CLA SysConfig expert.

    Thank you,

    Luke

  • Hi Luke, looks like there's some confusion, hopefully the following would help clarify so we're on the same page:

    1. The error lists in the previous messages in this thread relate ONLY to these two attempted migrations:

    from 280049 to 28076

    from 280049 to 28378s

    2. When migration to 28379D based on your recommendation to try "Switch" to the apex device was attempted, the error message simply was "TIDM 02008 is not supported for 28379D device". Please see attached snapshot.

    3. We're NOT interested in migration to 28379D, and tried it only because it was suggested. We're only focused on 100-pin parts as of now.

    4. We're looking to migrate ONLY to 100-pin version of  either 28378s or 28076. Please help us resolve the errors, mostly CLA related.

    5. Last, if the "Switch" options can be updated to include 28075 and 28377s, it'd be great, as our ultimate goal is to switch to either of these two devices from 280049 for the TIDM 02008 project.

    Thanks for your timely support and continued effort!

    Best Regards,

    Sundar

  • Hi Sundar,

    It's a bit difficult for me to grasp this issue over E2E responses, could you tell me where you imported this project from for F280049? Was it from C2000Ware or a different SDK?

    Have you made any updates to the project compared to what is in the SDK? If so can you share your .syscfg file?

    I will recreate this issue on my side so I can determine what fix needs to be made to make this migration possible.

    Thank you,

    Luke

  • Hi Luke, thanks so much for your efforts to get clarification, please see response below:

    "It's a bit difficult for me to grasp this issue over E2E responses, could you tell me where you imported this project from for F280049? Was it from C2000Ware or a different SDK?"

    This project is directly from Code Composer Studio SDK, with NO changes, except for renaming project each time since we were making multiple Switch attempts.

    Also, It'd be great if we can do this offline, may be you've access to my email id associated with this account. if there's another way to contact TI and get help directly, please do let me know!

    "Have you made any updates to the project compared to what is in the SDK? If so can you share your .syscfg file?"

    No change or update was made to the original CCS SDK project, except to rename the saved project. The .syscfg file is identical to the one in the original project.

    "I will recreate this issue on my side so I can determine what fix needs to be made to make this migration possible."

    It's very simple to recreate this issue through CCS and SDK 3.02, which has the TIDM 02008 project.

    Your timely response and sincere efforts to help us through this migration is greatly appreciated! We're excited and looking forward to successful migration with TI's help.

    Best Regards,

    Sundar

  • Hi Sundar.

    You can email me at l-jones2@ti.com

    I will work on testing this issue on my side in the meantime.

    Thank you,

    Luke

  • Hey Sundar,

    I tested the following on my side and didn't encounter any issues:

    Imported the ttplpfc_F28004x project from C2000Ware_DigitalPower_SDK_3_02_00_00.

    Used the "Switch" Button to migrate to F28379D, F28378S, F28076

    Could you let me know if I'm missing any other steps to reproduce this issue?

    Thank you,

    Luke