linux-gpib-general — linux-gpib package mailing list

Re: [Linux-gpib-general] HP 3488A kernel module

[Matthias G. <m_g...@wi...>]

Am 04.08.25 um 13:54 schrieb Wilhelm Kusian:
> Hi Matthias,
>
> I’m not sure whether I understand your issue correctly. The HP3488A is 
> a Switch/Control unit that can be controlled remotely via GPIB. 
> HP82335 is a GPIB ISA interface card for the ISA-bus in old 
> motherboards. The interface card needs a Kernel module, but the 
> HP3488A does not.
>
Ah, I see.
> If you would like to control the HP3488A via GPIB, you can write for 
> instance a python program that sends the comands via the GPIB using 
> linux-gpib. The commands for controlling the HP3488A remotely via GPIB 
> you’ll find in the description for the device, like this 
> https://www.keysight.com/us/en/assets/9018-05356/user-manuals/9018-05356.pdf 
>
>
>
Thanks, already had the datasheet at hand. I was able to get the basic 
communication up and running with the python example from the repo.

Will ask again in case I run into any issues.


best,

Matthias Geiger

Re: [Linux-gpib-general] HP 3488A kernel module

[Wilhelm K. <ku...@t-...>]

Hi Matthias,

I’m not sure whether I understand your issue correctly. The HP3488A is a 
Switch/Control unit that can be controlled remotely via GPIB. HP82335 is 
a GPIB ISA interface card for the ISA-bus in old motherboards. The 
interface card needs a Kernel module, but the HP3488A does not.

If you would like to control the HP3488A via GPIB, you can write for 
instance a python program that sends the comands via the GPIB using 
linux-gpib. The commands for controlling the HP3488A remotely via GPIB 
you’ll find in the description for the device, like this 
https://www.keysight.com/us/en/assets/9018-05356/user-manuals/9018-05356.pdf 


Best regards
Wilhelm

[Linux-gpib-general] HP 3488A kernel module

[Matthias G. <m_g...@wi...>]

Hi all,

I have been tasked with writing a kernel module for the HP 3488A device.

Looking at the source code for the existing HP 82335 module I was 
wondering where I get the constants for the board data from (register 
offsets, io memory regions etc.). The 3488A datasheet does not mention 
any of that.

Can I extract the information via the gpib-config tool ?

I'd be glad for any pointers to get me started to work on it.

I'm using a Pi 4 on Debian bookworm with a GPIB-I2C shield for 
debugging, the device show up as /dev/gpib.

best,

Matthias Geiger

Re: [Linux-gpib-general] libgpib: Permission denied

[David G. <dav...@po...>]

% package require gpib
2.5.0.0
% gpib interface exceptions on
% set osc [gpib open -address 25 -sendeoi true]
16
% gpib write -device $osc -message {INIT;ID?}
% gpib read -device $osc -mode ascii
ID TEK/SG5010,V81.1,F1.1;
%

Complete success!

Re: [Linux-gpib-general] libgpib: Permission denied

[Michael K <vk...@ya...>]

 Hi David,   The makefile that creates the device node (/dev/gpib0) should have created it with a group "gpib" (see linux-gpib-user/drivers/Makefile.am).You should add yourself to the "gpib" group. (see linux-gpib-user/INSTALL)
Michael
    On Sunday, August 3, 2025 at 06:54:07 PM EDT, David Gravereaux <dav...@po...> wrote:  
 
 Hi,

newbie here.  I'm sure this is an RTFM issue.  Please accept my apologies.

OS: Ubuntu 22.04

Linux-GPIB successfully built an installed
gpib-tcl successfully built and installed

$ lspci -ks 05:05.0
05:05.0 Communication controller: National Instruments PCI-GPIB (rev 01)
    Kernel modules: tnt4882

When I run tkcon, load the extension, and do the first open which calls 
ibdev, I get this in stderr:

libgpib: ibBoardOpen failed to open device file /dev/gpib0
libgpib: Permission denied

$ ls -l /dev/gpib0
crw-rw---- 1 root root 160, 0 Aug  3 15:19 /dev/gpib0


The device is owned by root.  I can chown the device, but what is the 
fix so it stays available?
_______________________________________________
Linux-gpib-general mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
  

Re: [Linux-gpib-general] libgpib: Permission denied

[David G. <dav...@po...>]

On 8/3/25 4:35 PM, Michael K wrote:
>   Hi David,   The makefile that creates the device node (/dev/gpib0) should have created it with a group "gpib" (see linux-gpib-user/drivers/Makefile.am).You should add yourself to the "gpib" group. (see linux-gpib-user/INSTALL)
> Michael

Got it, thanks

[Linux-gpib-general] libgpib: Permission denied

[David G. <dav...@po...>]

Hi,

newbie here.  I'm sure this is an RTFM issue.  Please accept my apologies.

OS: Ubuntu 22.04

Linux-GPIB successfully built an installed
gpib-tcl successfully built and installed

$ lspci -ks 05:05.0
05:05.0 Communication controller: National Instruments PCI-GPIB (rev 01)
	Kernel modules: tnt4882

When I run tkcon, load the extension, and do the first open which calls 
ibdev, I get this in stderr:

libgpib: ibBoardOpen failed to open device file /dev/gpib0
libgpib: Permission denied

$ ls -l /dev/gpib0
crw-rw---- 1 root root 160, 0 Aug  3 15:19 /dev/gpib0


The device is owned by root.  I can chown the device, but what is the 
fix so it stays available?

Re: [Linux-gpib-general] Counterfeit NI GPIB-USB-HS half-works?

[Hernán F. <hj...@hj...>]

ALL adapters on eBay are now counterfeit. Genuine ones cost over $1000 so
even used ones go for such prices.

I also bought a, of course fake, Keysight one and it didn't work either.
even the usb ID are wrong

El mié, 16 jul 2025, 18:42, Michael <Mi...@di...p> escribió:

> For the non compatible counterfeit NI GPIB-USB-HS adapters it would be
> nice if the driver detects it and refuses to load with an appropriate error.
> There are a lot of these now on the selling platforms, so I guess there
> will be more and more users that will face this problem and do not know why
> it does not work.
>
> PS:
> Greg Kroah-Hartman notes the GPIB code is about ready to graduate to the
> main area of the Linux kernel.
> https://www.phoronix.com/news/Linux-6.16-Staging
>
> I am thrilled, thanks to all contributors to get GPIB into the Kernel -
> that will help a lot of people!
>
> Best regards, Michael
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Counterfeit NI GPIB-USB-HS half-works?

[Michael <Mi...@Di...>]

For the non compatible counterfeit NI GPIB-USB-HS adapters it would be nice if the driver detects it and refuses to load with an appropriate error.There are a lot of these now on the selling platforms, so I guess there will be more and more users that will face this problem and do not know why it does not work.PS:Greg Kroah-Hartman notes the GPIB code is about ready to graduate to the main area of the Linux kernel.https://www.phoronix.com/news/Linux-6.16-StagingI am thrilled, thanks to all contributors to get GPIB into the Kernel - that will help a lot of people!Best regards, Michael

Re: [Linux-gpib-general] Counterfeit NI GPIB-USB-HS half-works?

[Hernán F. <hj...@hj...>]

Hi Dave
thanks. What exactly is the problem though? I've been going through the
code a bit and patched a couple of error messages, regarding these:
[    5.317767] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
expected 0x2, 0xe, 0xf or 0x16
[    5.318304] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
expected 0x96, 0x07 or 0x6e

I tested the following sequence with ibtest:

board mode, line status:
gpib status is:
ibsta = 0x178  < CMPL REM CIC ATN TACS >

switch to device mode, write *IDN?
fails and dmesg shows:

ni_usb_gpib: Addressing error retval 0 error code=3

go back to board mode in this situation:
gpib status is:
ibsta = 0x120  < CMPL CIC >

which i guess makes sense because Addressing error
is: NIUSB_ADDRESSING_ERROR occurs when you do a board read/write as CIC but
are not in LACS/TACS

why can't this be made to work with linux-gpib though? trying to understand
if I can patch the driver to make it work.



On Thu, Jun 12, 2025 at 9:06 AM dave penkler <dpe...@gm...> wrote:

> Hi Hernán,
> It looks like you have an unsupported clone. This line in the dmesg is
> relevant:
> [    4.830150] usb 1-1.6: config 1 interface 0 altsetting 0 endpoint 0x81
> has an invalid bInterval 0, changing to 7
> Unfortunately this board cannot be made to work with linux-gpib.
> cheers,
> -Dave
>
> On Wed, 11 Jun 2025 at 22:41, Hernán Freschi <hj...@hj...> wrote:
>
>> Hello. I installed the latest version from master (4c820721), but when
>> trying to use it, it half works, and it does a lot of other weird stuff.
>> I'm using a counterfeit GPIB-USB-HS from eBay (I assume it's counterfeit
>> because it costed $70). The device is not detected as counterfeit by NI
>> drivers on Windows, and works fine there. I can communicate with the GPIB
>> device. But not on Linux. I don't get any prompts to update its firmware
>> either.
>> This is dmesg on a fresh boot:
>>
>> $ sudo dmesg|grep gpib
>> [    4.912608] gpib_common: loading out-of-tree module taints kernel.
>> [    4.912658] gpib_common: module verification failed: signature and/or
>> required key missing - tainting kernel
>> [    4.915244] gpib_common: Linux-GPIB 4.3.7 core driver loaded
>> [    4.937190] usb 1-1.6: ni_usb_gpib: probe succeeded for path:
>> usb-0000:00:1a.0-1.6
>> [    4.937228] usbcore: registered new interface driver ni_usb_gpib
>> [    5.317767] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
>> expected 0x2, 0xe, 0xf or 0x16
>> [    5.318304] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
>> expected 0x96, 0x07 or 0x6e
>> [    5.324141] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
>> intf 0
>> [  155.040427] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
>> expected 0x2, 0xe, 0xf or 0x16
>> [  155.040443] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
>> expected 0x96, 0x07 or 0x6e
>> [  155.046186] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
>> intf 0
>> also:[    4.717800] usb 1-1.6: new high-speed USB device number 7 using
>> ehci-pci
>> [    4.830150] usb 1-1.6: config 1 interface 0 altsetting 0 endpoint 0x81
>> has an invalid bInterval 0, changing to 7
>> [    4.830649] usb 1-1.6: New USB device found, idVendor=3923,
>> idProduct=709b, bcdDevice= 1.01
>> [    4.830654] usb 1-1.6: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [    4.830657] usb 1-1.6: Product: GPIB-USB-HS
>> [    4.830659] usb 1-1.6: Manufacturer: National Instruments
>> [    4.830660] usb 1-1.6: SerialNumber: 019A335E
>> [    4.937190] usb 1-1.6: ni_usb_gpib: probe succeeded for path:
>> usb-0000:00:1a.0-1.6
>> [    5.317767] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
>> expected 0x2, 0xe, 0xf or 0x16
>> [    5.318304] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
>> expected 0x96, 0x07 or 0x6e
>> [    5.324141] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
>> intf 0
>> [  155.040427] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
>> expected 0x2, 0xe, 0xf or 0x16
>> [  155.040443] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
>> expected 0x96, 0x07 or 0x6e
>> [  155.046186] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
>> intf 0
>> Here are the issues:
>> 1) It appears my device (HP 34401A) receives the commands, but linux-gpib
>> doesn't get any acknowledgement. The device goes into remote mode if I send
>> *IDN?, but I get an error message
>>
>> : w
>> enter a string to send to your device: *RST
>> sending string: *RST
>>
>> gpib status is:
>> ibsta = 0x8000  < ERR >
>> iberr= 0
>> EDVR 0: OS error
>>
>> ibcntl = 6
>> ..: r
>> enter maximum number of bytes to read [1024]: 199
>> trying to read 199 bytes from device...
>> received string: ''
>> Number of bytes read: 0
>> gpib status is:
>> ibsta = 0xc000  < ERR TIMO >
>> iberr= 6
>> EABO 6: Operation aborted
>>
>> ibcntl = 0
>> this line appears in dmesg:[  164.340630] usb 3-1.6: ni_usb_gpib:
>> Addressing error retval 0 error code=3
>> That's as far as the first issue goes. Then:
>> 2) After some time, it stops working completely. The error message
>> changes to:gpib status is:
>> ibsta = 0x8000  < ERR >
>> iberr= 0
>> EDVR 0: OS error
>>
>> ibcntl = 14and dmesg is flooded with
>> [ 2980.442771] ni_usb_gpib: parse error: wrong start id
>> [ 2980.442775] ni_usb_gpib: parse error: wrong end id
>> [ 2980.442777] ni_usb_gpib: parse error: wrong count=0 for
>> NIUSB_REGISTER_READ_DATA_END
>> [ 2980.442779] ni_usb_gpib: unexpected data: raw_data[6]=0xff, expected 0
>> [ 2980.442781] ni_usb_gpib: unexpected data: raw_data[7]=0xff, expected 0
>> [ 2980.442784] 0c 00 68 00 00 00 ff ff                          ..h.....
>> also, something breaks completely in my computer's USB controller and a
>> reset won't fix it. When it goes into that mode, the computer even refuses
>> to boot when the USB adapter is plugged. The machine needs to be completely
>> turned off for it to work again. When it's in this state, gpib_config won't
>> work even after a reboot, and lsusb hangs if the device is plugged in.
>> Unplugging it and plugging it back in doesn't fix the issue, the computer
>> needs to be powered down.
>> Regards
>>
>>
>> _______________________________________________
>> Linux-gpib-general mailing list
>> Lin...@li...
>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>
>

Re: [Linux-gpib-general] Counterfeit NI GPIB-USB-HS half-works?

[dave p. <dpe...@gm...>]

Hi Hernán,
It looks like you have an unsupported clone. This line in the dmesg is
relevant:
[    4.830150] usb 1-1.6: config 1 interface 0 altsetting 0 endpoint 0x81
has an invalid bInterval 0, changing to 7
Unfortunately this board cannot be made to work with linux-gpib.
cheers,
-Dave

On Wed, 11 Jun 2025 at 22:41, Hernán Freschi <hj...@hj...> wrote:

