Hantek DSO2000 Master Thread (DSO2C10 DSO2C15 DSO2D10 DSO2D15)

[DavidAlfa]

Don't put spaces in files / folders names  .
Added to the faq!

[jovan_kineas]

Thanks David Alfa, you were right, it was that there were spaces in the folder name at the root of the pen drive. I was able to update and apply the mods I wanted, however my problem continues to be present as channel 2 appears inverted (photo 2) and another thing I have seen is that I cannot calibrate the oscilloscope, it gives an error "511d1", I tried calibrating from my backup with FW 3102 and SW 221028 and it does not give an error and channel 2 appears normal,  but with FW 3209 and 2024.03.26 the photo error appears when wanting to calibrate the oscilloscope from the utilities menu. I did some tests and I noticed that from the FW 3205 I have both errors. I don't understand why. Does it happen to you too?

[DavidAlfa]

Why are you using a wrong fw?
It's very clear at the beginning of the faq.

[jovan_kineas]

Thanks for the prompt response, do you mean that my oscilloscope should only use FW3102? That's what's not clear to me because of my bad English, Google translates it like that for me. I do notice that with FW 3102 it works very well.

[DavidAlfa]

do you mean that my oscilloscope should only use FW3102?

Exactly.
If your scope came from factory with 30xx/31xx (3000, 3001, 3002, 3101...) , whatever, but NOT 32xx, the latest update is 3102 and you should NOT apply 32xx versions.

I wonder what Google translator makes out of this in your language?
I often translate my own posts to make sure Google doesn't take it wrong for foreigners, Hantek FAQ was no exception.

»  For scopes coming with FW30xx-31xx, update to FW3102.
»  For scopes coming with FW320x, update to FW3209, try older 32xx versions if having issues.

[jovan_kineas]

I see, thank you very much, it is now clearer to me why these errors occurred to me. I thought I could also use more recent firmware, thanks David Alfa.

[Aldo22]

Yes, Pass/Fail is not very useful as trigger for single events.
Forget it and try to capture the event with normal triggers.

[OLderDan]

I have always wondered on what is the use case for pass\fail on my hantek. Could one of you guys please give me an example, or point me to a link that shows a usage example?

[cfgnunes]

I have always wondered on what is the use case for pass\fail on my hantek. Could one of you guys please give me an example, or point me to a link that shows a usage example?

Hi!
The Pass/Fail feature on an oscilloscope is used to automatically verify if a signal meets specific criteria. For example, you can test if a clock signal's pulse width, frequency, or voltage stays within acceptable limits. It's great for automating repetitive testing, debugging, or ensuring signals comply with standards.

Here are some usage examples for the Pass/Fail feature on an oscilloscope:
- Clock Signal Validation: Verify frequency and pulse width of a clock signal within defined tolerances.
- Voltage Threshold Testing: Ensure a power supply's output voltage stays within an acceptable range (e.g., 3.3 V ±0.1 V).
- Signal Integrity: Check for overshoot, undershoot, or signal glitches against a predefined waveform mask.
- Communication Protocol Testing: Validate UART, SPI, or I2C signals for correct timing and logic levels.
- Transient Detection: Monitor for unexpected spikes or drops in signal levels.

Check these videos for some examples:

[Aldo22]

If you need any specific waveform files or have suggestions for new ones, feel free to share your ideas!

Nice collection of waveforms! 
But one is missing: the frequency doubling for square waves.
Normally you can only set the square wave up to 10MHz, but with an AWF you can get up to 50MHz. 25MHz (12.5 x 2) also looks stable.
In-between frequencies have a lot of jitter.

[IC_Toaster]

DavidAlfa what is the default CPU frequency, and what is the overclocking safe frequency?

About the heatsink improvements, what heatsinks have you all used and what is the glue to use on them?

[OLderDan]

...About the heatsink improvements, what heatsinks have you all used and what is the glue to use on them?...

i used heatsinks available cheap and easy for raspberry pi cpu with stickon thermal pads, but never used it without, so have no comparison. I can however tell you that the overclock mod works great and is stable, when you follow the instructions, with a perceptible notice in reduction of sluggishness of the UI.

I will say too that the dso2d15 can be reliably made to lockup if i play with the controls in a heavy handed way when first turned on, but on restart will operate correctly for as long as i need.

[IC_Toaster]

...About the heatsink improvements, what heatsinks have you all used and what is the glue to use on them?...

i used heatsinks available cheap and easy for raspberry pi cpu with stickon thermal pads, but never used it without, so have no comparison. I can however tell you that the overclock mod works great and is stable, when you follow the instructions, with a perceptible notice in reduction of sluggishness of the UI.

I will say too that the dso2d15 can be reliably made to lockup if i play with the controls in a heavy handed way when first turned on, but on restart will operate correctly for as long as i need.

Thank you for your reply.
I will search for these heatsinks and thermal pads. But I think the hantek FPGA and CPU are bigger than the raspberry pi CPU.

That's a interesting behaviour the fact that the oscilloscope lockup the first turn on but not the second.
I have not had this issue si far.

DavidAlfa what is the default CPU frequency, and what is the overclocking safe frequency?

Hi IC_Toaster!

The oscilloscope is powered by the "Allwinner F1C200S" processor. According to its datasheet:

Note: The PLL output clock must be in the range of 200MHz~2.6GHz. Its default is 408MHz.

