From 93f2afa45f4cfcb8afd08dae5a17996dba5c7a9c Mon Sep 17 00:00:00 2001 From: David Brownell Date: Fri, 2 Jul 2010 16:45:28 -0400 Subject: initial "transport" framework This adds the guts of a transport framework with initialization, which should work with current JTAG-only configurations (tested with FT2232). Each debug adapter can declare the transports it supports, and exactly one transport is initialized. (with its commands) in any given OpenOCD session. * Define a new "struct transport with init hooks and a few "transport" subcommands to support it: "list" ... list the transports configured (just "jtag" for now) "select" ... makes the debug session use that transport "init" ... initializes the selected transport (internal) * "interface_transports" ... declares transports the current interface can support. (Some will do this from C code instead, when there are no hardware versioning (or other) issues to prevent it. Plus some FT2232 tweaks, including a few to streamline upcoming support for an SWD transport (initially for Luminary adapters). Eventually src/jtag should probably become src/transport, moving jtag-specific stuff to transport/jtag. Signed-off-by: David Brownell --- NEWS | 3 +++ 1 file changed, 3 insertions(+) (limited to 'NEWS') diff --git a/NEWS b/NEWS index db4485da..2dd14cc6 100644 --- a/NEWS +++ b/NEWS @@ -17,6 +17,9 @@ JTAG Layer: Boundary Scan: +Transport framework core ... supporting future work for SWD, SPI, and other +non-JTAG ways to debug targets or program flash. + Target Layer: ARM: - basic semihosting support (ARMv7M). -- cgit v1.2.3