Hantek - Tekway - DSO hack - get 200MHz bw for free

[steddyman]

Do we know that for sure?  Many scope manufacturers repackage the same model in different variants with only software unlocking certain features?

If we do, is the board the same but the memory just not installed?  Could it be added?  As anyone compared the boards of the two series side by side?

Thanks for the response.

[R4T]

I have found UART (it is next to the USB port on the back) and thanks to this descrption:
https://www.eevblog.com/forum/repair/voltcraft-dso-1102d/msg2036896/#msg2036896
i have managed to fix mine oscilloscope.

Hi Konsul,

I have a DSO-1062D S/N T121**** that arrived as a brick (long story - not my scope!) and has never got beyond the start-up logo - Linux isn't starting:

Freeing init memory: 128K
g_serial gadget: high-speed config #1: Generic Serial config
Kernel panic - not syncing: Attempted to kill init!

I have serial comms, obvs; hitting 'spacebar' works OK and I think DNW will work, though haven't tested that it will actually transmit stuff yet. Are you able to send me a link to a kernel image?

Much appreciated if you can help. I am little irritated with panicky kernels!

Thanks, R4T

[R4T]

Summarising where I have got to so far, with a bricked DSO-1062D 'scope:

It falls over at the start-up screen, and to the best my knowledge has never got further than this since new.

I established serial communications after some failures and this shows that it is stopping with a Linux 'kernel panic' as shown in my previous post.

For those in the same situation as me (not much of a clue, but willing to have a go!) I have found:

uart port on Voltcraft DSO-1062D HW 1.01 is at the back of the board, right next to the USB port and is labelled J801.  Mine has a header in it, some will just have holes, no doubt.

The pinout on J801 is (left to right, in the attached picture) 1 nc, 2 GND, 3 RXD, 4 TXD, 5 nc. Remember to connect RXD - TXD and TXD to RXD if this is news to you.  You need a usb to ttl device to communicate, the one that works for me is a DSD Tech SH-U09A with a Silicon Labs CP2102 chip - Windows 10 drivers readily available (bought on Amazon, search 'cp2102 usb to ttl').

Port settings are 115200, 8, n, 1 and you will need a terminal emulator program, such as PUTTY https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

Once you have serial comms, powering up the scope gives a boot log, which gives a clue about what is going on.  I am completely ignorant of Linux, so the full implications of this are somewhat lost on me, but it is very clear that the kernel is coming to a halt and that I now have to find a way forward that allows me to do stuff with the DSO and correct faults - a simple software update requires running Linux...

What clearly does work is that if I hit the space bar on my desktop as I am switching the DSO on, it will give me the Download Mode:

##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mod 0!
SD:File System init failed!

#####    Boot for SKY2416/TQ2416 Main Menu      #####
#####     EmbedSky USB download mode     #####

[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot (eboot.nb0) to Nand Flash
[3] Download Linux Kernel (zImage.bin) to Nand Flash
[4] Download LOGO Picture (logo.bin) to Nand  Flash
[5] Download UBIFS image (root.ubi) to Nand Flash
[6] Download YAFFS image (root.bin) to Nand Flash
[7] Download Program to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash

• Set the boot parameters

[a] Download User Program
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection:

So, the next plan is to try using these options to see if I can get the DSO going. My first thought was to try loading and testing a zImage using option [t] - but the only zImage I have at the moment is the one on the machine that falls over.

I have not downloaded anything to the scope yet, but I have a version of DNW on my Win10 machine to allow me to do this via usb, with luck.

Now thinking I may have to install ubuntu in a VM and compile a kernel for the DSO - but hoping someone can send me a zImage copy that is known to work on the Voltcraft instrument!!!

I hope this pulls together a few ideas for others who are struggling as much as I am!

[deisenberg]

Those of you that have done the LAN mod do you happen to have the part number for the ethernet port? Besides the PHY are there any other parts needed?

[villamany]

Hi guys, after several tries seems finally i got my DSO5102P "hacked to 200MHz". I bought it brand new at February 2020.

The serial pinout is here:

]https://i.imgur.com/XfhNmP6l.jpg[/url]]https://i.imgur.com/XfhNmP6l.jpg

