Dear community,
We have a problem with the Freertos component and the new project wizard in the MCUxpresso IDE. Previously we have been using template_application which added necessary files to the project created by NPW with Freertos component. My understanding was that by meta-requiring the template_application component, it will be added only to the project created by NPW, but now it seems it is added to all the other dependencies. There has been a lot of changes in the Freertos components recently and now we need to distinguish between different port files for an application that is created by the NPW and other applications that are created by the SDK team and imported into MCUXpresso IDE. Is there any mechanism that could assure that?
Thank you
Tomas Barak
Hi Tomas,
it should work the way you described. the project_template component should only be used for projects created by the new project wizard in the MCUX IDE.
Please, share the YML file and the SDK package (links to those files). BTW, you can use a SDK package share link feature to get the SDK package link:
Hi Peter,
I can't share the SDK Archive through the MCUXpresso SDK web, since it is a work in progress, however it can be accessed through our SDK repository on branch KPSDK-26447-unify-cm33-and-cm33f.
add_free_rtos.yml is link for the yml
and the package can be generated with following command:
bin\generator\batch_v1>ruby all_lpcxpresso55s69.rb -p freertos_hello,freertos_mpu_s,freertos_mpu_ns -c package_raw -o C:/_pkgs/niobe4
Regards
Tomas
Finally after we've clarified the problem.
The project_template component should only be used for projects created by the new project wizard in the MCUX IDE. It is ignored in other use cases. That works as expected.
There was a problem with an incorrect dependency that was included by the meta-requires element in YML and was overriding correct dependency defined by the __requires__ element. Description of the meta-requires element from the Yml data record guide:
meta-requires: # optional, "meta-requires" tag is for the "requires" in manifest/cmsis pack. If "meta-requires" and "__requires__" exist at the same time, generator will use "meta-requires" for the "requires" in the manifest/cmsis pack.