On Friday 12 March 2010, simon qian wrote:
> Sounds wonderful. :-)
I was hoping you'd like it ... I know you'd like to be able to
use more Versaloon capabilities through OpenOCD.
> Note that SRST isn't ONLY used in JTAG or SWD, AVR_ISP
> will also need control over SRST line, many other MCUs ma
On Friday 12 March 2010, David Brownell wrote:
> > How about make SRST a "transport"
If there were public specifications for Atmel's DebugWire
(which as I'm sure you know modulates SRST to achieve
another low-pincount equivalent of JTAG-for-debugging)
that would make sense as a transport.
... oth
Sounds wonderful. :-)
Note that SRST isn't ONLY used in JTAG or SWD, AVR_ISP
will also need control over SRST line, many other MCUs may
need it too, because it's basic signal in MCUs.
How about make SRST a "transport" and can generate a
reset event. Then, Cortex-M3 target will need JTAG+SRST
or SW
On Wednesday 03 March 2010, David Brownell wrote:
> Meanwhile, I'll draft something on transport modes (as they
> apply to "debug adapters" and targets. While the initial
> focus will of course be JTAG vs SWD, I'll keep in mind that
> others might come along (especially for "program" mode).
OK,
On Thursday 04 March 2010, CeDeROM wrote:
> > And For AVR ISP, SPI "interface" support will be needed.
> > So this is the framework for managing all these "interfaces".
>
> Oh yes, SPI interface would be very helpful also for FPGA devices
AND various Cortex-M3 devices too ... :)
THough it's wort
On Thu, Mar 4, 2010 at 7:10 PM, wrote:
> What I mean "interface" is not debug adaptors, and program_mode may be
> debug_mode in OpenOCD.
> Vsprog support program only, so I use program_mode.
> For Cortex-M3, there shoudl be JTAG and SWD debug mode, so it need JTAG and
> SWD "interfaces".
> And Fo
What I mean "interface" is not debug adaptors, and program_mode may be
debug_mode in OpenOCD.
Vsprog support program only, so I use program_mode.
For Cortex-M3, there shoudl be JTAG and SWD debug mode, so it need JTAG and
SWD "interfaces".
And For AVR ISP, SPI "interface" support will be needed.
So
On Wednesday 03 March 2010, simon qian wrote:
> What I mean "interface" is not debug adaptors,
Good. I suspected that. :)
Let's call this notion a "transport", then ... to avoid
introducing any more confusion.
Not that "interface" was a good word to use for "debug
adapters" (or for anything at
On Tuesday 02 March 2010, simon qian wrote:
> I think it's the time to implement this feature.
Depends what you mean by $SUBJECT, or "interface".
I'd tend to think "multi-transport" support would be more important
to have than supporting multiple debug adapters a the same time.
> For STM32 JTAG
I think it's the time to implement this feature.
For STM32 JTAG/SWD support, this feature is MUCH more difficult than the
change in ADIv5 code.
I demonstrate the multi-interface framework in vsprog, which is the
programmer for Versaloon supporting
JTAG/SWD/SPI/UART/USART/IIC/PSoC_ISSP/LPC900_ICP/C
10 matches
Mail list logo
