Lab 4: Add HTTP Web Server to Visualize Data

Step 2: With MHC, Configure TCPIP Stack

1

Open MHC with Tools > Embedded > MPLAB Harmony 3 Configurator.

2

Add Wi-Fi® Service under Available Components > Wireless > System Services > WIFI SERVICE.

lab4_step2_02a.png
Figure 1: Add WIFI SERVICE Component

MHC will pop up to get confirmation for component auto-activation:

  • NVM: select Yes
  • UART1: select No
  • Cryptographic (Crypto) Library: select Yes
  • wolfCrypt Library: select Yes
  • CONSOLE: select Yes
  • COMMAND: select Yes
  • PIC32MZW1: select Yes
  • NETCONFIG TCPIP CORE: select Yes
  • BA414E: select Yes
  • TCP/IP Application Layer Configurator: select Yes
  • IPv4: select Yes
  • ARP: select Yes
  • UDP: select Yes
  • ICMPv4: select Yes

Then, MCH will pop up to get confirmation for attachment auto-connect:

  • tcpipNetConfig_0 and drvWifiPic32mzw1: select Yes
  • lib_crypto and lib_wolfcrypt: select Yes
  • sys_console_0 and tcpipStack: select Yes
  • sys_console_0 and sys_debug: select Yes
  • sys_console_0 and sys_command: select Yes
  • drvWifiPic32mzw1:BA414E and drv_ba1414: select Yes

Finally, MHC will pop up to get confirmation for component auto-activation:

  • TCP: select Yes
  • WIFI PROVISIONING SERVICE: select Yes

3

Observe the organization of the components in MHC.

It is possible to navigate between the different layers and visualize the configuration of the components using the View list box.

lab4_step2_03.png
Figure 2: Observe the Project Graph Organization

4

Select the System Configuration view and make a connection between wolfCrypt Library > DRV_BA414E and BA414E.

lab4_step2_04.png
Figure 3: Connect wolfCrypt Library to BA414E

5

  • Select the Root view.
  • When MHC auto-activates components, it may break some already made connections. In this application, the connection between CDC Function Driver and Console has been broken, because both components are organized in two different layers.
  • Remove the CDC Function Driver component from the Root layer.
    • Select the CDC Function Driver.
    • Delete the selected component.
    • Reply Yes to deactivate the CDC Function Driver.
lab4_step2_05a.png
Figure 4: Remove the CDC Function Driver component
lab4_step2_05b.png
Figure 5: Deactivate the CDC Function Driver component

6

Select the System Configuration view and make sure the Console component is present.

Right-click on the yellow diamond next to USB_DEVICE_CDC in Instance 0. From the Satisfiers list, select CDC Function Driver.

lab4_step2_06a.png
Figure 6: Connect Console USB_Device_CDC with CDC Function Driver
lab4_step2_06b.png
Figure 7: Console linked to CDC Function Driver

7

At this point, the console requires a larger buffer for the application.

Select the Instance 0 of the CONSOLE component and set the following size:

  • Transmit Buffer Size: enter 256
  • Receive Buffer Size: enter 256
lab4_step2_07.png
Figure 8: Set Console Buffer Size to 256



Next Step >

© 2022 Microchip Technology, Inc.
Notice: ARM and Cortex are the registered trademarks of ARM Limited in the EU and other countries.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.