1.1.15 PIC32MX Ethernet Starter Kit II: Building and Running the USB Device HID Bootloader Applications
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 repo or download as zip file. This content can be download using content manager by following these instructions.
Path of the application within the repository is apps/usb_device_hid_bootloader/.
To build the application, refer to the following table and open the project using its IDE.
Bootloader Application
| Project Name | Description |
|---|---|
| bootloader/firmware/pic32mx_eth_sk2.X | MPLAB X Project for PIC32MX Ethernet Starter Kit II |
Test Application
| Project Name | Description |
|---|---|
| test_app/firmware/pic32mx_eth_sk2.X | MPLAB X Project for PIC32MX Ethernet Starter Kit II |
Setting Up PIC32MX Ethernet Starter Kit II
- Mount PIC32MX Ethernet Starter Kit II on the J1 connector of Starter Kit I/O Expansion Board
- Connect TX pin of USB UART Click to U2RX pin of J11 header on Starter Kit I/O Expansion Board
- Connect RX pin of USB UART Click to U2TX pin of J11 header on Starter Kit I/O Expansion Board
- Connect GND pin of USB UART Click to GND pin of J11 header on Starter Kit I/O Expansion Board
- Connect mini USB cable to the USB UART Click board. This will enumerate the USB to UART port.
- For programming, connect mini USB cable to the Debug USB connector (J7) on the PIC32MX Ethernet Starter Kit II to the computer
- Use the USB micro-AB port J3, which is located on the bottom side of the PIC32MX Ethernet Starter Kit II, to connect the USB device to the USB Host PC
Running the Application
- Open the test application project test_app/firmware/pic32mx_eth_sk2.X in the IDE.
- Build the project to generate the binary (Do not program the binary).
- Open the bootloader project bootloader/firmware/pic32mx_eth_sk2.X in the IDE.
- Build and program the application using the IDE.
- Once programming is completed and bootloader starts running:
- LED1 will be turned-on
- HID Custom device with product ID 3C will be enumerated on Host PC
- Open the Terminal application (e.g., Tera Term) on the computer to get test application messages through UART once bootloaded.
- Configure the serial port settings as follows:
- Baud: 115200
- Data: 8 Bits
- Parity: None
- Stop: 1 Bit
- Flow Control: None
- Launch the Unified Host application from below path:
- <harmony3_path>/bootloader/tools/UnifiedHost-*/UnifiedHost-*.jar
- Configure the Unified host application.
- Select the Device Architecture and Protocol as shown below

- Click the Configure button and select the USB Device as
3C

- Load the test application hex file to be programmed using below
option
- <harmony3_path>/bootloader_apps_usb/apps/usb_device_hid_bootloader/test_app/firmware/pic32mx_eth_sk2.X/dist/pic32mx_eth_sk2/production/pic32mx_eth_sk2.X.production.hex

- Open the Console window of the host application to view application
bootloading sequence

- Select the Device Architecture and Protocol as shown below
- Click the Program Device button to program the loaded test application
hex file on to the device.

- Following figure shows output of successfully programming the test application.

- If above step is successful then LED3 should start blinking and the user should
see below output on the console.

- Press and hold the Switch SW1 to trigger Bootloader from test application and
the user should see below output.

- Repeat Steps 10-12 once and jump to Step 15.
- This step is to verify that bootloader is running after triggering bootloader from test application in Step 13
- Press and hold the Switch SW1 and then Power cycle the device to force trigger bootloader at startup.
- Repeat Steps 10-12 once.
- This step is to verify whether bootloader is triggered by switch press at reset
Note: Unified Host application has to be closed in order to
program any application using MPLAB X IDE.
Additional Steps (Optional)
- To bootload any other application, refer to the Application Configurations
- Once done, repeat the applicable steps mentioned in Running the Application
