getting_started.md

Getting Started with WizFi360-EVB-Pico-C Examples

These sections will guide you through a series of steps from configuring development environment to running WizFi360-EVB-Pico-C examples using the WIZnet's Wi-Fi products.

• Getting Started with WizFi360-EVB-Pico-C Examples
  • Development environment configuration
  • Hardware requirements
  • WizFi360-EVB-Pico-C example structure
  • WizFi360-EVB-Pico-C example testing

Development environment configuration

To test the WizFi360-EVB-Pico-C examples, the development environment must be configured to use Raspberry Pi Pico or WizFi360-EVB-Pico.

The WizFi360-EVB-Pico-C examples were tested by configuring the development environment for Windows. Please refer to the '9.2. Building on MS Windows' section of 'Getting started with Raspberry Pi Pico' document below and configure accordingly.

• Getting started with Raspberry Pi Pico

Visual Studio Code was used during development and testing of WizFi360-EVB-Pico-C examples, the guide document in each directory was prepared also base on development with Visual Studio Code. Please refer to corresponding document.

Hardware requirements

The WizFi360-EVB-Pico-C examples use Raspberry Pi Pico and WizFi360-EVB - Wi-Fi module built on WIZnet's WizFi360 Wi-Fi module or WizFi360-EVB-Pico - Wi-Fi module built on RP2040 and WIZnet's WizFi360 Wi-Fi module.

• Raspberry Pi Pico

• WizFi360-EVB-Pico

WizFi360-EVB-Pico-C example structure

Examples are available at 'WizFi360-EVB-Pico-C/examples/' directory. As of now, following examples are provided.

• SSL Client Demo
• TCP Client Demo
• TCP Server Demo

Note that CMSIS_5, CMSIS_Driver, CMSIS_FreeRTOS, IoT_Socket, mbedtls, pico-sdk are needed to run WizFi360-EVB-Pico-C examples.

Libraries are located in the 'WIZFI360-EVB-PICO-C/libraries/' directory.

• CMSIS_5
• CMSIS_Driver
• CMSIS_FreeRTOS
• IoT_Socket
• mbedtls
• pico-sdk
• pico-extras

If you want to modify the code that MCU-dependent and use a MCU other than RP2040, you can modify it in the WIZFI360-EVB-PICO-C/port/ directory.

port is located in the 'WIZFI360-EVB-PICO-C/port/' directory.

• FreeRTOS-Kernel
• mbedtls
• RTE
• timer
• WizFi360

WizFi360-EVB-Pico-C example testing

1. Download

If the WizFi360-EVB-Pico-C examples are cloned, the library set as a submodule is an empty directory. Therefore, if you want to download the library set as a submodule together, clone the WizFi360-EVB-Pico-C examples with the following Git command.

/* Change directory */
// change to the directory to clone
cd [user path]

// e.g.
cd D:/RP2040

/* Clone */
git clone --recurse-submodules https://github.com/Wiznet/WizFi360-EVB-Pico-C.git

With Visual Studio Code, the library set as a submodule is automatically downloaded, so it doesn't matter whether the library set as a submodule is an empty directory or not, so refer to it.

2. Patch

With Visual Studio Code, each library set as a submodule is automatically patched, but if you do not use Visual Studio Code, each library set as a submodule must be manually patched with the Git commands below in each library directory.

• CMSIS-FreeRTOS

/* Change directory */
// change to the 'CMSIS-FreeRTOS' library directory
cd [user path]/WizFi360-EVB-Pico-C/libraries/CMSIS-FreeRTOS

// e.g.
cd D:/RP2040/WizFi360-EVB-Pico-C/libraries/CMSIS-FreeRTOS

/* Patch */
git apply ../../patches/01_CMSIS-FreeRTOS_cmsis_os2.patch

3. Test

Please refer to 'README.md' in each example directory to find detail guide for testing WizFi360-EVB-Pico-C examples.