On Tue, Jun 15, 2010 at 10:22 PM, Xiaofan Chen <[email protected]> wrote:
> On Tue, Jun 15, 2010 at 10:07 PM, Stacey Sheldon <[email protected]>
> wrote:
>> Once the contents of dirname and filename are known on other platforms,
>> it may be possible to make the config spec more user friendly. That
>> could be enhanced in a future commit.
>>
>
> The following are the typical output from libusb-win32 (from
> testlibusb-win.exe).
> Code:
> edit_printf("bus/device idVendor/idProduct\r\n");
> edit_printf("%s/%s %04X/%04X\r\n", bus->dirname, dev->filename,
> dev->descriptor.idVendor, dev->descriptor.idProduct);
>
> Output:
> bus/device idVendor/idProduct
> bus-0/\\.\libusb0-0001--0x058f-0x9360 058F/9360
>
> bus-0/\\.\libusb0-0003--0x0403-0xbcd9 0403/BCD9
>
> bus-0/\\.\libusb0-0007--0x04d8-0x000c 04D8/000C
>
In the future, if libusb-1.0 Windows (and libftdi-1.0) is used
with OpenOCD, then the output is something like this.
Code:
printf("%04x:%04x (bus %d, device %d)\n",
desc.idVendor, desc.idProduct,
libusb_get_bus_number(dev), libusb_get_device_address(dev));
Output:
$ ./lsusb.exe
1d6b:0002 (bus 0, device 255)
04b4:8613 (bus 0, device 1)
1d6b:0001 (bus 1, device 255)
058f:9360 (bus 1, device 1)
046d:c054 (bus 1, device 2)
0403:bcd9 (bus 1, device 3)
04d8:000c (bus 1, device 4)
--
Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