> Hello. I installed the latest version from master (4c820721), but when
> trying to use it, it half works, and it does a lot of other weird stuff.
> I'm using a counterfeit GPIB-USB-HS from eBay (I assume it's counterfeit
> because it costed $70). The device is not detected as counterfeit by NI
> drivers on Windows, and works fine there. I can communicate with the GPIB
> device. But not on Linux. I don't get any prompts to update its firmware
> either.
> This is dmesg on a fresh boot:
>
> $ sudo dmesg|grep gpib
> [    4.912608] gpib_common: loading out-of-tree module taints kernel.
> [    4.912658] gpib_common: module verification failed: signature and/or
> required key missing - tainting kernel
> [    4.915244] gpib_common: Linux-GPIB 4.3.7 core driver loaded
> [    4.937190] usb 1-1.6: ni_usb_gpib: probe succeeded for path:
> usb-0000:00:1a.0-1.6
> [    4.937228] usbcore: registered new interface driver ni_usb_gpib
> [    5.317767] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
> expected 0x2, 0xe, 0xf or 0x16
> [    5.318304] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
> expected 0x96, 0x07 or 0x6e
> [    5.324141] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
> intf 0
> [  155.040427] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
> expected 0x2, 0xe, 0xf or 0x16
> [  155.040443] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
> expected 0x96, 0x07 or 0x6e
> [  155.046186] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
> intf 0
> also:[    4.717800] usb 1-1.6: new high-speed USB device number 7 using
> ehci-pci
> [    4.830150] usb 1-1.6: config 1 interface 0 altsetting 0 endpoint 0x81
> has an invalid bInterval 0, changing to 7
> [    4.830649] usb 1-1.6: New USB device found, idVendor=3923,
> idProduct=709b, bcdDevice= 1.01
> [    4.830654] usb 1-1.6: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [    4.830657] usb 1-1.6: Product: GPIB-USB-HS
> [    4.830659] usb 1-1.6: Manufacturer: National Instruments
> [    4.830660] usb 1-1.6: SerialNumber: 019A335E
> [    4.937190] usb 1-1.6: ni_usb_gpib: probe succeeded for path:
> usb-0000:00:1a.0-1.6
> [    5.317767] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
> expected 0x2, 0xe, 0xf or 0x16
> [    5.318304] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
> expected 0x96, 0x07 or 0x6e
> [    5.324141] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
> intf 0
> [  155.040427] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
> expected 0x2, 0xe, 0xf or 0x16
> [  155.040443] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
> expected 0x96, 0x07 or 0x6e
> [  155.046186] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
> intf 0
> Here are the issues:
> 1) It appears my device (HP 34401A) receives the commands, but linux-gpib
> doesn't get any acknowledgement. The device goes into remote mode if I send
> *IDN?, but I get an error message
>
> : w
> enter a string to send to your device: *RST
> sending string: *RST
>
> gpib status is:
> ibsta = 0x8000  < ERR >
> iberr= 0
> EDVR 0: OS error
>
> ibcntl = 6
> ..: r
> enter maximum number of bytes to read [1024]: 199
> trying to read 199 bytes from device...
> received string: ''
> Number of bytes read: 0
> gpib status is:
> ibsta = 0xc000  < ERR TIMO >
> iberr= 6
> EABO 6: Operation aborted
>
> ibcntl = 0
> this line appears in dmesg:[  164.340630] usb 3-1.6: ni_usb_gpib:
> Addressing error retval 0 error code=3
> That's as far as the first issue goes. Then:
> 2) After some time, it stops working completely. The error message changes
> to:gpib status is:
> ibsta = 0x8000  < ERR >
> iberr= 0
> EDVR 0: OS error
>
> ibcntl = 14and dmesg is flooded with
> [ 2980.442771] ni_usb_gpib: parse error: wrong start id
> [ 2980.442775] ni_usb_gpib: parse error: wrong end id
> [ 2980.442777] ni_usb_gpib: parse error: wrong count=0 for
> NIUSB_REGISTER_READ_DATA_END
> [ 2980.442779] ni_usb_gpib: unexpected data: raw_data[6]=0xff, expected 0
> [ 2980.442781] ni_usb_gpib: unexpected data: raw_data[7]=0xff, expected 0
> [ 2980.442784] 0c 00 68 00 00 00 ff ff                          ..h.....
> also, something breaks completely in my computer's USB controller and a
> reset won't fix it. When it goes into that mode, the computer even refuses
> to boot when the USB adapter is plugged. The machine needs to be completely
> turned off for it to work again. When it's in this state, gpib_config won't
> work even after a reboot, and lsusb hangs if the device is plugged in.
> Unplugging it and plugging it back in doesn't fix the issue, the computer
> needs to be powered down.
> Regards
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] Counterfeit NI GPIB-USB-HS half-works?

[Hernán F. <hj...@hj...>]

Hello. I installed the latest version from master (4c820721), but when
trying to use it, it half works, and it does a lot of other weird stuff.
I'm using a counterfeit GPIB-USB-HS from eBay (I assume it's counterfeit
because it costed $70). The device is not detected as counterfeit by NI
drivers on Windows, and works fine there. I can communicate with the GPIB
device. But not on Linux. I don't get any prompts to update its firmware
either.
This is dmesg on a fresh boot:

$ sudo dmesg|grep gpib
[    4.912608] gpib_common: loading out-of-tree module taints kernel.
[    4.912658] gpib_common: module verification failed: signature and/or
required key missing - tainting kernel
[    4.915244] gpib_common: Linux-GPIB 4.3.7 core driver loaded
[    4.937190] usb 1-1.6: ni_usb_gpib: probe succeeded for path:
usb-0000:00:1a.0-1.6
[    4.937228] usbcore: registered new interface driver ni_usb_gpib
[    5.317767] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
expected 0x2, 0xe, 0xf or 0x16
[    5.318304] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
expected 0x96, 0x07 or 0x6e
[    5.324141] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
intf 0
[  155.040427] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
expected 0x2, 0xe, 0xf or 0x16
[  155.040443] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
expected 0x96, 0x07 or 0x6e
[  155.046186] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
intf 0
also:[    4.717800] usb 1-1.6: new high-speed USB device number 7 using
ehci-pci
[    4.830150] usb 1-1.6: config 1 interface 0 altsetting 0 endpoint 0x81
has an invalid bInterval 0, changing to 7
[    4.830649] usb 1-1.6: New USB device found, idVendor=3923,
idProduct=709b, bcdDevice= 1.01
[    4.830654] usb 1-1.6: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[    4.830657] usb 1-1.6: Product: GPIB-USB-HS
[    4.830659] usb 1-1.6: Manufacturer: National Instruments
[    4.830660] usb 1-1.6: SerialNumber: 019A335E
[    4.937190] usb 1-1.6: ni_usb_gpib: probe succeeded for path:
usb-0000:00:1a.0-1.6
[    5.317767] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
expected 0x2, 0xe, 0xf or 0x16
[    5.318304] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
expected 0x96, 0x07 or 0x6e
[    5.324141] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
intf 0
[  155.040427] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[6]=0x19,
expected 0x2, 0xe, 0xf or 0x16
[  155.040443] usb 1-1.6: ni_usb_gpib: unexpected data: buffer[10]=0x59,
expected 0x96, 0x07 or 0x6e
[  155.046186] usb 1-1.6: ni_usb_gpib: bus 1 dev num 7 attached to gpib0,
intf 0
Here are the issues:
1) It appears my device (HP 34401A) receives the commands, but linux-gpib
doesn't get any acknowledgement. The device goes into remote mode if I send
*IDN?, but I get an error message

: w
enter a string to send to your device: *RST
sending string: *RST

gpib status is:
ibsta = 0x8000  < ERR >
iberr= 0
EDVR 0: OS error

ibcntl = 6
..: r
enter maximum number of bytes to read [1024]: 199
trying to read 199 bytes from device...
received string: ''
Number of bytes read: 0
gpib status is:
ibsta = 0xc000  < ERR TIMO >
iberr= 6
EABO 6: Operation aborted

ibcntl = 0
this line appears in dmesg:[  164.340630] usb 3-1.6: ni_usb_gpib:
Addressing error retval 0 error code=3
That's as far as the first issue goes. Then:
2) After some time, it stops working completely. The error message changes
to:gpib status is:
ibsta = 0x8000  < ERR >
iberr= 0
EDVR 0: OS error

ibcntl = 14and dmesg is flooded with
[ 2980.442771] ni_usb_gpib: parse error: wrong start id
[ 2980.442775] ni_usb_gpib: parse error: wrong end id
[ 2980.442777] ni_usb_gpib: parse error: wrong count=0 for
NIUSB_REGISTER_READ_DATA_END
[ 2980.442779] ni_usb_gpib: unexpected data: raw_data[6]=0xff, expected 0
[ 2980.442781] ni_usb_gpib: unexpected data: raw_data[7]=0xff, expected 0
[ 2980.442784] 0c 00 68 00 00 00 ff ff                          ..h.....
also, something breaks completely in my computer's USB controller and a
reset won't fix it. When it goes into that mode, the computer even refuses
to boot when the USB adapter is plugged. The machine needs to be completely
turned off for it to work again. When it's in this state, gpib_config won't
work even after a reboot, and lsusb hangs if the device is plugged in.
Unplugging it and plugging it back in doesn't fix the issue, the computer
needs to be powered down.
Regards

Re: [Linux-gpib-general] Petalinux Kernel Compatability

[dave p. <dpe...@gm...>]

Hi Michael,
Are you using the same word width (32 or 64 bit) for both user space and
kernel?
cheers,
-dave

On Wed, 13 Nov 2024, 06:41 Michael Jaggers, <mgj...@gm...> wrote:

