Thanks for the replay
I’m still running the demo project(windows version) to see how it works, and I got many great ideas from it.
I think it is a great goal to support all cellular modems and provide unified APIs to users, it’s real cool, but as a embedded developer, we have some considerations:
-
MCU is resource limited, even when I use a 32 bit version. In general case, we just use few functions in one project for specific purpose. the MCU may not afford if the cellular interface has large size.
-
When I read the tutorial / Documentation / examples about the interface, it doesn’t provide instruction(steps) about how to port the interface to my project, especilly about the custom parts
when I read the tutorial(offical)(FreeRTOS Cellular Library)(GitHub)，the only info I found about how to construct the interface is: “It is recommended that you start by cloning the implementation of one of the existing modems, then make modifications where your modem’s vendor-specific (non-3GPP) AT commands are different.”
I think it is not enough to port the interface to a new project. We need more clear instructions about how to organize these files(custom part), any suggestions about folder/file naming rule and where to place them?
From demo project, I got following folder structure:
The cellular folder in lib is provided in document so I can just move it to my project and modify files in folder “Cellular_R4”, but I can’t find the instructions/suggestions about files in folder “source”.
We have a “Cellular” folder and some files inside, but also some files like “cellular_setup.c”/“demo_config.h”/“logging_levels.h”/“logging_stack.h” in the root of source folder.
I don’t know what is the correct way to organize these files (if I want to treat them as independent software module).
The cellular interface related files split into many folders but not gathered in one, I think it make things harder to work with it.
So, if there is a guide can show us the steps to port/organize the interface would relly helpful. (maybe with demo project of popular MCU like ST32/PIC32/Atmel SAM Series/…).
what is the entry point that I should include to use the cellular interface?
I think if there is a minimal interface that only include few Standard AT CMDs and we can easily make it work, then we can easily add our working flow too. that will be a good start for us to implement other modules~
Thanks for the great interface, and hope we can make it work easier