MPLAB® ICE 4 In-Circuit Emulator can be used as a hardware test tool for Continuous Integration / Continuous Delivery (or Deployment) because of its network communication capabilities. In MPLAB X IDE, use the CI/CD Wizard to create files for Jenkins-Docker or Docker-only integration. See the CI/CD Wizard in MPLAB X IDE User’s Guide (DS-5000xxxx) or the section in the MPLAB X IDE User’s Guide (DS-50002027) for details on CI/CD and using the wizard.
If Jenkins Pipeline Files are selected for creation in the wizard, the emulator may be included using one of the wizard screens (see table below.)
The ICE 4 Breakout Board (AC244141) will also be required to connect the MPLAB ICE 4 to the target.
| Option | Description |
|---|---|
| Enable Hardware Testing | Enable the emulator as a test tool. |
| Configuration to Build and Run on ICE4 | Select a project configuration that uses the emulator; either default or one dedicated to hardware use. |
| IP Address of ICE4 | Enter the IP address of the emulator you wish to use. If you do not
know the IP address of the emulator, you can use
ipconfig or a similar tool to search the system to
which the emulator is connected for the address. |
| Enable MPLAB Code Coverage | Enable the MPLAB Code Coverage feature. An MPLAB Analysis Tool Suite
license will be required to use this feature. Note: The Code Coverage API plugin
must be available on your Jenkins server if coverage reporting is
enabled.
|
| Scan Output for Unity Test Results | Enable if the configuration builds Unity test runners, and the build job should create a report based on the resulting output. For more info on how to write Unity tests see Unity - Getting Started. |