> Hey Dave,
>
> The dmesg log I sent is currently using the sourceforge user/kernel
> packages for tag v4_3_6.
> Would you like me to send you the udev script rules? I did change them a
> little bit to debug this issue, but it didn't improve things. It did prove
> that the rules are being enacted (I changed the group and saw that
> reflected in the /dev/gpib* files).
>
> Thanks,
> Michael
>
> On Mon, Nov 11, 2024 at 10:25 PM dave penkler <dpe...@gm...> wrote:
>
>> OK it is hitting EFAULT at the IBONL ioctl gpib_config. To be sure that
>> everything is compatible, you can download, build and install the standard
>> current combined  4.3.6 user and kernel packages from sourceforge
>> <https://sourceforge.net/projects/linux-gpib/files/latest/download> and
>> see if the problem persists. This package supports 6.1.xx kernels. BTW the
>> /dev/gpib* files are set up by the gpib_common module and the access
>> permissions in the  98-gpib-generic.rules udev script, so there should be
>> no problem there.
>> cheers,
>> -Dave
>>
>> On Mon, 11 Nov 2024 at 21:43, Michael Jaggers <mgj...@gm...>
>> wrote:
>>
>>> Yes, there is quite a bit in the console log. I have the debug turned on
>>> (and added some statements in myself), but this is pretty much what happens
>>> when I plug in the device:
>>> [ 9748.976545] usb 1-1.4: new high-speed USB device number 5 using
>>> xhci-hcd
>>> [ 9749.084858] usb 1-1.4: config 1 interface 0 altsetting 0 endpoint
>>> 0x81 has an invalid bInterval 0, changing to 7
>>> [ 9749.095353] usb 1-1.4: New USB device found, idVendor=3923,
>>> idProduct=709b, bcdDevice= 1.01
>>> [ 9749.103769] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
>>> SerialNumber=3
>>> [ 9749.111094] usb 1-1.4: Product: GPIB-USB-HS
>>> [ 9749.115289] usb 1-1.4: Manufacturer: National Instruments
>>> [ 9749.120690] usb 1-1.4: SerialNumber: 01D9F4A4
>>> [ 9749.210590] Linux-GPIB 4.3.6 Driver
>>> [ 9749.386255] ni_usb_gpib driver loading
>>> [ 9749.402265] ni_usb_gpib: probe succeeded for path:
>>> usb-xhci-hcd.1.auto-1.4
>>> [ 9749.414241] usbcore: registered new interface driver ni_usb_gpib
>>> [ 9749.423413] gpib: registered ni_usb_b interface
>>> [ 9749.927552] gpib debug: pid 0, gpib: opening minor 0
>>> [ 9749.935625] gpib debug: pid 0, gpib: request module returned 256
>>> [ 9749.942207] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>>> onl=0, arg=f523e908
>>> [ 9749.970918] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>>> onl=0
>>> [ 9749.978472] gpib debug: pid 0, gpib: closing minor 0
>>> [ 9808.492473] gpib debug: pid 0, gpib: opening minor 0
>>> [ 9808.500324] gpib debug: pid 0, gpib: request module returned 256
>>> [ 9808.506433] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>>> onl=0, arg=fb3f8278
>>>
>>> When I try to run "gpib_config", it only shows this line:
>>> [11325.680770] gpib debug: pid 0, gpib: opening minor 0
>>> [11325.688909] gpib debug: pid 0, gpib: request module returned 256
>>> [11325.695036] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>>> onl=0, arg=ef9596d8
>>> [11325.723526] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>>> onl=0
>>> [11325.730940] gpib debug: pid 0, gpib: closing minor 0
>>>
>>> Best Regards,
>>> Michael
>>>
>>> On Mon, Nov 11, 2024 at 1:28 PM dave penkler <dpe...@gm...> wrote:
>>>
>>>> Hi Michael,
>>>> The gpib.conf looks perfect. Somewhere during the configure we are
>>>> getting an EFAULT - Bad address. This would point to some incompatibility
>>>> between user space gpib_config and the gpib_common kernel module. Is there
>>>> anything in the console log (dmesg) ?
>>>> cheers,
>>>> -dave
>>>>
>>>>
>>>>
>>>> On Tue, 12 Nov 2024, 05:28 Michael Jaggers, <mgj...@gm...>
>>>> wrote:
>>>>
>>>>> Hey Dave,
>>>>>
>>>>> I went back and double checked on the configure argument you asked
>>>>> for, and I did provide the path to it. I also checked it by putting a
>>>>> syntax error into the gpib.conf file and that output an error and the path
>>>>> it was pointing to.
>>>>>
>>>>> Here is the conf file that I'm using:
>>>>>
>>>>> /* This section configures the configurable driver characteristics
>>>>>  * for an interface board, such as board address, and interrupt level.
>>>>>  * minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1,
>>>>> etc.
>>>>>  */
>>>>>
>>>>> interface {
>>>>>     minor = 0
>>>>>     board_type = "ni_usb_gpib"
>>>>>     name = "gpib0"
>>>>>     pad = 2
>>>>>     timeout = T1s
>>>>>     eos = 0x0A
>>>>>     set-reos = yes
>>>>>     set-bin = no
>>>>>     master = yes
>>>>>
>>>>> }
>>>>>
>>>>> Thanks!
>>>>> Michael
>>>>>
>>>>> On Sat, Nov 9, 2024 at 2:24 AM dave penkler <dpe...@gm...>
>>>>> wrote:
>>>>>
>>>>>> Hi Michael,
>>>>>> It looks like a gpib.conf problem. Did you provide a sysconfdir
>>>>>> argument to .configure ?
>>>>>> Please send me your gpib.conf file.
>>>>>> cheers,
>>>>>> -dave
>>>>>>
>>>>>> On Sat, 9 Nov 2024, 04:38 Michael Jaggers, <mgj...@gm...>
>>>>>> wrote:
>>>>>>
>>>>>>> Dave,
>>>>>>>
>>>>>>> I've run the gpib_config, but no luck on that end. Here is what
>>>>>>> happens to me:
>>>>>>> 1. First, I restart the device without plugging in the gpib (drivers
>>>>>>> aren't loaded).
>>>>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>>>>> failed to open device file '/dev/gpib0'
>>>>>>> main: No such file or directory
>>>>>>>
>>>>>>> 2. Now, I plug the gpib dongle in.
>>>>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>>>>> failed to bring board offline
>>>>>>> failed to configure board
>>>>>>> main: Bad address
>>>>>>>
>>>>>>> 3. Finally, I unplug the gpib dongle.
>>>>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>>>>> failed to bring board offline
>>>>>>> failed to configure board
>>>>>>> main: Bad address
>>>>>>>
>>>>>>> To me, this looks like the dongle isn't attaching to /dev/gpib0. I
>>>>>>> know the driver recognizes the device, it correctly starts the ni_usb_gpib
>>>>>>> driver, and probes the correct location on the device tree, and the driver
>>>>>>> in the device tree points to the correct place the dongle is attached to.
>>>>>>> What's got me scratching my head is why it's not attached to gpib0 (or even
>>>>>>> how to circumvent the need to attach to gpib0).
>>>>>>>
>>>>>>> Could it be related to my udev? In the rules, in file
>>>>>>> "/etc/udev/rules.d/98-gpib-generic.rules" I added:
>>>>>>> ACTION=="add|change",
>>>>>>> DEVPATH=="/devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0",
>>>>>>> ENV{GPIB_CONFIG_OPTIONS}="--minor 0"
>>>>>>>
>>>>>>> That's the path that udev recognizes. When I run udevadm monitor, I
>>>>>>> get this after plugging in the dongle:
>>>>>>> KERNEL[1122.600699] add
>>>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>>>> (usb)
>>>>>>> KERNEL[1122.650504] add
>>>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>>>> (usb)
>>>>>>> KERNEL[1122.671551] bind
>>>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>>>> (usb)
>>>>>>> KERNEL[1122.671684] bind
>>>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>>>> (usb)
>>>>>>> UDEV  [1122.676333] add
>>>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>>>> (usb)
>>>>>>> UDEV  [1122.769461] add
>>>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>>>> (usb)
>>>>>>> UDEV  [1122.772939] bind
>>>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>>>> (usb)
>>>>>>> UDEV  [1122.777553] bind
>>>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>>>> (usb)
>>>>>>>
>>>>>>> Could the version of udev be the cause?
>>>>>>> root@tester0:~/git/linux-gpib-git# udevd --version
>>>>>>> 251.8+
>>>>>>> root@tester0:~/git/linux-gpib-git# udevadm --version
>>>>>>> 251
>>>>>>>
>>>>>>> Thanks for your responses!
>>>>>>> Michael
>>>>>>>
>>>>>>> On Thu, Nov 7, 2024 at 9:04 PM dave penkler <dpe...@gm...>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> It looks like the board is not attached. Did you run # gpib_config
>>>>>>>> ? Normally the supplied udev scripts do this for you.
>>>>>>>> cheers,
>>>>>>>> -dave
>>>>>>>>
>>>>>>>> On Fri, 8 Nov 2024, 05:24 Charles Lane, <la...@dc...> wrote:
>>>>>>>>
>>>>>>>>> Setting up the /dev/gpib* devices is something that
>>>>>>>>> you might want to look at udev for...but as I recall
>>>>>>>>> there's some problems. That isn't necessarily in the
>>>>>>>>> linux-gpib git project, maybe in linux-gpib-packaging
>>>>>>>>> project....where the idea is to wrap the linux-gpib
>>>>>>>>> code in an rpm package (so that installation deals
>>>>>>>>> with udev scripts, protection issues, etc)
>>>>>>>>>
>>>>>>>>> On Thu, 7 Nov 2024 09:51:32 -0700
>>>>>>>>> Michael Jaggers <mgj...@gm...> wrote:
>>>>>>>>>
>>>>>>>>> > Hello,
>>>>>>>>> >
>>>>>>>>> > I'm working on installing the gpib kernel drivers to the
>>>>>>>>> Petalinux
>>>>>>>>> > platform. So far, I've managed to get the headers and get the
>>>>>>>>> gpib
>>>>>>>>> > drivers compiled + installed. The modules show up with modprobe,
>>>>>>>>> and
>>>>>>>>> > when I plug my gpib dongle in the driver loads properly and it
>>>>>>>>> seems
>>>>>>>>> > to recognize it. Below is the message I get when plugging in the
>>>>>>>>> > dongle: [19163.768240] usb 1-1.4: new high-speed USB device
>>>>>>>>> number 11
>>>>>>>>> > using xhci-hcd [19164.020393] usb 1-1.4: config 1 interface 0
>>>>>>>>> > altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing
>>>>>>>>> to 7
>>>>>>>>> > [19164.030876] usb 1-1.4: New USB device found, idVendor=3923,
>>>>>>>>> > idProduct=709b, bcdDevice= 1.01
>>>>>>>>> > [19164.039247] usb 1-1.4: New USB device strings: Mfr=1,
>>>>>>>>> Product=2,
>>>>>>>>> > SerialNumber=3
>>>>>>>>> > [19164.046560] usb 1-1.4: Product: GPIB-USB-HS
>>>>>>>>> > [19164.050739] usb 1-1.4: Manufacturer: National Instruments
>>>>>>>>> > [19164.056138] usb 1-1.4: SerialNumber: 01D9F4A4
>>>>>>>>> >
>>>>>>>>> > Here is where the issue comes up. When ibopen goes to set things
>>>>>>>>> up
>>>>>>>>> > with the dongle, the /dev/gpib0 doesn't seem to be properly
>>>>>>>>> > configured. I get this message when I run the ibtest utility:
>>>>>>>>> > [84391.688217] gpib debug: pid 0, gpib: opening minor 0
>>>>>>>>> > [84391.696029] gpib debug: pid 0, gpib: request module returned
>>>>>>>>> 256
>>>>>>>>> > [84391.702071] gpib debug: pid 0, minor 0, ioctl 3, interface=,
>>>>>>>>> use=0,
>>>>>>>>> > onl=0, arg=d8a171a0
>>>>>>>>> > [84391.710090] gpib: no gpib board configured on /dev/gpib0
>>>>>>>>> > [84391.715398] gpib debug: pid 0, minor 0, ioctl 3, interface=,
>>>>>>>>> > use=0, onl=0 [84391.722212] gpib debug: pid 0, minor 0, ioctl 5,
>>>>>>>>> > interface=, use=0, onl=0, arg=d8a17120
>>>>>>>>> > [84391.730218] gpib: no gpib board configured on /dev/gpib0
>>>>>>>>> > [84391.735527] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>>>>>>>>> > use=0, onl=0 [84391.742357] gpib debug: pid 0, minor 0, ioctl 5,
>>>>>>>>> > interface=, use=0, onl=0, arg=d8a17180
>>>>>>>>> > [84391.750363] gpib: no gpib board configured on /dev/gpib0
>>>>>>>>> > [84391.755673] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>>>>>>>>> > use=0, onl=0 [84391.762675] audit: type=1701
>>>>>>>>> > audit(1730996390.861:20): auid=0 uid=0 gid=0 ses=2 pid=10840
>>>>>>>>> > comm="ibtest" exe="/usr/local/bin/ibtest" sig=6 res=1
>>>>>>>>> [84391.764574]
>>>>>>>>> > gpib debug: pid 0, gpib: closing minor 0
>>>>>>>>> >
>>>>>>>>> > I've been debugging this for a week or so now. I'm fairly
>>>>>>>>> confident
>>>>>>>>> > that the probing of the dongle works. In fact, when I find the
>>>>>>>>> dongle
>>>>>>>>> > in the sys path, I see that the module driver is in that path of
>>>>>>>>> the
>>>>>>>>> > device itself: root@tester0:~# ls -ll
>>>>>>>>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/ total 0
>>>>>>>>> > -rw-r--r-- 1 root root 4096 Nov  7 16:25 authorized
>>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bAlternateSetting
>>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceClass
>>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceNumber
>>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceProtocol
>>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceSubClass
>>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bNumEndpoints
>>>>>>>>> > lrwxrwxrwx 1 root root    0 Nov  7 16:25 driver ->
>>>>>>>>> > ../../../../../../../../../../bus/usb/drivers/ni_usb_gpib
>>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_02
>>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_06
>>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_81
>>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_84
>>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_88
>>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 modalias
>>>>>>>>> > drwxr-xr-x 2 root root    0 Nov  7 16:25 power
>>>>>>>>> > lrwxrwxrwx 1 root root    0 Nov  7 16:18 subsystem ->
>>>>>>>>> > ../../../../../../../../../../bus/usb
>>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 supports_autosuspend
>>>>>>>>> > -rw-r--r-- 1 root root 4096 Nov  7 16:18 uevent
>>>>>>>>> >
>>>>>>>>> > root@tester0:~# grep ^
>>>>>>>>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/modalias
>>>>>>>>> > usb:*v3923p709B*d0101dc00dsc00dp00icFFisc00ip00in00
>>>>>>>>> >
>>>>>>>>> > The driver itself tells me that the interface registers properly
>>>>>>>>> too
>>>>>>>>> > (my apologies for the extra debug messages):
>>>>>>>>> > [85375.091233] ni_usb_gpib driver loading
>>>>>>>>> > [85375.098301] ni_usb_driver_probe
>>>>>>>>> > [85375.101436] set bus interface 0 to address 0x00000000bca009b3
>>>>>>>>> > [85375.107200] ni_usb_gpib: probe succeeded for path:
>>>>>>>>> > usb-xhci-hcd.1.auto-1.4
>>>>>>>>> > [85375.119145] usbcore: registered new interface driver
>>>>>>>>> ni_usb_gpib
>>>>>>>>> > [85375.128308] gpib: registered ni_usb_b interface
>>>>>>>>> >
>>>>>>>>> > However, everywhere I look in the code doesn't indicate to me
>>>>>>>>> where
>>>>>>>>> > the disconnect occurs. I'm fairly certain the issue is that the
>>>>>>>>> > /dev/gpib* section isn't pointing to the dongle area and that's
>>>>>>>>> my
>>>>>>>>> > problem. I've been trying to create a workaround to this that
>>>>>>>>> shows
>>>>>>>>> > the device working at all, but I'm not having any luck there.
>>>>>>>>> > So I'm at a loss for where to go next. Any suggestions? RIght
>>>>>>>>> now, I'm
>>>>>>>>> > trying to figure out why I'm getting "interface=". I feel like
>>>>>>>>> that's
>>>>>>>>> > the underlying problem, but I can't confirm it.
>>>>>>>>> > Just in case, here is some extra information about he system I'm
>>>>>>>>> on:
>>>>>>>>> > Operating System: PetaLinux 2023.2+update-61_04172258- (langdale)
>>>>>>>>> >           Kernel: Linux 6.1.30-xilinx-v2023.2
>>>>>>>>> >     Architecture: arm64
>>>>>>>>> >
>>>>>>>>> > Thanks,
>>>>>>>>> > Michael
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Drexel University  |/             /    ·   ν ·   Chuck Lane   |D
>>>>>>>>> ======]－－－>－－－C－－－－－π+－－<                Disque 911  |U
>>>>>>>>> Particle Physics    \             \    ~~ e+~~   215-895-1545 |N
>>>>>>>>> la...@dc...                    －​μ+－－+νν                 |E
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Linux-gpib-general mailing list
>>>>>>>>> Lin...@li...
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Linux-gpib-general mailing list
>>>>>>>> Lin...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>>>>>>>
>>>>>>>

Re: [Linux-gpib-general] Petalinux Kernel Compatability

[Michael J. <mgj...@gm...>]

Hey Dave,

The dmesg log I sent is currently using the sourceforge user/kernel
packages for tag v4_3_6.
Would you like me to send you the udev script rules? I did change them a
little bit to debug this issue, but it didn't improve things. It did prove
that the rules are being enacted (I changed the group and saw that
reflected in the /dev/gpib* files).

Thanks,
Michael

On Mon, Nov 11, 2024 at 10:25 PM dave penkler <dpe...@gm...> wrote:

