• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 33 subscribers
  • Views 227 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MCU-PLUS-SDK-AM243X: split up of SDK and industrial comms in MCU_PLUS_SDK 9

Felix Heil
Expert 1150 points
Part Number: MCU-PLUS-SDK-AM243X

Hello,

we updated our SDK to MCU_PLUS_SDK 9. we noticed that the industrial comms are now a separate SDK. This is really unfortunate, since the sdk is also present again inside the industrial comms. So this mixes up our build-system. Is there a possibility to add the path to the mcu-plus-sdk manually in a top-level make-file? Like you can as standard use the internal location but at least for us we would be able to change it there. I did adjustments now in every make-file for that and it works, but the current solution is really unfortunate.

Best regards

Felix

  • 0
    TI__Mastermind 26205 points

    Hi Felix,

    May I know the reason why you want tp use the mcu+ sdk standalone installation instead of one provides as part of industrial comms SDK?

    Intent of having the mcu+ sdk inside industrial comms SDK is to make SDK contained.

    Regards,

    Ankur

  • 0 in reply to Ankur Baranwal
    Expert 1150 points

    Hey Ankur,

    sorry for the late reply. Previously it was the other way round, so the ind_comms were contained in the SDK. Since the split updating the SDK separately does not seem to be intended. This is always bound to the containing industrial comms-kit. If there is a new SDK-update I guess the industrial comms will follow weeks/months later with the updated SDK inside. Also, since we are not using CCS as development-IDE and work on a solely command-line-based process, having the manual control over the placement of the sdk is really helpful since we have some modifications at the sdk and store the copy of it in a separate repository. With this new approach this possibility is then broken and it's only solveable by adjusting the paths manually.

    Regards,

    Felix

  • 0 in reply to Felix Heil
    TI__Intellectual 2135 points

    Hi Felix,

    Adding MCU+ SDK variable at top level will solve the CLI based builds, but it will create additional problem when we use GUI based tools (Code Composer Studio + Syscfg). We have observed issues with this approach. So we ended up in removing the MCU+ SDK variable from Industrial Communications SDK.

    BTW - Can you replace the MCU+ SDK with your SDK inside Industrial Communications SDK and check how it behaves.

    Thanks,
    Naresh Kumar A

  • 0 in reply to Naresh A
    Expert 1150 points

    sorry for the late reply.

    Ok, I understand this problem. But using the mcu-plus-sdk inside the industrial comms-sdk is no real option for us. This means a separate submodule in a submodule which is not wanted. Can be solved by having it not inside but beside the industrial comms sdk and the used for linking later on. I think we will then need to keep the files manually updated, even if it is a bit tedious.

    Best regards

    Felix