Here is the output for the LPC Link-2 running JLink firmware. Notice that
it has only one configuration, and based on JLink's documentation I expect
they all like that. The endpoints might be different for the very old ones.
Looks like the USB device descriptors can't identify the LPC Link-2
version, however once communication is working there is a command that will
query the version, and it can differentiate the particular JLink model.
I am not 100% certain, but I am pretty sure the serial number 000611000000
might be a constant for the LPC Link-2 firmware though.
Thanks for the discussion guys - this is kind of a tricky problem with all
the configurations.
root@eagle:~# uname -a
Linux eagle 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
root@eagle:~# lsusb -v -d 1366:0101
Bus 002 Device 012: ID 1366:0101 SEGGER J-Link ARM
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1366 SEGGER
idProduct 0x0101 J-Link ARM
bcdDevice 1.00
iManufacturer 1 SEGGER
iProduct 2 J-Link
iSerial 3 000611000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
On Wed, Sep 10, 2014 at 11:57 PM, Paul Fertser <[email protected]> wrote:
> On Thu, Sep 11, 2014 at 10:25:31AM +0400, Paul Fertser wrote:
> > Can someone with original JLink and JLink OB do the same please so
> > we can be sure all of the devices have only one configuration
> > anyway?
>
> Reported by [mbm] on IRC:
>
> JLink v8 (such as
>
> http://www.amazon.com/Jlink-Emulator-Upgrade-Support-Development/dp/B00MVPDNGK
> ),
> probably a clone, single configuration:
>
> Bus 003 Device 002: ID 1366:0101 SEGGER J-Link ARM
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 8
> idVendor 0x1366 SEGGER
> idProduct 0x0101 J-Link ARM
> bcdDevice 1.00
> iManufacturer 1 SEGGER
> iProduct 2 J-Link
> iSerial 3 000089898989
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 32
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0xc0
> Self Powered
> MaxPower 100mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 1
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 1
> Device Status: 0x0001
> Self Powered
>
> --
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:[email protected]
>
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