> OK it is hitting EFAULT at the IBONL ioctl gpib_config. To be sure that
> everything is compatible, you can download, build and install the standard
> current combined  4.3.6 user and kernel packages from sourceforge
> <https://sourceforge.net/projects/linux-gpib/files/latest/download> and
> see if the problem persists. This package supports 6.1.xx kernels. BTW the
> /dev/gpib* files are set up by the gpib_common module and the access
> permissions in the  98-gpib-generic.rules udev script, so there should be
> no problem there.
> cheers,
> -Dave
>
> On Mon, 11 Nov 2024 at 21:43, Michael Jaggers <mgj...@gm...> wrote:
>
>> Yes, there is quite a bit in the console log. I have the debug turned on
>> (and added some statements in myself), but this is pretty much what happens
>> when I plug in the device:
>> [ 9748.976545] usb 1-1.4: new high-speed USB device number 5 using
>> xhci-hcd
>> [ 9749.084858] usb 1-1.4: config 1 interface 0 altsetting 0 endpoint 0x81
>> has an invalid bInterval 0, changing to 7
>> [ 9749.095353] usb 1-1.4: New USB device found, idVendor=3923,
>> idProduct=709b, bcdDevice= 1.01
>> [ 9749.103769] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [ 9749.111094] usb 1-1.4: Product: GPIB-USB-HS
>> [ 9749.115289] usb 1-1.4: Manufacturer: National Instruments
>> [ 9749.120690] usb 1-1.4: SerialNumber: 01D9F4A4
>> [ 9749.210590] Linux-GPIB 4.3.6 Driver
>> [ 9749.386255] ni_usb_gpib driver loading
>> [ 9749.402265] ni_usb_gpib: probe succeeded for path:
>> usb-xhci-hcd.1.auto-1.4
>> [ 9749.414241] usbcore: registered new interface driver ni_usb_gpib
>> [ 9749.423413] gpib: registered ni_usb_b interface
>> [ 9749.927552] gpib debug: pid 0, gpib: opening minor 0
>> [ 9749.935625] gpib debug: pid 0, gpib: request module returned 256
>> [ 9749.942207] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>> onl=0, arg=f523e908
>> [ 9749.970918] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>> onl=0
>> [ 9749.978472] gpib debug: pid 0, gpib: closing minor 0
>> [ 9808.492473] gpib debug: pid 0, gpib: opening minor 0
>> [ 9808.500324] gpib debug: pid 0, gpib: request module returned 256
>> [ 9808.506433] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>> onl=0, arg=fb3f8278
>>
>> When I try to run "gpib_config", it only shows this line:
>> [11325.680770] gpib debug: pid 0, gpib: opening minor 0
>> [11325.688909] gpib debug: pid 0, gpib: request module returned 256
>> [11325.695036] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>> onl=0, arg=ef9596d8
>> [11325.723526] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
>> onl=0
>> [11325.730940] gpib debug: pid 0, gpib: closing minor 0
>>
>> Best Regards,
>> Michael
>>
>> On Mon, Nov 11, 2024 at 1:28 PM dave penkler <dpe...@gm...> wrote:
>>
>>> Hi Michael,
>>> The gpib.conf looks perfect. Somewhere during the configure we are
>>> getting an EFAULT - Bad address. This would point to some incompatibility
>>> between user space gpib_config and the gpib_common kernel module. Is there
>>> anything in the console log (dmesg) ?
>>> cheers,
>>> -dave
>>>
>>>
>>>
>>> On Tue, 12 Nov 2024, 05:28 Michael Jaggers, <mgj...@gm...> wrote:
>>>
>>>> Hey Dave,
>>>>
>>>> I went back and double checked on the configure argument you asked for,
>>>> and I did provide the path to it. I also checked it by putting a syntax
>>>> error into the gpib.conf file and that output an error and the path it was
>>>> pointing to.
>>>>
>>>> Here is the conf file that I'm using:
>>>>
>>>> /* This section configures the configurable driver characteristics
>>>>  * for an interface board, such as board address, and interrupt level.
>>>>  * minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1,
>>>> etc.
>>>>  */
>>>>
>>>> interface {
>>>>     minor = 0
>>>>     board_type = "ni_usb_gpib"
>>>>     name = "gpib0"
>>>>     pad = 2
>>>>     timeout = T1s
>>>>     eos = 0x0A
>>>>     set-reos = yes
>>>>     set-bin = no
>>>>     master = yes
>>>>
>>>> }
>>>>
>>>> Thanks!
>>>> Michael
>>>>
>>>> On Sat, Nov 9, 2024 at 2:24 AM dave penkler <dpe...@gm...> wrote:
>>>>
>>>>> Hi Michael,
>>>>> It looks like a gpib.conf problem. Did you provide a sysconfdir
>>>>> argument to .configure ?
>>>>> Please send me your gpib.conf file.
>>>>> cheers,
>>>>> -dave
>>>>>
>>>>> On Sat, 9 Nov 2024, 04:38 Michael Jaggers, <mgj...@gm...>
>>>>> wrote:
>>>>>
>>>>>> Dave,
>>>>>>
>>>>>> I've run the gpib_config, but no luck on that end. Here is what
>>>>>> happens to me:
>>>>>> 1. First, I restart the device without plugging in the gpib (drivers
>>>>>> aren't loaded).
>>>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>>>> failed to open device file '/dev/gpib0'
>>>>>> main: No such file or directory
>>>>>>
>>>>>> 2. Now, I plug the gpib dongle in.
>>>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>>>> failed to bring board offline
>>>>>> failed to configure board
>>>>>> main: Bad address
>>>>>>
>>>>>> 3. Finally, I unplug the gpib dongle.
>>>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>>>> failed to bring board offline
>>>>>> failed to configure board
>>>>>> main: Bad address
>>>>>>
>>>>>> To me, this looks like the dongle isn't attaching to /dev/gpib0. I
>>>>>> know the driver recognizes the device, it correctly starts the ni_usb_gpib
>>>>>> driver, and probes the correct location on the device tree, and the driver
>>>>>> in the device tree points to the correct place the dongle is attached to.
>>>>>> What's got me scratching my head is why it's not attached to gpib0 (or even
>>>>>> how to circumvent the need to attach to gpib0).
>>>>>>
>>>>>> Could it be related to my udev? In the rules, in file
>>>>>> "/etc/udev/rules.d/98-gpib-generic.rules" I added:
>>>>>> ACTION=="add|change",
>>>>>> DEVPATH=="/devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0",
>>>>>> ENV{GPIB_CONFIG_OPTIONS}="--minor 0"
>>>>>>
>>>>>> That's the path that udev recognizes. When I run udevadm monitor, I
>>>>>> get this after plugging in the dongle:
>>>>>> KERNEL[1122.600699] add
>>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>>> (usb)
>>>>>> KERNEL[1122.650504] add
>>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>>> (usb)
>>>>>> KERNEL[1122.671551] bind
>>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>>> (usb)
>>>>>> KERNEL[1122.671684] bind
>>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>>> (usb)
>>>>>> UDEV  [1122.676333] add
>>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>>> (usb)
>>>>>> UDEV  [1122.769461] add
>>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>>> (usb)
>>>>>> UDEV  [1122.772939] bind
>>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>>> (usb)
>>>>>> UDEV  [1122.777553] bind
>>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>>> (usb)
>>>>>>
>>>>>> Could the version of udev be the cause?
>>>>>> root@tester0:~/git/linux-gpib-git# udevd --version
>>>>>> 251.8+
>>>>>> root@tester0:~/git/linux-gpib-git# udevadm --version
>>>>>> 251
>>>>>>
>>>>>> Thanks for your responses!
>>>>>> Michael
>>>>>>
>>>>>> On Thu, Nov 7, 2024 at 9:04 PM dave penkler <dpe...@gm...>
>>>>>> wrote:
>>>>>>
>>>>>>> It looks like the board is not attached. Did you run # gpib_config ?
>>>>>>> Normally the supplied udev scripts do this for you.
>>>>>>> cheers,
>>>>>>> -dave
>>>>>>>
>>>>>>> On Fri, 8 Nov 2024, 05:24 Charles Lane, <la...@dc...> wrote:
>>>>>>>
>>>>>>>> Setting up the /dev/gpib* devices is something that
>>>>>>>> you might want to look at udev for...but as I recall
>>>>>>>> there's some problems. That isn't necessarily in the
>>>>>>>> linux-gpib git project, maybe in linux-gpib-packaging
>>>>>>>> project....where the idea is to wrap the linux-gpib
>>>>>>>> code in an rpm package (so that installation deals
>>>>>>>> with udev scripts, protection issues, etc)
>>>>>>>>
>>>>>>>> On Thu, 7 Nov 2024 09:51:32 -0700
>>>>>>>> Michael Jaggers <mgj...@gm...> wrote:
>>>>>>>>
>>>>>>>> > Hello,
>>>>>>>> >
>>>>>>>> > I'm working on installing the gpib kernel drivers to the Petalinux
>>>>>>>> > platform. So far, I've managed to get the headers and get the gpib
>>>>>>>> > drivers compiled + installed. The modules show up with modprobe,
>>>>>>>> and
>>>>>>>> > when I plug my gpib dongle in the driver loads properly and it
>>>>>>>> seems
>>>>>>>> > to recognize it. Below is the message I get when plugging in the
>>>>>>>> > dongle: [19163.768240] usb 1-1.4: new high-speed USB device
>>>>>>>> number 11
>>>>>>>> > using xhci-hcd [19164.020393] usb 1-1.4: config 1 interface 0
>>>>>>>> > altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing
>>>>>>>> to 7
>>>>>>>> > [19164.030876] usb 1-1.4: New USB device found, idVendor=3923,
>>>>>>>> > idProduct=709b, bcdDevice= 1.01
>>>>>>>> > [19164.039247] usb 1-1.4: New USB device strings: Mfr=1,
>>>>>>>> Product=2,
>>>>>>>> > SerialNumber=3
>>>>>>>> > [19164.046560] usb 1-1.4: Product: GPIB-USB-HS
>>>>>>>> > [19164.050739] usb 1-1.4: Manufacturer: National Instruments
>>>>>>>> > [19164.056138] usb 1-1.4: SerialNumber: 01D9F4A4
>>>>>>>> >
>>>>>>>> > Here is where the issue comes up. When ibopen goes to set things
>>>>>>>> up
>>>>>>>> > with the dongle, the /dev/gpib0 doesn't seem to be properly
>>>>>>>> > configured. I get this message when I run the ibtest utility:
>>>>>>>> > [84391.688217] gpib debug: pid 0, gpib: opening minor 0
>>>>>>>> > [84391.696029] gpib debug: pid 0, gpib: request module returned
>>>>>>>> 256
>>>>>>>> > [84391.702071] gpib debug: pid 0, minor 0, ioctl 3, interface=,
>>>>>>>> use=0,
>>>>>>>> > onl=0, arg=d8a171a0
>>>>>>>> > [84391.710090] gpib: no gpib board configured on /dev/gpib0
>>>>>>>> > [84391.715398] gpib debug: pid 0, minor 0, ioctl 3, interface=,
>>>>>>>> > use=0, onl=0 [84391.722212] gpib debug: pid 0, minor 0, ioctl 5,
>>>>>>>> > interface=, use=0, onl=0, arg=d8a17120
>>>>>>>> > [84391.730218] gpib: no gpib board configured on /dev/gpib0
>>>>>>>> > [84391.735527] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>>>>>>>> > use=0, onl=0 [84391.742357] gpib debug: pid 0, minor 0, ioctl 5,
>>>>>>>> > interface=, use=0, onl=0, arg=d8a17180
>>>>>>>> > [84391.750363] gpib: no gpib board configured on /dev/gpib0
>>>>>>>> > [84391.755673] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>>>>>>>> > use=0, onl=0 [84391.762675] audit: type=1701
>>>>>>>> > audit(1730996390.861:20): auid=0 uid=0 gid=0 ses=2 pid=10840
>>>>>>>> > comm="ibtest" exe="/usr/local/bin/ibtest" sig=6 res=1
>>>>>>>> [84391.764574]
>>>>>>>> > gpib debug: pid 0, gpib: closing minor 0
>>>>>>>> >
>>>>>>>> > I've been debugging this for a week or so now. I'm fairly
>>>>>>>> confident
>>>>>>>> > that the probing of the dongle works. In fact, when I find the
>>>>>>>> dongle
>>>>>>>> > in the sys path, I see that the module driver is in that path of
>>>>>>>> the
>>>>>>>> > device itself: root@tester0:~# ls -ll
>>>>>>>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/ total 0
>>>>>>>> > -rw-r--r-- 1 root root 4096 Nov  7 16:25 authorized
>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bAlternateSetting
>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceClass
>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceNumber
>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceProtocol
>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceSubClass
>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bNumEndpoints
>>>>>>>> > lrwxrwxrwx 1 root root    0 Nov  7 16:25 driver ->
>>>>>>>> > ../../../../../../../../../../bus/usb/drivers/ni_usb_gpib
>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_02
>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_06
>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_81
>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_84
>>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_88
>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 modalias
>>>>>>>> > drwxr-xr-x 2 root root    0 Nov  7 16:25 power
>>>>>>>> > lrwxrwxrwx 1 root root    0 Nov  7 16:18 subsystem ->
>>>>>>>> > ../../../../../../../../../../bus/usb
>>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 supports_autosuspend
>>>>>>>> > -rw-r--r-- 1 root root 4096 Nov  7 16:18 uevent
>>>>>>>> >
>>>>>>>> > root@tester0:~# grep ^
>>>>>>>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/modalias
>>>>>>>> > usb:*v3923p709B*d0101dc00dsc00dp00icFFisc00ip00in00
>>>>>>>> >
>>>>>>>> > The driver itself tells me that the interface registers properly
>>>>>>>> too
>>>>>>>> > (my apologies for the extra debug messages):
>>>>>>>> > [85375.091233] ni_usb_gpib driver loading
>>>>>>>> > [85375.098301] ni_usb_driver_probe
>>>>>>>> > [85375.101436] set bus interface 0 to address 0x00000000bca009b3
>>>>>>>> > [85375.107200] ni_usb_gpib: probe succeeded for path:
>>>>>>>> > usb-xhci-hcd.1.auto-1.4
>>>>>>>> > [85375.119145] usbcore: registered new interface driver
>>>>>>>> ni_usb_gpib
>>>>>>>> > [85375.128308] gpib: registered ni_usb_b interface
>>>>>>>> >
>>>>>>>> > However, everywhere I look in the code doesn't indicate to me
>>>>>>>> where
>>>>>>>> > the disconnect occurs. I'm fairly certain the issue is that the
>>>>>>>> > /dev/gpib* section isn't pointing to the dongle area and that's my
>>>>>>>> > problem. I've been trying to create a workaround to this that
>>>>>>>> shows
>>>>>>>> > the device working at all, but I'm not having any luck there.
>>>>>>>> > So I'm at a loss for where to go next. Any suggestions? RIght
>>>>>>>> now, I'm
>>>>>>>> > trying to figure out why I'm getting "interface=". I feel like
>>>>>>>> that's
>>>>>>>> > the underlying problem, but I can't confirm it.
>>>>>>>> > Just in case, here is some extra information about he system I'm
>>>>>>>> on:
>>>>>>>> > Operating System: PetaLinux 2023.2+update-61_04172258- (langdale)
>>>>>>>> >           Kernel: Linux 6.1.30-xilinx-v2023.2
>>>>>>>> >     Architecture: arm64
>>>>>>>> >
>>>>>>>> > Thanks,
>>>>>>>> > Michael
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Drexel University  |/             /    ·   ν ·   Chuck Lane   |D
>>>>>>>> ======]－－－>－－－C－－－－－π+－－<                Disque 911  |U
>>>>>>>> Particle Physics    \             \    ~~ e+~~   215-895-1545 |N
>>>>>>>> la...@dc...                    －​μ+－－+νν                 |E
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Linux-gpib-general mailing list
>>>>>>>> Lin...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Linux-gpib-general mailing list
>>>>>>> Lin...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>>>>>>
>>>>>>

Re: [Linux-gpib-general] Petalinux Kernel Compatability

[dave p. <dpe...@gm...>]

OK it is hitting EFAULT at the IBONL ioctl gpib_config. To be sure that
everything is compatible, you can download, build and install the standard
current combined  4.3.6 user and kernel packages from sourceforge
<https://sourceforge.net/projects/linux-gpib/files/latest/download> and see
if the problem persists. This package supports 6.1.xx kernels. BTW the
/dev/gpib* files are set up by the gpib_common module and the access
permissions in the  98-gpib-generic.rules udev script, so there should be
no problem there.
cheers,
-Dave

On Mon, 11 Nov 2024 at 21:43, Michael Jaggers <mgj...@gm...> wrote:

