On Wed, Sep 23, 2009 at 1:30 AM, michal smulski <michal.smul...@ooma.com> wrote: > > The offending code is called from this function: > static int ft2232_init_ftd2xx(uint16_t vid, uint16_t pid, int more, int* > try_more) > > And the actual function call is here: > status = FT_OpenEx(openex_string, openex_flags, &ftdih);
It's only to be expected that the hardware is in an undetermined state before OpenOCD accesses it + that signals go a bit haywire while the ft2232 is being set up. I don't think there is anything that OpenOCD could or should do with this... -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
