How to Use WizFi310 in mbed

WizFi310 is registered as a component of mbed.

The components of mbed are classified into categories such as Actuators, Communication, Display, Expansion Boards, Input, IoT & Web Service, Sensors, Storage.

https://os.mbed.com/components/

The products registered as mbed's components can easily be used to develop components easily using ARM's MCU and reusable libraries on mbed OS.

The mbed registration page for WizFi310 is shown below.

https://os.mbed.com/components/WizFi310-EVB/

Looking at WizFi310's headers in mbed, you can see various example code.

https://os.mbed.com/teams/WIZnet/code/WizFi310_TCP_Echo_Server_Example/

https://os.mbed.com/teams/WIZnet/code/WizFi310_STATION_HelloWorld/

https://os.mbed.com/teams/WIZnet/code/WizFi310_OpenWeatherMap/

https://os.mbed.com/users/jehoon/code/KT_IoTMakers_WizFi310_Example/

https://os.mbed.com/users/jehoon/code/WiFiTracker/

In the example above, you can see that there is an indication of OS2 next to the title.

This indication refers to an example running on mbed OS version 2.

Currently, mbed OS is released up to version 5.

https://os.mbed.com/blog/entry/Introducing-mbed-OS-5/

Therefore, it is difficult to refer to the above examples in order to use WizFi310 in the latest mbed OS 5.

The driver code for WizFi310 running under mbed OS 5 is distributed through github below, and if mbed OS 5 is used in the mbed online compiler, it is compiled using the latest github code below.

https://github.com/ARMmbed/wizfi310-driver

The driver code included in mbed OS 5 can be easily ported for reusability even if you use the source code of other Communication Components.

Using the above WizFi310 driver, the following items are linked to the Arm pelion Cloud.

https://github.com/wpgnss/mbed-cloud-client-example