1.22 TCP/IP WEB NET Server SDCARD FATFS
The Web Net Server SD Card configuration demonstrates creating an HTTP web server on a Microchip evaluation board. The FAT FS File System is used for storing the web pages on an external SD Card.
This demonstration uses the HTTPNET server module that supports encrypted communication with NET_PRES layer and third-party TLS service provider (like wolfSSL).
TCP/IP WEB NET Server SDCARD FATFS MCC Configuration
The following Project Graph diagram shows the Harmony components included in the WEB NET Server SDCARD FATFS application demonstration.
MCC is launched by selecting Tools > Embedded > MPLAB® Code Configurator from the MPLAB X IDE and after opening the project, TCP/IP demo project is ready to be configured and regenerated.
TCP/IP Root Layer Project Graph
The root layer project shows that UART2 peripheral is selected to do read and write operation for TCP/IP commands.
This is the basic configuration with SYS_CONSOLE, SYS_DEBUG and SYS_COMMAND modules. These modules are required for TCP/IP command execution.
PIC32MZ DA Starter Kit
PIC32MZ DA device performs read/write to an SD card using SDMMC driver. This demo application use SDMMC driver to read/write from SDHC peripheral module.
SDHC (SD/MMC Host Controller) PLIB provides low level APIs to configure and transfer data using the SD host controller. SD multimedia memory card ( SDMMC ) driver provides abstraction to communicate with SD/eMMC card through the SDHC peripheral library interface. The TCP/IP application use FAT file system with SDMMC driver to read/write to an SD card.
PIC32MZ EF Starter Kit
PIC32MZ EF Device performs read/write to an SD card using SDSPI Module. This module is selected with SPI peripheral.
SDSPI driver uses an instance of the SPI driver to communicate to the SD card over the SPI bus.
The TCP/IP application demonstrates FAT file system to read/write to an SD card using SDSPI driver. This demo application use SPI peripheral to read/write from SDMMC module.
Wolfssl crypto module enabled with MD5,SHA authentication and AES encryption/decryption privacy protocol are enabled. Wolfssl library configured with open secured socket.
TCP sockets calculate the ISN using the wolfSSL crypto library.
NOTE - The above screenshot contains FreeRTOS component and that is required for RTOS application. For bare-metal(non-RTOS) FreeRTOS component shouldn't be selected.
The FAT file system is selected for this application to read/write to an SD card. This is the below snapshot for the FAT FS configuration.
TCP/IP Configuration
PIC32MZ DA Starter Kit / PIC32MZ EF Starter Kit
TCP/IP Required Application
TCP/IP demo use these application module components for this demo.
Announce module to discover the Microchip devices within a local network.
DHCP Client module to discover the IPv4 address from the nearest DHCP Server.
DNS Client provides DNS resolution capabilities to the stack.
HTTPNET Server module is selected to run the web_server for the 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.
TCP/IP Data Link Layer
Internal ethernet driver(ethmac) is enabled with the external LAN8740 PHY driver library for both the starter kits. The MIIM Driver supports asynchronous read/write and scan operations for accessing the external PHY registers and notification when MIIM operations have completed.
TCP/IP WEB NET Server SDCARD FATFS Hardware Configuration
This section describes the hardware configuration for PIC32MZ DA/EF Starter Kit and one can be used for the respective application demonstration.
This section describes the PIC32MZ DA Starter Kit default hardware configuration which uses the on-board debugger and programmer for this application demonstration.
Refer to the PIC32MZ DA Starter Kit User Guide for the programming/debugging options supported & setting up the hardware.
Connect micro USB cable from the computer to the DEBUG USB connector(J19) on the PIC32MZ DA Starter Kit
Connect micro USB cable from the computer to the USB-UART connector(J5) on the PIC32MZ DA Starter Kit
Insert the SD Card in the SD Card slot (J10) on the PIC32MZ DA Starter Kit (as shown above).
Establish a connection between the router/switch with the PIC32MZ DA Starter Kit through the RJ45 connector on PHY daughter board
This section describes the PIC32MZ EF Starter Kit default hardware configuration which uses the on-board debugger and programmer for this application demonstration with SDMMC(Secure Digital/ MultiMediaCard interface) interface.
Refer to the PIC32MZ EF Starter Kit User Guide for the programming/debugging options supported & setting up the hardware.
Refer to the Starter Kit I/O Expansion Board - DM320002 User Guide
Refer to the SDMMC PICtail daughter board - AC164122 User Guide
Insert the SDMMC PICtail daughter board (AC164122) into the SPI1 slot of the I/O Expansion Board (DM320002)
Connect the 168 pin to 132 pin Starter Kit Adapter board to the Starter Kit I/O Expansion Board (DM320002), optionally use a nylon nut and bolt to secure the two boards together
Connect the PIC32MZ EF Starter kit to the 168 pin to 132 pin Starter Kit Adapter board, optionally use a nylon nut and bolt to secure the two boards together
Connect the mini USB cable from the computer to the USB DEBUG connector on the PIC32MZ EF Starter Kit
Connect the mini USB cable from the computer to the USB-UART connector on the PIC32MZ EF Starter Kit
Insert the SD Card in the SD Card slot on the SDMMC PICtail daughter board (AC164122)
Establish a connection between the router/switch with the PIC32MZ Starter Kit through the RJ45 connector on PHY daughter board.
The demo application is configured for the SPI1 slot, using the following I/O pins:
SPI 1 Pin Selection SCK1 - SPI clock RD1 SDI1 - SPI Data Input RD14 SDO1 - SPI Data Output RD10 SPI Chip Select RB1
TCP/IP WEB NET Server SDCARD FATFS Running Application
This Web Net Server application uses the SD card as a memory media and reads the web pages stored according to the configured mount path. Web Server reads the external SD card content using FAT FS API.
This table list the name and location of the MPLAB X IDE project folder for the demonstration.
Project Name | Target Device | Target Development Board | Description |
---|---|---|---|
pic32mz_das_sk.X | PIC32MZ2064DAS169 | PIC32MZ DA Starter Kit | Demonstrates the WEB NET Server SDCARD FATFS on development board with PIC32MZ2064DAS169 device and LAN8740 PHY daughter board. This implementation is based on bare-metal(non-RTOS). |
pic32mz_das_sk_freertos.X | PIC32MZ2064DAS169 | PIC32MZ DA Starter Kit | Demonstrates the WEB NET Server SDCARD FATFS on development board with PIC32MZ2064DAS169 device and LAN8740 PHY daughter board. This implementation is based on FreeRTOS. |
pic32mz_ef_sk_freertos.X | PIC32MZ2048EFH144 | PIC32MZ EF Starter Kit | Demonstrates the WEB NET Server SDCARD FATFS on development board with PIC32MZ2048EFH144 device and LAN8740 PHY daughter board. This implementation is based on FreeRTOS. |
Ensure a microSD/SD card is formatted and loaded with the web pages provided within the < install-dir > /net_apps_pic32mz/apps/web_net_server_sdcard_fatfs/firmware/src/web_pages directory.
Running Demonstration Steps
Build and download the demonstration project on the target board.
If the board has a UART connection:
A virtual COM port will be detected on the computer, when the USB cable is connected to USB-UART connector.
Open a standard terminal application on the computer (like Hyper-terminal or Tera Term) and configure the virtual COM port.
Set the serial baud rate to 115200 baud in the terminal application.
See that the initialization prints on the serial port terminal.
When the 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 serial port terminal.
Alternatively: Use the Announce service or ping to get the IP address of the board.
Run tcpip_discoverer.jar to discover the IPv4 and IPv6 address for the board.
Execution :
After the successful board bring up, the console output becomes
HTTP Server Output -
An HTTP server is hosted by the demonstration application. Open a web browser and direct it to the board running the HTTP server by typing the URL in the address bar (for example, https://mchpboard_e or https://< ip-address as shown in the console > ), and then pressing Enter.
The demonstration application features following:
Dynamic Variables and Real-time Hardware Control - On the Overview page the LEDs can be clicked to toggle the LEDs on the Microchip hardware development board. The SWITCHes on the Microchip hardware development board can be pressed to toggle the Buttons on the web page. The dynamic variables can be updated in real-time on the HTTP server.
Form Processing - Input can be handled from the client by using the GET and POST methods (this functionality controls the on-board LEDs and is operational only on the Explorer 16 Development Board)
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_accept_a 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_e/mpfsupload
Notes:
For the LED and SWITCH functionality portion of the demonstration, configure the GPIOs connected to LEDs and Switches on Microchip hardware development board, through the Pin Configuration manager in MPLAB® Code Configurator (MCC).