For interface, it just tries all the interface definitions in 
/usr/local/share/openocd/scripts/interface.
Whichever one is detected last is then loaded with an empty scan chain, and it 
should report all the detected TAPs on the chain. Note, that's just the test 
code which tests a wrapper class. Look at the bottom in the "if __name__ == 
'__main__':" section.

> -----Original Message-----
> From: Xiaofan Chen [mailto:[email protected]]
> Sent: Friday, February 19, 2010 1:17 AM
> To: Austin, Alex
> Cc: [email protected]
> Subject: Re: [Openocd-development] OpenOCD auto-config
> 
> On Thu, Feb 18, 2010 at 2:17 PM, Austin, Alex
> <[email protected]> wrote:
> > Just starting to write a wrapper to auto-config openocd. Using
> python,
> > it's a class that attempts to wrap openocd configuration. So far it
> > doesn't do much, but I would appreciate any comments anyone has. Go
> > ahead and run it on your machines (only Linux supported ATM) as it
> > doesn't write to any files except /dev/null.
> 
> What does it do right now? Just finding out the interface? I actually
> have the Luminary EK-LM3S1968 instead of LM3S811.
> 
> [mc...@myfreebsd ~/Downloads]$ pythin openocd.py
> bash: pythin: command not found
> [mc...@myfreebsd ~/Downloads]$ python openocd.py
> Finding interfaces...
> Found dummy
> Found luminary
> Found luminary-lm3s811
> Found jlink
> 
> 
> 
> --
> Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to