DSO Hantek 6022BE, re-flash firmware?

[sjuliancarrizo]

Hello to everybody!

I recently crashed my DSO Hantek 6022BE, by doing a really bad measurement in a AC/DC non-isolated source power 
As a result, when I connect the DSO to the PC, I have the "USB\DEVICE_DESCRIPTOR_FAILURE" message on the device management.

I checked the board and I remove the zenner diode which is placed near de USB-B connector, that was in short.
After that, I tested the ASM1117 3.3, and It was working fine. I mean, the 3V3 and 5V power rails are ok.

I also flashed the 24LC02 memory with a dump I got from other Hantek 6022BE DSO.

I assume that, may be, there is an issue with the fimrware inside de cy7c68013a. My question is, is there any way to re-load the firmware through UART or I2C ports? USB port seems to be inaccessible.

I was reading some datasheets and app notes, but I don't realize what would be the solutions.

Sorry for my poor English, I hope you can understand my issue and can help me..

Regards!!

Julián

[Gyro]

The cy7c68013a doesn't actually contain any flashed firmware. Also, the 24LC02 simply contains the USB PID/VID (ie. apart from the first few bytes, it is empty).

Every time the application starts, it downloads a firmware into RAM on the cy7c68013a.

The USB interface is built into the cy7c68013a, so it might have been damaged - if so, you can replace it without worrying about firmware.

Don't forget to replace the zener with a new one. It sounds as if it didn't protect the 6022BE but it might just have saved your PC!


P.S. You might want to try it on another USB port of the PC, just in case it is the PC port that got damaged.

[PKTKS]

use a good operating system with SIGROK firmware.

THe SIGROK is superior from the original one

and unless the USB chip was damaged you should
reflash the Hantek without problems

results are even better

Any doubt please be welcome to post..
Paul

[Renate]

I have the "USB\DEVICE_DESCRIPTOR_FAILURE"...

The state of your Hantek is unknown, but, as usual Windows is not very helpful.
Windows is slow/horrible at enumerating USB.
It can also lose its mind if something that it has seen before reappears with a different number of interfaces.
(I mention this in case Windows ever received garbled descriptors form the Hantek when it blew up.)
It's always worth trying a different port, better yet a different PC.
You can wipe out the offending parts of the registry so that Windows sees the device afresh.
HKLM\System\CurrentControlSet\Enum\USB

I have a 6052, so don't quote me on details.

As Gyro says, when you plug the Hantek in, it only knows VID/PID that it sees from the EEPROM.
On mine that is 04b4 (Cypress) / 6051
The first driver kicks in, uploads the firmware.
The Hantek does a reset and appears as a new device.
On mine that is 04b5 (Rohm!!!, they shouldn't do that!) / 6051
The second driver kicks in and opens 2 bulk endpoints.

What do you see when you use device manager (devmgmt.msc)?
Does it say Unknown Device or Hantek USB Driver 1 or Hantek USB Driver 2?

If you have a Linux box handy, you can plug in the Hantek and see how it announces itself in dmesg.

Check the values that you programmed the EEPROM with what appears and what is in \Windows\System32\Inf\Hantekxxxxxx.inf

[sjuliancarrizo]

Just in case, I want to share that finally I replaced the cy7c68013a and now my DSO is working again. So I did destroyed it by doing wrong measurements.
Thanks to everyone for helping.

Julián.

[Gyro]

Thanks for reporting back, it's always valuable to know outcomes.