MPAE-20216: Readme edits

Author: Ethan Layton

README.md

@@ -9,7 +9,7 @@
 </a>
 
 # Getting Started with SERCOM (UART) Communication on PIC32CM M0+ Devices
-This example project demonstrates basic UART communication using the SERCOM peripheral on a PIC32CM JH00 device. The application transmits the message “Hello World” once every 500 ms using the SysTick timer, and the output can be viewed on a serial terminal connected to the board. This project provides a straightforward introduction to initializing SERCOM for UART operation and sending periodic messages.
+This example project demonstrates basic UART communication using the SERCOM peripheral on a PIC32CM JH00 device. The application transmits the message “Hello World” once every 500 ms using the SysTick timer, and the output can be viewed on a serial terminal connected to the board. This project provides a straightforward introduction to initializing the SERCOM for UART operation and sending periodic messages.
 
 While this project uses a PIC32CM JH00 device, the same initialization and communication principles apply to other PIC32CM M0+ devices.
 
@@ -34,8 +34,10 @@ While this project uses a PIC32CM JH00 device, the same initialization and commu
 - [MPLAB® XC32 4.60 or newer](https://www.microchip.com/en-us/tools-resources/develop/mplab-xc-compilers/xc32)
 - [MPLAB® Code Configurator (MCC) v5.6.2](https://www.microchip.com/en-us/tools-resources/configure/mplab-code-configurator)
 
-## Opening projects in VS Code
-This example project was developed in MPLAB X IDE and can also be opened in VS Code using the [MPLAB Extension Pack](https://marketplace.visualstudio.com/items?itemName=Microchip.mplab-extension-pack). Follow the provided instructions [here](https://developerhelp.microchip.com/xwiki/bin/view/software-tools/ides/extensions/get-started/importing-mplab-x-project-vs-code/) to import and run the project in VS Code.
+## Opening Projects in Visual Studio Code (VS Code®)
+This example project was developed in MPLAB X IDE and can also be opened in VS Code® using the [MPLAB Extension Pack](https://marketplace.visualstudio.com/items?itemName=Microchip.mplab-extension-pack). Follow the provided instructions [here](https://developerhelp.microchip.com/xwiki/bin/view/software-tools/ides/extensions/get-started/importing-mplab-x-project-vs-code/) to  import and run the project in VS Code®.
+
+For a step-by-step walkthrough on importing the project, watch the video: [Importing an MPLAB® X Project into Microsoft® VS Code®](https://www.youtube.com/watch?v=cf1bK6aLdlo)
 
 
 ## Related Documentation
@@ -56,26 +58,26 @@ PIC32CM)](https://ww1.microchip.com/downloads/aemDocuments/documents/MCU32/Appli
 
 ### UART Communication Concept  
 
-UART communication is based on a simple point-to-point connection between two devices. One device’s TX (transmit) pin connects to the other device’s RX (receive) pin, and vice versa. This crossover allows data to flow in both directions, as shown in the diagram below.  
+UART communication is based on a simple point-to-point connection between two devices. One device’s TX (transmit) pin connects to the other device’s RX (receive) pin, and vice versa. This crossover allows data to flow in both directions, as shown in the following figure.  
 
-In this configuration, UART provides a straightforward way to exchange data without the need for a clock signal. For communication to work correctly, both devices must be configured with the same parameters:  
+In this configuration, the UART provides a straightforward way to exchange data without the need for a clock signal. For communication to work correctly, both devices must be configured with the same parameters:  
 
-- Baud Rate – Defines the speed of communication in bits per second. If the baud rates don’t match, the timing of bits will drift and data will be corrupted.  
+- Baud Rate – Defines the speed of communication in bits per second. If the baud rates do not match, the timing of bits will drift and data will be corrupted.  
 - Data Bits – Specifies how many bits represent the actual data (commonly 8). Both devices must agree to properly interpret each frame.  
 - Parity – An optional error-checking bit (None, Even, or Odd). If enabled, both sides must use the same setting to validate data integrity.  
 - Stop Bits – Mark the end of each data frame (typically 1 or 2). Mismatched stop bits cause framing errors.  
 
-Together, these settings ensure that transmitted bits are correctly packaged, sent, and interpreted on the receiving side, ensuring that transmitted bits are correctly interpreted on the receiving side.
+Together, these settings ensure that the transmitted bits are correctly packaged, sent, and interpreted on the receiving side.
 
   <br><img src="images/BasicUART.png" alt="BasicUART" width="600">
 
 
 
 
 ### Application on PIC32CM:
-In this example, the concept is applied using the SERCOM1 peripheral configured as a UART. The onboard debugger uses a Communications Device Class (CDC) interface that appears on the host computer as a virtual COM port, allowing data to stream in both directions between the host and the target device.
+In this example, the concept is applied using the SERCOM1 peripheral configured as a UART. The onboard debugger uses a Communications Device Class (CDC) interface that appears on the host computer as a virtual COM port, allowing the data to stream in both directions between the host and the target device.
 
-Characters sent from the host are transmitted on the debugger’s CDC TX pin, while characters received on the CDC RX pin are returned to the host. The UART output can be viewed in a terminal program such as MPLAB Data Visualizer, making it easy to monitor or interact with the application over USB without extra hardware.
+Characters sent from the host are transmitted on the debugger’s CDC TX pin, while characters received on the CDC RX pin are returned to the host. The UART output can be viewed in a terminal program such as the MPLAB Data Visualizer, making it easy to monitor or interact with the application over a USB without extra hardware.
 
 
 <br><img src="images/CDCDebugger.png" alt="CDCDebugger" width="700">
@@ -86,7 +88,7 @@ Characters sent from the host are transmitted on the debugger’s CDC TX pin, wh
 The application performs the following sequence:  
 
 1. SERCOM1 is initialized as a UART interface with the chosen baud rate.
-2. The SysTick timer is initialized provides a 500 ms time base.  
+2. The SysTick timer is initialized and provides a 500 ms time base.  
 3. A fixed message string, `Hello World`, is transmitted over the USB CDC connection to the host computer.  
 4. After 500 ms, the process repeats continuously.  
 
@@ -114,7 +116,7 @@ Once programmed, the device continuously sends the `Hello World` message, which
 
  <br>
 
-7. Click the Make and Program Device button in the MPLAB X IDE toolbar to program the device . Then, verify that the device is successfully programmed.
+7. Click the Make and Program Device button in the MPLAB X IDE toolbar to program the device. Then, verify that the device is successfully programmed.
      <br><img src="images/Program.png" alt="Program" width="700">
      <br><img src="images/programcomplete.png" alt="ProgramComplete" width="700">
 
@@ -123,7 +125,7 @@ Once programmed, the device continuously sends the `Hello World` message, which
 <br>
 
 ### View the results:
-To view the output of this project, launch MPLAB Data Visualizer from the MPLAB X IDE toolbar. In Data Visualizer, select the serial COM port associated with the PIC32CM JH00 Curiosity Nano and confirm that the settings match the configured SERCOM UART parameters in the Project Configuraiton section.
+To view the output of this project, launch the MPLAB Data Visualizer from the MPLAB X IDE toolbar. In the Data Visualizer, select the serial COM port associated with the PIC32CM JH00 Curiosity Nano and confirm that the settings match the configured SERCOM UART parameters in the Project Configuration section.
 
 <br><img src="images/TerminalWindow.gif" alt="TerminalWindow" width="1000">
 
@@ -140,7 +142,7 @@ The UART pins can be probed with a logic analyzer, where the output should decod
 
 <!-- Provide instructions for configuring the project, including modifying parameters, setting up configuration files, and tuning options when necessary. -->
 
-This example project is already provided as a preconfigured MPLAB X project. Start by opening the project in MPLAB X IDE. Once the project is loaded, launch MPLAB® Code Configurator (MCC) Harmony to review the configuration.
+This example project is already provided as a preconfigured MPLAB X project. Start by opening the project in MPLAB X IDE. Once the project is loaded, launch the MPLAB® Code Configurator (MCC) in Harmony to review the configuration.
 
 For detailed instructions on how to create and set up a new MPLAB X project and open MCC Harmony, refer to the this Microchip online reference [here](https://mplab-discover.microchip.com/v2/item/com.microchip.documentation/com.microchip.portal.webhelp/com.microchip.subcategories.tools.development-boards/tool-chain-guide.guid-45e21205-663c-4792-b2c1-e147f4c3ff92.html%23guid-45e21205-663c-4792-b2c1-e147f4c3ff92/1.0.0?view=about&dsl=3+AND+Tool+AND+Chain+AND+Guide)
 
@@ -171,7 +173,7 @@ To check the system clock, go to Project Graph → Plugins → Clock Configurato
 
 ### Step 2: Configuring the System Tick (SysTick)
 
-SysTick is a built-in timer that allows the application to create precise delays without relying on software loops. In this demo, it will be used to add a fixed delay between each `Hello World` message sent over UART.
+The SysTick is a built-in timer that allows the application to create precise delays without relying on software loops. In this demonstration, it will be used to add a fixed delay between each Hello World message sent over the UART.
 
 To enable SysTick:
 
@@ -180,14 +182,14 @@ To enable SysTick:
 
 <br>
 
-2. In the Configuration Options panel, expand Cortex M0+ Configuration and Enable the SysTick option
+2. In the Configuration Options panel, expand Cortex M0+ Configuration and enable the SysTick option.
      <br><img src="images/SysTickConfig.png" alt="SysTickConfig" width="650">
 
 <br>
 
 ### Step 3: Add and Configure the UART Peripheral (SERCOM1)
 
-The device includes multiple SERCOM peripherals that can be configured as UART, SPI, or I²C. On the Curiosity Nano, only SERCOM1 is internally routed to the onboard debugger’s CDC interface, so it must be used for sending UART data to a terminal over USB.
+The device includes multiple SERCOM peripherals that can be configured as UART, SPI, or I²C. On the Curiosity Nano, only SERCOM1 is internally routed to the onboard debugger’s CDC interface, so it must be used for sending the UART data to a terminal over a USB.
 
 This information is available in the Pinout section of the [Curiosity Nano User's Guide](https://ww1.microchip.com/downloads/aemDocuments/documents/MCU32/ProductDocuments/UserGuides/PIC32CM-JH-Value-Line-Curiosity-Nano%2B-Touch-Evaluation-+Kit-User%E2%80%99s-Guide-DS70005600.pdf).
 
@@ -239,16 +241,17 @@ To assign the pins:
 
 <br>
 
-### Step 5: Generate MCC Code
-With UART and SysTick configured, the final step is to generate code. MCC creates the initialization files, peripheral drivers, and APIs for UART communication and SysTick timing, preparing the project for application development.
+### Step 5: Generate the MCC Code
+With the UART and SysTick configured, the final step is to generate the code. The MCC creates the initialization files, peripheral drivers, and APIs for UART communication and SysTick timing, preparing the project for application development.
  <br><img src="images/Generate.png" alt="Generate" width="500">
 
 <br>
 
 ## Application Source Code
 <!-- Describe the main source code structure, including key functions or files, and explain how the application logic works. -->
 
-This code defines a macro for `"Hello World"`, starts the SysTick timer, and enters a loop that sends the `Hello_World` message over UART using `SERCOM1_USART_Write()`. Timing is provided by `SYSTICK_DelayMs()` to create a 500 ms delay and prevent flooding the terminal.  
+
+This code defines a macro for `"Hello World"`, starts the SysTick timer, and enters a loop that sends the `"Hello_World"` message over the UART using `SERCOM1_USART_Write()`. Timing is provided by `SYSTICK_DelayMs()` to create a 500 ms delay and prevent flooding the terminal.
 
 <br>
 
@@ -283,8 +286,13 @@ int main(void)
 <br>
 
 ## Conclusion
-This project showed how to configure SERCOM in UART mode on a PIC32CM M0+ device using MCC Harmony. The system clock, SysTick timer, and SERCOM1 peripheral were set up to send a `"Hello World"` message every 500 ms over the Curiosity Nano’s USB CDC interface. This simple example provides a foundation for expanding into bidirectional communication or more advanced embedded applications.  
+This project showed how to configure the SERCOM in UART mode on a PIC32CM M0+ device using MCC Harmony. The system clock, SysTick timer, and SERCOM1 peripheral were set up to send a `"Hello World"` message every 500 ms over the Curiosity Nano’s USB CDC interface. This simple example provides a foundation for expanding into bidirectional communication or more advanced embedded applications.  
 
 
 ## Related Projects
-<!-- Add links, descriptions or any details of related projects of this example, if any -->
+
+- [Getting Started with Blink LED on PIC32CM M0+ Devices](https://github.com/microchip-pic-avr-examples/pic32cmjh-blink-led-mplab-harmony)
+- [Getting Started with Analog-to-Digital Converters (ADC) on PIC32CM M0+ Devices](https://github.com/microchip-pic-avr-examples/pic32cmjh-basic-adc-mplab-harmony)
+- [Getting Started with QTouch® Button and Peripheral Touch Controller on PIC32CM M0+ Devices](https://github.com/microchip-pic-avr-examples/pic32cmjh-basic-ptc-mplab-harmony)
+- [Getting Started with SERCOM (I²C) Communication on PIC32CM M0+ Devices](https://github.com/microchip-pic-avr-examples/pic32cmjh-basic-i2c-mplab-harmony)
+- [Getting Started with SERCOM (SPI) Communication on PIC32CM M0+ Devices](https://github.com/microchip-pic-avr-examples/pic32cmjh-basic-spi-mplab-harmony)