Arch Linux User Repository

I don't get an entry for a Pico Bootloader...

When I first connect the scope I get

Mai 11 11:02:40 -- kernel: usb 1-2.4: new high-speed USB device number 9 using xhci_hcd
Mai 11 11:02:40 -- kernel: usb 1-2.4: New USB device found, idVendor=0ce9, idProduct=1213, bcdDevice= 1.00
Mai 11 11:02:40 -- kernel: usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mai 11 11:02:40 -- kernel: usb 1-2.4: Product: WestBridge 
Mai 11 11:02:40 -- kernel: usb 1-2.4: Manufacturer: Cypress
Mai 11 11:02:40 -- kernel: usb 1-2.4: SerialNumber: 0000000004BE

And then when starting the application:

Mai 11 11:03:10 -- systemd[918]: Started PicoScope 7 - PicoScope 7.
Mai 11 11:03:15 -- kernel: usb 1-2.4: USB disconnect, device number 9
Mai 11 11:03:15 -- kernel: usb 2-2.4: new SuperSpeed USB device number 4 using xhci_hcd
Mai 11 11:03:15 -- kernel: usb 2-2.4: LPM exit latency is zeroed, disabling LPM.
Mai 11 11:03:15 -- kernel: usb 2-2.4: New USB device found, idVendor=0ce9, idProduct=1213, bcdDevice= 0.32
Mai 11 11:03:15 -- kernel: usb 2-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mai 11 11:03:15 -- kernel: usb 2-2.4: Product: PicoScope 4000 Series PC Oscilloscope
Mai 11 11:03:15 -- kernel: usb 2-2.4: Manufacturer: Pico Technology Ltd
Mai 11 11:03:16 -- kernel: usb 2-2.4: reset SuperSpeed USB device number 4 using xhci_hcd
Mai 11 11:03:16 -- kernel: usb 2-2.4: LPM exit latency is zeroed, disabling LPM.
Mai 11 11:03:19 -- kernel: usb 2-2.4: reset SuperSpeed USB device number 4 using xhci_hcd
Mai 11 11:03:19 -- kernel: usb 2-2.4: LPM exit latency is zeroed, disabling LPM.

No idea why it says "PicoScope 4000". I have a 3203D and only have the 3000a driver installed.

when stable loads it momentarily recognizes 4444 before it disappears from list of visible devices. Can run in demo mode.

I'm curious what version of Pico Boatloader you have ? From my kernel logs: May 09 21:10:24 xxxxx kernel: usb 3-2: Product: Pico Bootloader 0.9.2

Funky :) I see similar behavior in my logs, but since I use the 3000a driver for my scope anyway the second "Attempting to load ps3000a" operation is happy. Sounds too suspicious to be a coincidence, but I'm pretty sure I'm not modifying anything in this regard... Does this happen on the stable version too?

that is a good suggestion Schorsch, should have thought to do that based on experience. But it didn't resolve the problem.

But I did install ps7b_lib3000a based on the error and it resolved. Seems that somehow this binary has 3000a related settings hardwired or pre-configured.

Take a look at a snippet (too large to paste in entirety ) from the generated error report below...

<event time="09/05/25 16:18:10.896" category="Device" level="Info">Attempting to load ps4000a</event> <event time="09/05/25 16:18:10.896" level="Info">Checking driver 'ps4000a' exists in executable path '/opt/picoscope/lib/</event> <event time="09/05/25 16:18:10.896" level="Info">Driver found '/opt/picoscope/lib/libps4000a.so'</event> <event time="09/05/25 16:18:10.908" category="Device" level="Info">Finished loading ps4000a</event> <event time="09/05/25 16:18:16.691" category="Device" level="Info">Opening device successful. Error PowerSupplyNotDetected.</event> <event time="09/05/25 16:18:16.693" category="Device" level="Info">Device opened FQ655/0029: PS4000A_PIRATE PS4444 PS4000A</event> <event time="09/05/25 16:18:16.694" category="Device" level="Info">USB version: 3.0</event> <event time="09/05/25 16:18:17.171" level="Info">Starting to load file 'default_configuration'</event> <event time="09/05/25 16:18:17.177" level="Info">Attempting to open PS6 File, File is streamed as object</event> <event time="09/05/25 16:18:17.185" category="Device" level="Info">Attempting to load ps3000a</event> <event time="09/05/25 16:18:17.185" level="Info">Checking driver 'ps3000a' exists in executable path '/opt/picoscope/lib/</event> <event time="09/05/25 16:18:17.185" level="Info">Driver not found 'ps3000a'</event> <event time="09/05/25 16:18:17.185" category="Device" level="Info">Finished loading ps3000a</event> <event time="09/05/25 16:18:17.185" level="Error">File 'default_configuration' is not supported - File was saved on a PS3406B device using an unsupported driver for this version of PicoScope.</event> <event time="09/05/25 16:18:18.263" level="Info">Creating window Blackman.32768.Coherent</event> <event time="09/05/25 16:18:18.263" level="Info">Creating window Blackman.32768.Coherent</event> <event time="09/05/25 16:18:18.263" level="Info">Creating window Blackman.32768.Coherent</event> <event time="09/05/25 16:18:18.263" level="Info">Creating window Blackman.32768.Coherent</event> <event time="09/05/25 16:18:18.263" level="Info">Creating window Blackman.32768.Coherent</event> <event time="09/05/25 16:18:18.263" level="Info">Creating window Blackman.32768.Coherent</event> <event time="09/05/25 16:18:59.934" category="Exception" level="Error">Exception:System.NullReferenceException: Object reference not set to an instance of an object.

@nurber Interesting, but I'm afraid there is probably not much I can do, I don't have the hardware to validate or reproduce any of this. If the error occurs when you close the application, maybe it's worth experimenting with the "Start-up Settings" setting or even clean out the ~/.local/share/Pico Technology/ folder.

I have a Picoscope 4444. FYI PicoLog for Linux as provided by Picoscope runs with the same 4444 without issue.

@nurber Do you have a Picoscope 3406B or is that just the error message?

seem to be working for me with the required ps7b_lib4000a that supports my scope, but each time I run I see a dialog that says:

"File was saved on a PS3406B device using an unsupported driver for this version of Picoscope"

Each time I exit the application it wants to generate an error report.

But otherwise it seems to recognize and work with my scope. I did have this scope working successfully on Ubuntu although I was regularly dealing with hiccups on that host that I suspect were either USB or just not properly vetted software. I'm bothered to admit that it works best on Windows. Thanks for providing package.

seem to be working for me with the required ps7b_lib4000a that supports my scope, but each time I run I see a dialog that says:

"File was saved on a PS3406B device using

I should try that one of these days, I've usually just been testing on Manjaro, so maybe Arch is missing some dependencies out of the box that I take for granted... Thanks.