首页 > 其他分享 >Jlink V8 Interface Description

Jlink V8 Interface Description

时间:2023-10-23 13:12:10浏览次数:40  
标签:used Description pin Interface connected V8 Link JTAG target

 

JTAG Interface Connection (20 pin)

 

J-Link and J-Trace have a JTAG connector compatible to ARM's Multi-ICE. The JTAG connector is a 20 way Insulation Displacement Connector (IDC) keyed box header (2.54mm male) that mates with IDC sockets mounted on a ribbon cable.

The following table lists the J-Link / J-Trace JTAG pinout:

PinSignalTypeDescription
1 VTref Input This is the target reference voltage.
It is used to check if the target has power, to create the logic-level reference for the input comparators and to control the output logic levels to the target. It is normally fed from Vdd of the target board and must not have a series resistor.
2 Not connected NC This pin is not connected in J-Link.
It is reserved for compatibility with other equipment.
Connect to Vdd or leave open in target system.
3 nTRST Output JTAG Reset.
Output from J-Link to the Reset signal of the target JTAG port. Typically connected to nTRST of the target CPU. This pin is normally pulled HIGH on the target to avoid unintentional resets when there is no connection.
5 TDI Output JTAG data input of target CPU.
It is recommended that this pin is pulled to a defined state on the target board. Typically connected to TDI of target CPU.
7 TMS Output JTAG mode set input of target CPU.
This pin should be pulled up on the target. Typically connected to TMS of target CPU.
9 TCK Output JTAG clock signal to target CPU.
It is recommended that this pin is pulled to a defined state of the target board. Typically connected to TCK of target CPU.
11 RTCK Input Return test clock signal from the target.
Some targets must synchronize the JTAG inputs to internal clocks. To assist in meeting this requirement, you can use a returned, and retimed, TCK to dynamically control the TCK rate. J-Link supports adaptive clocking, which waits for TCK changes to be echoed correctly before making further changes. Connect to RTCK if available, otherwise to GND.
13 TDO Input JTAG data output from target CPU.
Typically connected to TDO of target CPU.
15 nRESET I/O Target CPU reset signal.
Typically connected to the RESET pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". This signal is an active low signal.
17 DBGRQ NC This pin is not connected inside J-Link.
It is reserved for compatibility with other equipment to be used as a debug request signal to the target system. Typically connected to DBGRQ if available, otherwise left open.
19 5V-Supply Output This pin can be used to supply power to the target hardware.

Notes

All pins marked NC are not connected inside J-Link. Any signal can be applied here; J-Link will simply ignore such a signal. Pins 4, 6, 8, 10, 12, 14, 16, 18, 20 are GND pins connected to GND in J-Link. They should also be connected to GND in the target system.

Pin 2 is not connected inside J-Link. A lot of targets have pin 1 and pin 2 connected. Some targets use pin 2 instead of pin 1 to supply VCC. These targets will not work with J-Link, unless Pin 1 and Pin 2 are connected on the target's JTAG connector.

Pin 3 (TRST) should be connected to target CPUs TRST pin (sometimes called NTRST). J-Link will also work if this pin is not connected, but you may experience some limitations when debugging. TRST should be separate from the CPU Reset (pin 15)

Pin 11 (RTCK) should be connected to RTCK if available, otherwise to GND.

Pin 19 (5V-Target supply) of the connector can be used to supply power to the target hardware. Supply voltage is 5V, max. current is 300mA. The output current is monitored and protected against overload and short-circuit.

 

SWD and SWO (also called SWV) Compatibility

SWD Overview

The J-Link and J-Trace support ARMs Serial Wire Debug (SWD). SWD replaces the 5-pin JTAG port with a clock (SWDCLK) and a single bi-directional data pin (SWDIO), providing all the normal JTAG debug and test functionality. SWDIO and SWCLK are overlaid on the TMS and TCK pins. In order to communicate with a SWD device, J-Link sends out data on SWDIO, synchronous to the SWCLK. With every rising edge of SWCLK, one bit of data is transmitted or received on the SWDIO. The data read from SWDIO can than be retrieved from the input buffer.

 

SWD Connector Pinout

The J-Link and J-Trace JTAG connector is also compatible to ARM's Serial Wire Debug (SWD).

The following table lists the J-Link / J-Trace SWD pinout.

PinSignalTypeDescription
1 VTref Input This is the target reference voltage. It is used to check if the target has power, to create the logic-level reference for the input comparators and to control the output logic levels to the target. It is normally fed from Vdd of the target board and must not have a series resistor.
2 Vsupply NC This pin is not connected in J-Link. It is reserved for compatibility with other equipment. Connect to Vdd or leave open in target system.
3 Not used NC This pin is not used by J-Link. If the device may also be accessed via JTAG, this pin may be connected to nTRST, otherwise leave open.
5 Not used NC This pin is not used by J-Link. If the device may also be accessed via JTAG, this pin may be connected to TDI, otherwise leave open.
7 SWDIO I/O Single bi-directional data pin.
9 SWCLK Output Clock signal to target CPU. It is recommended that this pin is pulled to a defined state of the target board. Typically connected to TCK of target CPU.
11 Not used NC This pin is not used by J-Link. This pin is not used by J-Link when operating in SWD mode. If the device may also be accessed via JTAG, this pin may be connected to RTCK, otherwise leave open.
13 SWO Input Serial Wire Output trace port. (Optional, not required for SWD communication.)
15 nRESET I/O Target CPU reset signal. Typically connected to the RESET pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". This signal is an active low signal.
17 Not used NC This pin is not connected in J-Link.
19 5V-Supply Output This pin is used to supply power to some eval boards.

