On Tue, Jun 23, 2009 at 10:51 AM, Xiaofan Chen wrote:
> I see. Thanks for the reply. Which JTAG debugger are you using?
> Do you have "lsusb -vvv" output from that?
>
> In the JTAGkey case, it seems to have two JTAG channels and one
> serial port. And it seems to have only two interfaces in the USB
On Tue, Jun 23, 2009 at 10:45 AM, Alain Mouette wrote:
>
> Xiaofan Chen escreveu:
>>
>> Can you use usb serial port if you use Linux? If not, maybe the
>> FTDI driver has some extra ways to make the com port.
>
> Yes, it works great :)
>
> there is only a small glitch that when you restart OpenOCD,
On Mon, Jun 22, 2009 at 11:55 PM, Gene Smith wrote:
>> Have you tried the following method?
>>
>> Run cmd.exe as admin (under Vista) and
>> D:\libusb-win32-device-bin-0.1.12.1\bin>c:\windows\sys tem32\rundll32
>> libusb0.dll,usb_install_driver_np_rundll olimex.inf
>>
>
> Unfortunately, at least on
On Mon, Jun 22, 2009 at 11:16 PM, Gene Smith wrote:
> Xiaofan Chen wrote:
>>
>> No. By using libusb-win32 device driver as the driver for
>> the Olimex device instead of FTDI driver, you will lost the
>> serial port.
>
> Maybe I was not understanding. I think you are really saying that there
> is *
Xiaofan Chen wrote:
>
> Have you tried the following method?
>
> Run cmd.exe as admin (under Vista) and
> D:\libusb-win32-device-bin-0.1.12.1\bin>c:\windows\sys tem32\rundll32
> libusb0.dll,usb_install_driver_np_rundll olimex.inf
>
Unfortunately, at least on my XP setup, this does not survive a
Xiaofan Chen wrote:
>
> No. By using libusb-win32 device driver as the driver for
> the Olimex device instead of FTDI driver, you will lost the
> serial port.
Maybe I was not understanding. I think you are really saying that there
is *no way* to have the serial port *and* the jtag running togeth
On Fri, Jun 19, 2009 at 6:26 PM, Duane Ellis wrote:
> >> I think we should start to collect the inf files too?
>
> Agree, it would be nice to have a "libusb" - INF file for all ftdi based
> chips that point to libusb :-)
I tend to believe this is possible. Just need to collect the different
VID/
On Sat, Jun 20, 2009 at 12:48 PM, Gene Smith wrote:
> Xiaofan Chen wrote, On 06/19/2009 07:35 PM:
>
>> Glad to hear that OpenOCD works with the libusb-win32/libftdi
>> combination.
>>
>> As for the com port, if it is part of the device, then using libusb-win32
>> device driver (as the driver of the
Xiaofan Chen wrote, On 06/19/2009 07:35 PM:
> Glad to hear that OpenOCD works with the libusb-win32/libftdi
> combination.
>
> As for the com port, if it is part of the device, then using libusb-win32
> device driver (as the driver of the whole USB composite device) will
> disable it. That is the
On Sat, Jun 20, 2009 at 12:29 AM, Gene Smith wrote:
>
> I can switch back and forth between jlink and olimex/ftdi OK in openocd
> and debug wiht insight. They both work OK. However, I don't see a new
> serial port in Dev mgr for the olimex. Where should I see this? I only
> see the built-in COM1 wh
Xiaofan Chen wrote:
> On Fri, Jun 19, 2009 at 11:09 PM, Gene Smith wrote:
>>> That is right. This is an undocumented feature of libusb-win32
>>> that the author of libusb-win32 taught me to use back in 2007.
>>> He is a very nice guy. Unfortunately he seems to be busy lately
>>> so not much progres
On Fri, Jun 19, 2009 at 11:09 PM, Gene Smith wrote:
>> That is right. This is an undocumented feature of libusb-win32
>> that the author of libusb-win32 taught me to use back in 2007.
>> He is a very nice guy. Unfortunately he seems to be busy lately
>> so not much progress in the libusb-win32 fron
Xiaofan Chen wrote:
> On Fri, Jun 19, 2009 at 10:51 PM, Gene Smith wrote:
>>> Have you tried the following method?
>>>
>>> Run cmd.exe as admin (under Vista) and
>>> D:\libusb-win32-device-bin-0.1.12.1\bin>c:\windows\sys tem32\rundll32
>>> libusb0.dll,usb_install_driver_np_rundll olimex.inf
>>>
>>
On Fri, Jun 19, 2009 at 10:51 PM, Gene Smith wrote:
>> Have you tried the following method?
>>
>> Run cmd.exe as admin (under Vista) and
>> D:\libusb-win32-device-bin-0.1.12.1\bin>c:\windows\sys tem32\rundll32
>> libusb0.dll,usb_install_driver_np_rundll olimex.inf
>>
>
> I didn't see this at first
Xiaofan Chen wrote:
> On Fri, Jun 19, 2009 at 10:21 PM, Gene Smith wrote:
>>> Run inf-wizard.exe from libusb-win32-device-bin-0.1.12.1 directory.
>> I see it in the bin dir.
>>
>>> Click "Next"
>>> Click the correct VID/PID: "0x058B 0x002B USB Composite Device"
>>> Click "Next"
>>> Save the inf fil
On Fri, Jun 19, 2009 at 10:21 PM, Gene Smith wrote:
>> Run inf-wizard.exe from libusb-win32-device-bin-0.1.12.1 directory.
>
> I see it in the bin dir.
>
>> Click "Next"
>> Click the correct VID/PID: "0x058B 0x002B USB Composite Device"
>> Click "Next"
>> Save the inf file as "ftdi_libusb.inf" in t
Xiaofan Chen wrote:
> On Fri, Jun 19, 2009 at 5:39 PM, Xiaofan Chen wrote:
>> On Fri, Jun 19, 2009 at 5:35 PM, David Brownell wrote:
For libusb-win32, it is not too bad. You use the INF wizard to create the
INF file and then point to the directory with the inf file.
>>> This requires a lo
On Fri, Jun 19, 2009 at 5:39 PM, Xiaofan Chen wrote:
> On Fri, Jun 19, 2009 at 5:35 PM, David Brownell wrote:
>>> For libusb-win32, it is not too bad. You use the INF wizard to create the
>>> INF file and then point to the directory with the inf file.
>>
>> This requires a lot of Win32 knowledge.
>> I think we should start to collect the inf files too?
Agree, it would be nice to have a "libusb" - INF file for all ftdi based
chips that point to libusb :-)
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.
On Fri, Jun 19, 2009 at 5:35 PM, David Brownell wrote:
>> For libusb-win32, it is not too bad. You use the INF wizard to create the
>> INF file and then point to the directory with the inf file.
>
> This requires a lot of Win32 knowledge. I never even knew
> there *was* such a thing as an INF wiza
On Friday 19 June 2009, Xiaofan Chen wrote:
> On Fri, Jun 19, 2009 at 3:13 PM, David Brownell wrote:
> > On Thursday 18 June 2009, Michael Fischer wrote:
> >> I think we should start to collect the inf files too?
> >
> > In SVN? I'd think so.
> >
> > Along with installation and upgrade instruction
On Fri, Jun 19, 2009 at 4:06 PM, Xiaofan Chen wrote:
> On Fri, Jun 19, 2009 at 3:13 PM, David Brownell wrote:
>> On Thursday 18 June 2009, Michael Fischer wrote:
>>> I think we should start to collect the inf files too?
>>
>> In SVN? I'd think so.
>>
>> Along with installation and upgrade instruct
On Fri, Jun 19, 2009 at 3:13 PM, David Brownell wrote:
> On Thursday 18 June 2009, Michael Fischer wrote:
>> I think we should start to collect the inf files too?
>
> In SVN? I'd think so.
>
> Along with installation and upgrade instructions,
> since that's rarely painless on Windows.
For libusb-
On Thursday 18 June 2009, Michael Fischer wrote:
> I think we should start to collect the inf files too?
In SVN? I'd think so.
Along with installation and upgrade instructions,
since that's rarely painless on Windows.
___
Openocd-development mailing l
24 matches
Mail list logo
