Hello,
i think about to reorganize the stlink jtag-swd driver to support the jtag-swd AND swim interface. Both are more or less supported by the stlink/v1/v2. My usb sniffing tests on a v1 device and the available open source stuff give me same taste whats to do. Now the current problem and a solution. The configuration parser and underlaying logic is not able to use a stlink/v2 with a swim interface. It's currently hard coded to jtag-swd. In the interface configuration we can choose usb as stlink_layout. Would it make sense to expand it to support jtag-swd and swim like usb:jtag or usb:swim? So we are able to create a virtual tree that create the correct route from the new high level api-layer to the hardware interface-layer. Anyway, i think it's not a good idea to add some kind of stlink_sublayout command or a layouts named usbjtag/usbswim or something else. What do you think list? PS: the final plan is to add stm8 support to openocd ... Regards, Mathias ------------------------------------------------------------------------------ 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