> Yes, there is quite a bit in the console log. I have the debug turned on
> (and added some statements in myself), but this is pretty much what happens
> when I plug in the device:
> [ 9748.976545] usb 1-1.4: new high-speed USB device number 5 using xhci-hcd
> [ 9749.084858] usb 1-1.4: config 1 interface 0 altsetting 0 endpoint 0x81
> has an invalid bInterval 0, changing to 7
> [ 9749.095353] usb 1-1.4: New USB device found, idVendor=3923,
> idProduct=709b, bcdDevice= 1.01
> [ 9749.103769] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 9749.111094] usb 1-1.4: Product: GPIB-USB-HS
> [ 9749.115289] usb 1-1.4: Manufacturer: National Instruments
> [ 9749.120690] usb 1-1.4: SerialNumber: 01D9F4A4
> [ 9749.210590] Linux-GPIB 4.3.6 Driver
> [ 9749.386255] ni_usb_gpib driver loading
> [ 9749.402265] ni_usb_gpib: probe succeeded for path:
> usb-xhci-hcd.1.auto-1.4
> [ 9749.414241] usbcore: registered new interface driver ni_usb_gpib
> [ 9749.423413] gpib: registered ni_usb_b interface
> [ 9749.927552] gpib debug: pid 0, gpib: opening minor 0
> [ 9749.935625] gpib debug: pid 0, gpib: request module returned 256
> [ 9749.942207] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
> onl=0, arg=f523e908
> [ 9749.970918] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
> onl=0
> [ 9749.978472] gpib debug: pid 0, gpib: closing minor 0
> [ 9808.492473] gpib debug: pid 0, gpib: opening minor 0
> [ 9808.500324] gpib debug: pid 0, gpib: request module returned 256
> [ 9808.506433] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
> onl=0, arg=fb3f8278
>
> When I try to run "gpib_config", it only shows this line:
> [11325.680770] gpib debug: pid 0, gpib: opening minor 0
> [11325.688909] gpib debug: pid 0, gpib: request module returned 256
> [11325.695036] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
> onl=0, arg=ef9596d8
> [11325.723526] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
> onl=0
> [11325.730940] gpib debug: pid 0, gpib: closing minor 0
>
> Best Regards,
> Michael
>
> On Mon, Nov 11, 2024 at 1:28 PM dave penkler <dpe...@gm...> wrote:
>
>> Hi Michael,
>> The gpib.conf looks perfect. Somewhere during the configure we are
>> getting an EFAULT - Bad address. This would point to some incompatibility
>> between user space gpib_config and the gpib_common kernel module. Is there
>> anything in the console log (dmesg) ?
>> cheers,
>> -dave
>>
>>
>>
>> On Tue, 12 Nov 2024, 05:28 Michael Jaggers, <mgj...@gm...> wrote:
>>
>>> Hey Dave,
>>>
>>> I went back and double checked on the configure argument you asked for,
>>> and I did provide the path to it. I also checked it by putting a syntax
>>> error into the gpib.conf file and that output an error and the path it was
>>> pointing to.
>>>
>>> Here is the conf file that I'm using:
>>>
>>> /* This section configures the configurable driver characteristics
>>>  * for an interface board, such as board address, and interrupt level.
>>>  * minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1,
>>> etc.
>>>  */
>>>
>>> interface {
>>>     minor = 0
>>>     board_type = "ni_usb_gpib"
>>>     name = "gpib0"
>>>     pad = 2
>>>     timeout = T1s
>>>     eos = 0x0A
>>>     set-reos = yes
>>>     set-bin = no
>>>     master = yes
>>>
>>> }
>>>
>>> Thanks!
>>> Michael
>>>
>>> On Sat, Nov 9, 2024 at 2:24 AM dave penkler <dpe...@gm...> wrote:
>>>
>>>> Hi Michael,
>>>> It looks like a gpib.conf problem. Did you provide a sysconfdir
>>>> argument to .configure ?
>>>> Please send me your gpib.conf file.
>>>> cheers,
>>>> -dave
>>>>
>>>> On Sat, 9 Nov 2024, 04:38 Michael Jaggers, <mgj...@gm...> wrote:
>>>>
>>>>> Dave,
>>>>>
>>>>> I've run the gpib_config, but no luck on that end. Here is what
>>>>> happens to me:
>>>>> 1. First, I restart the device without plugging in the gpib (drivers
>>>>> aren't loaded).
>>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>>> failed to open device file '/dev/gpib0'
>>>>> main: No such file or directory
>>>>>
>>>>> 2. Now, I plug the gpib dongle in.
>>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>>> failed to bring board offline
>>>>> failed to configure board
>>>>> main: Bad address
>>>>>
>>>>> 3. Finally, I unplug the gpib dongle.
>>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>>> failed to bring board offline
>>>>> failed to configure board
>>>>> main: Bad address
>>>>>
>>>>> To me, this looks like the dongle isn't attaching to /dev/gpib0. I
>>>>> know the driver recognizes the device, it correctly starts the ni_usb_gpib
>>>>> driver, and probes the correct location on the device tree, and the driver
>>>>> in the device tree points to the correct place the dongle is attached to.
>>>>> What's got me scratching my head is why it's not attached to gpib0 (or even
>>>>> how to circumvent the need to attach to gpib0).
>>>>>
>>>>> Could it be related to my udev? In the rules, in file
>>>>> "/etc/udev/rules.d/98-gpib-generic.rules" I added:
>>>>> ACTION=="add|change",
>>>>> DEVPATH=="/devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0",
>>>>> ENV{GPIB_CONFIG_OPTIONS}="--minor 0"
>>>>>
>>>>> That's the path that udev recognizes. When I run udevadm monitor, I
>>>>> get this after plugging in the dongle:
>>>>> KERNEL[1122.600699] add
>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>> (usb)
>>>>> KERNEL[1122.650504] add
>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>> (usb)
>>>>> KERNEL[1122.671551] bind
>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>> (usb)
>>>>> KERNEL[1122.671684] bind
>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>> (usb)
>>>>> UDEV  [1122.676333] add
>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>> (usb)
>>>>> UDEV  [1122.769461] add
>>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>> (usb)
>>>>> UDEV  [1122.772939] bind
>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>>> (usb)
>>>>> UDEV  [1122.777553] bind
>>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>>> (usb)
>>>>>
>>>>> Could the version of udev be the cause?
>>>>> root@tester0:~/git/linux-gpib-git# udevd --version
>>>>> 251.8+
>>>>> root@tester0:~/git/linux-gpib-git# udevadm --version
>>>>> 251
>>>>>
>>>>> Thanks for your responses!
>>>>> Michael
>>>>>
>>>>> On Thu, Nov 7, 2024 at 9:04 PM dave penkler <dpe...@gm...>
>>>>> wrote:
>>>>>
>>>>>> It looks like the board is not attached. Did you run # gpib_config ?
>>>>>> Normally the supplied udev scripts do this for you.
>>>>>> cheers,
>>>>>> -dave
>>>>>>
>>>>>> On Fri, 8 Nov 2024, 05:24 Charles Lane, <la...@dc...> wrote:
>>>>>>
>>>>>>> Setting up the /dev/gpib* devices is something that
>>>>>>> you might want to look at udev for...but as I recall
>>>>>>> there's some problems. That isn't necessarily in the
>>>>>>> linux-gpib git project, maybe in linux-gpib-packaging
>>>>>>> project....where the idea is to wrap the linux-gpib
>>>>>>> code in an rpm package (so that installation deals
>>>>>>> with udev scripts, protection issues, etc)
>>>>>>>
>>>>>>> On Thu, 7 Nov 2024 09:51:32 -0700
>>>>>>> Michael Jaggers <mgj...@gm...> wrote:
>>>>>>>
>>>>>>> > Hello,
>>>>>>> >
>>>>>>> > I'm working on installing the gpib kernel drivers to the Petalinux
>>>>>>> > platform. So far, I've managed to get the headers and get the gpib
>>>>>>> > drivers compiled + installed. The modules show up with modprobe,
>>>>>>> and
>>>>>>> > when I plug my gpib dongle in the driver loads properly and it
>>>>>>> seems
>>>>>>> > to recognize it. Below is the message I get when plugging in the
>>>>>>> > dongle: [19163.768240] usb 1-1.4: new high-speed USB device number
>>>>>>> 11
>>>>>>> > using xhci-hcd [19164.020393] usb 1-1.4: config 1 interface 0
>>>>>>> > altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to
>>>>>>> 7
>>>>>>> > [19164.030876] usb 1-1.4: New USB device found, idVendor=3923,
>>>>>>> > idProduct=709b, bcdDevice= 1.01
>>>>>>> > [19164.039247] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
>>>>>>> > SerialNumber=3
>>>>>>> > [19164.046560] usb 1-1.4: Product: GPIB-USB-HS
>>>>>>> > [19164.050739] usb 1-1.4: Manufacturer: National Instruments
>>>>>>> > [19164.056138] usb 1-1.4: SerialNumber: 01D9F4A4
>>>>>>> >
>>>>>>> > Here is where the issue comes up. When ibopen goes to set things up
>>>>>>> > with the dongle, the /dev/gpib0 doesn't seem to be properly
>>>>>>> > configured. I get this message when I run the ibtest utility:
>>>>>>> > [84391.688217] gpib debug: pid 0, gpib: opening minor 0
>>>>>>> > [84391.696029] gpib debug: pid 0, gpib: request module returned 256
>>>>>>> > [84391.702071] gpib debug: pid 0, minor 0, ioctl 3, interface=,
>>>>>>> use=0,
>>>>>>> > onl=0, arg=d8a171a0
>>>>>>> > [84391.710090] gpib: no gpib board configured on /dev/gpib0
>>>>>>> > [84391.715398] gpib debug: pid 0, minor 0, ioctl 3, interface=,
>>>>>>> > use=0, onl=0 [84391.722212] gpib debug: pid 0, minor 0, ioctl 5,
>>>>>>> > interface=, use=0, onl=0, arg=d8a17120
>>>>>>> > [84391.730218] gpib: no gpib board configured on /dev/gpib0
>>>>>>> > [84391.735527] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>>>>>>> > use=0, onl=0 [84391.742357] gpib debug: pid 0, minor 0, ioctl 5,
>>>>>>> > interface=, use=0, onl=0, arg=d8a17180
>>>>>>> > [84391.750363] gpib: no gpib board configured on /dev/gpib0
>>>>>>> > [84391.755673] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>>>>>>> > use=0, onl=0 [84391.762675] audit: type=1701
>>>>>>> > audit(1730996390.861:20): auid=0 uid=0 gid=0 ses=2 pid=10840
>>>>>>> > comm="ibtest" exe="/usr/local/bin/ibtest" sig=6 res=1
>>>>>>> [84391.764574]
>>>>>>> > gpib debug: pid 0, gpib: closing minor 0
>>>>>>> >
>>>>>>> > I've been debugging this for a week or so now. I'm fairly confident
>>>>>>> > that the probing of the dongle works. In fact, when I find the
>>>>>>> dongle
>>>>>>> > in the sys path, I see that the module driver is in that path of
>>>>>>> the
>>>>>>> > device itself: root@tester0:~# ls -ll
>>>>>>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/ total 0
>>>>>>> > -rw-r--r-- 1 root root 4096 Nov  7 16:25 authorized
>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bAlternateSetting
>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceClass
>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceNumber
>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceProtocol
>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceSubClass
>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bNumEndpoints
>>>>>>> > lrwxrwxrwx 1 root root    0 Nov  7 16:25 driver ->
>>>>>>> > ../../../../../../../../../../bus/usb/drivers/ni_usb_gpib
>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_02
>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_06
>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_81
>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_84
>>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_88
>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 modalias
>>>>>>> > drwxr-xr-x 2 root root    0 Nov  7 16:25 power
>>>>>>> > lrwxrwxrwx 1 root root    0 Nov  7 16:18 subsystem ->
>>>>>>> > ../../../../../../../../../../bus/usb
>>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 supports_autosuspend
>>>>>>> > -rw-r--r-- 1 root root 4096 Nov  7 16:18 uevent
>>>>>>> >
>>>>>>> > root@tester0:~# grep ^
>>>>>>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/modalias
>>>>>>> > usb:*v3923p709B*d0101dc00dsc00dp00icFFisc00ip00in00
>>>>>>> >
>>>>>>> > The driver itself tells me that the interface registers properly
>>>>>>> too
>>>>>>> > (my apologies for the extra debug messages):
>>>>>>> > [85375.091233] ni_usb_gpib driver loading
>>>>>>> > [85375.098301] ni_usb_driver_probe
>>>>>>> > [85375.101436] set bus interface 0 to address 0x00000000bca009b3
>>>>>>> > [85375.107200] ni_usb_gpib: probe succeeded for path:
>>>>>>> > usb-xhci-hcd.1.auto-1.4
>>>>>>> > [85375.119145] usbcore: registered new interface driver ni_usb_gpib
>>>>>>> > [85375.128308] gpib: registered ni_usb_b interface
>>>>>>> >
>>>>>>> > However, everywhere I look in the code doesn't indicate to me where
>>>>>>> > the disconnect occurs. I'm fairly certain the issue is that the
>>>>>>> > /dev/gpib* section isn't pointing to the dongle area and that's my
>>>>>>> > problem. I've been trying to create a workaround to this that shows
>>>>>>> > the device working at all, but I'm not having any luck there.
>>>>>>> > So I'm at a loss for where to go next. Any suggestions? RIght now,
>>>>>>> I'm
>>>>>>> > trying to figure out why I'm getting "interface=". I feel like
>>>>>>> that's
>>>>>>> > the underlying problem, but I can't confirm it.
>>>>>>> > Just in case, here is some extra information about he system I'm
>>>>>>> on:
>>>>>>> > Operating System: PetaLinux 2023.2+update-61_04172258- (langdale)
>>>>>>> >           Kernel: Linux 6.1.30-xilinx-v2023.2
>>>>>>> >     Architecture: arm64
>>>>>>> >
>>>>>>> > Thanks,
>>>>>>> > Michael
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Drexel University  |/             /    ·   ν ·   Chuck Lane   |D
>>>>>>> ======]－－－>－－－C－－－－－π+－－<                Disque 911  |U
>>>>>>> Particle Physics    \             \    ~~ e+~~   215-895-1545 |N
>>>>>>> la...@dc...                    －​μ+－－+νν                 |E
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Linux-gpib-general mailing list
>>>>>>> Lin...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>>>>>>
>>>>>> _______________________________________________
>>>>>> Linux-gpib-general mailing list
>>>>>> Lin...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>>>>>
>>>>>

Re: [Linux-gpib-general] Petalinux Kernel Compatability

[Michael J. <mgj...@gm...>]

Yes, there is quite a bit in the console log. I have the debug turned on
(and added some statements in myself), but this is pretty much what happens
when I plug in the device:
[ 9748.976545] usb 1-1.4: new high-speed USB device number 5 using xhci-hcd
[ 9749.084858] usb 1-1.4: config 1 interface 0 altsetting 0 endpoint 0x81
has an invalid bInterval 0, changing to 7
[ 9749.095353] usb 1-1.4: New USB device found, idVendor=3923,
idProduct=709b, bcdDevice= 1.01
[ 9749.103769] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 9749.111094] usb 1-1.4: Product: GPIB-USB-HS
[ 9749.115289] usb 1-1.4: Manufacturer: National Instruments
[ 9749.120690] usb 1-1.4: SerialNumber: 01D9F4A4
[ 9749.210590] Linux-GPIB 4.3.6 Driver
[ 9749.386255] ni_usb_gpib driver loading
[ 9749.402265] ni_usb_gpib: probe succeeded for path:
usb-xhci-hcd.1.auto-1.4
[ 9749.414241] usbcore: registered new interface driver ni_usb_gpib
[ 9749.423413] gpib: registered ni_usb_b interface
[ 9749.927552] gpib debug: pid 0, gpib: opening minor 0
[ 9749.935625] gpib debug: pid 0, gpib: request module returned 256
[ 9749.942207] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
onl=0, arg=f523e908
[ 9749.970918] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
onl=0
[ 9749.978472] gpib debug: pid 0, gpib: closing minor 0
[ 9808.492473] gpib debug: pid 0, gpib: opening minor 0
[ 9808.500324] gpib debug: pid 0, gpib: request module returned 256
[ 9808.506433] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
onl=0, arg=fb3f8278

When I try to run "gpib_config", it only shows this line:
[11325.680770] gpib debug: pid 0, gpib: opening minor 0
[11325.688909] gpib debug: pid 0, gpib: request module returned 256
[11325.695036] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
onl=0, arg=ef9596d8
[11325.723526] gpib debug: pid 0, minor 0, ioctl 39, interface=, use=0,
onl=0
[11325.730940] gpib debug: pid 0, gpib: closing minor 0

Best Regards,
Michael

On Mon, Nov 11, 2024 at 1:28 PM dave penkler <dpe...@gm...> wrote:

