WICED vs MICO

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

Need to port an application originally developed with WICED 3.5 platform to different MCU using latest MICO platform.   The application interacts with cloud services (so uses tcp sockets, tls), http server to serve a small set of web pages, and typical hardware interfaces (SPI, GPIO, I2C).  Trying to evaluate the port effort, can quantify the WICED calls in the original code to get a rough idea what must be translated into equivalent MICO Api's. That is somewhat informative, how ever there is not a direct one to one correspondence from WICED to MICO Api's , for example, http server demos apps look quite different between the two, so some code sections may require some rewrite.

Anybody have experience with a port like this?  Suggest  more accurate way to estimate the effort with regards to WICED/MICO differences?

0 Likes
1 Solution
RaktimR_11
Moderator
Moderator
Moderator
500 replies posted 250 replies posted 100 replies posted

You can start by checking the HTTP_Server library implementation (43xxx_Wi-Fi/libraries/daemons/HTTP_server) of WICED vs MICO which can give you a very basic idea about the porting effort required.

View solution in original post

0 Likes
1 Reply
RaktimR_11
Moderator
Moderator
Moderator
500 replies posted 250 replies posted 100 replies posted

You can start by checking the HTTP_Server library implementation (43xxx_Wi-Fi/libraries/daemons/HTTP_server) of WICED vs MICO which can give you a very basic idea about the porting effort required.

0 Likes