Pins 4, 6, 8, 10, 12, 14, 16, 18, 20 are GND pins connected to GND in J-Link. They should also be connected to GND in the target system.

*On later J-Link products like the J-Link ULTRA+, these pins are reserved for firmware extension purposes. They can be left open or connected to GND in normal debug environment. They are not essential for JTAG/SWD in general.  

Serial Wire Output (SWO) Overview

J-Link can be used with devices that support Serial Wire Output (SWO). Serial Wire Output (SWO) support means support for a single pin output signal from the core.

Serial Wire Viewer (SWV) Overview

The Instrumentation Trace Macrocell (ITM) and Serial Wire Output (SWO) can be used to form a Serial Wire Viewer (SWV). The Serial Wire Viewer provides a low-cost method of obtaining information from inside the MCU. The SWO can output trace data in two output formats, but only one output mechanism may be selected at any time. The 2 defined encodings are UART and Manchester. J-Link expects UART encoding. Serial Wire Viewer uses the SWO pin to transmit different packets for different types of information. The three sources which can output information via this pin are:

  • Instrumentation Trace Macrocell (ITM) for application-driven trace source that supports printf-style debugging. It supports 32 different channels, which allow it to be used for other purposes such as real-time kernel information as well.
  • Data Watchpoint and Trace (DWT) for real-time variable monitoring and PC-sampling, which can in turn be used to periodically output the PC or various CPU-internal counters, which can be used to obtain profiling information from the target.
  • Timestamping. Timestamps are emitted relative to packets.

 

 

标签:used,Description,pin,Interface,connected,V8,Link,JTAG,target
From: https://www.cnblogs.com/zxdplay/p/17782171.html

相关文章

  • unity 使用interface 判断 null错误的问题
     在使用Interface,并且由Monobehaviour继承Interface情况下,判断interface的实际UnityEngine.Object是否null,出现错误,没有成功的判断出已经Destroy https://gamedev.stackexchange.com/questions/128971/unity-c-interface-object-never-equals-null解决方案:https://discuss......
  • “SecurityError: Error #2060: 安全沙箱冲突:ExternalInterface 调用者xxx不能访问xx
    今天,我把我的FlashPlayer插件做了一下升级,变为了10.0.42.34的版本。然后发现之前能够在本地正常运行的DVF,今天运行起来却抛出了异常信息。提示信息如下:SecurityError:Error#2060:安全沙箱冲突:ExternalInterface调用者file://D:\study\flex\service\bin\rainbowX.swf......
  • any与interface
    any大法✨前期开发代码量少,快速简单。......
  • CLI(Command Line Interface)简介
    CLI(CommandLineInterface)是一种通过命令行界面与计算机系统进行交互的方式。它提供了一种以文本形式输入命令和接收系统输出的方式,用于执行各种操作和管理计算机系统。以下是CLI的一些特点和常见用途:1.文本界面:CLI基于文本,用户通过键入命令来与计算机系统进行交互。命令通......
  • Course_Description
     CourseTitleBacheloryearCredit2CProgrammingLanguageC 7CourseDescription:课程内容包括:c语言概述,c语言基本数据类型、运算符及表达式,简单程序设计,选择结构程序设计,循环结构程序设计,数组,函数与预处理,指针,结构体、共用体和枚举,文件......
  • 文献阅读-We extend the well-established assumption-based interface of incrementa
      Abstract:Weextendthewell-establishedassumption-basedinterfaceofincrementalSATsolverstoclauses,allowingtheadditionofatemporaryclausethathasthesamelifespanasliteralassumptions.Ourapproachisefficientandeasytoimpleme......
  • 接口interface
    1. 接口的底层结构体iface和eface,区别在于iface描述的接口包含方法,而eface则是不包含任何方法的空接口:interface{}1.1iface源码typeifacestruct{ tab*itab dataunsafe.Pointer}typeitabstruct{ inter*interfacetype _type*_type link*itab hash......
  • 【ARMv8基础篇】CCI-400控制器简介
    CCI(CacheCoherentInterconnect)是ARM中的cache一致性控制器。CCI-400将互连和一致性功能结合到一个模块中。它支持多达两个ACE主节点的连接,例如:Cortex®-A7processorCortex-A15processorCortex-A17processorCortex-A53processorCortex-A57processorCCI-400还支持......
  • How to use Linux shell script to create a command line interactive menu window i
    HowtouseLinuxshellscripttocreateacommandlineinteractivemenuwindowinterfaceAllInOne如何使用Linuxshellscript制作一个命令行交互式菜单窗口界面AllInOneQ:如何实现一个类似raspi-config的交互式命令行菜单功能raspi-configistheRaspberr......
  • Node系列 — v8引擎堆内存详解
    参考:https://juejin.cn/post/6963170647207837710v8的堆内存限制Node程序中javascript的使用内存是有限制的,注意这个内存是指堆内存,在v8中,所有的js对象都存在堆中。在实际应用中不小心触碰到这个边界,进程就会退出。64位系统下为1.4GB,32位系统下为0.7GB。Node是基于v8......