Migration to Other Component Versions (or rather not)

danielholala — Wed, 14 Jan 2026 10:42:23 GMT

Hello,

I imported an older project from MCUXpresso IDE v11.7 into IDE v25.6 using simple drag&drop.

As I also have the newest SDK for the LPC5528 part installed.

The first time I opened the project, I got this warning window regarding "Project SDK management":

The dialog states this warning: "Changing the project SDK may cause issues" . Therefore I pressed "Cancel" to leave SDK setting unchanged.

Result: The project compils successfully.

The first time I opened Config Tools (i.e., Peripherals) I was confronted with another request to migrate. The "Migration to Other Component Versions" dialog opened:

Regarding this dialog, "MCUXpresso Config Tools User's Guide (IDE)" states: "When a configuration is open and the SDK component versions in the toolchain project do not match the version that is referenced in the configuration component, automatic migration is offered in the Component migration dialog."

When I click on "Proceed", the components are replaced. However, not all settings can be migrated. The ADC0 settings of "Trigger priority policy" obviously changed and the old value is not accepted any more:

Selecting the first value is sufficient to make Peripherals tool happy and it stores the new configuration and changes the board/* in my project files.

Result: The project does not compile any more (I assume because the new options for "Trigger priority policies" are not supported in the project's SDK version)

I reverted all changes (using git) and then went through this dialog again. This time I chose "Do not migrate" for all components and pressed "Proceed".

Result: The project compiles successfully.

I suggest adding a warning to the "Migration to Other Component Versions" dialog that migrating to a different version may break the project.

Thanks.
Daniel

Re: Migration to Other Component Versions (or rather not)

luis_maravilla — Thu, 15 Jan 2026 19:04:47 GMT

Hello Daniel

In MCUXpresso Config Tools User's Guide Chapter 5.4.7 say

"The default selection in the toolchain-less configuration is "Do not migrate". In the toolchain configuration, the default selection is the only version to which the migration can be performed. If "do not migrate" is selected, no changes are made to the particular component"

For avoiding modifications on your code by the migration configuration settings the default mode "Do not migrate" is the recommendation.

Best Regards.

Re: Migration to Other Component Versions (or rather not)

danielholala — Fri, 16 Jan 2026 14:05:08 GMT

All I'm saying is: Some additional information to this effect would be helpful in the dialog window.

topic Migration to Other Component Versions (or rather not) in MCUXpresso Config Tools

Migration to Other Component Versions (or rather not)

Re: Migration to Other Component Versions (or rather not)

Re: Migration to Other Component Versions (or rather not)