> Hi Michael,
> The gpib.conf looks perfect. Somewhere during the configure we are getting
> an EFAULT - Bad address. This would point to some incompatibility between
> user space gpib_config and the gpib_common kernel module. Is there anything
> in the console log (dmesg) ?
> cheers,
> -dave
>
>
>
> On Tue, 12 Nov 2024, 05:28 Michael Jaggers, <mgj...@gm...> wrote:
>
>> Hey Dave,
>>
>> I went back and double checked on the configure argument you asked for,
>> and I did provide the path to it. I also checked it by putting a syntax
>> error into the gpib.conf file and that output an error and the path it was
>> pointing to.
>>
>> Here is the conf file that I'm using:
>>
>> /* This section configures the configurable driver characteristics
>>  * for an interface board, such as board address, and interrupt level.
>>  * minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1, etc.
>>  */
>>
>> interface {
>>     minor = 0
>>     board_type = "ni_usb_gpib"
>>     name = "gpib0"
>>     pad = 2
>>     timeout = T1s
>>     eos = 0x0A
>>     set-reos = yes
>>     set-bin = no
>>     master = yes
>>
>> }
>>
>> Thanks!
>> Michael
>>
>> On Sat, Nov 9, 2024 at 2:24 AM dave penkler <dpe...@gm...> wrote:
>>
>>> Hi Michael,
>>> It looks like a gpib.conf problem. Did you provide a sysconfdir argument
>>> to .configure ?
>>> Please send me your gpib.conf file.
>>> cheers,
>>> -dave
>>>
>>> On Sat, 9 Nov 2024, 04:38 Michael Jaggers, <mgj...@gm...> wrote:
>>>
>>>> Dave,
>>>>
>>>> I've run the gpib_config, but no luck on that end. Here is what happens
>>>> to me:
>>>> 1. First, I restart the device without plugging in the gpib (drivers
>>>> aren't loaded).
>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>> failed to open device file '/dev/gpib0'
>>>> main: No such file or directory
>>>>
>>>> 2. Now, I plug the gpib dongle in.
>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>> failed to bring board offline
>>>> failed to configure board
>>>> main: Bad address
>>>>
>>>> 3. Finally, I unplug the gpib dongle.
>>>> root@tester0:~/git/linux-gpib-git# gpib_config
>>>> failed to bring board offline
>>>> failed to configure board
>>>> main: Bad address
>>>>
>>>> To me, this looks like the dongle isn't attaching to /dev/gpib0. I know
>>>> the driver recognizes the device, it correctly starts the ni_usb_gpib
>>>> driver, and probes the correct location on the device tree, and the driver
>>>> in the device tree points to the correct place the dongle is attached to.
>>>> What's got me scratching my head is why it's not attached to gpib0 (or even
>>>> how to circumvent the need to attach to gpib0).
>>>>
>>>> Could it be related to my udev? In the rules, in file
>>>> "/etc/udev/rules.d/98-gpib-generic.rules" I added:
>>>> ACTION=="add|change",
>>>> DEVPATH=="/devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0",
>>>> ENV{GPIB_CONFIG_OPTIONS}="--minor 0"
>>>>
>>>> That's the path that udev recognizes. When I run udevadm monitor, I get
>>>> this after plugging in the dongle:
>>>> KERNEL[1122.600699] add
>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>> (usb)
>>>> KERNEL[1122.650504] add
>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>> (usb)
>>>> KERNEL[1122.671551] bind
>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>> (usb)
>>>> KERNEL[1122.671684] bind
>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>> (usb)
>>>> UDEV  [1122.676333] add
>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>> (usb)
>>>> UDEV  [1122.769461] add
>>>> /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>> (usb)
>>>> UDEV  [1122.772939] bind
>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
>>>> (usb)
>>>> UDEV  [1122.777553] bind
>>>>  /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
>>>> (usb)
>>>>
>>>> Could the version of udev be the cause?
>>>> root@tester0:~/git/linux-gpib-git# udevd --version
>>>> 251.8+
>>>> root@tester0:~/git/linux-gpib-git# udevadm --version
>>>> 251
>>>>
>>>> Thanks for your responses!
>>>> Michael
>>>>
>>>> On Thu, Nov 7, 2024 at 9:04 PM dave penkler <dpe...@gm...> wrote:
>>>>
>>>>> It looks like the board is not attached. Did you run # gpib_config ?
>>>>> Normally the supplied udev scripts do this for you.
>>>>> cheers,
>>>>> -dave
>>>>>
>>>>> On Fri, 8 Nov 2024, 05:24 Charles Lane, <la...@dc...> wrote:
>>>>>
>>>>>> Setting up the /dev/gpib* devices is something that
>>>>>> you might want to look at udev for...but as I recall
>>>>>> there's some problems. That isn't necessarily in the
>>>>>> linux-gpib git project, maybe in linux-gpib-packaging
>>>>>> project....where the idea is to wrap the linux-gpib
>>>>>> code in an rpm package (so that installation deals
>>>>>> with udev scripts, protection issues, etc)
>>>>>>
>>>>>> On Thu, 7 Nov 2024 09:51:32 -0700
>>>>>> Michael Jaggers <mgj...@gm...> wrote:
>>>>>>
>>>>>> > Hello,
>>>>>> >
>>>>>> > I'm working on installing the gpib kernel drivers to the Petalinux
>>>>>> > platform. So far, I've managed to get the headers and get the gpib
>>>>>> > drivers compiled + installed. The modules show up with modprobe, and
>>>>>> > when I plug my gpib dongle in the driver loads properly and it seems
>>>>>> > to recognize it. Below is the message I get when plugging in the
>>>>>> > dongle: [19163.768240] usb 1-1.4: new high-speed USB device number
>>>>>> 11
>>>>>> > using xhci-hcd [19164.020393] usb 1-1.4: config 1 interface 0
>>>>>> > altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to 7
>>>>>> > [19164.030876] usb 1-1.4: New USB device found, idVendor=3923,
>>>>>> > idProduct=709b, bcdDevice= 1.01
>>>>>> > [19164.039247] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
>>>>>> > SerialNumber=3
>>>>>> > [19164.046560] usb 1-1.4: Product: GPIB-USB-HS
>>>>>> > [19164.050739] usb 1-1.4: Manufacturer: National Instruments
>>>>>> > [19164.056138] usb 1-1.4: SerialNumber: 01D9F4A4
>>>>>> >
>>>>>> > Here is where the issue comes up. When ibopen goes to set things up
>>>>>> > with the dongle, the /dev/gpib0 doesn't seem to be properly
>>>>>> > configured. I get this message when I run the ibtest utility:
>>>>>> > [84391.688217] gpib debug: pid 0, gpib: opening minor 0
>>>>>> > [84391.696029] gpib debug: pid 0, gpib: request module returned 256
>>>>>> > [84391.702071] gpib debug: pid 0, minor 0, ioctl 3, interface=,
>>>>>> use=0,
>>>>>> > onl=0, arg=d8a171a0
>>>>>> > [84391.710090] gpib: no gpib board configured on /dev/gpib0
>>>>>> > [84391.715398] gpib debug: pid 0, minor 0, ioctl 3, interface=,
>>>>>> > use=0, onl=0 [84391.722212] gpib debug: pid 0, minor 0, ioctl 5,
>>>>>> > interface=, use=0, onl=0, arg=d8a17120
>>>>>> > [84391.730218] gpib: no gpib board configured on /dev/gpib0
>>>>>> > [84391.735527] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>>>>>> > use=0, onl=0 [84391.742357] gpib debug: pid 0, minor 0, ioctl 5,
>>>>>> > interface=, use=0, onl=0, arg=d8a17180
>>>>>> > [84391.750363] gpib: no gpib board configured on /dev/gpib0
>>>>>> > [84391.755673] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>>>>>> > use=0, onl=0 [84391.762675] audit: type=1701
>>>>>> > audit(1730996390.861:20): auid=0 uid=0 gid=0 ses=2 pid=10840
>>>>>> > comm="ibtest" exe="/usr/local/bin/ibtest" sig=6 res=1 [84391.764574]
>>>>>> > gpib debug: pid 0, gpib: closing minor 0
>>>>>> >
>>>>>> > I've been debugging this for a week or so now. I'm fairly confident
>>>>>> > that the probing of the dongle works. In fact, when I find the
>>>>>> dongle
>>>>>> > in the sys path, I see that the module driver is in that path of the
>>>>>> > device itself: root@tester0:~# ls -ll
>>>>>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/ total 0
>>>>>> > -rw-r--r-- 1 root root 4096 Nov  7 16:25 authorized
>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bAlternateSetting
>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceClass
>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceNumber
>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceProtocol
>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceSubClass
>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bNumEndpoints
>>>>>> > lrwxrwxrwx 1 root root    0 Nov  7 16:25 driver ->
>>>>>> > ../../../../../../../../../../bus/usb/drivers/ni_usb_gpib
>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_02
>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_06
>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_81
>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_84
>>>>>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_88
>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 modalias
>>>>>> > drwxr-xr-x 2 root root    0 Nov  7 16:25 power
>>>>>> > lrwxrwxrwx 1 root root    0 Nov  7 16:18 subsystem ->
>>>>>> > ../../../../../../../../../../bus/usb
>>>>>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 supports_autosuspend
>>>>>> > -rw-r--r-- 1 root root 4096 Nov  7 16:18 uevent
>>>>>> >
>>>>>> > root@tester0:~# grep ^
>>>>>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/modalias
>>>>>> > usb:*v3923p709B*d0101dc00dsc00dp00icFFisc00ip00in00
>>>>>> >
>>>>>> > The driver itself tells me that the interface registers properly too
>>>>>> > (my apologies for the extra debug messages):
>>>>>> > [85375.091233] ni_usb_gpib driver loading
>>>>>> > [85375.098301] ni_usb_driver_probe
>>>>>> > [85375.101436] set bus interface 0 to address 0x00000000bca009b3
>>>>>> > [85375.107200] ni_usb_gpib: probe succeeded for path:
>>>>>> > usb-xhci-hcd.1.auto-1.4
>>>>>> > [85375.119145] usbcore: registered new interface driver ni_usb_gpib
>>>>>> > [85375.128308] gpib: registered ni_usb_b interface
>>>>>> >
>>>>>> > However, everywhere I look in the code doesn't indicate to me where
>>>>>> > the disconnect occurs. I'm fairly certain the issue is that the
>>>>>> > /dev/gpib* section isn't pointing to the dongle area and that's my
>>>>>> > problem. I've been trying to create a workaround to this that shows
>>>>>> > the device working at all, but I'm not having any luck there.
>>>>>> > So I'm at a loss for where to go next. Any suggestions? RIght now,
>>>>>> I'm
>>>>>> > trying to figure out why I'm getting "interface=". I feel like
>>>>>> that's
>>>>>> > the underlying problem, but I can't confirm it.
>>>>>> > Just in case, here is some extra information about he system I'm on:
>>>>>> > Operating System: PetaLinux 2023.2+update-61_04172258- (langdale)
>>>>>> >           Kernel: Linux 6.1.30-xilinx-v2023.2
>>>>>> >     Architecture: arm64
>>>>>> >
>>>>>> > Thanks,
>>>>>> > Michael
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Drexel University  |/             /    ·   ν ·   Chuck Lane   |D
>>>>>> ======]－－－>－－－C－－－－－π+－－<                Disque 911  |U
>>>>>> Particle Physics    \             \    ~~ e+~~   215-895-1545 |N
>>>>>> la...@dc...                    －​μ+－－+νν                 |E
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Linux-gpib-general mailing list
>>>>>> Lin...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>>>>>
>>>>> _______________________________________________
>>>>> Linux-gpib-general mailing list
>>>>> Lin...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>>>>
>>>>

Re: [Linux-gpib-general] Petalinux Kernel Compatability

[Michael J. <mgj...@gm...>]

+ Mailing List
Dave,

I've run the gpib_config, but no luck on that end. Here is what happens to
me:
1. First, I restart the device without plugging in the gpib (drivers aren't
loaded).
root@tester0:~/git/linux-gpib-git# gpib_config
failed to open device file '/dev/gpib0'
main: No such file or directory

2. Now, I plug the gpib dongle in.
root@tester0:~/git/linux-gpib-git# gpib_config
failed to bring board offline
failed to configure board
main: Bad address

3. Finally, I unplug the gpib dongle.
root@tester0:~/git/linux-gpib-git# gpib_config
failed to bring board offline
failed to configure board
main: Bad address

To me, this looks like the dongle isn't attaching to /dev/gpib0. I know the
driver recognizes the device, it correctly starts the ni_usb_gpib driver,
and probes the correct location on the device tree, and the driver in the
device tree points to the correct place the dongle is attached to. What's
got me scratching my head is why it's not attached to gpib0 (or even how to
circumvent the need to attach to gpib0).

Could it be related to my udev? In the rules, in file
"/etc/udev/rules.d/98-gpib-generic.rules" I added:
ACTION=="add|change",
DEVPATH=="/devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0",
ENV{GPIB_CONFIG_OPTIONS}="--minor 0"

That's the path that udev recognizes. When I run udevadm monitor, I get
this after plugging in the dongle:
KERNEL[1122.600699] add
/devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
(usb)
KERNEL[1122.650504] add
/devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
(usb)
KERNEL[1122.671551] bind
 /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
(usb)
KERNEL[1122.671684] bind
 /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
(usb)
UDEV  [1122.676333] add
/devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
(usb)
UDEV  [1122.769461] add
/devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
(usb)
UDEV  [1122.772939] bind
 /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4/1-1.4:1.0
(usb)
UDEV  [1122.777553] bind
 /devices/platform/axi/ff9d0000.usb/fe200000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.4
(usb)

Could the version of udev be the cause?
root@tester0:~/git/linux-gpib-git# udevd --version
251.8+
root@tester0:~/git/linux-gpib-git# udevadm --version
251

Thanks for your responses!
Michael

On Thu, Nov 7, 2024 at 9:04 PM dave penkler <dpe...@gm...> wrote:

