Migrating an application between different SDK versions using MCUXpresso

[Ricardo3]

We have a situation where we have an application project built on top of an existing SDK. We then get a new version of the SDK where some files are renamed/moved. That means that the application .project and .cproject need to be updated for the new SDK version. However, we have not found a way to do this except by hand comparing .cproject files and making the changes by hand. Also for files that are not changed, in new SDK versions, the .cproject files are changed with some magic numbers.

What is the recommended way to migrate application project files to a new SDK version? How can we keep our application and take in the new SDK files when a new release is received?

[Ricardo3]

Hi Erich

Thank you for your answer. Actually, we have no alternative but to switch SDKs. We are using SDKs that are fully under development and every few months we get an update that we need to migrate our applications to.

I think the link you sent could be useful, so i am checking that, but i am also concluding that it's unavoidable having some manual work required, which is not ideal if we have multiple applications with multiple configurations.

I'll keep this topic open for if someone else has a better suggestion.

[ErichStyger · Accepted solution]

Not sure if there is a recommended way, but I would say in general it would not be recommended to switch SDKs, because as you noticed there might be breaking changes.

What I'm using is the process I have described in https://mcuoneclipse.com/2021/04/27/upgrade-to-a-new-nxp-mcuxpresso-sdk/

Additionally I feel it is mandatory to have your project in a version control system (I'm using git/GitHub/GitLab, see https://mcuoneclipse.com/2018/09/30/tutorial-git-with-eclipse/ which allows me to track changes and always go back if necessary.

One thing to look out for is that some folders might get 'excluded from build', so you have to re-enable them, see https://mcuoneclipse.com/2014/07/22/exclude-source-files-from-build-in-eclipse/

I hope this helps,

Erich