Re: Fwd: Raspberry Pi Zero - GPIB
dave penkler <[email protected]> Wed, 4 Feb 2026 14:34:54 +0100
| Newsgroups | gmane.linux.hardware.gpib.general |
|---|---|
| Message-ID | <CAL=kjP3PjSykjQnP7t9+4RmmVAN9cQVPsbkNPD8uZugSZb=7Ag@mail.gmail.com> |
--===============7379424911103447265== Content-Type: multipart/alternative; boundary="000000000000b876920649ff9f64" --000000000000b876920649ff9f64 Content-Type: text/plain; charset="UTF-8" Hi Scott, There is an issue with your gpib.conf scott@hpib:/dev $ sudo gpib_config failed to configure boardtype: agilent_82357a failed to configure board main: Invalid argument Make sure that for minor = 0 board_type = "gpib_bitbang" like Marcello advised. cheers, -Dave On Tue, 3 Feb 2026 at 20:45, Scott Bouchard via Linux-gpib-general < [email protected]> wrote: > Hi Marcello, > > Thank you for the troubleshooting guidance, I got to 'sudo gpib_config' > before it went wrong. > > I have made a short log of the commands and outputs here: > https://scottbouch.com/tmp/hp-ib-pi-zero-troubleshooting-1.log > > Many thanks, Scott. > > > > On 03/02/2026 14:45 GMT marcello.carla via Linux-gpib-general < > [email protected]> wrote: > > > > > > Dear Scott, > > > > After a fresh reboot, check if the gpib modules are in the right place: > > > > ls -l /lib/modules/`uname -r`/gpib > > > > then load the gpib_bitbang module: > > > > sudo modprobe gpib_bitbang > > > > With a proper gpib.conf file in /etc/ or in /usr/local/etc/ (or in both), > > configure the driver: > > > > sudo gpib_config > > > > and set permissions for access by any user to the interface: > > > > sudo chmod 666 /dev/gpib0 > > > > Here is an example of the interface section in the gpib.conf file: > > > > interface { > > minor = 0 /* board index, minor = 0 uses /dev/gpib0, > > minor = 1 uses /dev/gpib1, etc. */ > > board_type = "gpib_bitbang" /* type of interface board > > being used */ > > name = "violet" /* optional name, allows you to get a board > > descriptor using ibfind() */ > > pad = 0 /* primary address of interface */ > > sad = 0 /* secondary address of interface */ > > timeout = T3s /* timeout for commands */ > > > > eos = 0x0a /* EOS Byte, 0xa is newline and 0xd is carriage > > return */ > > set-reos = yes /* Terminate read if EOS */ > > set-bin = no /* Compare EOS 8-bit */ > > set-xeos = no /* Assert EOI whenever EOS byte is sent */ > > set-eot = yes /* Assert EOI with last byte on writes */ > > > > /* settings for boards that lack plug-n-play capability */ > > base = 0 /* Base io ADDRESS */ > > irq = 0 /* Interrupt request level */ > > dma = 0 /* DMA channel (zero disables) */ > > > > /* pci_bus and pci_slot can be used to distinguish two pci boards > > supported by the same driver */ > > /* pci_bus = 0 */ > > /* pci_slot = 7 */ > > > > master = yes /* interface board is system controller */ > > } > > > > Let me know if and where this procedure fails. > > > > Good luck again! > > > > Marcello > > > > > > On 2/3/26 14:19, Scott Bouchard via Linux-gpib-general wrote: > > > Hi Michael, > > > > > > Thank you so much for the detailed instructions, and automation of the > commands where possible. this has been a great guide. > > > > > > I tried again from scratch by downloading and installing a fresh image > using the raspberry pi imager. > > > > > > I followed your guidance to the letter up to section 4.2 where I > encountered issues similar to before: > > > > > > scott@hpib:~ $ sudo ldconfig && sudo gpib_config > > > sudo: unable to resolve host hpib: Name or service not known > > > sudo: unable to resolve host hpib: Name or service not known > > > failed to open device file '/dev/gpib0' > > > main: No such file or directory > > > > > > And indeed, /dev has no gpib contents. > > > > > > One new issue of this installation is the hostname of the Raspberry > Pi... when I set it up I used "hpib" as it's hostname, but it didn't seem > to stop progress so I just carried on. > > > > > > I copied ALL terminal commands issued, along with their outputs into a > text file to hopefully help diagnosis, and I added my own //comments where > relevant. This log can be downloaded from here (too long to email): > https://scottbouch.com/tmp/hp-ib-pi-zero-setup.log > > > > > > > > > Many thanks again, Scott. > > > > > > > > > > > > > > > _______________________________________________ > > Linux-gpib-general mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > > > _______________________________________________ > Linux-gpib-general mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > --000000000000b876920649ff9f64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi Scott,<div>There is an issue with your gpib.conf=C2=A0<= /div><div><pre style=3D"color:rgb(0,0,0)">scott@hpib:/dev $ sudo gpib_confi= g failed to configure boardtype: agilent_82357a failed to configure board main: Invalid argument</pre></div><div>Make sure that for=C2=A0</div><div>m= inor =3D 0=C2=A0 =C2=A0 =C2=A0 =C2=A0</div><div>board_type =3D "gpib_b= itbang"</div><div>like Marcello advised.</div><div>cheers,</div><div>-= Dave</div><div><pre style=3D"color:rgb(0,0,0)"><br class=3D"gmail-Apple-int= erchange-newline"> </pre><br class=3D"gmail-Apple-interchange-newline"></div></div><br><div cl= ass=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_a= ttr">On Tue, 3 Feb 2026 at 20:45, Scott Bouchard via Linux-gpib-general <= ;<a href=3D"mailto:[email protected]">linux-gpib-gen= [email protected]</a>> wrote:<br></div><blockquote class=3D"gma= il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2= 04,204);padding-left:1ex">Hi Marcello,<br> <br> Thank you for the troubleshooting guidance, I got to 'sudo gpib_config&= #39; before it went wrong.<br> <br> I have made a short log of the commands and outputs here: <a href=3D"https:= //scottbouch.com/tmp/hp-ib-pi-zero-troubleshooting-1.log" rel=3D"noreferrer= " target=3D"_blank">https://scottbouch.com/tmp/hp-ib-pi-zero-troubleshootin= g-1.log</a><br> <br> Many thanks, Scott.<br> <br> <br> > On 03/02/2026 14:45 GMT marcello.carla via Linux-gpib-general <<a h= ref=3D"mailto:[email protected]" target=3D"_blank">l= [email protected]</a>> wrote:<br> > <br> >=C2=A0 <br> > Dear Scott,<br> > <br> > After a fresh reboot, check if the gpib modules are in the right place= :<br> > <br> >=C2=A0 =C2=A0 =C2=A0 ls -l /lib/modules/`uname -r`/gpib<br> > <br> > then load the gpib_bitbang module:<br> > <br> >=C2=A0 =C2=A0 =C2=A0 sudo modprobe gpib_bitbang<br> > <br> > With a proper gpib.conf file in /etc/ or in /usr/local/etc/ (or in bot= h),<br> > configure the driver:<br> > <br> >=C2=A0 =C2=A0 =C2=A0 sudo gpib_config<br> > <br> > and set permissions for access by any user to the interface:<br> > <br> >=C2=A0 =C2=A0 =C2=A0 sudo chmod 666 /dev/gpib0<br> > <br> > Here is an example of the interface section in the gpib.conf file:<br> > <br> > interface {<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 minor =3D 0=C2=A0 =C2=A0 =C2=A0 =C2= =A0/* board index, minor =3D 0 uses /dev/gpib0, <br> > minor =3D 1 uses /dev/gpib1, etc. */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 board_type =3D "gpib_bitbang&qu= ot;=C2=A0 =C2=A0 =C2=A0/* type of interface board <br> > being used */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 name =3D "violet" /* optio= nal name, allows you to get a board <br> > descriptor using ibfind() */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 pad =3D 0 /* primary address of inte= rface=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*/<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 sad =3D 0 /* secondary address of in= terface=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*/<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 timeout =3D T3s=C2=A0 =C2=A0/* timeo= ut for commands */<br> > <br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 eos =3D 0x0a=C2=A0 =C2=A0 =C2=A0 /* = EOS Byte, 0xa is newline and 0xd is carriage <br> > return */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 set-reos =3D yes=C2=A0 /* Terminate = read if EOS */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 set-bin =3D no=C2=A0 =C2=A0 /* Compa= re EOS 8-bit */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 set-xeos =3D no=C2=A0 =C2=A0/* Asser= t EOI whenever EOS byte is sent */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 set-eot =3D yes=C2=A0 =C2=A0/* Asser= t EOI with last byte on writes */<br> > <br> > /* settings for boards that lack plug-n-play capability */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 base =3D 0=C2=A0 =C2=A0 =C2=A0 =C2= =A0 /* Base io ADDRESS=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 irq=C2=A0 =3D 0=C2=A0 =C2=A0 =C2=A0 = =C2=A0 /* Interrupt request level */<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 dma=C2=A0 =3D 0=C2=A0 =C2=A0 =C2=A0 = =C2=A0 /* DMA channel (zero disables)=C2=A0 =C2=A0 =C2=A0 */<br> > <br> > /* pci_bus and pci_slot can be used to distinguish two pci boards <br> > supported by the same driver */<br> > /*=C2=A0 =C2=A0 =C2=A0 pci_bus =3D 0 */<br> > /*=C2=A0 =C2=A0 =C2=A0 pci_slot =3D 7 */<br> > <br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 master =3D yes=C2=A0 =C2=A0 /* inter= face board is system controller */<br> > }<br> > <br> > Let me know if and where this procedure fails.<br> > <br> > Good luck again!<br> > <br> > Marcello<br> > <br> > <br> > On 2/3/26 14:19, Scott Bouchard via Linux-gpib-general wrote:<br> > > Hi Michael,<br> > ><br> > > Thank you so much for the detailed instructions, and automation o= f the commands where possible. this has been a great guide.<br> > ><br> > > I tried again from scratch by downloading and installing a fresh = image using the raspberry pi imager.<br> > ><br> > > I followed your guidance to the letter up to section 4.2 where I = encountered issues similar to before:<br> > ><br> > > scott@hpib:~ $ sudo ldconfig && sudo gpib_config<br> > > sudo: unable to resolve host hpib: Name or service not known<br> > > sudo: unable to resolve host hpib: Name or service not known<br> > > failed to open device file '/dev/gpib0'<br> > > main: No such file or directory<br> > ><br> > > And indeed, /dev has no gpib contents.<br> > ><br> > > One new issue of this installation is the hostname of the Raspber= ry Pi... when I set it up I used "hpib" as it's hostname, but= it didn't seem to stop progress so I just carried on.<br> > ><br> > > I copied ALL terminal commands issued, along with their outputs i= nto a text file to hopefully help diagnosis, and I added my own //comments = where relevant. This log can be downloaded from here (too long to email): <= a href=3D"https://scottbouch.com/tmp/hp-ib-pi-zero-setup.log" rel=3D"norefe= rrer" target=3D"_blank">https://scottbouch.com/tmp/hp-ib-pi-zero-setup.log<= /a><br> > ><br> > ><br> > > Many thanks again, Scott.<br> > ><br> > ><br> > ><br> > <br> > <br> > _______________________________________________<br> > Linux-gpib-general mailing list<br> > <a href=3D"mailto:[email protected]" target=3D"= _blank">[email protected]</a><br> > <a href=3D"https://lists.sourceforge.net/lists/listinfo/linux-gpib-gen= eral" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/li= sts/listinfo/linux-gpib-general</a><br> <br> <br> _______________________________________________<br> Linux-gpib-general mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blan= k">[email protected]</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/linux-gpib-general"= rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/l= istinfo/linux-gpib-general</a><br> </blockquote></div> --000000000000b876920649ff9f64-- --===============7379424911103447265== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============7379424911103447265== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Linux-gpib-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-gpib-general --===============7379424911103447265==--