Explorer 16/32 Development Board User's Guide - Developer Help
a naming convention where each net (except power and ground) is prefixed with
"Pxx" where xx is a number 1-100. The Pxx number corresponds with the U1A male
PIM header pin number associated with the net. Nets that are also connected to one
or more dedicated hardware features on the Explorer 16/32 Development Board
have net names with underscores and suffixes denoting their associated feature(s).
For example, the net "P21_TEMP" is the electrical signal attached to the U1A male
PIM header pin 21, and it is also connected to the analog output pin of the TC1047A
temperature sensor (U4) on the Explorer 16/32 Development Board. Similarly, the
net "P92_S5_LED10" represents the signal attached to U1A male PIM header pin
92, which also connects to pushbutton S5, as well as LED D10, on the Explorer
16/32 Development Board.
It is important to note that the U1A male PIM header pin numbers usually do NOT
correspond 1:1 with the pin numbers of the microcontroller mounted on the PIM
PCB.
(http://www.microchip.com/MA240039)) is based on a TQFP-48 microcontroller,
which does not have enough total I/O pins to connect to and control all 100 PIM pins
independently (especially in a 1:1 fashion). Therefore, the PIM PCB maps
microcontroller pins to PIM header pins on a functional basis (ex: PIM pin 21, named
"P21_TEMP" is connected to an A/D input channel pin RA1/AN1 on the
microcontroller, which is TQFP-48 pin 22). We recommend you refer to both the PIM
schematics as well as the Explorer 16/32 Development Board schematics when
tracing signals between the microcontroller I/O pins and the connected hardware.
In addition to the above conventions, the signal names for dedicated signals
connecting to the mikroBUS interfaces end in "A" or "B". For example, the net
"P10_SCKA" connects to U1A male PIM header pin 10, as well as to the SPI
interface SCK pin on the mikroBUS interface A. Meanwhile, the "P55_SCKB" net
connects to the U1A PIM header pin 55, and to the SPI interface SCK pin on the
mikroBUS interface B. The "P57_SCL" and "P56_SDA" nets are, however,
associated with a shared I C bus that is connected to both mikroBUS A and
mikroBUS B interfaces. Consequently, these special signals do not end in "A" or "B",
unlike the dedicated mikroBUS signals.
Older schematics for PIM PCBs and PICtail Plus daughter boards that were
originally designed for the "classic" Explorer 16 Development Board do not follow the
above net naming conventions. These schematics typically use microcontroller
pin/function names as net names (ex: "RE5/PMD5", instead of "P3_LCDD5"), as
they
were
(http://www.microchip.com/MA240011)), which was the first PIM created for the
classic Explorer 16, and did use a 100 pin microcontroller with 1:1 PIM to
microcontroller pin number mapping. When using the Explorer 16/32 Development
Board in conjunction with PIMs and PICtail Plus boards based on this legacy naming
convention, we recommend you refer to the pin equivalency and description table,
5 z 18
For
example,
2
originally
based
the
PIC24FJ256GA705
on
the
PIC24FJ128GA010
http://microchipdeveloper.com/boards:explorer1632
PIM
(MA240039
PIM
(MA240011
7.6.2017 8:59
Need help?
Do you have a question about the Explorer 16/32 and is the answer not in the manual?