Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
chipkit_wifire:refmanual [2015/08/26 02:04] – lswanland | chipkit_wifire:refmanual [2017/04/13 16:16] (current) – James Colvin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
======Reference Manual====== | ======Reference Manual====== | ||
+ | March 31, 2017 | ||
- | May 12, 2014 | + | This manual applies to [[chipkit_wifire: |
+ | =====Production Release===== | ||
- | This manual applies to [[Rev B]] of the board | + | The production boards |
- | + | ||
- | + | ||
- | =====Pre-Production Limited Quantity Release===== | + | |
- | + | ||
- | The first manufacturing build of the chipKIT WiFire board wasis produced | + | |
+ | Rev D boards now include a new header for MIPS JTAG debugging and iFlowtrace and a few hardware changes to support this connector. Most components on the board remained the same, although nearly all of the silk screen designators were changed from Rev C. | ||
====Overview==== | ====Overview==== | ||
+ | The Wi-FIRE is based on the popular Arduino™ open-source hardware prototyping platform and adds the performance of the Microchip PIC32MZ microcontroller. The Wi-FIRE has a WiFi MRF24 and SD card on the board, both with dedicated SPI signals. The Wi-FIRE board takes advantage of the powerful PIC32MZ2048EFG microcontroller. This microcontroller features a 32-bit MIPS M5150 processor core running at 200 MHhz, 2MB of flash program memory, and 512K of RAM data memory. The Wi-FIRE can be programmed using the Arduino IDE with the Digilent Core. It contains everything needed to start developing embedded applications. The Wi-FIRE features a USB serial port interface for connection to the Arduino IDE and can be powered via USB or by an external power supply. In addition, the Wi-FIRE is fully compatible with the advanced Microchip MPLAB®X IDE and works with all MPLAB ®X compatible in-system programmer/ | ||
- | The chipKIT WiFire is based on the popular Arduino™ open-source hardware prototyping platform and adds the performance of the Microchip PIC32MZ microcontroller. The WiFire has a WiFi MRF24 and SD card on the board, both with dedicated SPI signals. The WiFire board takes advantage of the powerful PIC32MZ2048ECG microcontroller. This microcontroller features a 32-bit MIPS processor core running at 200 MHhz, 2MB of flash program memory, and 512K of SRAM data memory. The WiFire can be programmed using the Multi-Platform Integrated Development Environment (MPIDE), an environment based on the original Arduino IDE, modified to support PIC32. It contains everything needed to start developing embedded applications. The WiFire features a USB serial port interface for connection to the MPIDE and can be powered via USB or by an external power supply. In addition, the WiFire is fully compatible with the advanced Microchip MPLAB®X IDE and works with all MPLAB ®X compatible in-system programmer/ | + | {{: |
- | + | ||
- | Note: The Microchip PIC32MZ processor is a new generation microcontroller incorporating a very complex,n aggressively ambitious, analog to digital converter (ADC) design. The ADC is uses a high speed pipelined converter architecture that does not lend itself well to a multichannel applications or low speed sampling applications. As a result, the ADC does not meet Microchip’s original design specification. UnfortunatelyConsequently, | + | |
- | + | ||
- | + | ||
- | The analogRead() function in MPIDE was updated to mitigate the complexities and to improve the accuracy of the PIC32MZ ADC by careful selection of sampling times and oversampling of the input. These optimizations are only available when calling analogRead(); | + | |
- | + | ||
- | {{: | + | |
- | * Microchip® | + | * Microchip® |
* Microchip MRF24WG0MA WiFi module | * Microchip MRF24WG0MA WiFi module | ||
* Micro SD card connector | * Micro SD card connector | ||
Line 31: | Line 23: | ||
* 50 MHz SPI | * 50 MHz SPI | ||
* 43 available I/O pins | * 43 available I/O pins | ||
- | * four user LEDs | + | * Four user LEDs |
- | * PC connection uses a USB A > mini B cable (not included) | + | * PC connection uses a USB A > micro B cable (not included) |
* 12 analog inputs | * 12 analog inputs | ||
- | * 3.3V operating voltage | + | * 3.3 V operating voltage |
- | * 200Mhz | + | * 200MHz |
- | * 7V to 15V input voltage (recommended) | + | * 7 V to 15 V input voltage (recommended) |
- | * 30V input voltage (maximum) | + | * 30 V input voltage (maximum) |
- | * 0V to 3.3V analog input voltage range | + | * 0 V to 3.3 V analog input voltage range |
- | * High efficiency, switching 3.3V power supply providing low power operation | + | * High efficiency, switching 3.3 V power supply providing low power operation |
- | =====1 ChipKIT WiFire | + | =====1: |
+ | The Wi-FIRE has the following hardware features: | ||
- | The WiFire has the following hardware features: | ||
+ | {{ : | ||
+ | ^ Call Out ^ Component Description | ||
+ | | 1 | ||
+ | | 2 | ||
+ | | 3 | ||
+ | | 4 | ||
+ | | 5 | ||
+ | | 6 | ||
+ | | 7 | ||
+ | | 8 | ||
+ | | 9 | ||
+ | | 10 | User LEDs | 23 | J15- External Power Connector Barrel Jack | | ||
+ | | 11 | J8- SPI Connector | ||
+ | | 12 | JP6- USB Host or OTG Select | ||
+ | | 13 | J10 & J11- USB Connectors | ||
- | =====2 MPIDE and USB Serial Communications===== | ||
+ | =====2: | ||
- | The WiFire | + | The Wi-FIRE |
- | The MPIDE uses a serial communications port to communicate with a boot loader running on the WiFire | + | The Arduino IDE uses a serial communications port to communicate with a boot loader running on the Wi-FIRE |
- | The WiFire | + | The Wi-FIRE |
- | When the MPIDE needs to communicate with the WiFire | + | When the Arduino IDE needs to communicate with the Wi-FIRE |
- | When the MPIDE opens the serial communications connection on the PC, the DTR pin on the FT232RQ chip is driven low. This pin is coupled through a capacitor to the MCLR pin on the PIC32 microcontroller. Driving the MCLR line low resets the microcontroller, | + | When the Arduino IDE opens the serial communications connection on the PC, the DTR pin on the FT232RQ chip is driven low. This pin is coupled through a capacitor to the MCLR pin on the PIC32 microcontroller. Driving the MCLR line low resets the microcontroller, |
- | This automatic reset action (when the serial communications connection is opened) can be disabled. To disable this operation, there is a jumper labeled | + | This automatic reset action (when the serial communications connection is opened) can be disabled. To disable this operation, there is a jumper labeled |
- | Two red LEDs (LD5 and LD6) will blink when data is being sent or received between the WiFire | + | Two red LEDs (LD5 and LD6) will blink when data is being sent or received between the Wi-FIRE |
- | The header connector J4 provides access to the other serial handshaking signals provided by the FT232RQ. Connector J4 is not loaded at the factory and can be installed by the user to access these signals. | + | |
- | =====3 Power Supply===== | + | =====3: Power Supply===== |
- | The WiFire | + | The Wi-FIRE |
- | In order to operate the WiFire | + | In order to operate the Wi-FIRE |
- | When a shield is used, connectoer J5 provides power to the shield. | + | When a shield is used, connector J1 provides power to the shield. |
- | The WiFire | + | The Wi-FIRE |
- | The 5V regulator section provides a low dropout linear regulator. The 5.0 regulator is provided for powering external circuitry that needs a 5V power supply, such as providing for USB 5.0Vv when the WiFire | + | The 5 V regulator section provides a low dropout linear regulator. The 5.0 regulator is provided for powering external circuitry that needs a 5 V power supply, such as providing for USB 5.0 V when the Wi-FIRE |
- | The input voltage to the 5V regulator is taken from the VU bus, and the output is placed on the VCC5V0 power bus. There is a reverse polarity protection diode in the external power supply circuit. Considering the diode drop plus the forward drop across the regulator, the minimum input voltage to the regulator should be 7V to produce a reliable | + | The input voltage to the 5 V regulator is taken from the VU bus, and the output is placed on the VCC5V0 power bus. There is a reverse polarity protection diode in the external power supply circuit. Considering the diode drop plus the forward drop across the regulator, the minimum input voltage to the regulator should be 7 V to produce a reliable |
- | For input voltages above 9V, the regulator will get extremely hot when drawing high currents. The NCP1117LP has output short circuit protection as well asand internal thermal protection and will shut down automatically to prevent damage. | + | For input voltages above 9 V, the regulator will get extremely hot when drawing high currents. The NCP1117LP has output short circuit protection as well as internal thermal protection and will shut down automatically to prevent damage. |
- | The 5V regulator selection on JP17 provides four 5V power configurations: | + | The 5 V regulator selection on J15 provides four 5 V power configurations: |
- | 1) 5V regulator completely disabled and no 5V power available; | + | 1) 5 V regulator completely disabled and no 5 V power available; |
- | 2) 5V regulator bypassed and 5V provided from an external | + | 2) 5 V regulator bypassed and 5 V provided from an external |
- | 3) on-board | + | 3) on-board |
- | 4) External | + | 4) External |
- | Jumper block J17 is used to select these various options and the following diagrams describe the use of J16. This diagram shows the arrangement of the signals on J17: | + | Jumper block J15 is used to select these various options and the following diagrams describe the use of J13. This diagram shows the arrangement of the signals on J15: |
+ | {{ : | ||
+ | ^ Signals | ||
+ | | LDO In | ||
+ | | LDO Out | The output of the on-board regulator. | ||
+ | | VU | ||
+ | | 5V0 | The connection to the VCC5V0 power bus on the Wi-FIRE board. | ||
+ | | EN Ext | ||
+ | | GND | Connection to the digital ground bus on the Wi-FIRE board. | ||
- | To completely disable operation of the on-board linear regulator, remove all shorting blocks from J17. To use the on-board | + | To completely disable operation of the on-board linear regulator, remove all shorting blocks from J15. To use the on-board |
+ | {{ : | ||
- | Note: In this case, when J16 is in the EXT position, and J17 is jumpered to regulate the external input, do not apply more than 18V;. tThis can destroy the 5.0V regulator. | + | Note: In this case, when J13 is in the EXT position, and J15 is jumpered to regulate the external input, do not apply more than 18 V. This can destroy the 5.0 V regulator. |
- | To bypass the on-board | + | To bypass the on-board |
- | An external 5V regulator can be used. This would be desirable, for example, when operating from batteries. An external switching mode 5V regulator could be used to provide higher power efficiency than the on-board linear regulator. In this case, use wires as appropriate to connect VU to the unregulated input of the external regulator. Connect the regulated 5V output to 5V0. Connect GND to the ground connection of the external regulator. Optionally, connect EN Ext to the enable input control of the external regulator, if available. This allows the external regulator to be turned off for low power operation. Digital pin 50 is then used to turn on/off the external regulator. | + | {{ : |
- | The PIC32MZ microcontroller is rated to use a maximum of 60mA of current | + | An external 5 V regulator can be used. This would be desirable, for example, |
- | The POWER connector (J5) is used to power shields connected to the WiFire | + | The PIC32MZ microcontroller is rated to use a maximum of 60 mA of current when operating at 200 MHz. The MRF24WG0MA WiFi module typically consumes a maximum of 237 mA when transmitting. This allows approximately 303 mA of current to power the remaining 3.3 V circuitry on the Wi-FIRE board and external circuitry powered from the VCC3V3 bus. No circuitry on the Wi-FIRE board is powered from the VCC5V0 power bus, leaving all current available from the 5 V regulator to power external circuitry and the USB 5.0 V power bus when the Wi-FIRE is used as a USB Host. |
+ | |||
+ | The POWER connector (J1) is used to power shields connected to the Wi-FIRE | ||
* **IOREF** (pin 2): This pin is tied to the VCC3V3 bus. | * **IOREF** (pin 2): This pin is tied to the VCC3V3 bus. | ||
* **RST** (pin 3): This connects to the MCLR pin on the PIC32 microcontroller and can be used to reset the PIC32. | * **RST** (pin 3): This connects to the MCLR pin on the PIC32 microcontroller and can be used to reset the PIC32. | ||
- | * **3V3** (pin 4): This routes the 3.3V power bus to shields. | + | * **3V3** (pin 4): This routes the 3.3 V power bus to shields. |
- | * **5V0** (pin 5): This routes 3.3V or 5.0V power to shields depending on the position of JP9. | + | * **5V0** (pin 5): This routes 3.3 V or 5.0 V power to shields depending on the position of JP1. |
- | * **GND** (pin 6, 7): This provides a common ground connection between the WiFire | + | * **GND** (pin 6, 7): This provides a common ground connection between the Wi-FIRE |
- | * **VIN** (pin 8): This connects to the voltage provided at the external power supply connectors (J14 and J15). This can be used to provide unregulated input power to the shield. It can also be used to power the WiFire | + | * **VIN** (pin 8): This connects to the voltage provided at the external power supply connectors (J12 and J14). This can be used to provide unregulated input power to the shield. It can also be used to power the Wi-FIRE |
| | ||
- | ===== 4 5V Compatibility===== | + | ===== 4: 5 V Compatibility===== |
- | The PIC32 microcontroller operates at 3.3V. The original Arduino boards operate at 5V, as do many Arduino shields. | + | The PIC32 microcontroller operates at 3.3 V. The original Arduino boards operate at 5 V, as do many Arduino shields. |
- | There are two issues to consider when dealing with 5V compatibility for 3.3V logic. The first is protection of 3.3V inputs from damage caused by 5V signals. The second is whether the 3.3V output is high enough to be recognized as a logic high value by a 5V input. | + | There are two issues to consider when dealing with 5 V compatibility for 3.3 V logic. The first is protection of 3.3 V inputs from damage caused by 5 V signals. The second is whether the 3.3 V output is high enough to be recognized as a logic high value by a 5 V input. |
- | The digital I/O pins on the PIC32 microcontroller are 5V tolerant. The, whereas the analog capable I/O pins are not 5V tolerant. There are 48 analog capable I/O pins on the PIC32MZ, and this applies to most GPIO pins on the processor. Historically, | + | The digital I/O pins on the PIC32 microcontroller are 5 V tolerant. The, whereas the analog capable I/O pins are not 5 V tolerant. There are 48 analog capable I/O pins on the PIC32MZ, and this applies to most GPIO pins on the processor. Historically, |
- | The minimum high-voltage output of the PIC32 microcontroller is rated at 2.4V when sourcing | + | The minimum high-voltage output of the PIC32 microcontroller is rated at 2.4 V when sourcing |
- | =====5 Input/ | + | =====5: Input/ Output Connections===== |
+ | The Wi-FIRE board provides 43 of the I/O pins from the PIC32 microcontroller at pins on the input/ | ||
- | The WiFire board provides 43 of the I/O pins from the PIC32 microcontroller at pins on the input/output | + | The PIC32 microcontroller can source or sink a maximum |
- | The PIC32 microcontroller can source or sink a maximum of 15mA on all digital I/O pins; however, some pins can source or sink 25mA or even 33mA;, check with the PIC32MZ datasheet | + | The Arduino system uses logical pin numbers to identify |
- | Connectors J7 and J10 are 2x8 female pin header | + | Pins 0-7 and 27-33 are available on header |
- | Connector J8 is a 2x6 female pin header connector that provides access to the analog | + | Analog |
- | The chipKIT/ | + | In addition |
- | Pin numbers 0-13 are the outer row of pins on J10 and J7, from right to left. Pin numbers 14-19 are the outer row of pins on J8, from left to right. Pins 20-25 are the inner row of pins on J8, from left to right. Pin numbers 26-41 are the inner row of pins on J10 and J7, from right to left. Pin 42 is the pin labeled A on J7. This pin is normally the reference voltage for the microcontroller’s A/D converter, but can also be used as a digital I/O pin. | ||
- | In addition to the connector pin, Pin 13 also connects to the user LED LD1. Pin 43, 44, and 45 connect to user LEDs LD2, LD3, and LD4. Pins 43-45 do not attach to any connector. | + | =====6: 802.11b/g Interface===== |
- | The analog inputs on connector J8 are assigned pin numbers. The outer row of pins on J8 is analog inputs A0-A5. The inner row of pins is A6-A11. These pins are also assigned digital pin numbers; A0-A5 are digital pins 14-19, and A6-A11 are 20-25. | + | The 802.11b/g compatible WiFi interface on the Wi-FIRE |
- | + | ||
- | + | ||
- | =====6 802.11b/ | + | |
- | + | ||
- | + | ||
- | The 802.11b/g compatible WiFi interface on the WiFire | + | |
The MRF24WG0MA firmware provides the 802.11 network protocol software support. The DEIPcK and DEWFcK libraries provide the TCP/IP network protocol support that works with the 802.11 protocol support provided by the WiFi module. | The MRF24WG0MA firmware provides the 802.11 network protocol software support. The DEIPcK and DEWFcK libraries provide the TCP/IP network protocol support that works with the 802.11 protocol support provided by the WiFi module. | ||
- | The primary communications interface with the MRF24WG0MA WiFi module is a 4 wire SPI bus. This SPI bus uses SPI4 in the PIC32 microcontroller, | + | The primary communications interface with the MRF24WG0MA WiFi module is a 4 wire SPI bus. This SPI bus uses SPI4 in the PIC32 microcontroller, |
The WiFi module supports SPI clock speeds up to 25MHz. In addition to the SPI interface, the interface to the WiFi module also includes a reset signal, an interrupt signal and a hibernate signal. The active low RESET signal is used to reset the WiFi module The external interrupt signal, INT, is used by the module to signal to the host microcontroller that it needs servicing by the microcontroller software. The INT signal on the WiFi module is connected to external interrupt INT4 on the PIC32 microcontroller and is not routed to any connector. The active low HIBERNATE signal is used to power the WiFi module down and puts it into a low power state. | The WiFi module supports SPI clock speeds up to 25MHz. In addition to the SPI interface, the interface to the WiFi module also includes a reset signal, an interrupt signal and a hibernate signal. The active low RESET signal is used to reset the WiFi module The external interrupt signal, INT, is used by the module to signal to the host microcontroller that it needs servicing by the microcontroller software. The INT signal on the WiFi module is connected to external interrupt INT4 on the PIC32 microcontroller and is not routed to any connector. The active low HIBERNATE signal is used to power the WiFi module down and puts it into a low power state. | ||
- | The interface signals to the WiFi module are controlled by the network libraries and are not normally accessed by the user sketch. Refer to the schematic for the WiFire | + | The interface signals to the WiFi module are controlled by the network libraries and are not normally accessed by the user sketch. Refer to the schematic for the Wi-FIRE |
More detailed information about the operation of the MRF24WG0MA can be obtained from the manufacturer data sheet available from www.microchip.com. | More detailed information about the operation of the MRF24WG0MA can be obtained from the manufacturer data sheet available from www.microchip.com. | ||
- | =====7 Network Library Software===== | + | =====7: Network Library Software===== |
- | The WiFi module on the WiFire | + | The WiFi module on the Wi-FIRE |
- | The DEWFcK library supports the MRF24WG0MA WiFi module as loaded on the WiFire. The correct header file must be used to specify the network hardware being used by the sketch. When writing a network sketch on the WiFire, use the following hardware library: | + | The DEWFcK library supports the MRF24WG0MA WiFi module as loaded on the Wi-FIRE. The correct header file must be used to specify the network hardware being used by the sketch. When writing a network sketch on the Wi-FIRE, use the following hardware library: |
#include < | #include < | ||
- | The Digilent Embedded | + | The Digilent Embedded network libraries are available |
- | There are reference examples demonstrating the use of these libraries | + | There are reference examples demonstrating the use of these libraries |
+ | =====8: USB Interface===== | ||
- | =====8 USB Interface===== | ||
+ | The PIC32MZ microcontroller on the Wi-FIRE contains a USB 2.0 Compliant, Hi/ | ||
- | The PIC32MZ microcontroller on the WiFire contains a USB 2.0 Compliant, Hi/ | + | |
- | + | ||
- | | + | |
* Low speed host support. | * Low speed host support. | ||
* USB OTG support. | * USB OTG support. | ||
Line 193: | Line 203: | ||
- | Connector J12 is a standard USB type A receptacle. This connector will be used when the WiFire | + | Connector J12 is a standard USB type A receptacle. This connector will be used when the Wi-FIRE |
Connector J11, on the bottom of the board, is the Device/OTG connector. This is a standard USB micro-AB connector. Connect a cable with a micro-A plug (optionally available from Digilent) from this connector to an available USB port on a PC or USB hub for device operation. | Connector J11, on the bottom of the board, is the Device/OTG connector. This is a standard USB micro-AB connector. Connect a cable with a micro-A plug (optionally available from Digilent) from this connector to an available USB port on a PC or USB hub for device operation. | ||
The USB specification allows for two types of devices with regard to how they are powered: self-powered devices and bus powered devices. A self-powered device is one that is powered from a separate power supply and does not draw power from the USB bus. A bus powered device is one that draws power from the USB bus and does not have a separate power supply. | The USB specification allows for two types of devices with regard to how they are powered: self-powered devices and bus powered devices. A self-powered device is one that is powered from a separate power supply and does not draw power from the USB bus. A bus powered device is one that draws power from the USB bus and does not have a separate power supply. | ||
- | The WiFire | + | The Wi-FIRE |
- | For operation as a self-powered device, place a shorting block on the EXT position of J16 and connect a suitable external power supply to either | + | For operation as a self-powered device, place a shorting block on the EXT position of J13 and connect a suitable external power supply to either |
- | To operate the WiFire | + | To operate the Wi-FIRE |
- | Note that there are two completely independent USB interfaces on the WiFire | + | Note that there are two completely independent USB interfaces on the Wi-FIRE |
- | When the WiFire | + | When the Wi-FIRE |
- | A USB host is expected to be able to provide bus power to USB devices connected to it. Therefore, when operating as a USB host, the WiFire | + | A USB host is expected to be able to provide bus power to USB devices connected to it. Therefore, when operating as a USB host, the Wi-FIRE |
- | The USB host provides regulated | + | The USB host provides regulated |
- | If the external power supply being used is a regulated | + | If the external power supply being used is a regulated |
- | The power supply used must be able to supply enough current to power both the WiFire, and the attached USB device, since the WiFire | + | The power supply used must be able to supply enough current to power both the Wi-FIRE, and the attached USB device, since the Wi-FIRE |
- | Jumper JP6 is used to provide the required USB host capacitance to the host connector being used. Place the shorting block in the “A” position when using the standard USB type A (host) Connector (J12). Place the shorting block in the “AB” position for use with the USB micro-AB (OTG) connector (J11). | + | Jumper JP6 is used to provide the required USB host capacitance to the host connector being used. Place the shorting block in the “A” position when using the standard USB type A (host) Connector (J11). Place the shorting block in the “AB” position for use with the USB micro-AB (OTG) connector (J10). |
- | With JP8 shorted, | + | With JP5 shorted, |
- | When using the WiFire | + | When using the Wi-FIRE |
- | =====9 SD Card Interface===== | + | =====9: SD Card Interface===== |
- | The micro-SD card connector provides the ability to access data stored on micro-SD sized flash memory cards using the SD card library provided as part of the MPIDE software system. | + | The micro-SD card connector provides the ability to access data stored on micro-SD sized flash memory cards using the SD card library provided as part of the Arduino IDE software system. |
- | The SD card is accessed using an SPI interface on PIC32 microcontroller pins dedicated to this purpose. The MPIDE SD library uses a “bit-banged” software SPI implementation to talk to SD card. However, software can be written to access the SD card using SPI3. | + | The SD card is accessed using an SPI interface on PIC32 microcontroller pins dedicated to this purpose. The Arduino IDE SD library uses a “bit-banged” software SPI implementation to talk to SD card. However, software can be written to access the SD card using SPI3. |
- | On the WiFire | + | On the Wi-FIRE |
- | =====10 | + | =====10: |
+ | The PIC32 microcontroller on the Wi-FIRE board provides a number of peripheral functions. The provided peripherals are explained in the following sections. | ||
- | The PIC32 microcontroller on the WiFire board provides a number of peripheral functions. The provided peripherals are explained in the following sections. | + | ====10.1: UART Ports==== |
- | + | UART 4: Asynchronous serial port. Pin 0 (RX), Pin 1 (TX). This is accessed using the runtime object: Serial. These pins are connected to I/O connector | |
- | =====10.1 | + | |
- | + | ||
- | + | ||
- | UART 4: Asynchronous serial port. Pin 0 (RX), Pin 1 (TX). This is accessed using the runtime object: Serial. These pins are connected to I/O connector | + | |
UART 1: Asynchronous serial port. Pin 39 (RX), Pin 40 (TX). This is accessed using the runtime object: Serial1. This uses UART1 (U1RX, U1TX) on the PIC32 microcontroller. | UART 1: Asynchronous serial port. Pin 39 (RX), Pin 40 (TX). This is accessed using the runtime object: Serial1. This uses UART1 (U1RX, U1TX) on the PIC32 microcontroller. | ||
- | =====10.3 SPI===== | + | ====10.2: |
- | Synchronous serial port. Pin 10 (SS), Pin 11 (MOSI), Pin 12 (MISO), Pin 13 (SCK). This can be accessed using the SPI standard library. It can also be accessed using the DSPI0 object from the DSPI standard library. This uses SPI2 (SS2, SDI2, SDO2, SCK2) on the PIC32 microcontroller. These signals also appear on connector | + | Synchronous serial port. Pin 10 (SS), Pin 11 (MOSI), Pin 12 (MISO), Pin 13 (SCK). This can be accessed using the SPI standard library. It can also be accessed using the DSPI0 object from the DSPI standard library. This uses SPI2 (SS2, SDI2, SDO2, SCK2) on the PIC32 microcontroller. These signals also appear on connector |
**SPI1:** Synchronous serial port. This is an additional SPI interface on the PIC32 microcontroller that can be assessed using the DSPI1 object from the DSPI standard library. SS1 is accessed via digital pin number 7. SDO1 is accessed via digital pin 35. SDI1 is accessed via digital pin 36. SCK1 is connected to digital pin 5. | **SPI1:** Synchronous serial port. This is an additional SPI interface on the PIC32 microcontroller that can be assessed using the DSPI1 object from the DSPI standard library. SS1 is accessed via digital pin number 7. SDO1 is accessed via digital pin 35. SDI1 is accessed via digital pin 36. SCK1 is connected to digital pin 5. | ||
+ | ====10.3: | ||
- | =====10.4 | + | Synchronous serial interface. The PIC32 microcontroller shares analog pins A4 and A5 with the two I2C signals, SDA and SCL. This uses I2C4 (SDA4, SCL4) on the PIC32 microcontroller. Both SDA4 and SCL4 are accessible on connector |
- | + | ||
- | + | ||
- | Synchronous serial interface. The PIC32 microcontroller shares analog pins A4 and A5 with the two I2C signals, SDA and SCL. This uses I2C4 (SDA4, SCL4) on the PIC32 microcontroller. Both SDA4 and SCL4 are accessible on connector | + | |
Note: The I2C bus uses open collector drivers to allow multiple devices to drive the bus signals. This means that external pull-up resistors must be provided to supply the logic high state for the signals. | Note: The I2C bus uses open collector drivers to allow multiple devices to drive the bus signals. This means that external pull-up resistors must be provided to supply the logic high state for the signals. | ||
- | + | ====10.4: PWM==== | |
- | =====10.5 PWM===== | + | |
Pulse width modulated output; Pins 3 (OC1), 5 (OC2), 6 (OC3), 9 (OC4), 10 (OC9), and 11 (OC7). These can be accessed using the analogWrite() runtime function. | Pulse width modulated output; Pins 3 (OC1), 5 (OC2), 6 (OC3), 9 (OC4), 10 (OC9), and 11 (OC7). These can be accessed using the analogWrite() runtime function. | ||
- | =====10.6 External Interrupts===== | + | ====10.5: External Interrupts==== |
- | + | ||
- | + | ||
- | Pin 3 (INT0), Pin 2 (INT1), Pin 7 (INT2), Pin 8 (INT3), Pin 59 (INT4). Note that the pin numbers for INT0 and INT4 are different than on some other chipKIT boards. INT4 is dedicated for use with the MRF24WG0MA WiFi module and is not brought out to a connector pin. | + | |
+ | Pin 3 (INT0), Pin 2 (INT1), Pin 7 (INT2), Pin 8 (INT3), Pin 59 (INT4). Note that the pin numbers for INT0 and INT4 are different than on some other Digilent boards. INT4 is dedicated for use with the MRF24WG0MA WiFi module and is not brought out to a connector pin. | ||
- | =====10.7 User LEDs===== | + | ====10.6: User LEDs==== |
Line 280: | Line 281: | ||
- | =====10.8 User Push Buttons===== | + | ====10.7: User Push Buttons==== |
There are two push button switches, which are labeled BTN1 (pin 46), and BTN2 (pin 47). The digitalRead() function will return LOW if the button is not pressed and HIGH when the button is pressed. | There are two push button switches, which are labeled BTN1 (pin 46), and BTN2 (pin 47). The digitalRead() function will return LOW if the button is not pressed and HIGH when the button is pressed. | ||
- | =====10.9 A/D Converter Reference===== | + | ====10.8: A/D Converter Reference==== |
- | Labeled A, the left-most outer pin on connector | + | Labeled A, the left-most outer pin on connector |
- | =====10.10 | + | ====10.9: |
- | A potentiometer (pot) is provided on the board to be used as an analog signal source or analog control input. The pot is a 10KΩohm trimmer pot connected between the VCC3V3 supply and ground. The wiper of the pot is connected to analog input A12 or chipKIT | + | A potentiometer (pot) is provided on the board to be used as an analog signal source or analog control input. The pot is a 10 kΩ trimmer pot connected between the VCC3V3 supply and ground. The wiper of the pot is connected to analog input A12 or Digilent |
- | =====10.11 | + | ====10.10: VU Voltage Monitor==== |
- | The supply voltage as provided by J16 can be monitored on analog input A13 or digital pin 49. The voltage presented to the analog input is 1/11th of the actual VU voltage. This allows for a supply voltage between 2.2V to 30V to be monitored and still fall within the range of 0 to 3.3V on the analog input. By doing an analogRead(49), | + | The supply voltage as provided by J13 can be monitored on analog input A13 or digital pin 49. The voltage presented to the analog input is 1/11th of the actual VU voltage. This allows for a supply voltage between 2.2 V to 30 V to be monitored and still fall within the range of 0 to 3.3 V on the analog input. By doing an analogRead(49), |
- | =====10.12 | + | ====10.11: |
- | Real tTime cClock cCalendar. | + | The PIC32 microcontroller contains an RTCC circuit that can be used to maintain time and date information. The operation of the RTCC requires a 32.768 |
- | UPDATE: At this time, the PIC32MZ processor does not support crystals as a source for the secondary clock and an oscillator must be used. The unloaded circuit as provided may not be useable | + | UPDATE: At this time, the PIC32MZ processor does not support crystals as a source for the secondary clock and an oscillator must be used. The unloaded circuit as provided may not be usable |
- | =====10.13 | + | ====10.12: RESET==== |
+ | The PIC32 microcontroller is reset by bringing its MCLR pin low. The MCLR pin is connected to the RST pin, as presented on J1. | ||
- | The PIC32 microcontroller | + | As previously described earlier, reset of the PIC32 microcontroller |
- | As previously described earlier, reset of the PIC32 microcontroller can be initiated by the USB serial converter. The USB serial converter brings the DTR pin low to reset the microcontroller. Jumper JP2 can be used to enable/ | + | The RST is connected to pin 3 of connector J1. This allows circuitry on a shield |
- | The RST is connected to pin 3 of connector J5. This allows circuitry on a shield to reset the microcontroller, | + | Connector |
- | + | ||
- | Connector | + | |
On Arduino boards, the corresponding connector is also used as an in-system programming connector as well as providing access to some of the SPI signals. On Arduino boards, pin 5 of this connector is connected to the reset net. | On Arduino boards, the corresponding connector is also used as an in-system programming connector as well as providing access to some of the SPI signals. On Arduino boards, pin 5 of this connector is connected to the reset net. | ||
- | Some Arduino shields, most notably the Ethernet shield, connect pin 5 to the reset net on pin 3 of connector | + | Some Arduino shields, most notably the Ethernet shield, connect pin 5 on J8 to the reset net on pin 3 of connector |
A reset button is located to the right of the MRF24WG0MA WiFi module. Pressing this button resets the PIC32 microcontroller. | A reset button is located to the right of the MRF24WG0MA WiFi module. Pressing this button resets the PIC32 microcontroller. | ||
+ | =====11: | ||
+ | In addition to being used with the Arduino IDE, the Wi-FIRE board can be used as a more traditional microcontroller development board using Microchip Development Tools. | ||
- | =====11 Microchip Development Tool Compatibility===== | + | Unloaded connector |
- | + | ||
- | + | ||
- | In addition to being used with the MPIDE, the WiFire board can be used as a more traditional microcontroller development board using Microchip Development Tools. | + | |
- | + | ||
- | Unloaded connector | + | |
- | + | ||
- | Typically, a standard male connector and a 6-pin cable is used with JP1 so that a PICkit™3 can be attached to the WiFire board. | + | |
- | + | ||
- | The Digilent chipKIT PGM can also be used in place of a PICkit3 to program the WiFire with the Microchip Development tools. The chipKIT PGM has a smaller form factor and does not need a 6-pin cable to connect to JP1. | + | |
- | + | ||
- | The Microchip MPLAB ®X IDE can be used to program and debug code running on the WiFire board. The MPLAB ®X IDE can be downloaded from the Microchip web site. Please note that Microchip’s MPLAB®Vv8 and earlier IDEs cannot be used with the WiFire, as those versions of MPLAB® IDE do not support the MZ processor. | + | |
- | + | ||
- | Using the Microchip development tools to program the WiFire board will cause the boot loader to be erased. To use the board with the MPIDE again, it is necessary to program the boot loader back onto the board. The boot loader HEX file can be found at www.digilentinc.com. To reprogram the bootloader, use the Microchip IPE which comes with the MPLAB ®X tool set. The bootloader cannot be easily reprogrammed directly with the MPLAB ®X IDE. | + | |
+ | Typically, a standard male connector and a 6-pin cable is used with JP2 so that a PICkit™3 can be attached to the Wi-FIRE board. | ||
- | =====12 Pinout Tables===== | + | The Digilent chipKIT PGM can also be used in place of a PICkit3 to program the Wi-FIRE with the Microchip Development tools. The chipKIT PGM has a smaller form factor and does not need a 6-pin cable to connect to JP2. |
+ | The Microchip MPLAB ®X IDE can be used to program and debug code running on the Wi-FIRE board. The MPLAB ®X IDE can be downloaded from the Microchip web site. Please note that Microchip’s MPLAB® V8 and earlier IDEs cannot be used with the Wi-FIRE, as those versions of MPLAB® IDE do not support the MZ processor. | ||
- | The following tables show the relationship between | + | Using the Microchip development tools to program |
- | In the following tables, columns labeled chipKIT pin # refer to the digital pin number. This is the value that is passed to the pinMode(), digitalRead(), | ||
- | ====12.1 Pinout Table by ChipKIT Pin Number==== | + | =====12: Programming and Debugging with OpenOCD through the EJTAG/Trace Connector===== |
+ | OpenOCD (Open On-Chip Debugger) is a system that provides debugging, in-system programming, | ||
+ | Header J17 provides a EJTAG header where users may attach a debugging adapter such as the Bus Blaster v3C to use with OpenOCD. | ||
+ | More information on how to use OpenOCD Debug with the Wi-FIRE can be found via MIPS Debug OpenOCD with Bus Blaster Getting Started Guide available on the [[https:// | ||
+ | =====13: | ||
+ | The following tables show the relationship between the digital pin numbers, the connector pin numbers, and the microcontroller pin numbers. | ||
+ | In the following tables, columns labeled Digilent pin # refer to the digital pin number. This is the value that is passed to the pinMode(), digitalRead(), | ||
+ | ==== 13.1: Pinout Table by Digilent Pin Number ==== | ||
+ | ^ Digilent Pin # ^ MCU Pin ^ Port Bit ^ PIC32 Signal Name ^ Function | ||
+ | | 0 | 57 | RF02 | EBIRDY3/ | ||
+ | | 1 | 58 | RF08 | EBIRDY2/ | ||
+ | | 2 | 18 | RE08 | AN25/ | ||
+ | | 3 | 71 | RD00 | EMDIO/ | ||
+ | | 4 | 60 | RA03 | EBIRDY1/ | ||
+ | | 5 | 76 | RD01 | RPD1/ | ||
+ | | 6 | 77 | RD02 | EBID14/ | ||
+ | | 7 | 19 | RE09 | AN26/ | ||
+ | | 8 | 66 | RA14 | AETXCLK/ | ||
+ | | 9 | 78 | RD03 | EBID15/ | ||
+ | | 10 | 16 | RG09 | EBIA2/ | ||
+ | | 11 | 70 | RD11 | EMDC/ | ||
+ | | 12 | 85 | RF00 | EBID11/ | ||
+ | | 13 | 10 | RG06 | AN14/ | ||
+ | | 14 | 20 | RB05 | AN45/ | ||
+ | | 15 | 33 | RB09 | EBIA7/ | ||
+ | | 16 | 7 | RC02 | EBIA12/ | ||
+ | | 17 | 44 | RB15 | EBIA0/ | ||
+ | | 18 | 11 | RG07 | EBIA4/ | ||
+ | | 19 | 12 | RG08 | EBIA3/ | ||
+ | | 20 | 22 | RB03 | AN3/ | ||
+ | | 21 | 23 | RB02 | AN2/ | ||
+ | | 22 | 21 | RB04 | AN4/ | ||
+ | | 23 | 24 | RB01 | PGEC1/ | ||
+ | | 24 | 32 | RB08 | EBIA10/ | ||
+ | | 25 | 25 | RB00 | PGED1/ | ||
+ | | 26 | 91 | RE00 | EBID0/ | ||
+ | | 27 | 94 | RE01 | EBID1/ | ||
+ | | 28 | 98 | RE02 | EBID2/ | ||
+ | | 29 | 99 | RE03 | EBID3/ | ||
+ | | 30 | 100 | RE04 | EBID4/ | ||
+ | | 31 | 3 | RE05 | EBID5/ | ||
+ | | 32 | 4 | RE06 | EBID6/ | ||
+ | | 33 | 5 | RE07 | EBID7/ | ||
+ | | 34 | 82 | RD05 | SQICS1/ | ||
+ | | 35 | 6 | RC01 | EBIA6/ | ||
+ | | 36 | 86 | RF01 | EBID10/ | ||
+ | | 37 | 59 | RA02 | EBICS0/ | ||
+ | | 38 | 79 | RD12 | EBID12/ | ||
+ | | 39 | 47 | RD14 | AN32/ | ||
+ | | 40 | 48 | RD15 | AN33/ | ||
+ | | 41 | 28 | RA09 | VREF-/ | ||
+ | | 42 | 29 | RA10 | VREF+/ | ||
+ | | 43 | 81 | RD04 | SQICS0/ | ||
+ | | 44 | 35 | RB11 | AN6/ | ||
+ | | 45 | 1 | RG15 | AN23/ | ||
+ | | 46 | 2 | RA05 | EBIA5/ | ||
+ | | 47 | 61 | RA04 | EBIA14/ | ||
+ | | 48 | 42 | RB13 | AN8/ | ||
+ | | 49 | 41 | RB12 | EBIA11/ | ||
+ | | 50 | 80 | RD13 | EBID13/ | ||
+ | | 51 | 43 | RB14 | EBIA1/ | ||
+ | | 52 | 8 | RC03 | EBIWE/ | ||
+ | | 53 | 34 | RB10 | EBIA13/ | ||
+ | | 54 | 9 | RC04 | EBIOE/ | ||
+ | | 55 | 69 | RD10 | RPD10/ | ||
+ | | 56 | 68 | RD09 | EBIA15/ | ||
+ | | 57 | 65 | RF05 | EBIA8/ | ||
+ | | 58 | 88 | RG00 | EBID8/ | ||
+ | | 59 | 67 | RA15 | AETXEN/ | ||
+ | | 60 | 87 | RG01 | EBID9/ | ||
+ | | 61 | 64 | RF04 | EBIA9/ | ||
+ | | 62 | 38 | RA01 | TCK/ | ||
+ | | 63 | 17 | RA00 | TMS/ | ||
+ | | 64 | 40 | RF12 | TDO/ | ||
+ | | 65 | 39 | RF13 | TDI/ | ||
+ | | 66 | 89 | RA06 | TRCLK/ | ||
+ | | 67 | 97 | RG13 | TRD0/ | ||
+ | | 68 | 96 | RG12 | TRD1/ | ||
+ | | 69 | 95 | RG14 | TRD2/ | ||
+ | | 70 | 90 | RA07 | TRD3/ | ||
+ | | N/A | 13 | | VSS | POWER | | ||
+ | | N/A | 14 | | VDD | POWER | | ||
+ | | N/A | 15 | | MCLR | MCLR, ICSP | | ||
+ | | N/A | 26 | RB06 | PGEC2/ | ||
+ | | N/A | 27 | RB07 | PGED2/ | ||
+ | | N/A | 30 | | AVDD | POWER | | ||
+ | | N/A | 31 | | AVSS | POWER | | ||
+ | | N/A | 36 | | VSS | POWER | | ||
+ | | N/A | 37 | | VDD | POWER | | ||
+ | | N/A | 45 | | VSS | POWER | | ||
+ | | N/A | 46 | | VDD | POWER | | ||
+ | | N/A | 49 | RC12 | OSCI/ | ||
+ | | N/A | 50 | RC15 | OSCO/ | ||
+ | | N/A | 51 | | VBUS | POWER | | ||
+ | | N/A | 52 | | VUSB3V3 | ||
+ | | N/A | 53 | | VSS | POWER | | ||
+ | | N/A | 54 | | D- | PIC32_USBD- | ||
+ | | N/A | 55 | | D+ | PIC32_USBD+ | ||
+ | | N/A | 56 | RF03 | USBID/ | ||
+ | | N/A | 62 | | VDD | POWER | | ||
+ | | N/A | 63 | | VSS | POWER | | ||
+ | | N/A | 72 | RC13 | SOSCI/ | ||
+ | | N/A | 73 | RC14 | SOSCO/ | ||
+ | | N/A | 74 | | VDD | POWER | | ||
+ | | N/A | 75 | | VSS | POWER | | ||
+ | | N/A | 83 | | VDD | POWER | | ||
+ | | N/A | 84 | | VSS | POWER | | ||
+ | | N/A | 92 | | VSS | POWER | | ||
+ | | N/A | 93 | | VDD | POWER | | ||
+ | ==== 13.2: Pinout Table by MCU Pin and Port Bit Numbers ==== | ||
+ | ^ Port Bit ^ Digilent Pin # ^ MCU Pin ^ PIC32 Signal Name ^ Function | ||
+ | | RA00 | 63 | 17 | TMS/ | ||
+ | | RA01 | 62 | 38 | TCK/ | ||
+ | | RA02 | 37 | 59 | EBICS0/ | ||
+ | | RA03 | 4 | 60 | EBIRDY1/ | ||
+ | | RA04 | 47 | 61 | EBIA14/ | ||
+ | | RA05 | 46 | 2 | EBIA5/ | ||
+ | | RA06 | 66 | 89 | TRCLK/ | ||
+ | | RA07 | 70 | 90 | TRD3/ | ||
+ | | RA09 | 41 | 28 | VREF-/ | ||
+ | | RA10 | 42 | 29 | VREF+/ | ||
+ | | RA14 | 8 | 66 | AETXCLK/ | ||
+ | | RA15 | 59 | 67 | AETXEN/ | ||
+ | | RB00 | 25 | 25 | PGED1/ | ||
+ | | RB01 | 23 | 24 | PGEC1/ | ||
+ | | RB02 | 21 | 23 | AN2/ | ||
+ | | RB03 | 20 | 22 | AN3/ | ||
+ | | RB04 | 22 | 21 | AN4/ | ||
+ | | RB05 | 14 | 20 | AN45/ | ||
+ | | RB06 | N/A | 26 | PGEC2/ | ||
+ | | RB07 | N/A | 27 | PGED2/ | ||
+ | | RB08 | 24 | 32 | EBIA10/ | ||
+ | | RB09 | 15 | 33 | EBIA7/ | ||
+ | | RB10 | 53 | 34 | EBIA13/ | ||
+ | | RB11 | 44 | 35 | AN6/ | ||
+ | | RB12 | 49 | 41 | EBIA11/ | ||
+ | | RB13 | 48 | 42 | AN8/ | ||
+ | | RB14 | 51 | 43 | EBIA1/ | ||
+ | | RB15 | 17 | 44 | EBIA0/ | ||
+ | | RC01 | 35 | 6 | EBIA6/ | ||
+ | | RC02 | 16 | 7 | EBIA12/ | ||
+ | | RC03 | 52 | 8 | EBIWE/ | ||
+ | | RC04 | 54 | 9 | EBIOE/ | ||
+ | | RC12 | N/A | 49 | OSCI/ | ||
+ | | RC13 | N/A | 72 | SOSCI/ | ||
+ | | RC14 | N/A | 73 | SOSCO/ | ||
+ | | RC15 | N/A | 50 | OSCO/ | ||
+ | | RD00 | 3 | 71 | EMDIO/ | ||
+ | | RD01 | 5 | 76 | RPD1/ | ||
+ | | RD02 | 6 | 77 | EBID14/ | ||
+ | | RD03 | 9 | 78 | EBID15/ | ||
+ | | RD04 | 43 | 81 | SQICS0/ | ||
+ | | RD05 | 34 | 82 | SQICS1/ | ||
+ | | RD09 | 56 | 68 | EBIA15/ | ||
+ | | RD10 | 55 | 69 | RPD10/ | ||
+ | | RD11 | 11 | 70 | EMDC/ | ||
+ | | RD12 | 38 | 79 | EBID12/ | ||
+ | | RD13 | 50 | 80 | EBID13/ | ||
+ | | RD14 | 39 | 47 | AN32/ | ||
+ | | RD15 | 40 | 48 | AN33/ | ||
+ | | RE00 | 26 | 91 | EBID0/ | ||
+ | | RE01 | 27 | 94 | EBID1/ | ||
+ | | RE02 | 28 | 98 | EBID2/ | ||
+ | | RE03 | 29 | 99 | EBID3/ | ||
+ | | RE04 | 30 | 100 | EBID4/ | ||
+ | | RE05 | 31 | 3 | EBID5/ | ||
+ | | RE06 | 32 | 4 | EBID6/ | ||
+ | | RE07 | 33 | 5 | EBID7/ | ||
+ | | RE08 | 2 | 18 | AN25/ | ||
+ | | RE09 | 7 | 19 | AN26/ | ||
+ | | RF00 | 12 | 85 | EBID11/ | ||
+ | | RF01 | 36 | 86 | EBID10/ | ||
+ | | RF02 | 0 | 57 | EBIRDY3/ | ||
+ | | RF03 | N/A | 56 | USBID/ | ||
+ | | RF04 | 61 | 64 | EBIA9/ | ||
+ | | RF05 | 57 | 65 | EBIA8/ | ||
+ | | RF08 | 1 | 58 | EBIRDY2/ | ||
+ | | RF12 | 64 | 40 | TDO/ | ||
+ | | RF13 | 65 | 39 | TDI/ | ||
+ | | RG00 | 58 | 88 | EBID8/ | ||
+ | | RG01 | 60 | 87 | EBID9/ | ||
+ | | RG06 | 13 | 10 | AN14/ | ||
+ | | RG07 | 18 | 11 | EBIA4/ | ||
+ | | RG08 | 19 | 12 | EBIA3/ | ||
+ | | RG09 | 10 | 16 | EBIA2/ | ||
+ | | RG12 | 68 | 96 | TRD1/ | ||
+ | | RG13 | 67 | 97 | TRD0/ | ||
+ | | RG14 | 69 | 95 | TRD2/ | ||
+ | | RG15 | 45 | 1 | AN23/ | ||
+ | | | N/A | 13 | VSS | POWER | | ||
+ | | | N/A | 14 | VDD | POWER | | ||
+ | | | N/A | 15 | MCLR | MCLR, ICSP | | ||
+ | | | N/A | 30 | AVDD | POWER | | ||
+ | | | N/A | 31 | AVSS | POWER | | ||
+ | | | N/A | 36 | VSS | POWER | | ||
+ | | | N/A | 37 | VDD | POWER | | ||
+ | | | N/A | 45 | VSS | POWER | | ||
+ | | | N/A | 46 | VDD | POWER | | ||
+ | | | N/A | 51 | VBUS | POWER | | ||
+ | | | N/A | 52 | VUSB3V3 | ||
+ | | | N/A | 53 | VSS | POWER | | ||
+ | | | N/A | 54 | D- | PIC32_USBD- | ||
+ | | | N/A | 55 | D+ | PIC32_USBD+ | ||
+ | | | N/A | 62 | VDD | POWER | | ||
+ | | | N/A | 63 | VSS | POWER | | ||
+ | | | N/A | 74 | VDD | POWER | | ||
+ | | | N/A | 75 | VSS | POWER | | ||
+ | | | N/A | 83 | VDD | POWER | | ||
+ | | | N/A | 84 | VSS | POWER | | ||
+ | | | N/A | 92 | VSS | POWER | | ||
+ | | | N/A | 93 | VDD | POWER | | ||
+ | ==== 13.3: Pinout Table by PIC32 Microcontroller Pin ==== | ||
+ | ^ MCU Pin ^ Port Bit ^ Digilent Pin # ^ PIC32 Signal Name ^ Function | ||
+ | | 1 | RG15 | 45 | AN23/ | ||
+ | | 2 | RA05 | 46 | EBIA5/ | ||
+ | | 3 | RE05 | 31 | EBID5/ | ||
+ | | 4 | RE06 | 32 | EBID6/ | ||
+ | | 5 | RE07 | 33 | EBID7/ | ||
+ | | 6 | RC01 | 35 | EBIA6/ | ||
+ | | 7 | RC02 | 16 | EBIA12/ | ||
+ | | 8 | RC03 | 52 | EBIWE/ | ||
+ | | 9 | RC04 | 54 | EBIOE/ | ||
+ | | 10 | ||
+ | | 11 | ||
+ | | 12 | ||
+ | | 13 | ||
+ | | 14 | ||
+ | | 15 | ||
+ | | 16 | ||
+ | | 17 | ||
+ | | 18 | ||
+ | | 19 | ||
+ | | 20 | ||
+ | | 21 | ||
+ | | 22 | ||
+ | | 23 | ||
+ | | 24 | ||
+ | | 25 | ||
+ | | 26 | ||
+ | | 27 | ||
+ | | 28 | ||
+ | | 29 | ||
+ | | 30 | ||
+ | | 31 | ||
+ | | 32 | ||
+ | | 33 | ||
+ | | 34 | ||
+ | | 35 | ||
+ | | 36 | ||
+ | | 37 | ||
+ | | 38 | ||
+ | | 39 | ||
+ | | 40 | ||
+ | | 41 | ||
+ | | 42 | ||
+ | | 43 | ||
+ | | 44 | ||
+ | | 45 | ||
+ | | 46 | ||
+ | | 47 | ||
+ | | 48 | ||
+ | | 49 | ||
+ | | 50 | ||
+ | | 51 | ||
+ | | 52 | ||
+ | | 53 | ||
+ | | 54 | ||
+ | | 55 | ||
+ | | 56 | ||
+ | | 57 | ||
+ | | 58 | ||
+ | | 59 | ||
+ | | 60 | ||
+ | | 61 | ||
+ | | 62 | ||
+ | | 63 | ||
+ | | 64 | ||
+ | | 65 | ||
+ | | 66 | ||
+ | | 67 | ||
+ | | 68 | ||
+ | | 69 | ||
+ | | 70 | ||
+ | | 71 | ||
+ | | 72 | ||
+ | | 73 | ||
+ | | 74 | ||
+ | | 75 | ||
+ | | 76 | ||
+ | | 77 | ||
+ | | 78 | ||
+ | | 79 | ||
+ | | 80 | ||
+ | | 81 | ||
+ | | 82 | ||
+ | | 83 | ||
+ | | 84 | ||
+ | | 85 | ||
+ | | 86 | ||
+ | | 87 | ||
+ | | 88 | ||
+ | | 89 | ||
+ | | 90 | ||
+ | | 91 | ||
+ | | 92 | ||
+ | | 93 | ||
+ | | 94 | ||
+ | | 95 | ||
+ | | 96 | ||
+ | | 97 | ||
+ | | 98 | ||
+ | | 99 | ||
+ | | 100 | RE04 | 30 | EBID4/ |