. We have a custom
implementation of this but are looking to add support to openocd.
Thanks,
Ben
From: Fewell, Edward [mailto:efew...@ti.com]
Sent: 31 May 2017 15:19
To: Steven Stallion
Cc: openocd-devel@lists.sourceforge.net
Subject: Re: [OpenOCD-devel] Debug probe hardware that can read/write
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
ey get the firmware
update. Does that sound reasonable?
Edward
-Original Message-
From: Duane Ellis [mailto:open...@duaneellis.com]
Sent: Sunday, June 04, 2017 11:52 AM
To: Fewell, Edward
Cc: Andreas Fritiofson; openocd-devel@lists.sourceforge.net
Subject: Re: [OpenOCD-devel] Debug probe h
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
...@fritiofson.net [mailto:andr...@fritiofson.net] On Behalf Of
Andreas Fritiofson
Sent: Saturday, June 03, 2017 5:39 PM
To: Fewell, Edward
Cc: openocd-devel@lists.sourceforge.net
Subject: Re: [OpenOCD-devel] Debug probe hardware that can read/write target
memory directly
Hi and thanks for working on
Hi and thanks for working on OpenOCD!
On Wed, May 31, 2017 at 2:59 PM, Fewell, Edward wrote:
> I am currently implementing the Texas Instruments XDS110 debug probe in
> OpenOCD. The firmware of this probe includes APIs to read and write memory
> via the target’s DAP for ARM Cortex based devices.
Check out the HLA (high-level adapter) API--it specifies functions for bulk
memory reads and writes, so it might work for your use case. If you'd like
some examples on how to use it, take a look at the stlink_usb.c and
ti_icdi_usb.c drivers in src/jtag/drivers.
On Wed, May 31, 2017 at 7:59 AM, Few
Hi Edward,
It sounds like you're describing an algorithm (code that is executed on the
target). Is this something that is resident only when firmware is loaded?
Is this something that's baked into every firmware image or is it copied to
RAM during debugging?
Cheers,
Steve
On Wed, May 31, 2017 at
given away for “free” as part of an evaluation board.
Edward
From: Steven Stallion [mailto:stall...@squareup.com]
Sent: Wednesday, May 31, 2017 8:55 AM
To: Fewell, Edward
Cc: openocd-devel@lists.sourceforge.net
Subject: Re: [OpenOCD-devel] Debug probe hardware that can read/write target
memory
I am currently implementing the Texas Instruments XDS110 debug probe in
OpenOCD. The firmware of this probe includes APIs to read and write memory via
the target's DAP for ARM Cortex based devices. The OpenOCD software stack does
not appear to support this and only can execute DAP register trans
10 matches
Mail list logo
