Step 1.1: Criteria to Map a Pin
Supported Pin Mapping in Board Support Package (BSP)
For an application to access and use on-board modules, it must have the interface pins to these modules mapped appropriately. For example, an onboard CODEC module might require a Power Down Pin (PDN) to be made high for the CODEC device to reset and start functioning. The BSP should map the PIC32 pin connected to the PDN pin of the CODEC device as GPIO out and give it a suitable name to be used by the application.
The following are supported function types to which a pin can be mapped:
A pin can be mapped to only one of the supported function types. If a pin must be mapped to a functionality other than those detailed above (e.g., as an interrupt pin), it must be done by the application code.
Step 1.2: Decide on Pins to be Mapped in the BSP
Keep the schematic of your custom development board handy. If you are following the example in this training module, download the user's guide for the PIC32MZ EF Curiosity Development Board and refer to the schematics.
Pins to be Mapped in the BSP
Map the pins as per the criteria detailed in Step 1.1. The following table maps the pins for the PIC32MZ EF Curiosity Development Board.
Below is an analysis of the pins mapped for the PIC32MZ EF Curiosity Development Board.
Next Step >