SLA5032 logic Analyzer & Pulseview

[Electroalice]

Hi
I purchase one of these off ebay but can not get it to run on Windows 10.
I have an older LWLA1034 that works well with Sigrok PulseView ( a very nice GUI for any LA)
The SLA5032 was redesigned in about 2019.and reports version 1.2.
Has anyone been able to one of the new version SLA5032 to worK ?
Any suggestions would be appreciated.
Thanks
Robert

[coppice]

I have an SLA5032 that is maybe 6 or 7 years old. This is currently working OK with Sigrok Pulseview on a Fedora 32 machine, using whatever revision of Pulseview is in the Fedora repositories RPMs.

You didn't say what fails. Does Pulseview fail to recognise the hardware? Is it recognised but won't run?

[Electroalice]

I have renamed the FPGA bit file and placed it in the correct directory as directed.
Pulseview finds the hardware.
The error message I get is "Failed to open device generic/ unspecified error" but reading the log file give a different story

ssr: hwdriver: Scan found 0 devices (saleae-logic16).
sr: hwdriver: Scan found 0 devices (siglent-sds).
sr: hwdriver: Scan found 0 devices (sysclk-lwla).
sr: hwdriver: Scan found 1 devices (sysclk-sla5032).
sr: hwdriver: Scan found 0 devices (yokogawa-dlm).
sr: hwdriver: Scan found 0 devices (zeroplus-logic-cube).
sr: device: sysclk-sla5032: Opening device instance.
sr: usb: Trying to open USB device 2.17.
sr: usb: Opened USB device (VID:PID = 2961:66b0, bus.address = 2.17).
Notifying user of session error: "generic/unspecified error"

if I then used the device drop down menu to attempt to connect again the following is added to the log file.

sr: device: sysclk-sla5032: Device instance already active, can't re-open.
Notifying user of session error: "generic/unspecified error"

I have just started to look at the USB dialog with Wireshark to get more details.
There was a PCB redesign  last year changing it to a single PCB. My board is labeled SLA5032_2019A.
Maybe the new card is not compatible with Pulseview?

[Electroalice]

Looks more like a driver issue. When I checked events on the driver I saw

Device USB\VID_2961&PID_66B0\5&887acb0&0&9 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\VID_067B&PID_2303\5&887acb0&0&9
Class Guid: {4d36e978-e325-11ce-bfc1-08002be10318}
Location Path: PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(9)
Migration Rank: 0xF000FFFF00000023
Present: false
Status: 0xC0000719

As I have well and truly cross the boundary into an area of my knowledge where "a little knowledge is dangerous" it is time to stop and put it on the shelf for 6 months or run over it with my 4WD.
Fortunately I have an old LWLA1034 that works.