Hantek DSO2000 Master Thread (DSO2C10 DSO2C15 DSO2D10 DSO2D15)

[Aldo22]

A software update has been released.
1.0.3.0.1(250418.00)

Are there any noticeable changes?

[manotroll]

They didn't include anything about what changed, I didn't see any difference in usage.

[Aldo22]

They didn't include anything about what changed, I didn't see any difference in usage.

Thank you.
Actually, there has been an even newer version available for some time (dso3kb_20250509).
However, it is not “official.”
https://www.eevblog.com/forum/testgear/hantek-dso2x1x-models-master-thread/msg6099957/#msg6099957

[manotroll]

I'll take a look

[flez1966]

Just noticed firmware link on the site says 2026-02-26 but when you open the zip the filename is 20250418, bit odd..

I cant install it as my front panel buttons have spent the last 12-18mnth as 'random response generators'...
(well f1-f6+ch1 knob)

[manotroll]

It does this via USB cable, as if it were a recovery process.

[DavidAlfa]

Seems like the guys over at 4PDA got a newer system software update that isn't here or on Hantek's website yet, dso3kb_20250509. I installed it and seems to be working fine.

I forgot about this! I added both versions to the database 

It does this via USB cable, as if it were a recovery process.

As far as I know, you can't install UPK updates through USB.

[manotroll]

You will take someone's dump and use it for recovery via USB cable.

[manotroll]

Will this update be released later?

[manotroll]

hantek dso2d50

https://shophantek.com/products/2046879

It seems a 500MHz model has been released; perhaps we'll see software updates for these models again.

[Aldo22]

hantek dso2d50

https://shophantek.com/products/2046879

It seems a 500MHz model has been released; perhaps we'll see software updates for these models again.

https://www.eevblog.com/forum/testgear/hantek-dso2d20-series/msg6193521/

[blackbile]

I powered on the DSO2C10 (upgraded to 15) yesterday as I need to measure a pwm signal... unfortunately the rotary knobs didn't work.
So I disassembled and found that:




I measured the knobs but I could not find any small resistance as in the youtube video...
After that I cleared the pcb and now all the knobs are working.

Meanwhile I try to update to the latest sw, but the update doesn't work from the front USB port... FAT32 formatted pendrive, any idea?  with a verrry old 256MB pendrive solved the problem.

[DavidAlfa]

The flux is not an issue, check the encoder problem in the FAQ:

»  Rotating encoders unresponsive but buttons working? See [solution 1] and [solution 2]

[vistorik]

David, sorry for the question. You developed a dsoflash program based on xfel for Hantek DSO2XXX oscilloscopes. How to use xfel command "xfel spinand read <address> <length> <file>" (what is the <address>?) to read the entire EMMC 5.1 32GB 153FBGA chip YMEC6A2TB1A2C3 (firma YMTC) of "RIGOL DG821 pro" signal generator? The DG821 pro has an Allwinner A40i-H processor and a button for putting it to FEL mode. Thanks a lot.

[DavidAlfa]

I don't remember, but try 0, I think xfel automatically maps the addresss to the spi space.

[vistorik]

David, I tried the program xfel on my 2D10 scope with the W25N01GVZEIG memory chip. Reading the memory using the command "xfel spinand read 0x0 <length> dump.bin" is possible. The beginning of the dump.bin is identical to the beginning of the dump, obtained using your program dsoflash. But the xfel reads very slow - 13.6KB/s. It would take about 2h40m to read 128 MB of memory. What can be done to increase the reading speed?

[manotroll]

If it's working, doing it directly via USB with the app is more practical.

[vistorik]

If it's working, doing it directly via USB with the app is more practical.

manotroll, for using xfel, as well as dsoflash of David, the device must be set in FEL mode and connected to a computer's USB-port via a USB cable. The dsoflash v0.36 reads the memory of 2XXX oscilloscopes very quickly, but it does not work with the Rigol DG821 Pro signal generator.

[DavidAlfa]

Of course, it's a tool specifically made for this scope. Only.

I might rename it to DSO2D_Flash or something to make it more clear.
All the bits supporting other hardware were removed.
You can still use xfel, though.

[vistorik]

David, which software did you use to compile xfel and dsoflash?

[DavidAlfa]

cygwin64.

But... I was checking it, no idea what happened, neither my local or the uploaded sources seem to be synced with the latest binary!

It's missing the lastest changes, where I fixed xfel write32 function crashing by replacing the call with sunxi-tools code.

Only main.c was updated, the rest was completely original, which it's impossible as otherwise I wouldn't have compiled the new version.

Go figure.

Luckly I recalled talking about this here, so it's not totally lost:
https://github.com/xboot/xfel/issues/61#issuecomment-1925295005

But I still had to remember few obscure details I had completely forgotten, like to patch the spi payload so it uses the SDRAM address instead the internal (And small) SRAM.

Edit: Seems it's fixed now. I updated the sources in GDrive.

@vistorik Everything is described in the file README.TXT inside the sources.

Code: [Select]

## Compilation

Run cygwin64 installer, choose select these packages during the installation wizard:
- libusb1.0-devel
- make
- mingw64-i686-gcc-core
- mingw64-i686-libusb1.0

Compile by running:
> make -sjN (Where N is CPU cores+1, -sj5 for 4 cores, -sj9 for 8 cores...).


[vistorik]

Edit: Seems it's fixed now. I updated the sources in GDrive.

Super! You've updated the sources in GDrive, but where is now the dsoflash.exe? Seems you've removed the "bin" folder.