Quick note about usb_blaster_reset: usb_blaster is in much the same situation as ft2232. There are no defined bits for TRST/SRST in the USB Blaster pinout, so each interface-board combination will implement that differently. I'm leaning toward deferring that part until someone actually needs the functionality.
On Sun, Dec 20, 2009 at 4:09 PM, Catalin Patulea <[email protected]> wrote: > Please take another look. > > I have adressed: > - file header documentation > - separate documentation (NEWS, driver commands, examples, etc) > - "static" > ~/src/openocd/src$ !nm > nm -g --defined-only jtag/drivers/usb_blaster.o > 00000000 D _usb_blaster_interface > - formatting (line length, headers) > > Also moved some of the usb_blaster_write/read stuff around a bit to > make it look more like parport and easier to write things like > usb_blaster_blink. > > I'm not sure what to do about usb_blaster_speed. Even if I were to use > sleeps, after passing through the USB stacks, FIFOs, etc, the timing > would be grossly inaccurate. It might still be worth implementing it > that way so people can run their interfaces very slowly (kHz range) > for deep-sleep debugging. > > On Sun, Dec 20, 2009 at 3:13 PM, David Brownell <[email protected]> wrote: >> On Sunday 20 December 2009, Øyvind Harboe wrote: >>> > Agreed. It even fixes a bug: broken USB-Blaster support! :) >>> >>> Uh? Did we have any USB byte blaster support before this patch? >> >> No, and that's the bug. ;) >> >> > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
