Jump to main content

##

# 1.13 TCP/IP WEB NET Server QSPI MPFS

The Web Net Server MPFS configuration with QSPI peripheral demonstrates creating an HTTP web server on a Microchip evaluation board.

The Microchip Proprietary File System (MPFS) is used for reading the web pages from the flash and using MPFS upload feature, the QSPI flash is updated with new MPFS file.

This demonstration uses the HTTPNET server module that supports encrypted communication with NET_PRES layer and third-party TLS service provider (like wolfSSL).

## Description

The TCP/IP WEB NET Server QSPI MPFS 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 Server QSPI MPFS

The following Project Graph shows the Harmony components included in the TCP/IP WEB NET Server QSPI MPFS demo application.

Figure 1-61.Project Graph - SAMA5D2 Xplained Ultra
Figure 1-62.Project Graph - SAMA5D29-Curiosity

wolfSSL component is added for secure connection which supports TLS.

wolfCrypt module enabled with MD5 and SHA authentication.

FILE SYSTEM is added to select Memory module with Microchip file system (MPFS).

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 should not be selected.

TCP/IP Configuration - TCP/IP WEB NET Server QSPI MPFS

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-63.SAMA5D2 Xplained Ultra
Figure 1-64.SAMA5D29-Curiosity

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

- Application Layer Modules
  - ANNOUNCE to discover the Microchip devices within a local network.
  - DHCP Client to discover the IPv4 address from the nearest DHCP Server.
  - DNS Client provides DNS resolution capabilities to the stack.
  - HTTPNET SERVER enables the target board to act as a Web Server for the secured port number 443.
  - 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.

## 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_server_qspi_mpfs\firmware.

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

Table 1-13.Demo Configurations
Project Name | Target Device | Development Board | Description
--- | --- | --- | ---
sam_a5d2_xult.X | ATSAMA5D27 | SAMA5D2 Xplained Ultra | TCP/IP WEB NET Server QSPI MPFS Application with an on-board KSZ8081 PHY - Bare Metal
sam_a5d2_xult_freertos.X | ATSAMA5D27 | SAMA5D2 Xplained Ultra | TCP/IP WEB NET Server QSPI MPFS Application with an on-board KSZ8081 PHY - FreeRTOS
sam_a5d2_curiosity.X | ATSAMA5D29 | SAMA5D29-Curiosity | TCP/IP WEB NET Server QSPI MPFS Application with an external KSZ8041 PHY - Bare Metal
sam_a5d2_curiosity_freertos.X | ATSAMA5D29 | SAMA5D29-Curiosity | TCP/IP WEB NET Server QSPI MPFS Application with an external KSZ8041 PHY - FreeRTOS

## Hardware Setup - SAMA5D2 Xplained Ultra

The target board for running the application is SAMA5D2 Xplained Ultra.

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

Figure 1-65.SAMA5D2 Xplained Ultra Evaluation Kit

Board Setup

To set up the hardware, refer to the section Board Components in SAMA5D2 Xplained Ultra User Guide.

- Connect the micro USB cable from the computer to the EDBG USB connector on the SAMA5D2 Xplained Ultra Evaluation Kit.
- Establish a connection between the router/switch with the SAMA5D2 Xplained Ultra Evaluation Kit through the RJ45 connector.

## Hardware Setup - SAMA5D29-Curiosity

The target board for running the application is SAMA5D29-Curiosity.

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

Figure 1-66.SAMA5D29-Curiosity Development Board

Board Setup

To set up the hardware, refer to the section Board Setup in SAMA5D29-Curiosity User Guide.

- Connect the USB Type-C cable from the computer to connector J1 (USB_A port) on the SAMA5D29-Curiosity Development Board.
- Connect a USB-UART converter from the computer to J28 (UART_DEBUG port) on the SAMA5D29-Curiosity Development Board.
- Connect the J32-Debug probe debugger/programmer from the computer to the J27 (JTAG connector) on the SAMA5D29-Curiosity Development Board.
- Establish a connection between the router/switch with the SAMA5D29-Curiosity Development Board through the RJ45 connector.

## Setting up at91bootstrap loader

To load the application binary onto the target device, we need to use at91bootstrap loader.

Refer to the at91bootstrap loader documentation for details on how to configure and run/debug the application using MPLABX and booting application using an SD Card.

## Running the Application

The HTTPNET server module uses Microchip Proprietary File System (MPFS) to read web pages from the QSPI based peripheral Flash.

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-UART Port.
3. Set baud rate as 115200 in the terminal application.
4. Build and download the application project on the target board.
5. 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.

Web Server Test

- Open a web browser (like Google Chrome, etc).
- Type the board URL in the address bar of web browser (for example, https://mchpboard_c or https://<ip-address as shown in the console>).
- The web browser display following web page.

Application features are:

- Dynamic Variables and Real-time Hardware Control - Pressing Switches on target board toggles buttons on web page. Similarly, Clicking on LED symbol in web page can toggle LEDs on target board.
- Form Processing - Input can be handled from the client by the GET and POST methods.
- Authentication - Shows an example of the commonly used restricted access feature.
- Cookies - Shows an example of storing small text strings on the client side.
- Server Side Includes - An example of how SSI can be used to support dynamic content.
- File Uploads - Shows an example of a file upload using the POST method. The HTTP server can accepta user-defined MPFS/MPFS2 image file for web pages.
- Send E-mail - Shows simple SMTP POST methods.
- Dynamic DNS - Exercises Dynamic DNS capabilities.
- Network Configuration - The MAC address, host name, and IP address of the evaluation kit can be viewed in the Network Configuration page and some configurations can be updated.
- MPFS Upload - A new set of web pages can be uploaded to the web server using this feature, which is accessed through http://mchpboard_c/mpfsupload.

Notes:

- For the LED and SWITCH demo functionality, configure the GPIOs connected to LEDs and Switches on target development board, through the Pin Configuration manager in MCC.
- The size of the MPFS upload is limited to DRV_MEMORY_DEVICE_MEDIA_SIZE in the demonstration. The HTTP File Upload functionality has to be enabled when the project is generated.