Saleae clone 24MHz 8 Channel LA looses its brains - Page 1
Forum section: electronics / testgear

author: perdrix
author_rank: Frequent Contributor
timestamp: November 30, 2021, 05:18:25 pm
content: So my clone Saleae 8 bit LA just stopped working. It now reports the Cypress USB development PID 04B4 VID 8613 values so isn't recognised.This was just after an upgrade of the Saleae software to 2.3.40 - coincidence or not?I assume the 24C02 EEPROM has lost its memory or has been forcibly wiped.Has this happened to anyone else?David

author: langwadt
author_rank: Super Contributor
timestamp: November 30, 2021, 07:56:32 pm
content: I have a Xilinx platform cable II (original, from Digikey) something similar has happened towhen manually loading the firmware (using fxload) as normally done by the driver, it works as normal

author: voltsandjolts
author_rank: Unknown
timestamp: November 30, 2021, 08:21:56 pm
content: Well, it should still berecognisedby thesigrokdriver for the fx2 chips.Or you could fix the vid:pid withfx2tool, something similar to this maybe:Code:fx2tool -B -d 04b4:8613 read_eeprom -W 1 0 256...modify as required then write it back...fx2tool -B -d 04b4:8613 write_eeprom -W 1 -a 0 -f ./eeprom.bin

author: perdrix
author_rank: Frequent Contributor
timestamp: December 01, 2021, 01:31:37 pm
content: If the first 8 byes are gone I don't exactly trust the rest of the contents of the ROM!D.

author: voltsandjolts
author_rank: Unknown
timestamp: December 01, 2021, 02:34:30 pm
content: I doubt you need more than the first 8 bytes (which I found after 20 seconds searching online), I just gave an example use of fx2tool.

author: perdrix
author_rank: Frequent Contributor
timestamp: December 01, 2021, 03:44:44 pm
content: Probably do need the entire ROM content as the rest of the content is typically the code to run in the Cypress chip ...Hmmm Maybe not - the 24C02 is only 2kb (256 bytes) - the GPIB adapter used a much bigger ROM that DID have the code to run in the Cypress chip.Will fx2tool.py run on windows? Or does that have to be linux?D.

author: langwadt
author_rank: Super Contributor
timestamp: December 01, 2021, 03:58:31 pm
content: Quote from: perdrix on December 01, 2021, 03:44:44 pmI haven't tried it:https://wiki.epfl.ch/cfavi/fxload-libusbthere must be something that works on windows because the driver normally handles it, but with the wrong vid:pid it doesn't get triggered

author: perdrix
author_rank: Frequent Contributor
timestamp: December 01, 2021, 04:31:02 pm
content: Will I *tried* to install libfx2 but when I got the last stage it barfed:Code:root@charon:/home/amonra/Downloads/Fx2/libfx2-master# python3 software/setup.py develop --userrunning developrunning egg_infocreating fx2.egg-infowriting fx2.egg-info/PKG-INFOwriting dependency_links to fx2.egg-info/dependency_links.txtwriting entry points to fx2.egg-info/entry_points.txtwriting requirements to fx2.egg-info/requires.txtwriting top-level names to fx2.egg-info/top_level.txtwriting manifest file 'fx2.egg-info/SOURCES.txt'reading manifest file 'fx2.egg-info/SOURCES.txt'writing manifest file 'fx2.egg-info/SOURCES.txt'running build_extmake -C ../firmware/librarymake: *** ../firmware/library: No such file or directory. Stop.error: command 'make' failed with exit status 2REVISION - I ran python3 setup.py etc in the software directory and it then worked.David

author: perdrix
author_rank: Frequent Contributor
timestamp: December 01, 2021, 05:27:27 pm
content: VID/PID now set back to x0925/x03881Thanks for the pointer to fxtool!David

author: perdrix
author_rank: Frequent Contributor
timestamp: December 02, 2021, 03:47:57 am
content: Just for amusement here is an Intel hex file with the correct contents for the EEPROMDavid

author: voltsandjolts
author_rank: Unknown
timestamp: December 02, 2021, 10:32:21 am
content: Which version of software works with your device now?

author: perdrix
author_rank: Frequent Contributor
timestamp: December 03, 2021, 05:06:49 pm
content: Logic 2.3.40 works ok

author: Gyro
author_rank: Super Contributor
timestamp: December 03, 2021, 08:41:37 pm
content: The last version I used with one of those clones was 1.1.18 beta. Irrc, after that (from the next revision) they went into a very protracted rewrite of the UI (and everything else) to support new hardware, which resulted in a much murkier and lower contrast display to my eyes. I'm not sure where the development went after that, presumably much of it into support of their newer products, analogue+digital etc.I haven't tried the latest V2.xx software but looking at the site, it doesn't seem to have gained any decoders that would make sense on the little 24MHz 8 bit clone (eg. USB2). You might want to see what the old legacy 1.1.18 one is like if you've bought a clone more recently [Edit:and maybe a bit less guilty].