The how to do is here: http://tefatronix.g6.cz/display.php?page=hantek&lang=en

Some tips:
-I didnt see the "dso1102b" file on my scope but i see a "dst1102b" file that i renamed to "dst1202b".
-My "sys.ini" file doesnt contain any data so i didnt change nothing here.
-Note i got several calibration errors until i removed all data of the i2c.log file leaving only the chars posted in the link plus a 0x0A after each line (a lot of 0x00 garbage bytes i removed at beginning, middle and end of the file)

[deisenberg]

Well I bricked mine good (MSO derivative).  No UART output now. Is this fixable via JTAG? I backed up via a USB key.

[acdrvc]

Hi, first post here. sorry about the long post.
I can tell you that the eeprom hacking method posted by villamany is not for the faint hearted, there is a real risk of bricking your oscilloscope, so if you follow the website instructions (http://tefatronix.g6.cz/display.php?page=hantek&lang=en) do it carefully. I have spent hours fixing a recovery loop, and after sucessfully modding the eeprom it still wasn't the right way, so it couldn't perform self calibration without success, it gave error 0x802.
Here is how i managed to do it.

Get acess to the console via rs232 adapter connected to the pcb, the pads near the usb connector
use Putty, or similar and get the i2c.log file copied to the usb stick. insert usb stick on your computer.

I use windows so i edited the file with HxD hex editor.

On top of the HxD editor you will see a window that reads "Windows(ANSI)", select in the dropdown list "DOS/IBM-ASCII(OEM)" so you can see the unix line terminators "◙" on each line.
Delete all 0x00 entries until the "[" character in "[--LOG0--], there is usually a bunch of 0x00 in the middle of the file, erase them too, and also at the end of the file, after "[bw]200◙".

So your file should look like this on HxD (the serial number is censored ):
[attachimg=1]

save it as i2c.org and connect stick to the dso.

Continue with the site instructions and reboot the dso when you're finished.
Now comes the important part. if the first message after rebooting the dso is not "formatting e2prom" but "backing e2prom", or self calibration fails then your file is not edited right(see image above), take special precaution with extra spaces or missing characters, it must be exactly like the image above, no more, no less.

If it is stuck in a recovery loop, connect via terminal(rs232 to usb adaptor) and choose on the dso the recovery option and wait, when "backing i2prom" or "formatting i2prom" appear on the dso screen hit killalll dsod, two times to be sure...

and copy i2c.org on the usb stick to both i2c.org and i2c.log:

cp /mnt/udisk i2c.org i2c.org
cp /mnt/udisk i2c.org i2c.log
touch i2c.format
sync
reboot

See if the dso reboots and "format e2prom" appears normally and after that it reboots normally, if so perform the self calibration, it should pass with success, if not, take your time evaluate your modded i2c.log file with patience, like the site said, a single misplaced character can brick or make your dso fail self calibration.
Simply don't rush it, take time and do it carefully.

[martinisonline]

There is a recent version for the Hantek P5000 series on the site from 24-10-2019.
dso5kp_func_dso5102p20191024

Did someone already test it? No log description as usual

[ADZ]

Hello. Anybody can upload voltcraft_dso3000series.zip that was located at http://ftp.gpl-devices.org/pub/vendors/Voltcraft/VOLTCRAFT_dso3000series.zip

[Level42]

Hey guys,

Thanks to this thread I hacked my Voltcraft DSO-1062D many moons ago but I was wondering if there was a newer firmware version now (because there are some rather "rough edges" in the older firmware ) and if I can upgrade without loosing the 200Mhz hack.

Current SW version is 3.30.0 (140111.0)

My questions:
- should I stick with the Voltcraft firmware versions as I can find on the Voltcraft site: http://voltcraftdownload.info/Default.aspx?modelno=DSO-1062D  or should I go with a later Hantek version ?
- are there any new cool hacks ?

[Ulle]

Hi. Today I get my new DSO5102P, so it's a current model. I would like to expand this to 200 MHz. Do I understand correctly that I ONLY have to change the i2c.org EEPROM file (0x00 and [bw] 200)? Or is that an additional step before the old standard procedure? Thank you!

[Level42]

About my last posting: I discovered that the Voltcraft firmwares are the same as the Hantek ones and I simply used the version for the 200Mhz model, all went without problems, but I have no idea what has changed....I guess some bugs were fixed like menus etc. It’s annoying that there are no logs that show what changes have been made....o well...

[robert.rozee]

i'm posting to this thread as it seems to be the place where all Hantek DSO5xxxP discussion goes on - hopefully no one minds what is a bit of an off-topic request!

i've got a Hantek DSO5072P (actually a 5102) with very blown switchmode power supply here, that belongs to a friend of mine. while repairing the power supply isn't impossible, i've been discussing with him the idea of converting the scope to battery operation instead of attempting any repair; cheap switchmodes are cantankerous devices at best, and it strikes me that battery operation may well be more useful.

for photos of the same PSU as i'm working with, with an identical failure mode, see this thread:
https://www.eevblog.com/forum/repair/hantek-dso5072p-power-issue/


so... if anyone reading this has a DSO5000P series scope that they have opened up, i'd be very keen to find out what the approximate current draw on the various supply rails is, these being: +14v, -8v (analog), +5v, +3v3 (digital).

the PSU is labelled as:
"DSO5000 SERIES POWER
Data: 3013/05
Ver 1.0",
indicating perhaps a hw version 1010?


my thinking is that in theory it should be possible to simply cobble together something based upon buck/boost modules from ebay: a 7.2v NiMh battery pack (6-cells) bucked down to 5v with a LM2596 module, and then a linear regulator down to 3v3. a small +/-12v module swinging about 3v3 could then give +15.3v/-8.7v for the analog stuff, provided the current requirement is suitably low.


many thanks for any info about the current draw from DSO5072P series owners.

cheers,
rob   :-)

