On Mon, Jul 6, 2009 at 11:29 AM, Gary Carlson<[email protected]> wrote:
> Based on your most recent information, I am pretty sure this a different
> problem that my patch won't fix.
Yes I agree. There are more fundamental problems there.
> I have a sneaking suspicion that you are
> running into some issue with libusb. If you don't have access to a DSO, do
> you have at least a DMM?
Yes I have a multimeter at home.
> If you do, I think there is some value writing a simple test routine in
> jlink_init after the USB handle is available that does the following:
>
> jlink_jtag_handle = jlink_usb_open();
>
> if (jlink_jtag_handle == 0)
> {
> blah...blah...blah...
> }
>
> /* Begin new test stuff here */
>
> while (1)
> {
> jlink_simple_command(EMU_CMD_HW_RESET0);
> sleep(1);
> jlink_simple_command(EMU_CMD_HW_RESET1);
> sleep(1);
> }
>
> You should see the reset line transition on your target once a second from
> high to low on your DMM without skipping a beat. If it does this likely
> will help you rule out libusb.
Good idea. I will probably build libusb by myself. Sometimes distros
are doing funny things.
> As for using USBMon, I can't disagree that it is hard to use and is
> deficient compared to a true hardware protocol analyzer. I wouldn't waste
> my time with that.
USBmon can be very useful. The Linux USB guys can read them, but
not laymen like me. ;-)
--
Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
