Linux: DSView v0.96 doesn't detect hardware anymore

Help to track any bugs about DSView software
Hi,

i compiled the latest version of DSView v0.96 from GIT without problems. But it doesn't detect my DSLogic anymore. After the start it logs in the console that it only found the demo device:

Code: Select all
sr: Sanity-checking all drivers.
sr: Sanity-checking all input modules.
sr: Sanity-checking all output modules.
sr: hwdriver: Initializing driver 'virtual-demo'.
sr: hwdriver: Initializing driver 'DSLogic'.
sr: hwdriver: Initializing driver 'DSCope'.
sr: hwdriver: Scan of 'virtual-demo' found 1 devices.
Protocol decoder enabled!

Starting a hotplug thread...


I used the following installation steps:

Code: Select all
cd dsview-git
git pull

cd libsigrok4DSL/
./autogen.sh
./configure
make -j4
sudo make install
cd ..

cd libsigrokdecode4DSL/
./autogen.sh
./configure
make -j4
sudo make install
cd ..

cd DSView/
mkdir build
cd  build
cmake -DCMAKE_INSTALL_PREFIX=/usr/local/dsview ../
make -j4
sudo make install


In older versions like v0.94 it still detects the attached hardware.

Here the corresponding output when attaching the DSLogic in /var/log/kern.log:
Code: Select all
Oct  9 10:52:20 fox-mulder kernel: [  987.478625] usb 1-2: new high-speed USB device number 7 using ehci-pci
Oct  9 10:52:20 fox-mulder kernel: [  987.610980] usb 1-2: New USB device found, idVendor=2a0e, idProduct=0001
Oct  9 10:52:20 fox-mulder kernel: [  987.610991] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0


And here the output from lsusb:
Code: Select all
Bus 001 Device 007: ID 2a0e:0001 
Bus 001 Device 002: ID 04a9:2225 Canon, Inc. CanoScan LiDE 70
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 046d:c01d Logitech, Inc. MX510 Optical Mouse
Bus 002 Device 003: ID 03f0:1204 Hewlett-Packard DeskJet 930c
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


It's a bit strange that lsusb lists no name for the DSLogic.

Ciao,
Rainer
Rainer
 
Posts: 17
Joined: Tue Aug 19, 2014 1:53 am

Hallo,

exact the same trouble. Use DSlogic Pro and SW 0.96 compile at Debian 8 64-bit.


Jörg
jolinux
 
Posts: 13
Joined: Thu Nov 19, 2015 1:33 am

please try with root permission: sudo DSView
if want to run as normal linux-user, try to copy following file to /etc/udev/rules.d/
/usr/lib/udev/rules.d/DreamSourceLab.rules

Thanks.
Andy
Site Admin
 
Posts: 149
Joined: Fri Jul 11, 2014 9:20 am

Thanks for the hint.

After i copied the rules file to the udev directory i get a bit further but it still doesn't work.
I tried starting DSView as root and as user and in both cases i get the following output in the console:

Code: Select all
sr: Sanity-checking all drivers.
sr: Sanity-checking all input modules.
sr: Sanity-checking all output modules.
sr: hwdriver: Initializing driver 'virtual-demo'.
sr: hwdriver: Initializing driver 'DSLogic'.
sr: hwdriver: Initializing driver 'DSCope'.
sr: hwdriver: Scan of 'virtual-demo' found 1 devices.
DreamSourceLab Hardware Attaced!

Protocol decoder enabled!

Starting a hotplug thread...


So far so good it now lists the hardware. But within DSView in can still only select the demo device and not the real hardware.
Am i still missing something here?

Ciao,
Rainer
Rainer
 
Posts: 17
Joined: Tue Aug 19, 2014 1:53 am

I compiled the original Sigrok libraries and Pulseview as alternative to test if something with my hardware is wrong. But with Pulseview the DSLogic Hardware is recognized and working.

So i think the error must be somewhere within DSView. :?

Maybe it would be a better approach to get the changes from DSView upstream and work with native sigrok and pulseview instead of creating your own fork and work in it?

Ciao,
Rainer
Rainer
 
Posts: 17
Joined: Tue Aug 19, 2014 1:53 am

Is there any other information i could supply to find the error why DSView doesn't recognize the DSLogic anymore?
Rainer
 
Posts: 17
Joined: Tue Aug 19, 2014 1:53 am

Hi Rainer,

Could you show me the content of directory of /usr/local/share/DSView/res ?
I think you may lost some configuration files.

Additionally, you can mail to : support@dreamsourelab.com
So we can respond to you in a timely manner

Regards
Andy
Site Admin
 
Posts: 149
Joined: Fri Jul 11, 2014 9:20 am

With help of Dreamsourcelab i found the problem. It is a hardcoded installation path constant in libsigrok4DSL/libsigrok.h:
#define DS_RES_PATH "/usr/local/share/DSView/res/"

So any installation outside the default path (/usr/local/) wouldn't work. After i changed the definition to my installation path and recompiled libsigrok4DSL and DSView (both have dependencies to DS_RES_PATH) it works again. :)

I hope in the future this constant will be adapted to the real installation path. :roll:

Ciao,
Rainer
Rainer
 
Posts: 17
Joined: Tue Aug 19, 2014 1:53 am

or copy the files from the directory of /res

to /usr/local/share/DSView/res/


Are the firmware-files of /res fix you can place the other files of the new software-versions in local directories.

jo
jolinux
 
Posts: 13
Joined: Thu Nov 19, 2015 1:33 am

jolinux wrote:or copy the files from the directory of /res

to /usr/local/share/DSView/res/


There are many ways including setting a symlink to /usr/local/share/DSView/res/ instead of copying.

But i think the required point for a local installation is that all files are local and not only some.

Ciao,
Rainer
Rainer
 
Posts: 17
Joined: Tue Aug 19, 2014 1:53 am


Return to Bugs Report

Who is online
Users browsing this forum: No registered users and 1 guest
cron