I'm trying to build this example:
evkmimx8ulp/multicore_examples/rpmsg_lite_str_echo_rtos
It builds with SDK 2.16.000, but fails in 2.16.100 with the following error:
middleware_multicore_rpmsg_lite dependency does not meet, please check middleware/multicore/set_middleware_multicore.cmake.
The error seems to be caused by the changes made to the set_middleware_multicore.cmake file in the mcuxsdk-middleware-multicore repository in commit "Apply 2.16.100 release update". See the diff here.
The error message I'm getting is triggered when the value of CONFIG_DEVICE_ID or CONFIG_BOARD is not one of a list of supported values. In 2.16.000, the middleware_multicore_rpmsg_lite dependency allows for 82 possible values of CONFIG_DEVICE_ID and 27 of CONFIG_BOARD, but in 2.16.100 this is reduced to only 15 accepted CONFIG_DEVICE_ID values and 9 CONFIG_BOARD values.
This feels unintentional. Why would a minor release drop support for over 80% of all devices? And the release notes for 2.16.100 list mcux-sdk-middleware-multicore as "does not have source change, only have manifest version change".
Did something go wrong in whatever generates this .cmake file between 2.16.000 and 2.16.100? Why were such extensive reductions in supported devices and boards made without a mention in the release notes?
I'd appreciate it if someone could take a closer look at this.
More details:
I retrieve the SDK using the following commands, from an initially empty directory:
For 2.16.000:
west init -m https://github.com/nxp-mcuxpresso/mcux-sdk --mr "MCUX_2.16.000"
west update
For 2.16.100:
west init -m https://github.com/nxp-mcuxpresso/mcux-sdk --mr "MCUX_2.16.100"
west update
Then, in each case, I go into the armgcc folder of the example and run build_release (.bat on windows, .sh on Linux).
It builds fine with 2.16.000 but not 2.16.100.
