On Tue, Jun 23, 2009 at 3:36 PM, Xiaofan Chen<xiaof...@gmail.com> wrote: > On Tue, Jun 23, 2009 at 1:48 AM, Freddie Chopin<freddie_cho...@op.pl> wrote: >> Xiaofan Chen pisze: >>> >>> In this case, I think you do not need the master entry. Please >>> try it again with the master entry deleted. >> >> The master entry (the one without &MI00 and &MI01) is not necessary. >> >> I attach a changed driver file. > >> [Devices] >> "FTDI FT2232 (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_6001&MI_00 >> "FTDI FT2232 (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_6001&MI_01 >> >> "Amontec JTAGkey (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_00 >> "Amontec JTAGkey (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_01 >> >> "egnite Turtelizer 2 (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_bdc8&MI_00 >> "egnite Turtelizer 2 (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_bdc8&MI_01 >> >> [Devices.NT] >> "FTDI FT2232 (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_6001&MI_00 >> "FTDI FT2232 (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_6001&MI_01 >> >> "Amontec JTAGkey (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_00 >> "Amontec JTAGkey (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_01 >> >> "egnite Turtelizer 2 (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_bdc8&MI_00 >> "egnite Turtelizer 2 (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_bdc8&MI_01 >> > > What if you remove Channel B from the INF file? Will the USB virtual COM port > appear again? Will it affect the JTAG channel A for OpenOCD? > > This will need the SVN version of libusb0.sys according to Freddie. > > I hope this works. Then it can solve the problems of losing the COM port. > Please try it (Michael, Freddie, Gene and others). Thanks. >
>From the EEPROM Configuration of Turtelizer 2, I think the above solution is possible. http://www.ethernut.de/en/hardware/turtelizer/ Channel A is configured as 245 FIFO mode for Jtag. Channel B is configured as RS232 UART for the serial port. Therefore we should only use libusb-win32 for Channel A and use the FTDI driver for Channel B. I can foresee there might be a possible problem of usb_set_configuration. If that is the case, I believe there is a patch for libusb-win32 to address this issue. Hope not. -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
