This library can be used in mbed driver or mbed OS2. So If you want to use WizFi310 on mbed OS5, You have to use another WizFi310 library(wizfi310-driver). That is git repository for wizfi310-driver. - https://github.com/ARMmbed/wizfi310-driver
Dependents: KT_IoTMakers_WizFi310_Example WizFi310_STATION_HelloWorld WizFi310_DNS_TCP_HelloWorld WizFi310_Ubidots ... more
This library can be used in mbed driver or mbed OS2. So If you want to use WizFi310 on mbed OS5, You have to use another WizFi310 library(wizfi310-driver).
That is git repository for wizfi310-driver. - https://github.com/ARMmbed/wizfi310-driver
Diff: WizFi310Interface.h
- Revision:
- 1:16e57103a7dd
- Parent:
- 0:df571f8f8c03
- Child:
- 3:dae9a0924a73
--- a/WizFi310Interface.h Wed Oct 05 09:40:30 2016 +0000 +++ b/WizFi310Interface.h Mon Oct 10 05:12:51 2016 +0000 @@ -25,11 +25,15 @@ /** WizFi310Interface class * Implementation of the NetworkStack for the WizFi310 */ + + class WizFi310Interface : public NetworkStack, public WiFiInterface { public: WizFi310Interface(PinName tx, PinName rx, PinName cts, PinName rts, PinName reset, PinName alarm, int baud=115200 ); + + virtual int connect( const char *ssid, const char *pass, @@ -49,7 +53,13 @@ * @return MAC address of the interface */ virtual const char *get_mac_address(); - + + + WizFi310* get_WizFi310_Pointer() + { + return &_wizfi310; + } + protected: /** Open a socket * @param handle Handle in which to store new socket @@ -148,6 +158,9 @@ * @note Callback may be called in an interrupt context. */ virtual void socket_attach(void *handle, void (*callback)(void *), void *data); + + + private: WizFi310 _wizfi310;