-
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 -
I have a Xilinx platform cable II (original, from Digikey) something similar has happened to
when manually loading the firmware (using fxload) as normally done by the driver, it works as normal
-
Well, it should still be recognised by the sigrok driver for the fx2 chips.
Or you could fix the vid:pid with fx2tool, something similar to this maybe:Code: [Select]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 -
If the first 8 byes are gone I don't exactly trust the rest of the contents of the ROM!
D. -
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.
-
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. -
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.
I haven't tried it: https://wiki.epfl.ch/cfavi/fxload-libusb
there must be something that works on windows because the driver normally handles it, but with the wrong vid:pid it doesn't get triggered
-
Will I *tried* to install libfx2 but when I got the last stage it barfed:Code: [Select]
root@charon:/home/amonra/Downloads/Fx2/libfx2-master# python3 software/setup.py develop --user
running develop
running egg_info
creating fx2.egg-info
writing fx2.egg-info/PKG-INFO
writing dependency_links to fx2.egg-info/dependency_links.txt
writing entry points to fx2.egg-info/entry_points.txt
writing requirements to fx2.egg-info/requires.txt
writing top-level names to fx2.egg-info/top_level.txt
writing 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_ext
make -C ../firmware/library
make: *** ../firmware/library: No such file or directory. Stop.
error: command 'make' failed with exit status 2
REVISION - I ran python3 setup.py etc in the software directory and it then worked.
David -
VID/PID now set back to x0925/x03881
Thanks for the pointer to fxtool!
David -
Just for amusement here is an Intel hex file with the correct contents for the EEPROM
David
-
Which version of software works with your device now?
-
Logic 2.3.40 works ok
-
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]. -
Can't seem to download 1.1.18 from https://support.saleae.com/logic-software/legacy-software/older-software-releases#1.1.18-download
-
V2 software work great. There're plugins for additional decoders.
-
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? -
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 -
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).
I've just ordered a CH341A based USB programmer. Can you recommend what the 'go to' Windows based application is to work with these programmers?
David -
I've just ordered a CH341A based USB programmer. Can you recommend what the 'go to' Windows based application is to work with these programmers?
Apparently NeoProgrammer works great with it, although I've never used it myself.
The creator is posting the software on 4PDA which requires registration for downloading, but the russian captchas are a pain...so here is a link:
NeoProgrammer V2.2.0.10.zip -
Regarding fx2tool, it uses libusb for communication with the fx2 mcu.
In Windows you need to use zadig to 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: [Select]C:\Work> pip3 install fx2
C:\Work> py -m fx2.fx2tool --help
Then 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: [Select]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: [Select]C:\Work> py -m fx2.fx2tool -B -d 04b4:8613 write_eeprom -W 1 -a 0 -F saleae.hex
Read back eeprom data, assuming eeprom size of 256 bytes:Code: [Select]C:\Work> py -m fx2.fx2tool -B -d 04b4:8613 read_eeprom -W 1 0 256
The 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/82d154153f548b29b1be60f1c11d7a5bc102486d
You 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\fx2
Edit: JAN24 pip package now updated, so you should get the latest versionCode: [Select]pip install fx2 --upgrade -
Logic 2.3.40 works ok
I am using the logic version 2.3.46, in small Arduino projects, it has not given me any problems.