Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| chipkit_wifire:reference_manual_revd [2017/04/05 21:17] – [2Arduino IDE and USB Serial Communications] James Colvin | chipkit_wifire:reference_manual_revd [2022/10/04 11:38] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| This manual applies to [[chipkit_wifire: | This manual applies to [[chipkit_wifire: | ||
| - | |||
| - | FIXME | ||
| =====Production Release===== | =====Production Release===== | ||
| - | The production boards of the Wi-FIRE are manufactured using the Microchip PIC32MZ2048EFG100 MCU. Earlier pre-production, | + | The production boards of the Wi-FIRE are manufactured using the Microchip PIC32MZ2048EFG100 MCU. Earlier pre-production, |
| 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. | 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. | ||
| Line 15: | Line 13: | ||
| ====Overview==== | ====Overview==== | ||
| - | The chipKIT | + | 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/ |
| - | + | ||
| - | + | ||
| - | =====1 Wi-FIRE Hardware Overview===== | + | |
| - | The Wi-FIRE has the following hardware features: | + | |
| {{: | {{: | ||
| Line 38: | Line 32: | ||
| * 0 V to 3.3 V analog input voltage range | * 0 V to 3.3 V analog input voltage range | ||
| * High efficiency, switching 3.3 V power supply providing low power operation | * High efficiency, switching 3.3 V power supply providing low power operation | ||
| + | |||
| + | |||
| + | =====1: | ||
| + | The Wi-FIRE has the following hardware features: | ||
| + | |||
| + | |||
| {{ : | {{ : | ||
| - | ^ Call Out ^ Component Description | + | ^ Call Out ^ Component Description |
| - | | 1 | + | | 1 | IC3- Microchip MRF24WG0MA WiFi Module |
| - | | 2 | + | | 2 | |
| - | | 3 | + | | 3 | JP7- Reset Disable |
| - | | 4 | + | | 4 | |
| - | | 5 | + | | 5 | JP2- Microchip Debug Tool Connector |
| - | | 6 | + | | 6 | J4- I2C Signals |
| - | | 7 | + | | 7 | J5- Digital Signal Connector |
| - | | 8 | + | | 8 | PIC32 Microcontroller |
| - | | 9 | + | | 9 | J6- Digital Signal Connector |
| - | | 10 | + | | 10 |
| - | | 11 | + | | 11 |
| - | | 12 | + | | 12 |
| - | | 13 | + | | 13 |
| - | =====2 Arduino IDE and USB Serial Communications===== | + | =====2: Arduino IDE and USB Serial Communications===== |
| - | The Wi-FIRE board is designed to be used with the Arduino IDE with the Digilent core. FIXME to talk about where to get the Arduino IDE and the installation file for the Digilent Core. | + | The Wi-FIRE board is designed to be used with the Arduino IDE with the Digilent core. Users can learn how to download |
| - | + | ||
| - | the MPIDE development platform was created by modifying | + | |
| The Arduino IDE uses a serial communications port to communicate with a boot loader running on the Wi-FIRE board. The serial port on the Wi-FIRE board is implemented using an FTDI FT232RQ USB serial converter. Before attempting to use the Arduino IDE to communicate with the Wi-FIRE, the appropriate USB device driver must be installed; when you connect the Wi-FIRE on a Windows machine, the appropriate driver should install automatically. | The Arduino IDE uses a serial communications port to communicate with a boot loader running on the Wi-FIRE board. The serial port on the Wi-FIRE board is implemented using an FTDI FT232RQ USB serial converter. Before attempting to use the Arduino IDE to communicate with the Wi-FIRE, the appropriate USB device driver must be installed; when you connect the Wi-FIRE on a Windows machine, the appropriate driver should install automatically. | ||
| Line 76: | Line 74: | ||
| Two red LEDs (LD5 and LD6) will blink when data is being sent or received between the Wi-FIRE and the PC over the serial connection. | Two red LEDs (LD5 and LD6) will blink when data is being sent or received between the Wi-FIRE and the PC over the serial connection. | ||
| - | =====3 Power Supply===== | + | =====3: Power Supply===== |
| The Wi-FIRE is designed to be powered via USB (J16), from an external power supply (J12 or J14), or from the USB OTG receptacle (J10). Jumper block J13 is used to select which power supply is used. The power supply voltage selected by J13 is applied to the unregulated power bus, VU. | The Wi-FIRE is designed to be powered via USB (J16), from an external power supply (J12 or J14), or from the USB OTG receptacle (J10). Jumper block J13 is used to select which power supply is used. The power supply voltage selected by J13 is applied to the unregulated power bus, VU. | ||
| Line 105: | Line 103: | ||
| 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: | 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 J15. To use the on-board 5 V regulator, use the provided shorting blocks to connect VU to LDO In, and to connect LDO Out to 5V0, as follows: | To completely disable operation of the on-board linear regulator, remove all shorting blocks from J15. To use the on-board 5 V regulator, use the provided shorting blocks to connect VU to LDO In, and to connect LDO Out to 5V0, as follows: | ||
| + | {{ : | ||
| 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. | 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 5 V regulator when powering the board from an externally regulator 5 V power supply, such as USB, Use one of the provided shorting blocks to connect VU to 5V0, as follows: | To bypass the on-board 5 V regulator when powering the board from an externally regulator 5 V power supply, such as USB, Use one of the provided shorting blocks to connect VU to 5V0, as follows: | ||
| + | |||
| + | {{ : | ||
| An external 5 V regulator can be used. This would be desirable, for example, when operating from batteries. An external switching mode 5 V 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 5 V 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. | An external 5 V regulator can be used. This would be desirable, for example, when operating from batteries. An external switching mode 5 V 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 5 V 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. | ||
| Line 128: | Line 137: | ||
| | | ||
| - | ===== 4 5 V Compatibility===== | + | ===== 4: 5 V Compatibility===== |
| Line 135: | Line 144: | ||
| 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. | 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 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 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.4 V when sourcing 12 mA of current. When driving a high impedance input (typical of CMOS logic) the output high voltage will be close to 3.3 V. Some 5 V devices will recognize this voltage as a logic high input, and some won’t. Many 5 V logic devices will work reliably with 3.3 V inputs. | The minimum high-voltage output of the PIC32 microcontroller is rated at 2.4 V when sourcing 12 mA of current. When driving a high impedance input (typical of CMOS logic) the output high voltage will be close to 3.3 V. Some 5 V devices will recognize this voltage as a logic high input, and some won’t. Many 5 V logic devices will work reliably with 3.3 V inputs. | ||
| - | =====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 Wi-FIRE 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 15 mA on all digital I/O pins; however, some pins can source or sink 25 mA or even 33 mA, check with the PIC32MZ datasheet for more information. To keep the output voltage within the specified output voltage range (VOL 0.4 V, VOH 2.4 V) the pin current must be restricted to +/-10 mA on the 15 mA pins, or for the higher current pins check the PIC32MZ datasheet for the maximum currents. The maximum current that can be sourced or sunk across all I/O pins simultaneously is +/-150 mA. The maximum voltage that can be applied to any I/O pin is 3.6 V. For more detailed specifications, | + | The Arduino system uses logical pin numbers to identify digital I/O pins on the connectors. The logical pin numbers for the I/O pins on the Wi-FIRE are 0-42. These pin numbers are labeled in the silk screen on the board. Additional pins 43-70 allow access to the on board components such as the uSD, MRF24 WiFi radio, User LEDs / BTNs, and POT. |
| - | + | ||
| - | The chipKIT/Arduino system uses logical pin numbers to identify digital I/O pins on the connectors. The logical pin numbers for the I/O pins on the Wi-FIRE are 0-42. These pin numbers are labeled in the silk screen on the board. Additional pins 43-70 allow access to the on board components such as the uSD, MRF24 WiFi radio, User LEDs / BTNs, and POT. | + | |
| Pins 0-7 and 27-33 are available on header J6 on the outer and inner row of pins, respectively. Pins 8-13 and 34-41 are available on header J5 on the outer and inner row of pins, respectively. Pin 42 is also available on the outer pin labeled " | Pins 0-7 and 27-33 are available on header J6 on the outer and inner row of pins, respectively. Pins 8-13 and 34-41 are available on header J5 on the outer and inner row of pins, respectively. Pin 42 is also available on the outer pin labeled " | ||
| Line 155: | Line 163: | ||
| - | =====6 802.11b/ | + | =====6: 802.11b/g Interface===== |
| The 802.11b/g compatible WiFi interface on the Wi-FIRE is provided by a Microchip MRF24WG0MA WiFi module. This module provides the radio transceiver, | The 802.11b/g compatible WiFi interface on the Wi-FIRE is provided by a Microchip MRF24WG0MA WiFi module. This module provides the radio transceiver, | ||
| Line 170: | Line 178: | ||
| - | =====7 Network Library Software===== | + | =====7: Network Library Software===== |
| - | The WiFi module on the Wi-FIRE is intended for use with the Digilent Embedded | + | The WiFi module on the Wi-FIRE is intended for use with the Digilent Embedded network libraries, DEIPcK and DEWFcK. The DEIPcK library provides TCP/UDP/IP protocol support for all compatible network interfaces supported by Digilent products, including the Wi-FIRE. The DEWFcK library provides the additional library support required for connecting to and operating with the Microchip MRF24WG0MA wireless network modules. Caution should be used in understanding that the DEIPcK library is different than the DNETcK network libraries. DEIPcK is the Digilent Embedded Open Source IP stack that supports both the MX and MZ processor lines, while the DNETcK IP stack is built on top of the Microchip MLA proprietary stack and only supports the MX processor line, and will not work with the Wi-FIRE. |
| 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: | 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: | ||
| Line 179: | Line 187: | ||
| #include < | #include < | ||
| - | The Digilent Embedded | + | The Digilent Embedded network libraries are available as part of the Digilent core (Arduino IDE) download at our [[learn/software/tutorials/digilent-core-install/ |
| There are reference examples demonstrating the use of these libraries as part of the examples code downloaded with the Digilent core (Arduino IDE). | There are reference examples demonstrating the use of these libraries as part of the examples code downloaded with the Digilent core (Arduino IDE). | ||
| - | =====8 USB Interface===== | + | =====8: USB Interface===== |
| Line 220: | Line 228: | ||
| 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). | 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 JP5 shorted, | + | With JP5 shorted, |
| When using the Wi-FIRE outside the Arduino IDE environment, | When using the Wi-FIRE outside the Arduino IDE environment, | ||
| - | =====9 SD Card Interface===== | + | =====9: SD Card Interface===== |
| Line 235: | Line 243: | ||
| - | =====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 Wi-FIRE board provides a number of peripheral functions. The provided peripherals are explained in the following sections. | ||
| - | + | ====10.1: UART Ports==== | |
| - | =====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 J6 and are also connected to the FT232RQ USB serial converter. It is possible to use these pins to connect to an external serial device when not using the FT232RQ USB serial interface. This uses UART4 (U4RX, U4TX) on the PIC32 microcontroller. | 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 J6 and are also connected to the FT232RQ USB serial converter. It is possible to use these pins to connect to an external serial device when not using the FT232RQ USB serial interface. This uses UART4 (U4RX, U4TX) on the PIC32 microcontroller. | ||
| Line 249: | Line 254: | ||
| - | =====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 J5. Be aware that pin 13 (SCK) is shared with USER LED1, and that both LED1 and the SPI port cannot be used concurrently. | 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 J5. Be aware that pin 13 (SCK) is shared with USER LED1, and that both LED1 and the SPI port cannot be used concurrently. | ||
| Line 255: | Line 260: | ||
| **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 J4. | 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 J4. | ||
| Line 263: | Line 266: | ||
| 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 282: | 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==== |
| Line 293: | Line 292: | ||
| - | =====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 10 kΩ 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==== |
| Line 305: | Line 304: | ||
| - | =====10.12 | + | ====10.11: |
| Line 314: | Line 313: | ||
| - | =====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 is reset by bringing its MCLR pin low. The MCLR pin is connected to the RST pin, as presented on J1. | ||
| Line 327: | Line 325: | ||
| 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 J1. This causes the processor to be reset each time an attempt is made to access the SPI port. Jumper JP3 can be used to break the connection between J8 pin 5 and reset when using Arduino shields that make this connection. JP3 has a cuttable trace on the top of the board that can be cut to break the connection between SPI SS and reset. JP3 is not loaded at the factory. To restore the connection, solder a two pin header at the JP3 position and install a shorting block. | + | Some Arduino shields, most notably the Ethernet shield, connect pin 5 on J8 to the reset net on pin 3 of connector J1. This causes the processor to be reset each time an attempt is made to access the SPI port. Jumper JP3 can be used to break the connection between J8 pin 5 and reset when using Arduino shields that make this connection. JP3 has a cuttable trace on the top of the board that can be cut to break the connection between SPI SS and reset. JP3 is not loaded at the factory. To restore the connection, solder a two pin header at the JP3 position and install a shorting block. |
| 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: Microchip Development Tool Compatibility===== | |
| - | + | ||
| - | =====11 Microchip Development Tool Compatibility===== | + | |
| 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. | 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. | ||
| Line 351: | Line 346: | ||
| - | =====12 Pinout Tables===== | + | =====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. | 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 | + | In the following tables, columns labeled |
| + | ==== 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 | | ||
| - | ====12.1 Pinout Table by Digital | + | ==== 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 ==== |
| - | | | + | ^ |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | 3 |
| - | | | + | | |
| - | | | + | | 5 |
| - | | | + | | |
| - | | | + | | 7 |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | 16 |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | 24 |
| - | | | + | | |
| - | | | + | | 26 | |
| - | | | + | | 27 |
| - | | | + | | |
| - | | | + | | 29 | |
| - | | | + | | 30 |
| - | | | + | | 31 |
| - | | | + | | 32 |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | 38 |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | 50 |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | 53 |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | 56 |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | 59 |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | 64 |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| - | | | + | | |
| + | | | ||
| + | | | ||
| + | | | ||
| + | | 74 | ||
| + | | 75 | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | 84 | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | 92 | ||
| + | | 93 | ||
| + | | | ||
| + | | 95 | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | | | ||