Bug 1886 - FX2 LA (8ch) not acquiring in latest PulseView
Summary: FX2 LA (8ch) not acquiring in latest PulseView
Status: CONFIRMED
Alias: None
Product: PulseView
Classification: Unclassified
Component: Acquisition (show other bugs)
Version: 0.5.0
Hardware: Other Windows
: Normal critical
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-06 23:28 CEST by Joe Butler
Modified: 2024-01-16 12:30 CET (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Butler 2023-10-06 23:28:54 CEST
FX2 LA (8ch) not acquiring in latest PulseView 64-bit Windows.

PulseView 0.5.0-git-3d396c8 exhibits this problem.

Log:
sr: asix-omega-rtm-cli: Cannot execute RTM CLI process: Failed to execute helper program (Invalid argument)
sr: ftdi-la: Failed to get the FTDI strings: -4
sr: usb: Failed to get libusb file descriptors.
pv: Acquisition took 0.00 s

(note, there was an FTDI lead also attached which is always present and should not be relevant to the issue.)

I did a reinstall of the driver using zadig.exe which made no difference.

If I close this new version of PulseView and run an earlier version (0.5.0-git-7e5c839) I can acquire normally.

Both versions of PulseView are installed side-by-side and I run only one instance at a time.
Comment 1 Joe Butler 2023-10-06 23:33:49 CEST
I've just re-opened the new PulseView to check something else and it can't even see the FX2 LA.

sr: asix-omega-rtm-cli: Cannot execute RTM CLI process: Failed to execute helper program (Invalid argument)
sr: ftdi-la: Failed to get the FTDI strings: -4
fx2lafw: Failed to open potential device with VID:PID 1d50:608c: LIBUSB_ERROR_ACCESS.
Comment 2 Joe Butler 2023-10-06 23:48:31 CEST
Ignore Comment 1, above. I could not open the FX2 because it was still running in a previous instance (reporting another issue elsewhere).

The bug report remains valid.
Comment 3 Antonio Vázquez Blanco 2024-01-16 12:23:07 CET
I am also affected by this bug.
Comment 4 Antonio Vázquez Blanco 2024-01-16 12:30:06 CET
Possible fix available at https://github.com/sigrokproject/libsigrok/pull/235