On 7/8/09 8:18 AM, "Spencer Oliver" <[email protected]> wrote:

>> You asked me what the result of Spencer's patch was under Mac
>> OS X.  I tested it against my system this evening and as you
>> will see below, it caused a number of startup faults.  It
>> also appears to make the j-link dongle completely
>> unresponsive thereafter.
>> 
>> I guess the bigger question is this.  Did the Windows version
>> ever suffer from the intermittent startup problem or was this
>> exclusively a problem with Linux/Mac systems?
>> 
>> If Windows doesn't need the usb_reset and doesn't suffer from
>> the intermittent issue, doesn't it make more sense to put a
>> conditional around it that excludes that step for windows
>> rather then forcing the device search again?
>> 
>> 
>> Info : J-Link initialization started / target CPU reset initiated
>> Error: J-Link command 0xde failed (-13)
>> Error: J-Link command 0xdc failed (-13)
>> Error: J-Link command 0x01 failed (-13)
>> Error: J-Link command EMU_CMD_VERSION failed (-13)
>> 
>> Info : J-Link JTAG Interface ready
>> Error: J-Link command 0xdd failed (-13)
>> Error: J-Link command 0xdf failed (-13)
>> Error: J-Link setting speed failed (-13)
>> Error: usb_bulk_write failed (requested=6, result=-13)
>> Error: jlink_tap_execute, wrong result -107 (expected 1)
>> Error: usb_bulk_write failed (requested=6, result=-13)
>> Error: jlink_tap_execute, wrong result -107 (expected 1) .
>> .
>> .
>> 
> 
> Strange, i fail to see why my patch would cause this.
> I have only tested the patch on linux and win32 and it works fine on these.
> 
> All the patch does is re-enumerate after the usb_reset.
> Could you step through and see that a valid handle is returned?
> 
> Cheers
> Spen

Hi Spencer,

The problem for Mac OS X starts when the second usb_open call is made after
re-enumeration.  Based on my testing the second call returns a valid handle.
Unlike the first handle, however, it is a zombie since anything using it
ends up in a permanent black hole.  If I comment out that single line, your
patch works OK.

The problem is I am guessing that statement is critical to Windows operation
or you would not have likely put it in there.

I am trying some other things, to see if I can find a solution that works
across all three platforms.  What a pesky problem.

Gary



Gary Carlson

Gary Carlson, MSEE
Principal Engineer
Carlson-Minot Inc.







_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to