> It looks like the board is not attached. Did you run # gpib_config ?
> Normally the supplied udev scripts do this for you.
> cheers,
> -dave
>
> On Fri, 8 Nov 2024, 05:24 Charles Lane, <la...@dc...> wrote:
>
>> Setting up the /dev/gpib* devices is something that
>> you might want to look at udev for...but as I recall
>> there's some problems. That isn't necessarily in the
>> linux-gpib git project, maybe in linux-gpib-packaging
>> project....where the idea is to wrap the linux-gpib
>> code in an rpm package (so that installation deals
>> with udev scripts, protection issues, etc)
>>
>> On Thu, 7 Nov 2024 09:51:32 -0700
>> Michael Jaggers <mgj...@gm...> wrote:
>>
>> > Hello,
>> >
>> > I'm working on installing the gpib kernel drivers to the Petalinux
>> > platform. So far, I've managed to get the headers and get the gpib
>> > drivers compiled + installed. The modules show up with modprobe, and
>> > when I plug my gpib dongle in the driver loads properly and it seems
>> > to recognize it. Below is the message I get when plugging in the
>> > dongle: [19163.768240] usb 1-1.4: new high-speed USB device number 11
>> > using xhci-hcd [19164.020393] usb 1-1.4: config 1 interface 0
>> > altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to 7
>> > [19164.030876] usb 1-1.4: New USB device found, idVendor=3923,
>> > idProduct=709b, bcdDevice= 1.01
>> > [19164.039247] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
>> > SerialNumber=3
>> > [19164.046560] usb 1-1.4: Product: GPIB-USB-HS
>> > [19164.050739] usb 1-1.4: Manufacturer: National Instruments
>> > [19164.056138] usb 1-1.4: SerialNumber: 01D9F4A4
>> >
>> > Here is where the issue comes up. When ibopen goes to set things up
>> > with the dongle, the /dev/gpib0 doesn't seem to be properly
>> > configured. I get this message when I run the ibtest utility:
>> > [84391.688217] gpib debug: pid 0, gpib: opening minor 0
>> > [84391.696029] gpib debug: pid 0, gpib: request module returned 256
>> > [84391.702071] gpib debug: pid 0, minor 0, ioctl 3, interface=, use=0,
>> > onl=0, arg=d8a171a0
>> > [84391.710090] gpib: no gpib board configured on /dev/gpib0
>> > [84391.715398] gpib debug: pid 0, minor 0, ioctl 3, interface=,
>> > use=0, onl=0 [84391.722212] gpib debug: pid 0, minor 0, ioctl 5,
>> > interface=, use=0, onl=0, arg=d8a17120
>> > [84391.730218] gpib: no gpib board configured on /dev/gpib0
>> > [84391.735527] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>> > use=0, onl=0 [84391.742357] gpib debug: pid 0, minor 0, ioctl 5,
>> > interface=, use=0, onl=0, arg=d8a17180
>> > [84391.750363] gpib: no gpib board configured on /dev/gpib0
>> > [84391.755673] gpib debug: pid 0, minor 0, ioctl 5, interface=,
>> > use=0, onl=0 [84391.762675] audit: type=1701
>> > audit(1730996390.861:20): auid=0 uid=0 gid=0 ses=2 pid=10840
>> > comm="ibtest" exe="/usr/local/bin/ibtest" sig=6 res=1 [84391.764574]
>> > gpib debug: pid 0, gpib: closing minor 0
>> >
>> > I've been debugging this for a week or so now. I'm fairly confident
>> > that the probing of the dongle works. In fact, when I find the dongle
>> > in the sys path, I see that the module driver is in that path of the
>> > device itself: root@tester0:~# ls -ll
>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/ total 0
>> > -rw-r--r-- 1 root root 4096 Nov  7 16:25 authorized
>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bAlternateSetting
>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceClass
>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceNumber
>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceProtocol
>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceSubClass
>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bNumEndpoints
>> > lrwxrwxrwx 1 root root    0 Nov  7 16:25 driver ->
>> > ../../../../../../../../../../bus/usb/drivers/ni_usb_gpib
>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_02
>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_06
>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_81
>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_84
>> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_88
>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 modalias
>> > drwxr-xr-x 2 root root    0 Nov  7 16:25 power
>> > lrwxrwxrwx 1 root root    0 Nov  7 16:18 subsystem ->
>> > ../../../../../../../../../../bus/usb
>> > -r--r--r-- 1 root root 4096 Nov  7 16:25 supports_autosuspend
>> > -rw-r--r-- 1 root root 4096 Nov  7 16:18 uevent
>> >
>> > root@tester0:~# grep ^
>> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/modalias
>> > usb:*v3923p709B*d0101dc00dsc00dp00icFFisc00ip00in00
>> >
>> > The driver itself tells me that the interface registers properly too
>> > (my apologies for the extra debug messages):
>> > [85375.091233] ni_usb_gpib driver loading
>> > [85375.098301] ni_usb_driver_probe
>> > [85375.101436] set bus interface 0 to address 0x00000000bca009b3
>> > [85375.107200] ni_usb_gpib: probe succeeded for path:
>> > usb-xhci-hcd.1.auto-1.4
>> > [85375.119145] usbcore: registered new interface driver ni_usb_gpib
>> > [85375.128308] gpib: registered ni_usb_b interface
>> >
>> > However, everywhere I look in the code doesn't indicate to me where
>> > the disconnect occurs. I'm fairly certain the issue is that the
>> > /dev/gpib* section isn't pointing to the dongle area and that's my
>> > problem. I've been trying to create a workaround to this that shows
>> > the device working at all, but I'm not having any luck there.
>> > So I'm at a loss for where to go next. Any suggestions? RIght now, I'm
>> > trying to figure out why I'm getting "interface=". I feel like that's
>> > the underlying problem, but I can't confirm it.
>> > Just in case, here is some extra information about he system I'm on:
>> > Operating System: PetaLinux 2023.2+update-61_04172258- (langdale)
>> >           Kernel: Linux 6.1.30-xilinx-v2023.2
>> >     Architecture: arm64
>> >
>> > Thanks,
>> > Michael
>>
>>
>>
>> --
>> Drexel University  |/             /    ·   ν ·   Chuck Lane   |D
>> ======]－－－>－－－C－－－－－π+－－<                Disque 911  |U
>> Particle Physics    \             \    ~~ e+~~   215-895-1545 |N
>> la...@dc...                    －​μ+－－+νν                 |E
>>
>>
>> _______________________________________________
>> Linux-gpib-general mailing list
>> Lin...@li...
>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Petalinux Kernel Compatability

[Michael J. <mgj...@gm...>]

+Mailing List
Charles,

I'm okay with circumventing the /dev/gpib* area if possible. I've only
checked out tag 4.3.6 of linux-gpib, so if that includes the packaging then
that might be where that's coming from. I'm not set on having that area,
and overall I'm pretty flexible on possible ideas for troubleshooting.
I tried to see if I could maybe go back to an earlier version of the
project, but I'm not sure which one would support my kernel and I only
found a reference to when the project was updated to support the latest
linux kernel.

On Thu, Nov 7, 2024 at 11:54 AM Charles Lane <la...@dc...> wrote:

> Setting up the /dev/gpib* devices is something that
> you might want to look at udev for...but as I recall
> there's some problems. That isn't necessarily in the
> linux-gpib git project, maybe in linux-gpib-packaging
> project....where the idea is to wrap the linux-gpib
> code in an rpm package (so that installation deals
> with udev scripts, protection issues, etc)
>
> On Thu, 7 Nov 2024 09:51:32 -0700
> Michael Jaggers <mgj...@gm...> wrote:
>
> > Hello,
> >
> > I'm working on installing the gpib kernel drivers to the Petalinux
> > platform. So far, I've managed to get the headers and get the gpib
> > drivers compiled + installed. The modules show up with modprobe, and
> > when I plug my gpib dongle in the driver loads properly and it seems
> > to recognize it. Below is the message I get when plugging in the
> > dongle: [19163.768240] usb 1-1.4: new high-speed USB device number 11
> > using xhci-hcd [19164.020393] usb 1-1.4: config 1 interface 0
> > altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to 7
> > [19164.030876] usb 1-1.4: New USB device found, idVendor=3923,
> > idProduct=709b, bcdDevice= 1.01
> > [19164.039247] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=3
> > [19164.046560] usb 1-1.4: Product: GPIB-USB-HS
> > [19164.050739] usb 1-1.4: Manufacturer: National Instruments
> > [19164.056138] usb 1-1.4: SerialNumber: 01D9F4A4
> >
> > Here is where the issue comes up. When ibopen goes to set things up
> > with the dongle, the /dev/gpib0 doesn't seem to be properly
> > configured. I get this message when I run the ibtest utility:
> > [84391.688217] gpib debug: pid 0, gpib: opening minor 0
> > [84391.696029] gpib debug: pid 0, gpib: request module returned 256
> > [84391.702071] gpib debug: pid 0, minor 0, ioctl 3, interface=, use=0,
> > onl=0, arg=d8a171a0
> > [84391.710090] gpib: no gpib board configured on /dev/gpib0
> > [84391.715398] gpib debug: pid 0, minor 0, ioctl 3, interface=,
> > use=0, onl=0 [84391.722212] gpib debug: pid 0, minor 0, ioctl 5,
> > interface=, use=0, onl=0, arg=d8a17120
> > [84391.730218] gpib: no gpib board configured on /dev/gpib0
> > [84391.735527] gpib debug: pid 0, minor 0, ioctl 5, interface=,
> > use=0, onl=0 [84391.742357] gpib debug: pid 0, minor 0, ioctl 5,
> > interface=, use=0, onl=0, arg=d8a17180
> > [84391.750363] gpib: no gpib board configured on /dev/gpib0
> > [84391.755673] gpib debug: pid 0, minor 0, ioctl 5, interface=,
> > use=0, onl=0 [84391.762675] audit: type=1701
> > audit(1730996390.861:20): auid=0 uid=0 gid=0 ses=2 pid=10840
> > comm="ibtest" exe="/usr/local/bin/ibtest" sig=6 res=1 [84391.764574]
> > gpib debug: pid 0, gpib: closing minor 0
> >
> > I've been debugging this for a week or so now. I'm fairly confident
> > that the probing of the dongle works. In fact, when I find the dongle
> > in the sys path, I see that the module driver is in that path of the
> > device itself: root@tester0:~# ls -ll
> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/ total 0
> > -rw-r--r-- 1 root root 4096 Nov  7 16:25 authorized
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bAlternateSetting
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceClass
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceNumber
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceProtocol
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceSubClass
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bNumEndpoints
> > lrwxrwxrwx 1 root root    0 Nov  7 16:25 driver ->
> > ../../../../../../../../../../bus/usb/drivers/ni_usb_gpib
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_02
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_06
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_81
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_84
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_88
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 modalias
> > drwxr-xr-x 2 root root    0 Nov  7 16:25 power
> > lrwxrwxrwx 1 root root    0 Nov  7 16:18 subsystem ->
> > ../../../../../../../../../../bus/usb
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 supports_autosuspend
> > -rw-r--r-- 1 root root 4096 Nov  7 16:18 uevent
> >
> > root@tester0:~# grep ^
> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/modalias
> > usb:*v3923p709B*d0101dc00dsc00dp00icFFisc00ip00in00
> >
> > The driver itself tells me that the interface registers properly too
> > (my apologies for the extra debug messages):
> > [85375.091233] ni_usb_gpib driver loading
> > [85375.098301] ni_usb_driver_probe
> > [85375.101436] set bus interface 0 to address 0x00000000bca009b3
> > [85375.107200] ni_usb_gpib: probe succeeded for path:
> > usb-xhci-hcd.1.auto-1.4
> > [85375.119145] usbcore: registered new interface driver ni_usb_gpib
> > [85375.128308] gpib: registered ni_usb_b interface
> >
> > However, everywhere I look in the code doesn't indicate to me where
> > the disconnect occurs. I'm fairly certain the issue is that the
> > /dev/gpib* section isn't pointing to the dongle area and that's my
> > problem. I've been trying to create a workaround to this that shows
> > the device working at all, but I'm not having any luck there.
> > So I'm at a loss for where to go next. Any suggestions? RIght now, I'm
> > trying to figure out why I'm getting "interface=". I feel like that's
> > the underlying problem, but I can't confirm it.
> > Just in case, here is some extra information about he system I'm on:
> > Operating System: PetaLinux 2023.2+update-61_04172258- (langdale)
> >           Kernel: Linux 6.1.30-xilinx-v2023.2
> >     Architecture: arm64
> >
> > Thanks,
> > Michael
>
>
>
> --
> Drexel University  |/             /    ·   ν ·   Chuck Lane   |D
> ======]－－－>－－－C－－－－－π+－－<                Disque 911  |U
> Particle Physics    \             \    ~~ e+~~   215-895-1545 |N
> la...@dc...                    －​μ+－－+νν                 |E
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Petalinux Kernel Compatability

[dave p. <dpe...@gm...>]

It looks like the board is not attached. Did you run # gpib_config ?
Normally the supplied udev scripts do this for you.
cheers,
-dave

On Fri, 8 Nov 2024, 05:24 Charles Lane, <la...@dc...> wrote:

> Setting up the /dev/gpib* devices is something that
> you might want to look at udev for...but as I recall
> there's some problems. That isn't necessarily in the
> linux-gpib git project, maybe in linux-gpib-packaging
> project....where the idea is to wrap the linux-gpib
> code in an rpm package (so that installation deals
> with udev scripts, protection issues, etc)
>
> On Thu, 7 Nov 2024 09:51:32 -0700
> Michael Jaggers <mgj...@gm...> wrote:
>
> > Hello,
> >
> > I'm working on installing the gpib kernel drivers to the Petalinux
> > platform. So far, I've managed to get the headers and get the gpib
> > drivers compiled + installed. The modules show up with modprobe, and
> > when I plug my gpib dongle in the driver loads properly and it seems
> > to recognize it. Below is the message I get when plugging in the
> > dongle: [19163.768240] usb 1-1.4: new high-speed USB device number 11
> > using xhci-hcd [19164.020393] usb 1-1.4: config 1 interface 0
> > altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to 7
> > [19164.030876] usb 1-1.4: New USB device found, idVendor=3923,
> > idProduct=709b, bcdDevice= 1.01
> > [19164.039247] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=3
> > [19164.046560] usb 1-1.4: Product: GPIB-USB-HS
> > [19164.050739] usb 1-1.4: Manufacturer: National Instruments
> > [19164.056138] usb 1-1.4: SerialNumber: 01D9F4A4
> >
> > Here is where the issue comes up. When ibopen goes to set things up
> > with the dongle, the /dev/gpib0 doesn't seem to be properly
> > configured. I get this message when I run the ibtest utility:
> > [84391.688217] gpib debug: pid 0, gpib: opening minor 0
> > [84391.696029] gpib debug: pid 0, gpib: request module returned 256
> > [84391.702071] gpib debug: pid 0, minor 0, ioctl 3, interface=, use=0,
> > onl=0, arg=d8a171a0
> > [84391.710090] gpib: no gpib board configured on /dev/gpib0
> > [84391.715398] gpib debug: pid 0, minor 0, ioctl 3, interface=,
> > use=0, onl=0 [84391.722212] gpib debug: pid 0, minor 0, ioctl 5,
> > interface=, use=0, onl=0, arg=d8a17120
> > [84391.730218] gpib: no gpib board configured on /dev/gpib0
> > [84391.735527] gpib debug: pid 0, minor 0, ioctl 5, interface=,
> > use=0, onl=0 [84391.742357] gpib debug: pid 0, minor 0, ioctl 5,
> > interface=, use=0, onl=0, arg=d8a17180
> > [84391.750363] gpib: no gpib board configured on /dev/gpib0
> > [84391.755673] gpib debug: pid 0, minor 0, ioctl 5, interface=,
> > use=0, onl=0 [84391.762675] audit: type=1701
> > audit(1730996390.861:20): auid=0 uid=0 gid=0 ses=2 pid=10840
> > comm="ibtest" exe="/usr/local/bin/ibtest" sig=6 res=1 [84391.764574]
> > gpib debug: pid 0, gpib: closing minor 0
> >
> > I've been debugging this for a week or so now. I'm fairly confident
> > that the probing of the dongle works. In fact, when I find the dongle
> > in the sys path, I see that the module driver is in that path of the
> > device itself: root@tester0:~# ls -ll
> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/ total 0
> > -rw-r--r-- 1 root root 4096 Nov  7 16:25 authorized
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bAlternateSetting
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceClass
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceNumber
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceProtocol
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceSubClass
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 bNumEndpoints
> > lrwxrwxrwx 1 root root    0 Nov  7 16:25 driver ->
> > ../../../../../../../../../../bus/usb/drivers/ni_usb_gpib
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_02
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_06
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_81
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_84
> > drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_88
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 modalias
> > drwxr-xr-x 2 root root    0 Nov  7 16:25 power
> > lrwxrwxrwx 1 root root    0 Nov  7 16:18 subsystem ->
> > ../../../../../../../../../../bus/usb
> > -r--r--r-- 1 root root 4096 Nov  7 16:25 supports_autosuspend
> > -rw-r--r-- 1 root root 4096 Nov  7 16:18 uevent
> >
> > root@tester0:~# grep ^
> > /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/modalias
> > usb:*v3923p709B*d0101dc00dsc00dp00icFFisc00ip00in00
> >
> > The driver itself tells me that the interface registers properly too
> > (my apologies for the extra debug messages):
> > [85375.091233] ni_usb_gpib driver loading
> > [85375.098301] ni_usb_driver_probe
> > [85375.101436] set bus interface 0 to address 0x00000000bca009b3
> > [85375.107200] ni_usb_gpib: probe succeeded for path:
> > usb-xhci-hcd.1.auto-1.4
> > [85375.119145] usbcore: registered new interface driver ni_usb_gpib
> > [85375.128308] gpib: registered ni_usb_b interface
> >
> > However, everywhere I look in the code doesn't indicate to me where
> > the disconnect occurs. I'm fairly certain the issue is that the
> > /dev/gpib* section isn't pointing to the dongle area and that's my
> > problem. I've been trying to create a workaround to this that shows
> > the device working at all, but I'm not having any luck there.
> > So I'm at a loss for where to go next. Any suggestions? RIght now, I'm
> > trying to figure out why I'm getting "interface=". I feel like that's
> > the underlying problem, but I can't confirm it.
> > Just in case, here is some extra information about he system I'm on:
> > Operating System: PetaLinux 2023.2+update-61_04172258- (langdale)
> >           Kernel: Linux 6.1.30-xilinx-v2023.2
> >     Architecture: arm64
> >
> > Thanks,
> > Michael
>
>
>
> --
> Drexel University  |/             /    ·   ν ·   Chuck Lane   |D
> ======]－－－>－－－C－－－－－π+－－<                Disque 911  |U
> Particle Physics    \             \    ~~ e+~~   215-895-1545 |N
> la...@dc...                    －​μ+－－+νν                 |E
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Petalinux Kernel Compatability