Unfortunately, the datasheet doesn’t provide any information about overclocking.

However, some contributors in the Hacking Thread have reported success with overclocking the CPU to 720 MHz (or 696 MHz for added safety) and the RAM to 360 MHz. They’ve noted that this improves the UI’s responsiveness.

I suggest experimenting with different parameters to see if overclocking works well for your setup.

The best values I was able to use on my oscilloscope DSO2D15, with the software 1.0.3.0.0(240326.00) and the firmware 3209, were the parameters:

Code: [Select]

CPU_OC_PLL_N=27
# This value: (24*(27+1)*(0+1))/(0+1) = 672MHz

MEM_OC_PLL_N=14
# This value: (24*(14+1)*(0+1))/(0+1) = 360MHz

Best of luck, and let us know how it goes!

Thank you for your reply.
This is the information I wanted.
I have the same software and firmware version than you, so I will try with the same values.

Is it possible to modify the software to add new functions and change the UI?
If the hardware works right, it could be a good idea to improve the oscilloscope. But I don't have much idea about programming.

[Aldo22]

What is the purpose of these heatsinks and fans?
I don't think they are needed, at least not with newer hardware versions (7V PSU, for example).
My device never locks up when it's warm, only sometimes shortly after startup when it's cold.
What problem do you want to solve with this?

[OLderDan]

I had the heatsinks on hand and one of the chips does get quite warm in normal use so I couldn't see the harm, but like I said in my earlier post, I have only used the scope with the heatsinks fitted, so I have no comparison.

[IC_Toaster]

What is the purpose of these heatsinks and fans?
I don't think they are needed, at least not with newer hardware versions (7V PSU, for example).
My device never locks up when it's warm, only sometimes shortly after startup when it's cold.
What problem do you want to solve with this?

I have not had any problem so far. Just I saw a video where heatsinks are installed and it was also commented here in the forum.

[pcprogrammer]

Hi all,

I'm curious about which FPGA is used in the versions that work with firmware version 3209. Is it still marked with Lemontree?

We know it is a Gowin GWA2-18 FPGA, but there are two versions of it in respect to the memory that is used. There is a version with PSRAM and one with SDRAM, and I wonder if that is why there are two firmware versions.

[OLderDan]

hello pc, i have seen your work in more than one thread here and I would like to say thankyou for your contributions of not just amazing custom firmwares, but the way you take the time to help people with simply a smile. You are a great example of online etiquette.

[DavidAlfa]

My device never locks up when it's warm, only sometimes shortly after startup when it's cold.

Did you overclock already? Because that's a common issue.
Better to leave RAM unmodified, and don't set the CPU over 648MHz.

I've just updated the script to set the RAM to the default 156MHz, RAM is quite sensitive so better to leave it alone.
These are the default OC values:

Code: [Select]

# ------ USER ADJUSTABLE ------
# This example: (24*(26+1)*(0+1))/(0+1) = 648MHz
CPU_OC_PLL_N=26
CPU_OC_PLL_K=0
CPU_OC_PLL_M=0

# This example: (24*(12+1)*(0+1))/(0+1) = 312MHz (156MHz DDR)
MEM_OC_PLL_N=12
MEM_OC_PLL_K=0
MEM_OC_PLL_M=0


[IC_Toaster]

Hi all,

I'm curious about which FPGA is used in the versions that work with firmware version 3209. Is it still marked with Lemontree?

We know it is a Gowin GWA2-18 FPGA, but there are two versions of it in respect to the memory that is used. There is a version with PSRAM and one with SDRAM, and I wonder if that is why there are two firmware versions.

My oscilloscope was bought two weeks ago.
The board is version 1.7 with date 2021.1.14 and works with formware version 3209.
Yes, the FPGA is marked with Lemontree 2090.

[Aldo22]

Did you overclock already? Because that's a common issue.
Better to leave RAM unmodified, and don't set the CPU over 648MHz.

Yes, I have slightly higher values (see below), but it rarely hangs and I have it under control.
Before switching off, for example, turn the memory depth down to 4k and make sure that not too much is going on (FFT, cursors, zoom etc..), then hardly anything goes wrong at the next start. Otherwise it restarts in 12 seconds. No problem for me.

Thank you.

Code: [Select]

# ------ USER ADJUSTABLE ------
# This example: (24*(28+1)*(0+1))/(0+1) = 696MHz
CPU_OC_PLL_N=28
CPU_OC_PLL_K=0
CPU_OC_PLL_M=0

# This example: (24*(13+1)*(0+1))/(0+1) = 336MHz (168MHz DDR)
MEM_OC_PLL_N=13
MEM_OC_PLL_K=0
MEM_OC_PLL_M=0

[pcprogrammer]

The board is version 1.7 with date 2021.1.14 and works with formware version 3209.
Yes, the FPGA is marked with Lemontree 2090.

That is the same version and date as on my board. I have never updated my scope and firmware is 3200, so should also work with 3209.

So the question is for those who use the firmware versions 31xx and below, what the FPGA marking is on those boards.

[DavidAlfa]

[pcprogrammer]

So the only difference lies in the date code and the marking below that. Mine says 2105C and N43X03.00

With your flash foot print and the foil it looks a bit like a surgical procedure. 

[Aldo22]

So the only difference lies in the date code and the marking below that. Mine says 2105C and N43X03.00

Mine says: 2208C and N4PX12.00