j-link usage (continuous updates)

---

1. The difference between SWD and JTAG of j-link downloader

2. Matters related to the use of the j-link ob I use: (Note: I only record the j-link ob I use. Due to subsequent version updates, supported kernels may be different)

2-1. Introduction to j-link ob:

It is usually designed on the evaluation boards ("ON-BOARD") of major companies, hence the reason for the suffix "ob"; the
simulation downloader named "ARM-OB" has USB communication and can communicate with the PC, and the other end passes The SWD/JTAG method can communicate with supporting devices to complete the task of simulation download and debugging;
this j-link ob and the original ob debugger lack the JTAG interface and only retain the SWD interface;

2-2. Supported cores supported by j-link ob:

All ARM7/9/11 with SWD interface;
CORTEX-M0/M1/M2/M3/M4/A5/A6/A7/A8/A9, etc.

2-2-1. Support mcu generation

2-2-2. Connection method

2-3. Product features

2-4. Download j-link ob driver and related information

Link: https://pan.baidu.com/s/1bnprRVb8viXmLjc9llYAcQ
Extraction code: 8yev

2-5. Precautions during use:

1. When the target board is powered by USB, do not connect the debugger's vcc, otherwise it may cause the target board or the debugger to burn out.

3. [Problem]: Records of problems that arise during the use of j-link ob

3-1. [Question]: Prompt J-Link Vxxxx Emulatot selection

Problem analysis: When encountering this kind of problem, it is usually because the downloader is not plugged in or the driver is not installed, or JLINK is not used.
Problem solution: After installing the driver j-link ob driver (in the cloud disk download link above), it will be fine.