Re: [OpenOCD-devel] Debug probe hardware that can read/write target memory directly

2017-06-04 Thread Duane Ellis
If I was to re-write a USB protocol for OpenOCD - I would do exactly this. Look very carefully at the SWD commands. The commands are exactly 1 byte + 4 byte read, or 1 byte + 4byte write. The first SWD byte always has bits 7 and 0 set (START + PARK) thus there are really only (256/4)=64 possible

Re: [OpenOCD-devel] Debug probe hardware that can read/write target memory directly

2017-06-04 Thread Fewell, Edward
Thanks for that info. The "box cars" analogy helps with describing the issue. Yes, we are very, very guilty of sending out trains with just 1 box. The direct memory API was essentially a patch to our code base to correct that issue, especially for large memory block transfers. Our current targ

Re: [OpenOCD-devel] Debug probe hardware that can read/write target memory directly

2017-06-04 Thread Duane Ellis
ed>> Keep in mind this is a full speed device, not high speed. Cutting down on the number of USB packets needed does help considerably. Full vrs High speed is not important here. Better: draw a timeline of the USB traffic of actual usb traffic captured on the wire and work on fixing that. I a

Re: [OpenOCD-devel] Debug probe hardware that can read/write target memory directly

2017-06-04 Thread Fewell, Edward
You’re right, I don’t think the XDS110 will qualify as an HLA adapter. It’s only optimization is to read/write memory as block accesses. It has no further knowledge or APIs to do debug on the target. Keep in mind this is a full speed device, not high speed. Cutting down on the number of USB pa