Hantek DSO2000 Master Thread (DSO2C10 DSO2C15 DSO2D10 DSO2D15)

[vistorik]

Edit: That didn't work either.
Found 32 and 64-bit versions, tested working on 32 and 64bit Windows.
XP is too old and needs manual FEL driver installation.
Everything should be fine now. Platform-tools also updated with the new drivers.

- Download FEL / Fastboot Driver Installer and follow the included instructions.

No, not everything is fine.
For a 32-bit OS, both drivers install without problems. dsoflash works fine.
But platform-tools (I used the platform-tools from Hantek) stops after launch. The „Fel driver Allwinner Device in FEL Mode“ disappears in the Device Manager and „USB download gadget“ appears.
I replaced the wdi-simple.exe file in your first variant with the wdi-32bit.exe and wdi-64bit.exe files from yor second variant and modified the install_driver.bat file accordingly.
After reinstalling of the drivers, everything worked.
The „Windows Driver Package – Google, Inc. (WinUSB) AndroidUsbDeviceClass“ also appeared in the list of installed programs (with your second variant the „Windows Driver Package – Google, Inc. (WinUSB) AndroidUsbDeviceClass" didn't appear in the list of installed programs), and when launching the platform-tools, the The „Fel driver Allwinner Device in FEL Mode“ driver disappears in the Device Manager and the „Android Bootloader Interface“ driver appears.

install_driver.bat:

Code: [Select]

@echo off & cd /d "%~dp0"
REM :::::::::::::::::::::::::::::::::::::::::
REM Elevate.cmd - Freedom edition
REM Automatically check & get admin rights
REM See "https://stackoverflow.com/a/79585058" for description
REM :::::::::::::::::::::::::::::::::::::::::
 
 for %%k in (%0) do set batchName=%%~nk
 set "vbsGetPrivileges=%temp%\OEgetPriv_%batchName%.vbs"

:checkPrivileges
  %SystemRoot%\System32\whoami.exe /groups /nh | %SystemRoot%\System32\find.exe "S-1-16-12288" >nul
  if errorlevel 1 goto getPrivileges
  %SystemRoot%\System32\net.exe session >nul 2>&1
  if not errorlevel 1 goto gotPrivileges

:getPrivileges
  ECHO **************************************
  ECHO Invoking UAC for Privilege Escalation
  ECHO **************************************
 
  %SystemRoot%\System32\cmd.exe /u /c ECHO CreateObject("Shell.Application").ShellExecute "%SystemRoot%\System32\cmd.exe", "/c""%~f0""", "", "runas", 1 >"%vbsGetPrivileges%"
  %SystemRoot%\System32\cmd.exe /u /c ECHO CreateObject("Scripting.FileSystemObject").DeleteFile "%vbsGetPrivileges%">>"%vbsGetPrivileges%"

 "%SystemRoot%\System32\WScript.exe" "%vbsGetPrivileges%"
 exit /B

:gotPrivileges
cd drv
IF %PROCESSOR_ARCHITECTURE% == AMD64 (
    echo 64-bit system detected
    echo ## Installing FEL driver...
    wdi-64bit.exe -s -n "Allwinner Device in FEL Mode" -m "Allwinner" -v 0x1F3A -p 0xEFE8 -t 0
    echo ## Installing FastBoot driver...
    start /w DPInst64.exe /S
) ELSE (
    echo 32-bit system detected
    echo ## Installing FEL driver...
    wdi-32bit.exe -s -n "Allwinner Device in FEL Mode" -m "Allwinner" -v 0x1F3A -p 0xEFE8 -t 0
    echo ## Installing FastBoot driver...
    start /w DPInst.exe /S
)
rd /Q /S usb_driver >nul 2>nul
echo Done!
ping 127.0.0.1 -n 4 -w 1 >nul


[DavidAlfa]

I don't understand, what you did doesn't seem to be related to the current driver package...?
Edit: Oh, the 32bit falder has a wrong file, WdfCoInstaller01011.dll, should be WdfCoInstaller01009.dll.
I don't understand how it worked for me, probably it was already installed from a previous test.

[vistorik]

I don't understand, what you did doesn't seem to be related to the current driver package...?
Edit: Oh, the 32bit falder has a wrong file, WdfCoInstaller01011.dll, should be WdfCoInstaller01009.dll.
I don't understand how it worked for me, probably it was already installed from a previous test.

It seems that the 32-bit folder x86 is also wrong, perhaps it should be i386. After these two correlation - yours with the file WdfCoInstaller01009.dll and mine - with the folder i386 and drivers reinstallation platform-tools works on 32-bit OS. I will check this once more after reinstallation of 32-bit and 64-bit OS.

[vistorik]

David, in your last version for drivers installation, in dvr folder I replaced the folder name x86 with i386 and in it WdfCoInstaller01011.dll with WdfCoInstaller01009.dll - see the attached archive.
I tested this drivers installation on newly installed 32-bit and 64-bit OS.
After driver installing dsoflash and platform-tools work for both 32-bit and 64-bit OS for both W25N01GVZEIG and GD5F1GQ5UEYIG memory chips.

[DavidAlfa]

I know! I just hadn't time to update the files.

[DavidAlfa]

Driver files updated... 

[vistorik]

Driver files updated... 

David, Why is this? This doesn't work on a 32-bit OS.

[DavidAlfa]

Hmm that folder doesn't exist in my computer.

Edit: Indeed, 7-zip adds/modifies the contents if the zip file already exists, instead of replacing it.
Updated.

[vistorik]

Hmm that folder doesn't exist in my computer.

Edit: Indeed, 7-zip adds/modifies the contents if the zip file already exists, instead of replacing it.
Updated.

Super, but this is not all. Sorry.
FAQ:
it should be:
"After installation, the FEL device should appear in the Device Manager"
Allwinner Device in FEL Mode

The driver installation and instruction in Dsoflash also should be updated.

[DavidAlfa]

Updated...

[pjrebordao]

I have a DSO2D10 and some time ago I upgraded the FW to 3209.
However, some problems appeared,namely the unability to read the USB stick.
Whenever I try it, it's not recognized and it asks me to insert it again.

I would like to go to an earlier version (3205), but with this USB issue how can I do it ?
I know there's and UPK file that fixes this but how to read it into the DSO if the USB stick isn't recognized ?

Thanks for any help.

[Aldo22]

I have a DSO2D10 and some time ago I upgraded the FW to 3209.
However, some problems appeared,namely the unability to read the USB stick.

Is something plugged into the rear USB port?
Did the same stick with the same partitioning and formatting work before?
I also have FW 3209 and no problems with the USB stick.

Did you read the first page?
https://www.eevblog.com/forum/testgear/hantek-dso2x1x-models-master-thread/

[pjrebordao]

Fixed.
It was the stick. Tried another and it works fine.

Thanks

[pjrebordao]

Now I got into another issue...

As the USB reading was working, I decided to try the overclocking mod.
First try was with N=28
I used it for a while and as everything seemed fine I decided to try N=30
Changed the script and tried to update, but now I can't.
When I try the update option, the stick is recognized but everything hangs soon after. Sometimes the display goes black, sometimes it just freezes.
However, the list of files in the stick never appears.
The only option is to recycle power, but the update option always leads to a hang.

Any ideas ? Platform-tools ?
PS - FW is 3205

[DavidAlfa]

Did you read anything? Because it's very clear in the readme inside the file you downloaded...

Code: [Select]

----------------------------------------------------------------
Install
----------------------------------------------------------------
- Unzip the file into the root of the usb drive
- The overclock folder should be in the root of the drive
- Run system update and select "dso3kb_install_overclock.upk" / "dso3kb_test_overclock.upk" file.
- The system will reboot automatically.

----------------------------------------------------------------
Test mode (dso3kb_test_overclock.upk)
----------------------------------------------------------------
The system will execute the file overclock/oc_manager from the usb drive. If there's no drive, overclock won't be applied.
Now you can try rising the CPU_OC_PLL_N multiplier in that file, rebooting each time to apply the new settings.
When your system becomes unstable, lower the multiplier and try again.
After finding the stable CPU overclock, proceed with the memory overclock, increasing MEM_OC_PLL_N value.
This value have little adjustment, the limit is usually near 16.

Sometimes the system doesn't crash instantly, but after few minutes, so test it carefully.
If you had installed the Lock-up fix mod, uninstall it before trying overclocking,
or it will try to relaunch the system when it crashes after you overclocked too much.

----------------------------------------------------------------
Permanent mode (dso3kb_install_overclock.upk)
----------------------------------------------------------------
It will copy the file overclock/oc_manager from the usb drive to the internal memmory and execute it on each boot.
This mode can cause instant crashing at boot if wrong settings were used, requiring reinstalling the system with platform tools.
Ensure to use test mode first!

----------------------------------------------------------------
Uninstall (Permanent/test mode)
----------------------------------------------------------------
- Run system update and select "dso3kb_remove_overclock.upk" file.
- The system will reboot automatically.

----------------------------------------------------------------
Notes:
----------------------------------------------------------------
- The update consists on 2 files: S99overclock.sh (Runs last at system boot) and oc_manager (Executed as daemon by S99overclock).
- In test mode, oc_manager_test is used, which then loads oc_manager from the usb drive.
- Before applying overclock, it will ensure the system clocks are unmodified.
- There's a delay of 30 seconds to let the FPGA and USB init.
- To abort overclocking, press F0 key within that time, or create a file called "DISABLE_OC" in the root of the usb drive.
- Platform-tools 20210517 disabled keyboard logging, so F0 failsafe method won't work!


[pjrebordao]

Yes I read it, and I don't understand what I didn't understand...

I increased N to 28, used for a while and everything was OK.
Decided to try N=30 but then I couldn't access the USB. So I can't even go back to remove overclocking.

What did I do wrong?

[pjrebordao]

Sorry I got it.
It's in the notes.

[DavidAlfa]

It seems to me you went with the permanent OC since the beginning, that's why...

[pjrebordao]

No. It was the temp.

[DavidAlfa]

The temp never crashes unless you have a USB at boot. As stated, if you boot without usb it won't apply the OC.
But if you insert it too fast (<30s or so), OC Manager won't have executed yet, and will run the OC anyway, maybe that was the issue.
In any case, simply deleting the IC files or using the disable_oc file will stop it.

[arichli]

Hello everyone, it's a relief to find such a generous group that shares their experiences and solutions. Unfortunately, for now, I'm on the side of those in need:

Yesterday I received my DSO2D10, and it had a problem from the very first moment. I've read all the threads and I suspect I'm going to have to request a replacement.

As soon as I turned on the oscilloscope straight out of the box, it showed a waveform of approximately 0.5V and 1.5KHz. I've attached the image at 500mV/div; the values ​​are always in that range, although they vary. If I change the scale to 200mV/div, the waveform disappears, and I only find noise at 10mV/div.

By cooling it with air, I've been able to get it to start up properly, but after a minute it's malfunctioning again, and I have to leave it off for a while to restart it. If I don't, it turns on with the fault.

Software 1.0.3.0.0(230327.00)
Hardware 003.002.001.000.000.000.000.001
Firmware 3202

I shouldn't perform any updates before contacting my supplier to avoid jeopardizing any possibility of a replacement.

I haven't seen such a serious problem anywhere on the forum. Do you think it can be fixed without needing a screwdriver?

[hassan66]

Hello dear friend
You need to upgrade your device to version 3209

[Aldo22]

I would return it.

[oldthree]

1. The SDS804X HD product returns will be picked up at your doorstep today morning. It will arrive on the 22nd and you can use it for half a day. 【The fan noise is too loud and unbearable. Even 5 meters away, you can still hear it disturbing.】 I am applying for a return.
2. Trial experience: Apart from the loud noise, the small font, the small screen touch screen is not efficient and it also blocks the waveform.
3. I am a beginner and think the Hantek DSO2D15 is sufficient for me. It has large fonts, all buttons are easy to operate and reliable. The key point is that it comes with a built-in signal generator, which is convenient for learning. It has no fan and is quiet.
4. If there is an improvement in the future, I should know what kind of machine I really need.
5. Purchased from the siglent鼎阳京东自营旗舰店 of Siglent. RMB 2243 (with a 200 shopping card as a gift

[manotroll]

A software update has been released.
1.0.3.0.1(250418.00)