1.17 TCP/IP WEB NET Super Set SDCard FATFS

This application demo enables almost all the Application Layer modules in MPLAB® Harmony 3 TCP/IP Stack. It is also based on Web Net Server SD Card application.

Description

The TCP/IP WEB NET Super Set SDCard FATFS application is based on MPLAB® Harmony 3 TCP/IP Stack.

The Harmony TCP/IP stack is a collection of different network protocols.

The source files of Harmony 3 TCP/IP stack is available here.

The demo is created with MPLAB X IDE and MCC plugin.

MCC Project Graph - TCP/IP WEB NET Super Set SDCard FATFS

The following Project Graph shows the Harmony components included in the TCP/IP WEB NET Super Set SDCard FATFS demo application.

Figure 1-49. Project Graph

wolfSSL component is added for secure connection which supports TLS.

wolfCrypt module enabled with MD5 and SHA authentication

FILE SYSTEM is added to read and write from the SDMMC( sdcard ) module with FAT file system.

FreeRTOS component is required for RTOS application. For bare-metal (non-RTOS) FreeRTOS component should not be selected.

NOTE - The above diagram contains FreeRTOS component and that is required for RTOS application. For bare-metal(non-RTOS) FreeRTOS component shouldn't be selected.

TCP/IP Configuration - TCP/IP WEB NET Super Set SDCard FATFS

The TCP/IP modules enabled for the demo is shown in the TCP/IP Configuration Overview

More details of TCP/IP Configuration plugin is available here

Figure 1-50. TCP/IP Configuration

The Application Layer modules enabled in the demo are as follows:

  • Application Layer Modules
    • ANNOUNCE to discover the Microchip devices within a local network.
    • Berkeley API provides the Berkeley_Socket_Distribution (BSD) wrapper to the native Harmony TCP/IP Stack APIs.
    • DHCP Client to discover the IPv4 address from the nearest DHCP Server.
    • DHCP SERVER is used to assign IP addresses to DHCP clients from the configured IP address database.
    • DHCPv6 CLIENT module will allow your application to dynamically obtain an IPv6 address from a DHCPv6 server.
    • DNS Client provides DNS resolution capabilities to the stack.
    • FTP CLIENT module allows application to upload the files to, and download the files from, any FTP server.
    • FTP SERVER facilitates the uploading of files to, and downloading of files from, a network device.
    • HTTPNET SERVER enables the target board to act as a Web Server.
    • IPERF implements the iPerf protocol to measure networking bandwidth and performance
    • NBNS NetBIOS Name Service protocol associates host names with IP addresses. This assign of human-name host names to access boards on the same subnet.
    • SMTP CLIENT let applications send e-mails to any recipient worldwide.
    • SNTP Simple Network Time Protocol updates its internal time periodically using a pool of public global time servers.
    • TELNET provides bidirectional, interactive communication between two nodes on the Internet or on a Local Area Network.
    • TFTP CLIENT module supports reading and writing of files (or mail) from/to a remote server.
    • TFTP SERVER is a simple protocol used to transfer files. It waits for client requests to read and write files.
    • ZEROCONF, enables devices on an IP network to automatically configure themselves.

Downloading and Building the application

To clone or download this application from Github, go to the main page of this repository and then click Clone button to clone this repository or download as zip file.

This content can also be downloaded using content manager by following these instructions.

Path of the application within the repository is apps\web_net_super_set_sdcard_fatfs\firmware .

To build the application, refer to the following list of demo configurations and open the project using MPLAB X IDE.

Table 1-18. Demo Configurations
Project NameTarget DeviceDevelopment BoardDescription
pic32cz_ca80_curiosity_ultra.XPIC32CZ8110CA80208PIC32CZ CA80 Curiosity UltraTCP/IP WEB NET Super Set SDCard FATFS Application with KSZ9031 G-bit Ethernet PHY - Bare Metal
pic32cz_ca80_curiosity_ultra_freertos.XPIC32CZ8110CA80208PIC32CZ CA80 Curiosity UltraTCP/IP WEB NET Super Set SDCard FATFS Application with KSZ9031 G-bit Ethernet PHY - FreeRTOS

Hardware Setup

The target board for running the application is PIC32CZ CA80 Curiosity Ultra.

This section provides essential hardware configuration of this target board to run TCP/IP applications.

Figure 1-51. PIC32CZ CA80 Curiosity Ultra Evaluation Board

Board Setup

To set up the hardware, refer to the section Board Setup in PIC32CZ CA80 Curiosity Ultra User Guide.

  • Connect the power supply ranging from 6.5 to 14V to the VIN port of the PIC32CZ CA80 Curiosity Ultra Evaluation Board.
  • Connect the micro USB cable from the computer to the DEBUG USB connector on the PIC32CZ CA80 Curiosity Ultra Evaluation Board.
  • Insert the SD Card into the SD Card slot (which is on backside of the board) as shown above
  • Establish a connection between the router/switch with the PIC32CZ CA80 Curiosity Ultra Evaluation Board through the RJ45 connector.

Running the Application

  1. Open a terminal application on the host computer (like Hyper-terminal or Tera Term).
  2. Configure the terminal application for serial port connected to USB debug port of the board.
  3. Set baud rate as 115200 in the terminal application.
  4. Build and download the application project on the target board.
  5. Ensure SD card is formatted and loaded with the web pages provided within the /net_apps_pic32cz_ca/apps/web_net_super_set_sdcard_fatfs/firmware/src/web_pages directory.
  6. Insert SD Card to the slot on target board.
  7. Verify the TCP/IP Stack initialization console messages.

Console Start up

If DHCP client is enabled in the demonstration, wait for the DHCP server to assign an IP address for the development board.

This will be printed on the console. Otherwise, the default static IP address will be assigned to the board.

By entering the command netinfo, the response is obtained as shown above.

Demo Test

  • To test the web server functionality, refer Web Net Server demo.
  • The command interface is enabled for all the Application Layer modules. These modules can be configured and tested with commands from Console.