• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 385 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28388D: SYSCONFIG path error

Conor
Guru 13265 points

Part Number: TMS320F28388D
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Hi,

I'm replacing the PC and doing the porting work for each project.　Most of the errors have been resolved, but only the SYSCONFIG error has not been resolved.

The error contents are as follows.
ーーーーー
"C:/ti/ccs1210/ccs/utils/sysconfig_1.14.0/sysconfig_cli.bat" -s "{C2000WARE_ROOT}/.metadata/sdk.json" -d "F2838x" --script "C:/Users/Desktop/ DEMO/user_setting.syscfg" -o "syscfg" --package 337bga --part F2838x_337bga --compiler ccs
subdir_rules.mk:16: recipe for target 'build-836951249' failed
Invalid argument '-s': File "C:\Users\Desktop\DEMO\CPU1_RAM\{C2000WARE_ROOT}\.metadata\sdk.json" does not exist
gmake: *** [build-836951249] Error 1
gmake: Target 'all' not remade because of errors.
ーー

I updated the SDK path referring to E2E similar to the error content, but it is not resolved.
https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/910829/faq-how-do-i-add-sysconfig-support-pinmux-and-peripheral-initialization-to-an-existing-driverlib-project

What should I do?

Thanks,

Conor

  • 0
    TI__Mastermind 19795 points

    Hi Conor,

    Thanks for your question. This is probably specifically the sdk.json path.

    From the E2E thread you linked:

    "6. Update the SDK path, for C2000WARE the path path is: [C2000WARE_INSTALL]/.metadata/sdk.json"

    So It looks like the path provided in the error might have duplicate paths:

    "Invalid argument '-s': File "C:\Users\Desktop\DEMO\CPU1_RAM\{C2000WARE_ROOT}\.metadata\sdk.json" does not exist"

    If you replaced "C2000WARE_ROOT" with the actual path, it probably has "C:\Users\..." in the path again, so you end up with a path that has the "C" drive in there twice.

    Can you double-check what the C2000WARE_ROOT path is?

    Regards,

    Vince