WizFi360-EVB-Pico is based on Raspberry Pi RP2040 and adds WiFi connectivity using WizFi360. It is pin compatible with Raspberry Pi Pico board and can be used for IoT Solution development.
WizFi-EVB-Pico pinout is directly connected to the GPIO of RP2040. It has the same pinout as the Raspberry Pi Pico board. However, GPIO4, GPIO5, GPIO6, GPIO7, GPIO20 are connected to WizFi360 inside the board. These pins enable UART communication with WizFi360 to use WiFi function. If you are using the WiFi function, these pins cannot be used for any other purpose.
If a board needs code or communicates somehow, you're going to need to know how to program or interface with it. The programming skill is all about communication and code.
Skill Level: Competent - The toolchain for programming is a bit more complex and will examples may not be explicitly provided for you. You will be required to have a fundamental knowledge of programming and be required to provide your own code. You may need to modify existing libraries or code to work with your specific hardware. Sensor and hardware interfaces will be SPI or I2C.
See all skill levels
If it requires power, you need to know how much, what all the pins do, and how to hook it up. You may need to reference datasheets, schematics, and know the ins and outs of electronics.
Skill Level: Rookie - You may be required to know a bit more about the component, such as orientation, or how to hook it up, in addition to power requirements. You will need to understand polarized components.
See all skill levels
We welcome your comments and suggestions below. However, if you are looking for solutions to technical questions please see our Technical Assistance page.
No reviews yet.
So far I have gotten a simple network data logger to work using CircuitPython. Installed the regular pico version of CircuitPython and used the wiz360 library from:
https://github.com/Wiznet/WizFi360-EVB-Pico-CircuitPython
Using this library, it was not difficult to connect to my home access point and send UDP datagrams. The library appears to support TCP and other access modes, but all I've tried so far is just UDP output (I don't think the library support reading UDP).