On Wed, Jul 16, 2014 at 9:53 AM, Paul Fertser <[email protected]> wrote:
> On Wed, Jul 16, 2014 at 08:08:31AM -0700, Andrey Smirnov wrote:
>> On Wed, Jul 16, 2014 at 6:04 AM, Paul Fertser <[email protected]> wrote:
>> > On Wed, Jul 16, 2014 at 05:45:29AM -0700, Andrey Smirnov wrote:
> ...
>> >> with Segger J-Link Lite and there were number of patches floating
> ...
>> It wasn't even getting to the point of talking to the HW, so that
>> wouldn't really make a difference. It was failing at getting a
>> response to the very first "get version" USB packet(USB reads were
>> returning 0 bytes). I suspect it is some libusb on OSX related
>> problem, but I need to look more into that.
>
> Hm, that'd be really strange because OpenOCD is using libusb >= 1.0.9
> (IIRC) happily on OS X with stlink, ftdi and the others. I wonder if
> the device might got claimed by some OS X "kext" that needs to be
> unloaded.

I agree, I used OS X to finish development of the F021 driver and the
devkit I used for it comes with FTDI chip, so that worked fine for me.
I need to fire up a Linux setup for this and see if I it a
"nRF51/Segger combo problem" or "OS X problem".

>
> --
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:[email protected]

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to