Hello,

this doesn't work for stm8l yet:

2012-02-21T11:37:53 DEBUG src/stlink-common.c: st vid         = 0x0483 (expect 
0x0483)
2012-02-21T11:37:53 DEBUG src/stlink-common.c: stlink pid     = 0x3744
2012-02-21T11:37:53 DEBUG src/stlink-common.c: stlink version = 0x1
2012-02-21T11:37:53 DEBUG src/stlink-common.c: jtag version   = 0x0
2012-02-21T11:37:53 DEBUG src/stlink-common.c: swim version   = 0x3

stlink_usb results in:

libusb_handle_events() | has_error
[!] send_recv
libusb_handle_events() | has_error
[!] send_recv
libusb_handle_events() | has_error
[!] send_recv
libusb_handle_events() | has_error
[!] send_recv
libusb_handle_events() | has_error
[!] send_recv
-- version


Regards,

Mathias

On 21.02.2012 11:10, Uwe Bonnes wrote:
>>>>>> "Szymon" == Szymon Modzelewski <[email protected]> writes:
> 
>     Szymon> Hi all, The current openocd git doesn't have usable stlink-v1
>     Szymon> support.
> 
>     Szymon> Memory writes are completely broken (meaning they don't work at
>     Szymon> all).  The current code tries to issue two SG commands and check
>     Szymon> the status twice, while it should: -send the command -write the
>     Szymon> actual data bytes -check the status
> 
>     Szymon> After reading texane's code it seems to me that all st-link
>     Szymon> commands follow this pattern (although his code doesn't): -send
>     Szymon> the command -optionally send or receive data bytes (depends on
>     Szymon> the command) -read the SG status (v1 only)
> 
> You can also use the V2 code path and prepend the SCSI header to V1 cables,
> as I have implemented in current stlink git. So no more code duplication.
> 
> Bye


------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to