<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 25: Raspberry Pi 3 B+ and NI USB-GPIB-HS communication using linux gpib</title><link href="https://sourceforge.net/p/linux-gpib/support-requests/25/" rel="alternate"/><link href="https://sourceforge.net/p/linux-gpib/support-requests/25/feed.atom" rel="self"/><id>https://sourceforge.net/p/linux-gpib/support-requests/25/</id><updated>2019-06-21T21:05:32.721000Z</updated><subtitle>Recent changes to 25: Raspberry Pi 3 B+ and NI USB-GPIB-HS communication using linux gpib</subtitle><entry><title>#25 Raspberry Pi 3 B+ and NI USB-GPIB-HS communication using linux gpib</title><link href="https://sourceforge.net/p/linux-gpib/support-requests/25/?limit=25#213d" rel="alternate"/><published>2019-06-21T21:05:32.721000Z</published><updated>2019-06-21T21:05:32.721000Z</updated><author><name>Frank Mori Hess</name><uri>https://sourceforge.net/u/fmhess/</uri></author><id>https://sourceforge.net44224749feb0d5a30f7f30f37c828cc645bf0665</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The null dereference is happening in the kernel, gdb isn't going to be able to see anything after the call to ioctl().  The ioctl call will result in the ibioctl function getting called in the kernel module, that is why I suggested adding some printk in osfuncs.c.   Judging by your gdb output, you should see ibioctl() getting called with cmd parameter set to IBMUTEX, which should then result in a call to mutex_ioctl().&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#25 Raspberry Pi 3 B+ and NI USB-GPIB-HS communication using linux gpib</title><link href="https://sourceforge.net/p/linux-gpib/support-requests/25/?limit=25#49cd" rel="alternate"/><published>2019-06-21T16:02:09.929000Z</published><updated>2019-06-21T16:02:09.929000Z</updated><author><name>Giorgos Tsapparellas</name><uri>https://sourceforge.net/u/gtsapparellas18/</uri></author><id>https://sourceforge.net904fd5bfbd4ad8bdb6dfa50f0174bb3c4dce97df</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ok, so I was trying to debug using gdb and it seems that device (gpib-usb-hs) cannot be configured propoerly. See attached photo for the backtrace.&lt;/p&gt;
&lt;p&gt;I am also using linux-gpib 4.2.0 on a raspberry pi using a 4.19.50-v7+ kernel (the raspberrypi-kernel and raspberrypi-kernel-headers packages in Raspberrian).&lt;/p&gt;
&lt;p&gt;By the way, I have also tried communicating with the gpib-usb-hs on Windows with NI VISA tool and is working fine (so this is not a hardware fault!!).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#25 Raspberry Pi 3 B+ and NI USB-GPIB-HS communication using linux gpib</title><link href="https://sourceforge.net/p/linux-gpib/support-requests/25/?limit=25#40c3" rel="alternate"/><published>2019-06-14T20:28:33.978000Z</published><updated>2019-06-14T20:28:33.978000Z</updated><author><name>Frank Mori Hess</name><uri>https://sourceforge.net/u/fmhess/</uri></author><id>https://sourceforge.net61685a9fe2a29766187d254a6305011d4d9d9968</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ok, I just built and tried linux-gpib 4.2.0 on a raspberry pi using a 4.19.42-v7+ kernel (the raspberrypi-kernel and raspberrypi-kernel-headers packages in Raspberrian).  I was unable to reproduce your problem, gpib_config worked fine with a gpib-usb-hs+.&lt;/p&gt;
&lt;p&gt;Can you zero in on where the NULL dereference is happening in the ibioctl function?  You could add some printk to debug ibioctl() in  drivers/gpib/sys/osfuncs.c.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#25 Raspberry Pi 3 B+ and NI USB-GPIB-HS communication using linux gpib</title><link href="https://sourceforge.net/p/linux-gpib/support-requests/25/?limit=25#d0eb" rel="alternate"/><published>2019-06-14T10:14:33.153000Z</published><updated>2019-06-14T10:14:33.153000Z</updated><author><name>Giorgos Tsapparellas</name><uri>https://sourceforge.net/u/gtsapparellas18/</uri></author><id>https://sourceforge.net709658dc0e65c6df24a712d53e92ed1a07374d0d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Yes, in fact I'm getting an internal error Oops: 17 &lt;a class="alink strikethrough" href="/p/linux-gpib/support-requests/1/"&gt;[#1]&lt;/a&gt; SMP ARM&lt;/p&gt;
&lt;p&gt;See attachements for full output of dmesg after the segmentation fault.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;GT&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#25 Raspberry Pi 3 B+ and NI USB-GPIB-HS communication using linux gpib</title><link href="https://sourceforge.net/p/linux-gpib/support-requests/25/?limit=25#9f62" rel="alternate"/><published>2019-06-13T10:44:35.846000Z</published><updated>2019-06-13T10:44:35.846000Z</updated><author><name>Giorgos Tsapparellas</name><uri>https://sourceforge.net/u/gtsapparellas18/</uri></author><id>https://sourceforge.neta002eb387a95b6501df1b5cc15ea32ba7bb7312b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Frank,&lt;/p&gt;
&lt;p&gt;Thanks for getting back.&lt;/p&gt;
&lt;p&gt;So I have managed to get the linux-gpib installed and recognize my device.&lt;/p&gt;
&lt;p&gt;However, I am now getting the error of Segmentation fault when promtping the command gpib_config. &lt;/p&gt;
&lt;p&gt;Any thoughts why this is caused?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#25 Raspberry Pi 3 B+ and NI USB-GPIB-HS communication using linux gpib</title><link href="https://sourceforge.net/p/linux-gpib/support-requests/25/?limit=25#63f4" rel="alternate"/><published>2019-06-10T20:17:13.535000Z</published><updated>2019-06-10T20:17:13.535000Z</updated><author><name>Frank Mori Hess</name><uri>https://sourceforge.net/u/fmhess/</uri></author><id>https://sourceforge.netc666d3c3c37f7e4a16a118d3e3d697bd29083b6c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;You'll have to provide more detailed information about what errors you are encountering.  One thing is, I believe the udev scripts in your version fail to run gpib_config unless the ni_usb_gpib kernel module is already loaded when the gpib adapter is plugged in.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Raspberry Pi 3 B+ and NI USB-GPIB-HS communication using linux gpib</title><link href="https://sourceforge.net/p/linux-gpib/support-requests/25/" rel="alternate"/><published>2019-06-07T16:05:35.579000Z</published><updated>2019-06-07T16:05:35.579000Z</updated><author><name>Giorgos Tsapparellas</name><uri>https://sourceforge.net/u/gtsapparellas18/</uri></author><id>https://sourceforge.net90cbd0710c6a1fae98f408c3901190209e10df55</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am trying to get a communication between a Raspberry Pi 3 B+ and NI USB-GPIB-HS.&lt;/p&gt;
&lt;p&gt;I have downloaded the latest linux gpib 4.2.0 and my pi is running on the latest 4.19.46-v7+ kernel. I have been through tons of tutorial but none could get my communication working properly, as it turns out that they might have been out-dated by now. &lt;/p&gt;
&lt;p&gt;Do you have any specific procedure I can follow in order to make this working? &lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;GT18&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>