To Chris and Ryan,

I've pored over those pages for awhile as well and, based on that
cursory reading, DGI CMSIS, etc., may be restricted to the pins.

I want to send something over the virtual COM port using some terminal
emulation program, and get some response.

For example, I can connect using "picocom /dev/ttyACM0", but then...
what?  I've tried various things, in vain.  It doesn't act like a
modem, it cannot see the files on the ramdisk, and I don't receive an
OK if I try some of those commands on that eDBG protocol page that
should elicit one.

poop.  This means that debugging must be done using MPLABs virtual
machine :(. I can't even use my pickit3.

On 6/28/18, Chris Roper <caroper@gmail.com> wrote:
> This may help:
>
> Atmel EDBG-based Tools Protocols
> Introduction
> SIDEBAR <https://www.microchip.com/webdoc/protocoldocs/ch01s02.html#> PRE=
V
> <https://www.microchip.com/webdoc/protocoldocs/ch01s01.html> | UP
> <https://www.microchip.com/webdoc/protocoldocs/protocoldocs.Introduction.=
html>
>  | NEXT
> <https://www.microchip.com/webdoc/protocoldocs/protocoldocs.cmsis_dap.htm=
l>
> Atmel EDBG-based tool implementations
>
> The protocol-set described in this document is intended for use on EDBG
> platforms as well as standalone debuggers. The JTAGICE3 firmware version =
3
> upgrades that tool to support SAMD20, and implements parts of the
> protocol-set described here. EDBG implementations are very limited subset=
s
> os this protocol which support the particular Atmel controller mounted on
> that board.
>
> *Table 1. Atmel EDBG-based tool implementations*
> ToolUSB PIDSupportsNotes
> EDBG 0x2111
>
> Only the Atmel device mounted on that board
>
> CDC Virtual COM port and Atmel Data Gateway Interface support varies
> between different kits
>
> As used on Xplained Pro boards
> mEDBG 0x2145
>
> Only the Atmel device mounted on that board
>
> CDC Virtual COM port
>
> As used on Xplained Mini boards
> JTAGICE3 0x2140
>
> Programming of all Atmel AVR devices using SPI, PDI, JTAG and aWire
>
> Debugging of all Atmel AVR devices with on-chip debug capability using
> debugWIRE, PDI, JTAG and aWire
>
> Programming and debugging of all Atmel SAMD, SAM3 and SAM4 devices using
> SWD and JTAG
>
> FW version 3 and later
> Atmel-ICE 0x2141
>
> Programming of all Atmel AVR devices using SPI, TPI, PDI, JTAG and aWire
>
> Debugging of all Atmel AVR devices with on-chip debug capability using
> debugWIRE, PDI, JTAG and aWire
>
> Programming and debugging of all Atmel SAMD, SAM3 and SAM4 devices using
> SWD and JTAG
>
>
> Note that capability of each implementation should be queried from the to=
ol
> itself rather than based upon the lists here.
>
> Future Atmel standalone debuggers will also implement the same CMSIS-DAP
> based protocol as described here.
>
> JTAGICE3 (FW version 2 and earlier) implements a custom USB interface whi=
ch
> is no longer supported.
>
>
> >From Here:
>
> https://www.microchip.com/webdoc/protocoldocs/ch01s02.html
> --
> http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>


--=20
If you're in my band you can't have too much of a sense of dignity. --
"Weird Al" Yankovic
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.