Broken DSLogicPro troubleshooting

Topics about DSLogic as a logic analyzer
My DSLogicPro seems to have failure.

Device is not "recognised" any more by DSView.

I tried it quickly with Different OS X machines and Linux machines.

At least it is "recognised" by USB on linux:

Code: Select all
[1104208.199763] usb 2-2: new high-speed USB device number 6 using xhci_hcd
[1104208.329258] usb 2-2: New USB device found, idVendor=04b4, idProduct=8613
[1104208.329263] usb 2-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[1104208.329795] usbtest 2-2:1.0: FX2 device
[1104208.329802] usbtest 2-2:1.0: high-speed {control bulk-in bulk-out} tests (+alt)


Code: Select all
Bus 002 Device 006: ID 04b4:8613 Cypress Semiconductor Corp. CY7C68013 EZ-USB FX2 USB 2.0 Development Kit


but not with DSView

# DSView
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.
sr: hwdriver: Scan of 'DSLogic' found 0 devices.
sr: hwdriver: Scan of 'DSCope' found 0 devices.
Protocol decoder enabled!

Starting a hotplug thread...


LED is Red. 5V and 3,3V in JTAG exist.

What shall I test to be sure that it is hardware failure?
silverk
 
Posts: 3
Joined: Fri Mar 18, 2016 12:17 am

idVendor=04b4, idProduct=8613?
It seems the EEPROM have been overwritten.
You can use cypress CyConsole tool to reprogramme the circuit.
Options -> EZ-USB Interface -> s eeprom.

The id for DSLogic Pro is:
idVendor=2A0E, idProduct=0003
Andy
Site Admin
 
Posts: 149
Joined: Fri Jul 11, 2014 9:20 am


Return to Logic Analyzer

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