• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 467 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.

MCU-PLUS-SDK-AM243X: How to upgrade from version 8.03.00.18 to 8.04.00.17

Johannes von Löwis
Expert 1816 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: SYSCONFIG

I have a project that is based on SDK version 8.03.00.18 and sysconfig 1.12.1.

Now I would like to base it on SDK version 8.04.00.17 and sysconfig 1.13.0. I have imported the project into a workspace (of CCS12) and changed "products":

When I now double-click on the example.syscfg file of my project, I get:

The details are:

What is the recommended procedure to upgrade the sdk and sysconfig a project is based on?

Best regards

Johannes

  • 0
    TI__Guru 55965 points

    Hi Johannes,

    The MCU+ SDK 08.04.00.17 uses the SysCfg 1.13.0.2553, while the 08.03.0.18 is using the SysCfg 1.12.1.2446. You will need to install the new SysCfg from:

    https://dr-download.ti.com/software-development/ide-configuration-compiler-or-debugger/MD-nsUM6f7Vvb/1.13.0.2553/sysconfig-1.13.0_2553-setup.exe

    Best regards,

    Ming

  • 0 in reply to Ming Wei
    Expert 1816 points

    Hi Ming,

    I'm trying to use SysCfg 1.13.0 (the version that came with CCSv12, don't know the digits of that version that come after .0) to open a syscfg file that was used with SysCfg 1.12.1 and I'm getting the error messages that I posted in my initial post.

    How do I get rid of them?

    How do I open an old syscfg file (from 1.12.1) with SysCfg 1.13.0 in order to transfer my project from SDK 08.03.0.18 to SDK 08.04.00.17?

    Best regards

    Johannes

  • 0 in reply to Johannes von Löwis
    TI__Guru 55965 points

    Hi Johannes,

    I agree with you that the SysCfg should be backward compatible to the configuration files generated by the previous versions of the SysCfg. Looks like the suggestSolution field of some peripherals are not defined anymore with the new version of the SysCfg. The workaround is to compare the example.syscfg of your example.syscfg file with the ones in the 8.4.0 which uses the same peripherals and see the difference especially the ones with suggestSolution. 

    There are some major changes in the example.syscfg for the MCSPI and OSPI examples from 8.3 to 8.4, so those two peripherals are the primary suspects

    I will inform the tools team about this backward compatibility issue.

    Keep us updated on which peripheral actually caused your SysCfg failure. Thanks!

    Best regards,

    Ming 

  • +1 in reply to Ming Wei
    Expert 1816 points

    Hi Ming,

    thank you for your response. I ended up taking an example.syscfg from sdk 8.4.0 and, using sysconfig 1.13, make it as similar as possible to my original file opened in sysconfig 1.12:

    The resulting syscfg file is pretty similar to the one from 1.12:

    I don't know what caused the problem to open the file on the left with sysconfig 1.13.

    Best regards

    Johannes

  • 0 in reply to Johannes von Löwis
    TI__Guru 55965 points

    Hi Johannes,

    I think the issue was caused by the 184-186 on the left. Somehow the suggestSolution is not valid for those three items anymore. I will report this to the SysCfg team.

    Did the one on the right works for you now? If so, can you mark this thread as "Resolved"? Thanks!

    Ming