1.23 TCP/IP WolfSSL TCP Client

This configuration demonstrates creating an Internet client that uses the MPLAB Harmony TCP API to create a TCP/IP connection to a Web server. The connection can either be clear text, or it can use TLS to encrypt the connection with wolfSSL. The demonstration uses IPv4. (But it can use either IPv4 or IPv6)

This demonstration uses the NET_PRES layer for encrypted communication through an external service provider for TLS support.

TCP/IP WolfSSL TCP Client MCC Configuration

The following Project Graph diagram shows the Harmony components included in the WolfSSL TCP Client demonstration application.

  • 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 SERCOM2 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.

    tcpip_same54_project

    TCP sockets calculate the ISN using the wolfSSL crypto library.

  • TCP/IP Configuration

    • SAM E54 Xplained Pro
      tcpip_same54_project

  • TCP/IP Required Application

    TCP/IP demo use these application module components for this demo.

    DHCP Client module to discover the IPv4 address from the nearest DHCP Server.

    DNS Client provides DNS resolution capabilities to the stack.

    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(gmac) is enabled with the external KSZ8091 PHY driver library. 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 WolfSSL TCP Client Hardware Configuration

This is the following section describes the hardware configuration used for this application demonstration.

  • This section describes the required default hardware configuration use USB device as on board debugger and programmer for this application demonstration.

    • No hardware related configuration or jumper setting changes are necessary

    • Refer to the SAM E54 Xplained Pro User Guide

      required_hardware

    • Connect the micro USB cable from the computer to the DEBUG USB connector on the SAM E54 Xplained Pro.

    • Establish a connection between the router/switch with the SAM E54 Xplained Pro through the RJ45 connector

      required_hardware

TCP/IP WolfSSL TCP Client Running Application

This table list the name and location of the MPLAB X IDE project folder for the demonstration.

Project NameTarget DeviceTarget Development BoardDescription
sam_e54_xpro_sw.XATSAME54P20ASAM E54 Xplained ProDemonstrates the WolfSSL TCP Client on development board with ATSAME54P20A device and KSZ8091 PHY daughter board. This implementation is based on bare-metal(non-RTOS).

Running Demonstration Steps

  1. Build and download the demonstration project on the target board.

  2. If the board has a SERCOM2 configuration:

    1. A virtual COM port will be detected on the computer, when the USB cable is connected to USB-UART connector.

    2. Open a standard terminal application on the computer (like Hyper-terminal or Tera Term) and configure the virtual COM port.

    3. Set the serial baud rate to 115200 baud in the terminal application.

    4. See that the initialization prints on the serial port terminal.

    5. 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.

  3. Execution :

    As soon as a valid IP address is assigned through the DHCP to the demonstration, it is ready to accept console commands.

    • There are some commands available in the demonstration from the serial port:

      • openurl < url > - The < url > argument must be a fully formed URL; for instance, http://www.microchip.com/
      • ipmode < mode > - The < mode > argument selects the IP version. 0 - Any IP version, 4 - IPv4 only, 6 - IPv6 only
      • stats - Output the statistics of the previous openurl run. Statistics such as how long each phase of the connection took, and how many bytes were transferred.

    1. After the successful board bring up, the console output becomes

      tcpip_same54_project

    2. TCP Client Test

      a. Clear text connection (Port 80):

      Enter following command in console: openurl < url >. For example, openurl http://www.microchip.com/ or http://www.google.com/ , the connection established here is clear text.

      By entering the command stats, the response is obtained as shown below.

      The response from the server will be printed on the console as shown below.

      The expected output -

      tcpip_same54_project

      b. Encrypted connection (Port 443):

      Enter following command in console: openurl < url >. For example, openurl https://www.microchip.com/ or https://www.google.com/ , the connection established here is encrypted connection with wolfSSL.

      The response from the server will be printed on the console as shown below.

      By entering the command stats, the response is obtained as shown below.

      The expected output -

      tcpip_same54_project