Custom Board Support Package (BSP) Tutorial: Step 1

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 >
© 2024 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.