author: euzer
author_rank: Regular Contributor
timestamp: March 04, 2022, 09:16:45 am
content: Can't seem to download 1.1.18 fromhttps://support.saleae.com/logic-software/legacy-software/older-software-releases#1.1.18-download

author: DavidAlfa
author_rank: Super Contributor
timestamp: March 04, 2022, 10:36:07 am
content: V2 software work great. There're plugins for additional decoders.

author: Tjuurko
author_rank: Regular Contributor
timestamp: March 05, 2022, 04:08:50 am
content: Quote from: euzer on March 04, 2022, 09:16:45 amhttps://downloads.saleae.com/betas/1.1.18/Logic+Setup+1.1.18+(32-bit).exehttps://downloads.saleae.com/betas/1.1.18/Logic+Setup+1.1.18+(64-bit).exe

author: euzer
author_rank: Regular Contributor
timestamp: March 07, 2022, 02:25:39 pm
content: My Saleae clone has stopped responding at some point using sigrok PulseView and is now showing as an unknown device in Device Manager. I'd been using Saleae Logic+ up until then, but switched to sigrok to see if it would show the sample points in the waveforms. I had been experimenting using different sample settings in the dropdown box in PulseView with the fx2lafw driver just before it disappeared.My LA has a Cypress CY7C68013A-56 (FX2LP ?) and an Atmel 24C02BN EEPROM. I've tried using the libfx2 from github (under spyder) but not had any success getting the code to run.Can anyone help?

author: perdrix
author_rank: Frequent Contributor
timestamp: March 08, 2022, 01:47:10 am
content: If you have an (E)EPROM burner that supports the 24C02, just desolder it and program it using the hex file I uploaded earlier in the thread (or even use grabbers in circuit).David

author: euzer
author_rank: Regular Contributor
timestamp: March 08, 2022, 03:36:05 pm
content: Quote from: perdrix on March 08, 2022, 01:47:10 amI've just ordered a CH341A based USB programmer. Can you recommend what the 'go to' Windows based application is to work with these programmers?

author: voltsandjolts
author_rank: Unknown
timestamp: March 08, 2022, 05:07:27 pm
content: Quote from: euzer on March 08, 2022, 03:36:05 pmApparently NeoProgrammer works great with it, although I've never used it myself.The creator is posting the software on4PDAwhich requires registration for downloading, but the russian captchas are a pain...so here is a link:NeoProgrammer V2.2.0.10.zip

author: voltsandjolts
author_rank: Unknown
timestamp: March 08, 2022, 05:37:53 pm
content: Regardingfx2tool, it uses libusb for communication with the fx2 mcu.In Windows you need to usezadigto apply the WINusb driver to your usb device (unless already using it), as libusb uses winusb on windows.Zadig is included with PulseView for Windows, so you should have it already.Once that is done, you will need the VID:PID of your device from Device Manager (right click on device > Properties > Details > Hardware IDs)Install fx2tool at the dos command line and view help info:Code:C:\Work> pip3 install fx2C:\Work> py -m fx2.fx2tool --helpThen you can use the python fx2tool to write the eeprom (example below VID:PID is 04b4:8613 and has eeprom device with one address byte -W 1, writes hex data given above)Code:C:\Work> py -m fx2.fx2tool -B -d 04b4:8613 write_eeprom -W 1 -a 0 -d C0250981380100007D2C5D848E2CE2A3..hmm, or maybe you should use the saleae.hex to ensure other locations are erased to 0xFF:Code:C:\Work> py -m fx2.fx2tool -B -d 04b4:8613 write_eeprom -W 1 -a 0 -F saleae.hexRead back eeprom data, assuming eeprom size of 256 bytes:Code:C:\Work> py -m fx2.fx2tool -B -d 04b4:8613 read_eeprom -W 1 0 256The above are just a guess, your command line options will be similar to, or maybe the same as above.Then replug.Maybe the VID:PID has changed. Maybe not.You need to ensure the OEM driver is used now, not winusb/libusb (i.e. if it is still assigned to winusb/libusb, right-click on device and uninstall driver).Unless of course the oem is using winusb anyway, then it doesn't matter.Edit: JAN24 the fx2 pip packageis out of date and needs this fix:https://github.com/whitequark/libfx2/commit/82d154153f548b29b1be60f1c11d7a5bc102486dYou can manually fix that, line 352 in fx2tool.py.On Windows, pip keeps the fx2 package here:C:\Users\<username>\AppData\Local\Programs\Python\Python311\Lib\site-packages\fx2Edit: JAN24 pip package now updated, so you should get the latest versionCode:pip install fx2 --upgrade

author: Adrian_Arg.
author_rank: Frequent Contributor
timestamp: March 12, 2022, 04:03:07 pm
content: Quote from: perdrix on December 03, 2021, 05:06:49 pmI am using the logic version 2.3.46, in small Arduino projects, it has not given me any problems.