On 15 January 2013 17:17, Tomek CEDRO <[email protected]> wrote:
> Hello Spen :-)
>
> On Tue, Jan 15, 2013 at 5:45 PM, Spencer Oliver <[email protected]> wrote:
>> I have been testing the current swd patches in gerrit and feel this is
>> the better place at the moment to discuss issues until we are further
>> along with the patches.
>
> Yes this is more convenient :-)
>
>> The following adapters have been tested with the same issues.
>> luminary_icdi and JTAGkey2 with ARM-JTAG-SWD adapter
>>
>> 1. how to reset using srst.
>
> Current RESET implementation is tied to JTAG it needs to be redefined
> and this is the first on my list with internals redesign, I have made
> some tests already and it can work on INTERFACE level...
>
> At the momen you can use INTERFACE BITBANG functionality - that allows
> to read and write designated port pin _mask_. Therefore you only need
> to define SRST with "interface_signal srst mask" and then use it with
> "interface_bitbang srst=hi/lo"...
>
> I want to move these commands into interface subcommands, but this
> requires internals redesign :-)
>
>
>> 2. resume not working.
>
> Did not test debugging yet as the speed was too slow. When the changes
> are there I want to see the new mpsse interface and write TRANSFER and
> BITBANG methods to be able to work with LibSWD - this could
> dramaticaly improve the speed and the debug process will be possible
> more conveniently :-)
>

As Freddie pointed out a poll is required, so this suggests the
handle_target is not working as it should.

>
>> 3. cannot reconnect unless target is power cycled.
>
> Yes I have noted that too. Maybe hardware reset is necessary.
> According to ARM specification DAP RESET sequence should reset it into
> initial state, but it does not work that way :-( Maybe someone with
> more experience can have an idea on how to overcome this :-)
>
>
>> 4. hla adapters (stlink and ti-icdi) do not work
>
> This is good time Spen that we can cooperate :-) I have introduced
> "Interface Features" that implement Transport for a given interface.
> If interface is a generic one and provide Transfer and Bitbang methods
> it can use generic transport drivers (such as LibSWD). But this is
> also perfect match for HLA - your interface should define its own
> feature set that can handle DAP operations on its own, so it does not
> use generic LibSWD, but gets commands directly into the firmware and
> returns the result. The outcome of this is the dramatically improved
> preformance for HLA and still the possibility to use different
> transports with a generic interfaces :-)
>

The hla adapters (currently stlink and ti_icdi behave at a much higher
layer, eg resume/stop.
>From the OpenOCD point of view they are more like targets.

>> One tweak i have made is that all my adapters tested use the inverse
>> "RnW" logic, so i think we need to add support for this.
>
> I think I have forseen that - please try "nRnW" signal name, it should
> work together with "RnW" signal - this is the pair for driving the
> output buffers on a direction change :-)
>

I have looked in the src and cannot see anything that implements this
- can you double check ?
The swd support still needs a lot of work/cleanup before it can be
merged into master.

Cheers
Spen

------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612 
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to