[Charles L. <la...@dc...>]

Setting up the /dev/gpib* devices is something that 
you might want to look at udev for...but as I recall 
there's some problems. That isn't necessarily in the
linux-gpib git project, maybe in linux-gpib-packaging
project....where the idea is to wrap the linux-gpib 
code in an rpm package (so that installation deals 
with udev scripts, protection issues, etc) 

On Thu, 7 Nov 2024 09:51:32 -0700
Michael Jaggers <mgj...@gm...> wrote:

> Hello,
> 
> I'm working on installing the gpib kernel drivers to the Petalinux
> platform. So far, I've managed to get the headers and get the gpib
> drivers compiled + installed. The modules show up with modprobe, and
> when I plug my gpib dongle in the driver loads properly and it seems
> to recognize it. Below is the message I get when plugging in the
> dongle: [19163.768240] usb 1-1.4: new high-speed USB device number 11
> using xhci-hcd [19164.020393] usb 1-1.4: config 1 interface 0
> altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to 7
> [19164.030876] usb 1-1.4: New USB device found, idVendor=3923,
> idProduct=709b, bcdDevice= 1.01
> [19164.039247] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [19164.046560] usb 1-1.4: Product: GPIB-USB-HS
> [19164.050739] usb 1-1.4: Manufacturer: National Instruments
> [19164.056138] usb 1-1.4: SerialNumber: 01D9F4A4
> 
> Here is where the issue comes up. When ibopen goes to set things up
> with the dongle, the /dev/gpib0 doesn't seem to be properly
> configured. I get this message when I run the ibtest utility:
> [84391.688217] gpib debug: pid 0, gpib: opening minor 0
> [84391.696029] gpib debug: pid 0, gpib: request module returned 256
> [84391.702071] gpib debug: pid 0, minor 0, ioctl 3, interface=, use=0,
> onl=0, arg=d8a171a0
> [84391.710090] gpib: no gpib board configured on /dev/gpib0
> [84391.715398] gpib debug: pid 0, minor 0, ioctl 3, interface=,
> use=0, onl=0 [84391.722212] gpib debug: pid 0, minor 0, ioctl 5,
> interface=, use=0, onl=0, arg=d8a17120
> [84391.730218] gpib: no gpib board configured on /dev/gpib0
> [84391.735527] gpib debug: pid 0, minor 0, ioctl 5, interface=,
> use=0, onl=0 [84391.742357] gpib debug: pid 0, minor 0, ioctl 5,
> interface=, use=0, onl=0, arg=d8a17180
> [84391.750363] gpib: no gpib board configured on /dev/gpib0
> [84391.755673] gpib debug: pid 0, minor 0, ioctl 5, interface=,
> use=0, onl=0 [84391.762675] audit: type=1701
> audit(1730996390.861:20): auid=0 uid=0 gid=0 ses=2 pid=10840
> comm="ibtest" exe="/usr/local/bin/ibtest" sig=6 res=1 [84391.764574]
> gpib debug: pid 0, gpib: closing minor 0
> 
> I've been debugging this for a week or so now. I'm fairly confident
> that the probing of the dongle works. In fact, when I find the dongle
> in the sys path, I see that the module driver is in that path of the
> device itself: root@tester0:~# ls -ll
> /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/ total 0
> -rw-r--r-- 1 root root 4096 Nov  7 16:25 authorized
> -r--r--r-- 1 root root 4096 Nov  7 16:25 bAlternateSetting
> -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceClass
> -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceNumber
> -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceProtocol
> -r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceSubClass
> -r--r--r-- 1 root root 4096 Nov  7 16:25 bNumEndpoints
> lrwxrwxrwx 1 root root    0 Nov  7 16:25 driver ->
> ../../../../../../../../../../bus/usb/drivers/ni_usb_gpib
> drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_02
> drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_06
> drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_81
> drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_84
> drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_88
> -r--r--r-- 1 root root 4096 Nov  7 16:25 modalias
> drwxr-xr-x 2 root root    0 Nov  7 16:25 power
> lrwxrwxrwx 1 root root    0 Nov  7 16:18 subsystem ->
> ../../../../../../../../../../bus/usb
> -r--r--r-- 1 root root 4096 Nov  7 16:25 supports_autosuspend
> -rw-r--r-- 1 root root 4096 Nov  7 16:18 uevent
> 
> root@tester0:~# grep ^
> /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/modalias
> usb:*v3923p709B*d0101dc00dsc00dp00icFFisc00ip00in00
> 
> The driver itself tells me that the interface registers properly too
> (my apologies for the extra debug messages):
> [85375.091233] ni_usb_gpib driver loading
> [85375.098301] ni_usb_driver_probe
> [85375.101436] set bus interface 0 to address 0x00000000bca009b3
> [85375.107200] ni_usb_gpib: probe succeeded for path:
> usb-xhci-hcd.1.auto-1.4
> [85375.119145] usbcore: registered new interface driver ni_usb_gpib
> [85375.128308] gpib: registered ni_usb_b interface
> 
> However, everywhere I look in the code doesn't indicate to me where
> the disconnect occurs. I'm fairly certain the issue is that the
> /dev/gpib* section isn't pointing to the dongle area and that's my
> problem. I've been trying to create a workaround to this that shows
> the device working at all, but I'm not having any luck there.
> So I'm at a loss for where to go next. Any suggestions? RIght now, I'm
> trying to figure out why I'm getting "interface=". I feel like that's
> the underlying problem, but I can't confirm it.
> Just in case, here is some extra information about he system I'm on:
> Operating System: PetaLinux 2023.2+update-61_04172258- (langdale)
>           Kernel: Linux 6.1.30-xilinx-v2023.2
>     Architecture: arm64
> 
> Thanks,
> Michael



-- 
Drexel University  |/             /    ·   ν ·   Chuck Lane   |D
======]－－－>－－－C－－－－－π+－－<                Disque 911  |U
Particle Physics    \             \    ~~ e+~~   215-895-1545 |N
la...@dc...                    －​μ+－－+νν                 |E

[Linux-gpib-general] Petalinux Kernel Compatability

[Michael J. <mgj...@gm...>]

Hello,

I'm working on installing the gpib kernel drivers to the Petalinux
platform. So far, I've managed to get the headers and get the gpib drivers
compiled + installed. The modules show up with modprobe, and when I plug my
gpib dongle in the driver loads properly and it seems to recognize it.
Below is the message I get when plugging in the dongle:
[19163.768240] usb 1-1.4: new high-speed USB device number 11 using xhci-hcd
[19164.020393] usb 1-1.4: config 1 interface 0 altsetting 0 endpoint 0x81
has an invalid bInterval 0, changing to 7
[19164.030876] usb 1-1.4: New USB device found, idVendor=3923,
idProduct=709b, bcdDevice= 1.01
[19164.039247] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[19164.046560] usb 1-1.4: Product: GPIB-USB-HS
[19164.050739] usb 1-1.4: Manufacturer: National Instruments
[19164.056138] usb 1-1.4: SerialNumber: 01D9F4A4

Here is where the issue comes up. When ibopen goes to set things up with
the dongle, the /dev/gpib0 doesn't seem to be properly configured. I get
this message when I run the ibtest utility:
[84391.688217] gpib debug: pid 0, gpib: opening minor 0
[84391.696029] gpib debug: pid 0, gpib: request module returned 256
[84391.702071] gpib debug: pid 0, minor 0, ioctl 3, interface=, use=0,
onl=0, arg=d8a171a0
[84391.710090] gpib: no gpib board configured on /dev/gpib0
[84391.715398] gpib debug: pid 0, minor 0, ioctl 3, interface=, use=0, onl=0
[84391.722212] gpib debug: pid 0, minor 0, ioctl 5, interface=, use=0,
onl=0, arg=d8a17120
[84391.730218] gpib: no gpib board configured on /dev/gpib0
[84391.735527] gpib debug: pid 0, minor 0, ioctl 5, interface=, use=0, onl=0
[84391.742357] gpib debug: pid 0, minor 0, ioctl 5, interface=, use=0,
onl=0, arg=d8a17180
[84391.750363] gpib: no gpib board configured on /dev/gpib0
[84391.755673] gpib debug: pid 0, minor 0, ioctl 5, interface=, use=0, onl=0
[84391.762675] audit: type=1701 audit(1730996390.861:20): auid=0 uid=0
gid=0 ses=2 pid=10840 comm="ibtest" exe="/usr/local/bin/ibtest" sig=6 res=1
[84391.764574] gpib debug: pid 0, gpib: closing minor 0

I've been debugging this for a week or so now. I'm fairly confident that
the probing of the dongle works. In fact, when I find the dongle in the sys
path, I see that the module driver is in that path of the device itself:
root@tester0:~# ls -ll /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/
total 0
-rw-r--r-- 1 root root 4096 Nov  7 16:25 authorized
-r--r--r-- 1 root root 4096 Nov  7 16:25 bAlternateSetting
-r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceClass
-r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceNumber
-r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceProtocol
-r--r--r-- 1 root root 4096 Nov  7 16:25 bInterfaceSubClass
-r--r--r-- 1 root root 4096 Nov  7 16:25 bNumEndpoints
lrwxrwxrwx 1 root root    0 Nov  7 16:25 driver ->
../../../../../../../../../../bus/usb/drivers/ni_usb_gpib
drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_02
drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_06
drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_81
drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_84
drwxr-xr-x 3 root root    0 Nov  7 16:25 ep_88
-r--r--r-- 1 root root 4096 Nov  7 16:25 modalias
drwxr-xr-x 2 root root    0 Nov  7 16:25 power
lrwxrwxrwx 1 root root    0 Nov  7 16:18 subsystem ->
../../../../../../../../../../bus/usb
-r--r--r-- 1 root root 4096 Nov  7 16:25 supports_autosuspend
-rw-r--r-- 1 root root 4096 Nov  7 16:18 uevent

root@tester0:~# grep ^  /sys/bus/usb/drivers/ni_usb_gpib/1-1.4\:1.0/modalias
usb:*v3923p709B*d0101dc00dsc00dp00icFFisc00ip00in00

The driver itself tells me that the interface registers properly too (my
apologies for the extra debug messages):
[85375.091233] ni_usb_gpib driver loading
[85375.098301] ni_usb_driver_probe
[85375.101436] set bus interface 0 to address 0x00000000bca009b3
[85375.107200] ni_usb_gpib: probe succeeded for path:
usb-xhci-hcd.1.auto-1.4
[85375.119145] usbcore: registered new interface driver ni_usb_gpib
[85375.128308] gpib: registered ni_usb_b interface

However, everywhere I look in the code doesn't indicate to me where the
disconnect occurs. I'm fairly certain the issue is that the /dev/gpib*
section isn't pointing to the dongle area and that's my problem. I've been
trying to create a workaround to this that shows the device working at all,
but I'm not having any luck there.
So I'm at a loss for where to go next. Any suggestions? RIght now, I'm
trying to figure out why I'm getting "interface=". I feel like that's the
underlying problem, but I can't confirm it.
Just in case, here is some extra information about he system I'm on:
Operating System: PetaLinux 2023.2+update-61_04172258- (langdale)
          Kernel: Linux 6.1.30-xilinx-v2023.2
    Architecture: arm64

Thanks,
Michael

Re: [Linux-gpib-general] WaitSRQ() or ibwait(dev, RQS)

[dave p. <dpe...@gm...>]

Using ibwait both with RQS for device and SRQI for board works fine.
/d

On Wed, 25 Sept 2024 at 13:41, Vladimir Vassilev via Linux-gpib-general <
lin...@li...> wrote:

> On 7/14/24 19:05, Michael Schwingen wrote:
>
> ...
> > I am unsure about SRQ interrupt handling, as I don't understand how this
> is
> > supposed to work and I can't test it, so I left that as-is.
> >
>
> We  would also like to put some resources into validation of the SRQ
> functionality.
>
> Would a testcase calling WaitSRQ() or ibwait(dev, RQS) and validating
> that the functions return when the SRQ line is pulled down by a peer be
> a sufficient test?
>
> /V
>
>
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] WaitSRQ() or ibwait(dev, RQS)

[Vladimir V. <vla...@li...>]

On 7/14/24 19:05, Michael Schwingen wrote:

...
> I am unsure about SRQ interrupt handling, as I don't understand how this is
> supposed to work and I can't test it, so I left that as-is.
>

We  would also like to put some resources into validation of the SRQ 
functionality.

Would a testcase calling WaitSRQ() or ibwait(dev, RQS) and validating 
that the functions return when the SRQ line is pulled down by a peer be 
a sufficient test?

/V

Re: [Linux-gpib-general] gpib_bitbang: problem with GPIO tables

[dave p. <dpe...@gm...>]

Hi Michael,
Yes that is normal - your Pi3 is probably based on a bcm2710 SoC which has
the same line-names as Pi4/5.
Raspberry Pi made a couple of Pi3 variants based on different SoCs. The
table labelled p3 is for the bcm2387 variant.
I should change the names of the table variables to be just 0,1 and 2 to
avoid confusion.
cheers,
-Dave

On Wed, 28 Aug 2024 at 19:00, Michael Schwingen <mi...@sc...>
wrote:

> On 28.08.24 15:37, dave penkler wrote:
> > Hi,
> > The tables come from the different RPi device trees. Earlier Pi3A+,
> > Pi3B+ based on bcm2837 had the same DT as Pi2B based on bcm2836 but
> > with gpio14 and 15 called TXD1 and RXD1 instead of TXD0 and RXD0 as
> > for the Pi2B. The bcm2710 and bcm2711 are all like table index 2. As
> > we have no clean way to test what system we are running on we try the
> > three different tables from the oldest to newest.
>
> That approach works fine for me - however, it feels strange that the Pi3
> uses the Pi4/5 table, while the attempt to use the Pi3 table fails.
>
> Is that normal?
>
>
> cu
>
> Michael
>
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] gpib_bitbang: problem with GPIO tables

[Michael S. <mi...@sc...>]

On 28.08.24 15:37, dave penkler wrote:
> Hi,
> The tables come from the different RPi device trees. Earlier Pi3A+, 
> Pi3B+ based on bcm2837 had the same DT as Pi2B based on bcm2836 but 
> with gpio14 and 15 called TXD1 and RXD1 instead of TXD0 and RXD0 as 
> for the Pi2B. The bcm2710 and bcm2711 are all like table index 2. As 
> we have no clean way to test what system we are running on we try the 
> three different tables from the oldest to newest.

That approach works fine for me - however, it feels strange that the Pi3 
uses the Pi4/5 table, while the attempt to use the Pi3 table fails.

Is that normal?


cu

Michael