Picoscope 7 / 2204A device not visible

[jamescarlyle]

Hi

I'm trying to run a Picoscope 2204A on Debian on a Chromebook (where I have to approve USB devices).

Code: Select all

Operating System: Debian GNU/Linux 11 (bullseye)
            Kernel: Linux 5.10.142-19743-gd301e86c39f7
      Architecture: x86-64

I can see the usb device using

Code: Select all

lsusb

Code: Select all

Bus 001 Device 016: ID 0ce9:1007 Pico Technology PicoScope 2000 series PC Oscilloscope

I'm running

Code: Select all

PicoScope 7 T&M Early Access - PC oscilloscope software 
version: 7.0.113.13201

but when I start it only shows a demo device and "PicoScope 2000 .... searching"

My trace.xml shows

Code: Select all

    Trace opened 11/23/2022.
    Application 'PicoScope 7 T&M Early Access' (version 7.0.113.13201 X64) starting.
    2966D0D28EE892F10F5455575B95DAA2
    User is not Guest
    No Administrator Privileges
    OS Version - Linux Debian GNU/Linux
    .net Version - 4.0.30319.42000
    Settings file version - 11.5.1
    Preferences file version - 2.0.0
    Probes file version - 1.0.0
    Data file binary header version - 1
    Loaded libusb-1.0 ver. 1.0.24.11584
    USB Hotplug available
    Using default culture: English (United States).
    Attempting to load ps2000.dll from '/opt/picoscope/lib/libps2000.so'
    Checking driver '/opt/picoscope/lib/libps2000.so' exists in executable path '/opt/picoscope/lib/
    Finished loading ps2000.dll
    Attempting to load ps2000.dll from '/opt/picoscope/lib/libps2000.so'
    Checking driver '/opt/picoscope/lib/libps2000.so' exists in executable path '/opt/picoscope/lib/
    Finished loading ps2000.dll
    Opening device using DLL ps2000.dll
    NoData
    GlobalDeviceManager.Close()

Can anyone provide some pointers about what might be wrong or where I should go next? Annoyingly, one time I could see the Picoscope device listed but greyed out, and the OK/Cancel buttons were also disabled.

Many thanks
James

[jamescarlyle]

I've got my scope working with a dedicated Linux machine, so I'm guessing my problem was related to the fact that Chromebook exposes Linux in a container (and I assume the USB data is somehow being mangled). So this request is no longer urgent, but I'd be happy to be a guinea pig if Chromebook compliance is desired.

[Martyn]

This is probably related to the two step start up process for a PicoScope. Initially they are identified as a simple PicoTech USB device as seen by your Chromebook, but then when opened by the software the firmware is loaded onto the device, it then disconnects and reconnects on the USB bus, and re enumerates. The timing of this process may be the issue on the Chromebook.