Products > Test Equipment

Warning about USBee

<< < (4/7) > >>

magic:

--- Quote from: comox on January 02, 2024, 04:15:09 am ---Jan 1 2024: This is EXACTLY what has happened to me!   I pulled my USBee DX out of the drawer to put it to use, re-installed software and BAM the USB IDs had been changed!   Also paid $1600 for it new back in 2009 or so....     Company now out of business...  What can I do?

--- End quote ---
Get a suitable EEPROM programmer (not 100% sure, but isn't it possible to use the FX2 itself to program its EEPROM?) and investigate.

See if it's enough to reprogram PID/VID back to original values.

If not, beg for somebody to upload full image from a working unit. Or look if an image hasn't been published somewhere.
Or buy a clone and copy the firmware :-DD

kloetpatra:

--- Quote from: Mechatrommer on January 02, 2024, 05:11:20 am ---1600? You got to be kidding me! You must be a rich man.. what now? Buy saelae logic..

--- End quote ---
Well, despite I like, and prefer Saleae logic analyzers over every other one, $1,499.00 isn't far away from your kidding $1600. In this regard Saleae isn't any different and they are actively bricking counterfeit analyzers as well. Until now I bought over 10 original analyzers from them and I absolutely recommend Saleae. Their support is outstanding. However when I tested a clone which uses a spartan 3 FPGA, it used to work until an update in 2015 or so. After that update it was completely dead even using previous SW versions. Either they've burned fuses in the FPGA or reprogrammed the I2C EEPROM with incorrect data.

comox:
Thanks everyone for your suggestions.

The reason I dug it out was to try it with Sigrok, as I wanted to use the USB PD protocol decoding capabilities.

I first wanted to make sure that it was working so reinstalled the USBee software I had downloaded years ago - before USBee disappeared - and that it when I started having problems.   At first it was working.  The USBee DX software recognized the device, would run for a bit, then crash.  This happened a few times.

Then decided to try on a different machine that I had the USBee software installed.  It was at that point the device was no longer recognized.  The USBee device enumerates in Windows Device Manager, but is not connected to the correct drivers.

I then found this post, and confirmed that the USB VID and PID had been changed to the 69C0 and 6909 as the original poster indicated.  This means that Windows no longer recognizes the USB device and therefore cannot associate it with the USBee drivers.   So it is clear that that VID and PID in the USBee DX ROM has been corrupted.

I then tried the Cypress USB programmer (a software package from Infineon) that allows programming of the Cypress chips used by the USBee, which contains two CY7C68013A-56XVC, one for the digital inputs and the other for the analog.   No luck, as it could not see the USB devices.   Oddly It found the USB mouse and keyboard, but not the USBee.   

Assuming that the EEPROM code is valid but only the VID and PID have been altered, it may be salvageable, but if the EEPROM contents have been corrupted further, then, yes, a new software image will be required.

The question is, how do I program the bloody thing if even the Cypress software can no longer attach to the device?

kloetpatra:

--- Quote from: comox on January 02, 2024, 09:50:05 pm ---The question is, how do I program the bloody thing if even the Cypress software can no longer attach to the device?

--- End quote ---

Well two options:

* short SDA line to ground -> FX2LP detects eeprom corruption and boots to VID/PID of 04B4/8613
* use external programmer

Randy222:
Would be helpful for those confirming the issue to post SHA256 or MD5 hashes of the culprit executable.

Not all bad software is malware bad, but bad is still bad.  ;)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod