Recent changes to 27: Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-22T22:25:07.933000Z

Ok, I've finished my first attempt at a firmware loader for the hs+. Get it here:

if you try it, let me know how it goes.

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-17T00:32:08.778000Z

Hmm this is not the usual ezusb initialization. It looks straightforward though, I could probably write a little C program and libusb to do the firmware load. What I see in the capture is:

packets 23 and 24:
control read with bRequest 144
response: 0x7618 (little endian) which is the product id the HS+ will have post initialization

packets 25 and 26:
control write with bRequest 145, data is a 4 byte integer which gives the number of 1st stage data bytes which will follow (0x5ea6 or 24230 decimal)

packets 27 to 38:
control writes with bRequest 146 containing the 24230 1st stage data bytes in 4096 byte chunks maximum

packets 39 and 40:
control read with bRequest 147. Reads back zero, so maybe checking for an error?

packets 41 and 42:
control write with bRequest 148 and wValue 0x100. Not sure what this does.

packets 43 and 44:
bulk read of 4 bytes with value 0xc0. Not sure what this means.

packets 45 and 46:
control write with bRequest 160 of 4 bytes with value 0xde12 (56850 decimal). This is the number of 2nd stage data bytes which will follow over the bulk endpoint.

packets 47 and 48:
bulk read of 4 bytes with value 0x2. Not sure what this means.

packets 49 to 52:
bulk writes of 2nd stage firmware data in chunks of maximum size 32768.

packets 53 and 54:
bulk read of 4 bytes with value 0x1. Not sure what this means.

packets 55 and 56:
control write with bRequest 162. This completes the initialization and the adapter reenumerates as a functional HS+

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-16T18:44:22.114000Z

All HS+ do that. It is because the Linux driver was updated to support the HS which doesn't have the analyzer. The HS+ is mostly compatible with the HS but there is some difference which affects the led state. Noone has ever bothered to look into it.

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-16T18:41:14.001000Z

Ah thanks. This looks good, it appears to have the firmware upload. I'll let you know when I have something you can test.

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-16T18:21:33.569000Z

also when connected to windows the hs+ showsamber light. But whenconnected to same raspberrypi(raspbian) it blinks between amber and green. Still the gpib_config command works andlooks like it is up. do you know if this is a matter of concern ?

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-16T18:13:40.393000Z

well then would it be not possible to connect the device to linux for first time ?

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-16T18:09:02.499000Z

Hi frank

I connected a newHS+ device first time to windows and have capturedthe following attached. We can see here that device id changes fro 761e to 7618.

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-16T09:06:04.468000Z

Hello Frank

The lsusb -v gives the following :

Bus 001 Device 004: ID 3923:7618 National Instruments Corp.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x3923 National Instruments Corp.
idProduct 0x7618
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x004c
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 5
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 6
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 100
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 100
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 100
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 100
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 7
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 100
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 4

the device id is changed to 7618.And theadaptor seems to be working with linux even after power on and off.

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-15T15:26:52.874000Z

So after connecting towindows , I disconnected it and connected to raspberry pi (raspbian ) and looks like th edriver is up. this means the firmware was already loaded to it from Windows sidewhen it was connected ?

#27 Problem in bringing up NI GPIB_USB_H+adapator in raspberrypi 3 model b+

2020-04-15T12:45:03.750000Z

Hi Frank

I just captured the belowusing wireshark. Does this help ?