In general, there are some limitations when using J-LINK to debug PIC32 under MPLAB X IDE; the recommended approach is to use Microchip's own debugging tools.
The following is an excerpt from the help document regarding J-LINK.
SEGGER J-Link Debug Probes
SEGGER J-Link debug probes bring JTAG development to MPLAB X IDE.
J-Link Debug Probes Supported
The following J-Link probe versions and types have been tested and are supported in MPLAB X IDE:
Version 9 and newer: J-Link BASE
The following J-Link probe versions and types should work in MPLAB X IDE:
Version 9 and newer: J-Link PLUS, J-Link EDU
Version 4 and newer: J-Link ULTRA+, J-Link PRO
To determine your probe version, look at the label on the back side of the probe, which describes the serial number and hardware version.
If you have an older version of J-Link debug probe, SEGGER offers a trade-in program which permits you to upgrade to the latest hardware version. SEGGER provides a discounted rate of the current list cost for the unit being traded in.
Supported Microchip Devices
To see a list of Microchip devices supported by the probe, go to:
http://www.segger.com/jlink_supported_devices.html?m=Microchip
SEGGER J-Link Debug Probes : J-Link Microchip Adapter
J-Link Microchip Adapter
A adapter to use the J-Link probe with Microchip PIC32 devices is provided with a Segger J-Link probe purchased through Microchip. If you already own a supported Segger J-Link probe, you may purchase the adapter separately at:
Adapter configurations are shown in the figures below.
Figure: J-Link Microchip Adapter - 2-Wire JTAG
Figure: J-Link Microchip Adapter - 4-Wire JTAG
Available target interfaces
In general, there are three target interfaces available on PIC32 devices:
1. Debug via traditional 4-wire JTAG (IEEE1149.1)
2. Debug via Microchip proprietary 2-wire JTAG
3. Programming via Microchip proprietary 2-wire JTAG
(1) and (3) are supported by all PIC32 devices. (2) is supported by all later PIC32 devices, but not by some old ones. On such devices, debugging via 4-wire JTAG should be used. The following devices do not support full debugging via 2-wire JTAG:
• PIC32MX320 / 340 / 360 series devices
• PIC32MX420 / 440 / 460 series devices
• PIC32MX534 / 564 / 575 series devices
• PIC32MX664 / 675 / 695 series devices
• PIC32MX775 / 764 / 795 series devices
The J-Link PIC32 Adapter provides connectors for all commonly used headers for PIC32:
• 14-pin 0.1” connector for 4-wire JTAG
• RJ11 connector for 2-wire JTAG
• 6-pin PICkit connector (soldering option)
What is 2-wire JTAG?
2-wire JTAG is a proprietary debug interface defined by Microchip. Based on 4-wire JTAG device internally, using a 2-wire converter that multiplexes the TMS, TDI, TDO JTAG lines to a single data line to the outside and demultiplexes it to the inside. Requires a special conversion unit in the device. On older devices, this conversion unit was only activated in case the device was in the special 2-wire programming mode, but did not allow full debugging using the 2-wire protocol.
Previous article:MPLAB v8.60 Color Settings
Next article:MPLAB X IDE editor red vertical line position movement and Chinese comment under the wavy line removal
- Popular Resources
- Popular amplifiers
- Learn ARM development(16)
- Learn ARM development(17)
- Learn ARM development(18)
- Embedded system debugging simulation tool
- A small question that has been bothering me recently has finally been solved~~
- Learn ARM development (1)
- Learn ARM development (2)
- Learn ARM development (4)
- Learn ARM development (6)
Professor at Beihang University, dedicated to promoting microcontrollers and embedded systems for over 20 years.
- LED chemical incompatibility test to see which chemicals LEDs can be used with
- Application of ARM9 hardware coprocessor on WinCE embedded motherboard
- What are the key points for selecting rotor flowmeter?
- LM317 high power charger circuit
- A brief analysis of Embest's application and development of embedded medical devices
- Single-phase RC protection circuit
- stm32 PVD programmable voltage monitor
- Introduction and measurement of edge trigger and level trigger of 51 single chip microcomputer
- Improved design of Linux system software shell protection technology
- What to do if the ABB robot protection device stops
- CGD and Qorvo to jointly revolutionize motor control solutions
- CGD and Qorvo to jointly revolutionize motor control solutions
- Keysight Technologies FieldFox handheld analyzer with VDI spread spectrum module to achieve millimeter wave analysis function
- Infineon's PASCO2V15 XENSIV PAS CO2 5V Sensor Now Available at Mouser for Accurate CO2 Level Measurement
- Advanced gameplay, Harting takes your PCB board connection to a new level!
- Advanced gameplay, Harting takes your PCB board connection to a new level!
- A new chapter in Great Wall Motors R&D: solid-state battery technology leads the future
- Naxin Micro provides full-scenario GaN driver IC solutions
- Interpreting Huawei’s new solid-state battery patent, will it challenge CATL in 2030?
- Are pure electric/plug-in hybrid vehicles going crazy? A Chinese company has launched the world's first -40℃ dischargeable hybrid battery that is not afraid of cold
- What kind of accomplishment should an embedded hardware engineer have? I want to change jobs
- #TItraininglearningwithcourtesy#Master this little trick? Make your learning more efficient and easier!
- Please advise, how to calculate the switching frequency of MOS tube?
- The god of bad luck possessed me, and I bombed for two days
- DRA7xx Evaluation Module
- The tutorial video does not play. Introducing the Value Line series
- Verilog latch trigger register difference
- After mesh1.0 router joins the network, the coordinator does not respond to the first router request
- Experience in drawing PCB circuit boards
- Understanding CCS Link Command Files (.cmd)