Hi, I need to add support for the AMB5201 WiFi module, that has a serial interface with the MCU. I'm new to Keil (used Atollic and STMCubeIde) and I want to integrate as good as possible the keil packs approach and development workflow. What do you think is the best path, to configure it as WiFi Custom in the Run-time environment for the CMSIS/Drivers, or to develop a new set of files like there are for the ESP32 or the WizFi360 in the CMSIS-Driver folder? Is there some example of how to do it in any of these paths?
One possibility I thought is to consider as a WiFi_Custom driver, so the net module will be automatically configured to use the Driver_WiFi0, and then implement in the application code something similar to the WizFi360 driver code, that way will be easier at least in a first step to manage the code being developed, since it will be in the application and not as a driver in a different source tree. It will be great if there is some tutorial or workflow recomendation for this kind of development.
Best regards
Fernando
Hi Fernando,
the quickest way is to copy the whole folder WizFi360 from the CMSIS-Driver pack to your local project.
In the Manage Run-Time Environment (RTE) select CMSIS Driver - WiFi (API) - Custom to get WiFi API and definitions.
Then include all WizFi360 source .c files into your project, and add include paths to your local WizFi360 folders in C/C++ Options for Target.
It should compile.
At that point you go into editing of the source files to fit your particular WiFi module.
When you have the driver finished you can pack it into your own pack for redistribution.
For pack usage you can refer to: https://arm-software.github.io/CMSIS_5/Pack/html/index.html or use CMSIS-Driver as a reference for your pack.
WiFi driver documentation is here: https://arm-software.github.io/CMSIS_5/Driver/html/group__wifi__interface__gr.html
Best regards, Milorad