Is there any reason that the FreeRTOS plus TCP SDK component is not available for RT1051 devices?
The manifest file has a dependency on RT1052, making it a nuisance to use the SDK version in projects.
SDK version 2.16
Hi @otsl
Thank you for your reply and patience.
I manage to reproduce the issue, I already reported this to the SDK team.
I do not have specific dates about when will the fix will be made. However the change is minimum, so I expect this to be ready on a minor release, or at least next major release.
I appreciate your efforts reporting this.
Diego
It was downloaded from the web and added to MCUXpresso IDE. I also have the 1052 SDK and EVKB-IMXRT1050 SDK installed. All are very near the same. However, when I start a new project in MCUXPresso using the RT1051 I have the problem. Selecting the 1051 processor only gives me the option for the 1051 SDK (not the EVK SDK):
If I select the 1052 processor, I have the ability to choose the EVK to use (and everything works fine using the 1052):
Hi @otsl
I agree with you, thank you for your report! I already escalated this issue internally.
Edit: @otsl Are you using a plug-in SDK downloaded from the IDE or from https://mcuxpresso.nxp.com/en ?
I noticed that I can import the middleware on my side, see below details.
Imported midleware files using Manage SDK components look like this.
I downloaded the SDK from https://mcuxpresso.nxp.com/en
I acknowledge that your report is correct and you need to be able to import this middleware as I did. Therefore, I want to check with you any troubles with the SDK generation.
All the best,
Diego
The software is included in the SDK, but the MCUXpresso "new project tool" (and any subsequent attempt to "Manage SDK Components" from the GUI) do not show FreeRTOS+TCP as an import option:
(MCUXpresso v11.10.0, and NXP Config Tools Framework 16.0.0.202407020751)
I don't know exactly how the tools "decide" to show options, but it's very likely because of the content of the manifest file:
All SDK components that are selectable in the GUI have an entry for the 1051, but freertos-plus-tcp does not.
This oversight means I can't easily use the tools to manage SDK components. I can manually add the component from the zip of the SDK, but then in the future if I'm updating SDK components (to new versions for example), I have to remember to manually update the FreeRTOS+TCP. As previously mentioned, It's a nuisance, and there doesn't seem to be any reason for it to be this way (other than possibly an oversight).
Hi @otsl
Thank you for reaching out!
The midleware is only available for RT1051 with sillicon revision B SDK. Below a referecen picture.
I would like to dig further on your issue, it seems that you are getting troubles with the manifest, could you detail how it limitates you, as well your procedure to import the midleware files?
Thank you!
Diego