[Lesheg]

Hello. After an unsuccessful firmware update of my DSO 5102B hw1010, I restored it through JTAG. In H-Flasher I chose the type: main-only, since my backup does not contain oob data. I tried after this a nandump without -o key, and oob data blocks contain only FF. But the scope now is working. Can something happen to my device in the future after such recovery without oob data?

[nakunda]

anyone knows the hw version or pcb version to use with the DSO tool for DSO8202E?
accidentally written 1007

[nakunda]

found.

DSO8202E，sw version 3.2.35（171121.0），hw version 1080*900383eb04

[david.ercoli]

Hello group:

I recently bought a Hantek oscilloscope model Dso4104b.

My question is, do you know if there is a hack for these model?

Thank you, best regards!

[Microcheap]

Hello group:

I recently bought a Hantek oscilloscope model Dso4104b.

My question is, do you know if there is a hack for these model?

Thank you, best regards!

Yes, check this thread: https://www.eevblog.com/forum/testgear/upgrading-the-hantek-dso4072c-osciloscope-bandwidth-from-70mhz-to-200mhz/

[Evgeni62]

Hello to all! Did anyone manage to run it on DSO5102B LAN - so that it would work? Thank.

[Evgeni62]

Those of you that have done the LAN mod do you happen to have the part number for the ethernet port? Besides the PHY are there any other parts needed?

Amphenol RJHSE-5381

[mhi]

I am considering purchase of some new low-end scope to space on my desk. Either some Hantek or Micsig tBook ("tablet" scope). One of things I would like to try to do is to modify the "main scope app" (firmware) to do some additional jobs. I have not digged into this yet, just looked at some firmware dumps. For Micsig scopes I have "oscillo_pad" Linux executable with full debug symbols (which is linked against Qt btw), making it quite easy to analyze. I am looking for dso.exe with enabled debug symbols, has anyone got such file ?

Also is there any info about Hantek/Micsig FPGAs available, at least how are they connected in the system?

[mzs66]

Hi All,

could anybody share or send me the Hantek Rescue tool?

Thanks in advance