Any chance of simplifying the Cellular libraries? In my opinion they don’t fit the previous ways things fit together.
For example, there is no clear relationship to +TCP, yet it would appear to be somewhat integrated?
I’ve used +TCP for some years now, but I’m having difficultly understanding how the parts fit together on this one. Its arranged a little like aws services I’m afraid.
A side note, the demos for the r4 don’t want to build on windows.
You do not need a separate TCP stack on the host processor as the cellular modem provides a TCP stack. You can refer to the Cellular demos here - GitHub - FreeRTOS/Lab-Project-FreeRTOS-Cellular-Demo.
If it doesn’t need +tcp, why does the demo build require the +tcp lib?
Where do you see that? I do not see +TCP here - https://github.com/FreeRTOS/Lab-Project-FreeRTOS-Cellular-Demo/blob/main/.gitmodules
I see that when I tried to build the demo. The vs solution builds against the lib. Which doesn’t build because of libslip for some reason.
Which demo are you talking about? What do I need to do to repro it?
The repo situation is rather confusing, but clone the master Freertos repo, then build the Sara r4 demo in the cellular demos on a windows environment. You do have to define a few things in the confits.
Why would that demo be under +tcp folder?
What do you mean by " under +tcp folder"? The complete path to that demo is
FreeRTOS/FreeRTOS-Plus/Demo/FreeRTOS_Cellular_Interface_Windows_Simulator/MQTT_Mutual_Auth_Demo_with_SARA_R4 . Where do you see TCP in that path?
Yes, I see what you mean now there isn’t tcp there.
There is another thread about this demo build problem in FreeRTOS/FreeRTOS issue. I suggest we move the discussion there to help us reply the problem in single forum.