Hantek DSO1152S - Wont boot after firmware update - Page 1
Forum section: electronics / testgear

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 04:27:01 am
content: Hello,I was just wondering if there is anyone on here who may be able to help.My scope was running the stock factory firmware on my Hantek DSO1152S (Handheld 150Mhz isolated scope), and I noticed there was an update available as there were a few bugs I had found, such as the MEAS button not being able to measure any other channel other than CH1. So I thought I would try a firmware update.I went on the Hantek website and downloaded the latest update. Put it on a USB drive, went to the update menu and placed the USB drive in the scope, waited for it to be detected and then clicked update.It did 10/10 on the process update and then restarted. All looked fine.Now I am in a boot loop and it will not get past the main start screens. The first shows the Handheld oscilloscope picture, and then the 2nd screen shows the Hantek name, website and the version number. It then restarts and repeats over and over.Not sure what could have happened, unless the firmware was somehow corrupt?Was plugged into AC, didn't touch it during the update.Is there a way to force an update or restore it?Any help would be appreciated. Currently dead in the water and urgently needing the scope working againKind RegardsWanaGo

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 04:51:36 am
content: Seems someone else may have encountered a similar thing to me...I couldnt get the hantek.org forum up, so I had to seek out a cached version, here:http://webcache.googleusercontent.com/search?q=cache:http://www.hantek.org/asken/iaskdetail.aspx?id=2014052620325673Can someone please explain if they know the process to fix this. I am happy to open the case and connect a TTL to serial cable and do something with Linux if required.I have a Ubuntu VM I could use, and have 3.3V TTL cables, may even find a 5V one...If someone could help that would be highly appreciatedKind RegardsWanaGo

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 05:47:15 am
content: Here are some photos of the internals if this helpsI assume the UART header is the one marked J801, and the pin with the arrow marks the 3.3V pin, followed by GND, TXD and RXD ?How do I connect to it, what program? What baud rate etc?What do I need to do?Any help would be appreciatedThanks in advanceRegardsWanaGo

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 06:03:31 am
content: OK Yip that seems to be the UART port.Baud seems to be 115200Here is the output after pressing power button ON.Quote

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 07:00:29 am
content: It talks about pressing Space at the start, to enter download modeWould this then let me download an older firmware to correct this mess?It talks about pressing Enter later on. I did this and it enters the Linux prompt.Not sure what to do in either thoughRegardsWanaGo

author: tautech
author_rank: Super Contributor
timestamp: July 13, 2014, 07:22:56 am
content: Quote from: WanaGo on July 13, 2014, 07:00:29 amTinheadis our Hantek expert, be patient and he will spot your thread.Maybe PM him?

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 07:27:01 am
content: Yes thanks - have sent him a quick PM. Thank you.Pressing Space resulted in this, which is the download option.Not sure what I need though.Quote

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 09:07:22 am
content: More playing, but nothing discovered, just more questions..Thought I would try to decrypt the update file. Found a bit of info on this site, but I didnt know the password for the up file.> gpg -d dso1kb_2.01.1_DSO1152S\(140408.0\).up > dso1kb_2.01.1.gzgpg: CAST5 encrypted datagpg: encrypted with 1 passphrasegpg: decryption failed: bad keygpg: block_filter 0xaf0730: read error (size=16233,a->size=16233)gpg: block_filter: pending bytes!tried what I found on here, and guessed at a dozen more, but nothing seemed to work.WanaGo

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 09:15:07 am
content: Had a bit of a look around in linux, but it seems after a very short time, maybe 30 seconds?... it rebootsQuote

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 09:18:13 am
content: Quote from: TinheadFrom another post. Thank you.

author: bwat
author_rank: Frequent Contributor
timestamp: July 13, 2014, 09:25:51 am
content: Quote from: WanaGo on July 13, 2014, 09:07:22 amCAST uses 128-bit keys, so if you brute force it expect to take 2^127 attempts. Also, many keys may end up giving you an executable binary, just not the right one. Note the universe is roughly 2^80 microseconds old. Source:The Block Cipher Companion, Knudsen and Robshaw.If you want to save time, the key is somewhere in the machine doing the decryption and CAST is a symmetric cipher so you can encrypt with the same key if you want to load your own software.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 09:32:16 am
content: yeah wasnt hopeful guessing would work, however the passwords I had seen on this forum and others were the model numbers of the scope, or the family models.I tried:dso1000dso1000sdso1152dso1152setcNo joy.In terms of hunting out the key on this machine - wouldnt know where to start to be honest.

author: bwat
author_rank: Frequent Contributor
timestamp: July 13, 2014, 09:47:03 am
content: Is it a linux process that decrypts the file? If you're lucky it'll be a script so they'll probably use the openssl command. I use a script like this:Code:#!/bin/shopenssl des3 -d -salt -in secret_file.tar.gz.des3 -out secret_file.tar.gzSomewhere on that machine will be a similar script using cast instead of des3. Maybe try an update and run "ps" at the same time to see what is doing the decryption. If it's a binary linked with the openssl libs then hexdump that binary looking for the password which you know will probably start with "dso" and be NUL terminated.Edit: Maybe just build your own openssl libs that dump debug info giving you the passwords used on the machine. That would be quickest.

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 09:54:38 am
content: don't play too much, i will help you on that.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 10:08:37 am
content: great, thanks!Ready when you are.Noticed when logged in to the linux console, after a few minutes one of the relay clicks on and off, and then again, and then again... and gets faster and faster. I shut it down after a couple of clicks as I dont know why its doing it.Thought it was due to it getting hot, but I have put a big case fan above the scope board and its still doing it.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 10:12:56 am
content: >cat sys.inf[DST type]dst1202b[soft version]2.01.1(121207.1)[fpga version]0x555583e8[start time]-1[update time]0

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 10:23:33 am
content: I have 2 firmware files, downloaded one a while back but didnt upgrade as I was looking at the 2.01.1 rather than the date.Didnt think anything had changed.dso1kb_2.01.1_DSO1152S(130129.0).updso1kb_2.01.1_DSO1152S(140408.0).upIts that 2nd one that I tried today which got me into this mess.Looks like I was running 121207.1 prior to that.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 10:32:45 am
content: now thats interesting..../dso.exescope booted and launched as per normal. beeper was beeping every 3 seconds or so, but I could navigate menus etc.Utility button, and Sys Info shows its running 140408Turned it off again.will wait for instructions

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 10:37:25 am
content: i'm on windows, so some steps might be different on windows:1- go to Hantek OneDrivehttp://1drv.ms/1cA9vjgand download firmware for your model (DSO1152S_Firmware.zip)2- unzip that file, you will get dso1kb_2.01.1_DSO1152S(140408.0).up3- get gnupg, run in command prompt from directory with the *.up file likegpg -o fw.tar.tar.gz dso1kb_2.01.1_DSO1152S(140408.0).up4- when asked type password:1111115- now you should have that file fw.tar.tar.gz created in this directory6- open it with winrar, then the content again with winrar - you will see "tekwayup_client" directory, unpack it to harddrive7- in that directoy there will be "update" script, in my opinion there is bug, there should be mv /tmp/tekwayup_client/dso.exe /dso_update.exeand not mv /tmp/tekwayup_client/dso.exe /dso.exeI don't know, maybe it's only me, but i never managed to overwrite dso.exe when it was started, it crashed or didn't got overwritten properly on linux 2.6.13 and 2.6.30 (that might work on 3.x, so on other models, but you have 2.6.30.4).I think these guys from Hantek, they already forgot thatOne can see in the bootlog "no update file to foud" whichis message coming from script which checks if there is /dso_update.exe in place and renames it to /dso.exe before this will be started (right after first rebot after fw update) .. anyway, maybe that's only me hehe, but i can kill all my s3c2440 dev boardswith all the DSO/MSO firmwares on it when i do what they did on latest S, B and BV models updates.Anyway, copy that dso.exe to flash drive (and ensure windows copied it properly before you remove flash drive).Now let' got to the linux console on your DSO. Luckily you did the major work already, so do following:1- power up DSO2- do not push any buttons or you will be in boot menu and we dont need that!3- as soon you see "Please press Enter to activate this console" push ENTER and or CTRL+C and ENTER.4- now tpe as fast you can following (and then ENTER)killall dsodand then arrow key up (to reply last command) and ENTER, and againUntil you get "dsod: no process killed".The dsod is watchdog, rebooting your DSO over and over again because dso.exe not started. Normally one could check with ps x the process id and kill -9 processid, but killall dsod is faster typed (at least for my fat fingers).Now you should be on the linux shell, without any reboot over and over again. Insert now the flash drive into DSO,you should see now some messages that it got monted. Check that withls /mnt/udisk/You should see that copied before dso.exe. Copy it now to root of the DSO, likecp /mnt/udisk/dso.exe /dso.exethen flush the cash withsyncsyncand give executo rightschmod 777 /dso.exeNo check if your DSO is working. Go back to / ( cd / ), and type /dso.exe and enter. The firmwar should start now.I assume you executed before that update file dso1kb_2.01.1_DSO1152S(140408.0).up anyway, so there is not needto copy other files from that "tekway_client" directory. In case you applied different update, let me know this, thenyou will have to copy other files as well.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 10:41:50 am
content: thank you!I am on windows too.Only know how to drive linux as good as I can find answers on google. Assumed that would be the method to use.Already downloaded the firmware, which got me in this mess in the first place, however will get it from where you stated.Will report back shortlyThank you!

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 10:43:24 am
content: btw, when you DSO anyway open, can you please make pictures of the other side of the PCB as well ? I wish to see how they made the isolation, and all these parts from isolation (ADCs, FPGA and SoC as well - but they known) are of the other PCB side.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 10:54:11 am
content: OK, did all the fix, however still got the boot loop.Yes I updated the firmware as per the update menu on that latest update prior to all this, then got the boot loop.copied the dso.exe file over as you said, restarted the unit and its still got a boot loop.Any ideas?Ill take photos of the other side while I await your replyRegardsWanaGo

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 10:56:50 am
content: so you copied the dso.exe, changed the execution rights and when you kill the dsod and run /dso.exe it reboot then still after few seconds? Try to do this as well:rm /param/sav/run*and then try to run the /dso.exeEDIT: once dsod killed there should be no reboot. It would be interessting as well to see what message is coming right before reboot.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 11:03:17 am
content: What I mean is, before I did what you said....Start the unit up, Press Enter to get to linux prompt.If I sit there it will reboot after about 20 seconds.So to prevent that, I did the killall dsod.I then put in the flash drive and copied over the dso.exe file I extracted from the up file.i then did the rest of your instructions about the chmod etc, sync etc. running /dso.exe at this point starts the scope, no problem. All seems fine.However rebooting the scope again, results in a boot loop like before.Whatever is normally opening dso.exe it seems is not working.I still get that same first warning message: "*** Warning - bad CRC or NAND, using default environment"When I am looking at the UART.Hope that makes senseOpening scope now.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 11:19:17 am
content: OK here are some photos, both sides.If you want larger res, let me know. Made smaller for the forum, but still 1280x853. Got them 4752x3168.Its night here, so if you want better quality ones, let me know and ill take some in the day light tomorrow.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 11:31:41 am
content: Here is the output after doing a reboot command from the UART terminal.Quote

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 11:36:53 am
content: Note quite sure about these dates, as I dont know if the scope knows dates unless on a LAN...?But some more info:Quote

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 11:44:53 am
content: Is the solution to this going to be to fix the script, and re-encode the up file and get the scope to update itself again?or should I manually do each of the steps in the update file, but fix the dso.exe manually at the end?Looking in the update file, it has:Quote

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 12:03:15 pm
content: ok, i've installed handheld image, updated to their latest zimage, installed that update for S models and my dev board is now boot looping as well. Good (at least i have same shit now).Try following:- on the shell go to /dso/app/ directory- rename the dsod in that dir to dsod.old (mv dsod dsod.old)- reboot DSO

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 12:04:13 pm
content: Ran the update again while monitoring the serial port, this is what resulted(Took out the rubbish in between which padded it out, normal talk when dso.exe is running)Quoteetc etc, as it reboots...

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 12:06:45 pm
content: Quote from: tinhead on July 13, 2014, 12:03:15 pmNope, sadly still not workingits not boot looping now, but its just stuck waiting to do something, it doesnt load dso.exe itselfQuote

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 12:12:45 pm
content: /etc/init.d/rcS: line 63: /dso/app/dsod: not foundthat's ok, you renamed the dsod so there have to be an error. The next line in rcS is loading the dso.exe,which is the DSO app itself. You can check your rcS (scroll down with cursor down)vi /etc/init.d/rcSto see this. There should be line/dso.exeAnyway, when it is not running check the /dso.exe rights, or simply do chmod 777 * in /.Now run the /dso.exe, do default setup, autosetup, then change e.g. timebase and wait 10sec. The dso fw should nowstored the profile. Reboot not the dso (powercycle, not reboot command) and tell my what is doing after reboot.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 12:16:17 pm
content: If I try to run /dso.exe now, I get thisQuoteok inside vi /etc/init.d/rcS I see this:Quote

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 12:18:32 pm
content: check again what i wrote, i'v edited while you was typing

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 12:20:57 pm
content: What I wrote didnt seem to be complete.I did a cat instead of vi this time:QuoteChecking what you wrote now

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 12:23:31 pm
content: [root@Hantek /]# chmod 777 *[root@Hantek /]#hmmAlso in that rcS file, it looks like it is still looking for dso_update.exe ?

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 12:29:07 pm
content: Quote from: WanaGo on July 13, 2014, 12:23:31 pmthis is exactly what i sadi, Hantek implemented that check into rcS but since i don't know when exactly, they overwriting the running dso.exe with new one during firmware update (which never works on my systems). anyway, this is not the point here, leave that as it is.All you can do now is try again to:- kill dsod (in case still there, but you renamed it so should be ok now)- kill dso.exe- copy the new dso.exe into /- in / chmod 777 *- rm /param/sav/r*- power cycle DSO and watch what is doingin principle it have to work now. If now tell me what you see (segfault again? is something on screen/key reaction?)

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 12:34:44 pm
content: Its still the same.Boots the first logo, 2nd logo, then goes black screen.UART just outputs the same stuff:QuoteSits there, black screen. Doesnt boot into dso.exe

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 12:39:27 pm
content: hmm, do you want to try to downgrade te firmware?here on my onedrivehttp://1drv.ms/1hf4SgOyou will find in "DSO hacks->firmware->hw1.00.4" older fw versions.While downgrading all you have to do is to copy to your DSO is then the dso.exe and English.lan from the olderfirmware version (so you have to use gpg, winrar again to get them).killall dso.execd /cp /mnt/udisk/dso.exe /dso.exerm /OurLanguages/*cp /mnt/udisk/Engish.lan /OurLanguages/chmod 777 *

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 12:39:56 pm
content: Ran the last command from the rcS file manually, to see what happensQuoteWhich is what I get on the UART when it does it itself.running./dso.exeworks fine.it running./dso.exe &however doesnt work fineQuote

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 12:43:19 pm
content: Mr Google saidQuote

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 12:50:02 pm
content: I can certainly try the old firmware.So I should do that rather than using the update utility from inside the dso.exe app when its running?Or does that FW have the same script issue?111111 didn't seem to open the file. Is the password different?Just thinking...What if I ran the script when dso wasn't running. All the errors I got during the update, I assume are all due to the things running. Would that solve it?Still what is strange how dso.exe wouldn't run in the background as per the startup file, but would when manually executed as a normal executable.

author: rob77
author_rank: Super Contributor
timestamp: July 13, 2014, 12:56:55 pm
content: Quote from: WanaGo on July 13, 2014, 12:50:02 pmprobably it needs a terminal to run => the dso.exe in the new firmware is "broken" if it doesn't work the way it should.try to start it with outputs and input redirected (in fact daemonise)./dso.exe > /dev/null 2>/dev/null < /dev/null &and see if it works - if works then edit your init script accordingly (if that's on a persistent filesystem).i was planning to update my DSO1102B in the next days.. but reading your troubles after upgrade.... i will rather connect a serial line and find a way how to backup first

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 01:05:21 pm
content: Have no idea what that does, but I tried it, and the scope ran[root@Hantek /]# ./dso.exe > /dev/null 2>/dev/null < /dev/null &[root@Hantek /]# s3c2440_clkcon=00FFFFF0s3c2440_clkcon=00FFFFF0save exit: isCheckpointed 0seems like its functional.1am here, I need to get some sleep.Will continue this tomorrow!Thank you very much for the help guys, much appreciated.I hope this helps some people at some stage.Tinhead, do you have contacts at Hantek to get this solved, or should I make contact with them and tell them the findings?Goodnight all, will catchup on chat in the morningRegardsWanaGo

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 01:57:10 pm
content: Quote from: WanaGo on July 13, 2014, 01:05:21 pmwell yes, when started manually it will run, but not when started from rcS. It looks like the dso.exe from 2.01.1_(140408.0) is not initializing properly when runned from rcS (i can't connect via USB to my dev board, so it deos NOT run properly). When killed and started manually it does works. So there must be general problem with that executable version.I did tested it now with older version, 2.01.1_(140214.0) and there are no issues, runs from rcS or manually and it allows USB connection/access. I did tested (just for sake) 2.01.1_(140408.0) but from B and not S model, and guess what, it works as well. So it seems to be specific problem with dso.exe for S model, version 2.01.1_(140408.0).So i would say do the downgrade as described. Don't play with other scripts, you will run in trouble during next update, so leave them all as they are. Replace only the English.lan (and different languages if necessary) in /OurLanguages/ directory and the /dso.exe in root, chmod 777 * in root and power cycle.Quote from: WanaGo on July 13, 2014, 01:05:21 pmfeel free to contact them, you have such handheld - i don't. Tests on dev boards, like i'm doing, are good but sometimes not sufficient (especially when firmware is waiting for soemthing missing on dev board).

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 02:00:28 pm
content: regards pictures, thank you very much!. Sure, when you have time you can uplaod higher res somewhere. It would be cool if you would try to check what numbers/name/logo on these ICs in attachement.

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 02:51:29 pm
content: i've checked your pictures and it seems that you have hardware revision hw1.00.1 and not hw1.00.4, like on current "S" models:https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg433286/#msg433286On your PCB the date is 2012-04, so that really old one. I remember Hantek introduced S models long time ago, but i never ever saw any from that time, you the first one. On hw 1.00.4 they improved the PCB a bit (moved some passive parts to top, isolation clearance better on DMM, smaller LAN IC), howeve the funtion should be the same.

author: othello
author_rank: Contributor
timestamp: July 13, 2014, 03:48:44 pm
content: The CRC warning he gets, could that mean some kind of corruption is in their firmware for that model causing these problems ?

author: rob77
author_rank: Super Contributor
timestamp: July 13, 2014, 04:44:56 pm
content: Quote from: tinhead on July 13, 2014, 01:57:10 pmapparently yes, the binary is broken.. tha's why i suggested to daemonize the executable from shell.my guess is that when running from a tty - it's in some kind of "debug" mode - dumping messages to the tty . and the guys messed up the binary and it doesn't turn itself into a daemon properly when started from initscript - therefore doesn't run from init scripts.if it works ok when redirecting stdout, stderr and stdin descriptors (the workaround i suggested), then the "solution" is just to modify the startup script (add the redirections to /dev/null) and wait for a new version from Hantek.

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 06:01:03 pm
content: Quote from: othello on July 13, 2014, 03:48:44 pmthe "*** Warning - bad CRC or NAND, using default environment" can be ignored, it does not have anything to do with firmware but only with env for bootloader.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 09:03:04 pm
content: Hi GuysTinhead - what is the password for the previous update I should try?111111 doesn't workThanksWanaGo

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 09:19:53 pm
content: Quote from: tinhead on July 13, 2014, 02:00:28 pmMost of the chips have been scrubbed! Thats not cool.2 places there are smt passives which have been hand reworked and reconfigured with little jumpers etc - mistakes on the PCB I assume.Ill get some photos up shortly, although it doesnt show much

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 09:22:15 pm
content: Actually, all of the chips you pointed to... are scrubbed :S

author: tautech
author_rank: Super Contributor
timestamp: July 13, 2014, 09:32:46 pm
content: Looks like you both will crack it in time.Fascinating thread, watching with interest.Think about tidying up later to make it an easy follow for anybody with similar problems.link to anotherHantek .....a work still in progress.https://www.eevblog.com/forum/testgear/hantek-dso1200-handheld-dead/msg452374/#msg452374

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 09:54:23 pm
content: Quote from: WanaGo on July 13, 2014, 09:03:04 pmno idea what you doing, but 111111 is for sure proper password.Quote from: WanaGo on July 13, 2014, 09:19:53 pmhmm, so i will try to recognize them from picturesQuote from: WanaGo on July 13, 2014, 09:19:53 pmyeah, that looks bit funny, but as long it works ...

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 09:58:16 pm
content: Booted up the scope this morning via the UART to get into dso.exeCouldn't extract the up files for the last release as the password didn't work, so I decided to update via the menu system in the dso itself using the up file on the USB Flash, and using the update feature.That worked fine. Scope is now booting fine.So yes, definitely something wrong with the last update.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 09:59:42 pm
content: Hmm deffinitely didnt work for me TinheadQuote

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 10:02:46 pm
content: dso.exe and English.lan attached, btw. decrypted with 111111. It is the file name, rename these (\ in _ or remove them.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 10:33:52 pm
content: Nope, still doesnt like it> gpg -o fw2.tar.tar.gz dso1kb_2.01.1.upgpg: CAST5 encrypted datagpg: encrypted with 1 passphraseFile `fw2.tar.tar.gz' exists. Overwrite? (y/N) ygpg: block_filter 0x1da96f0: read error (size=12249,a->size=12249)gpg: [don't know]: invalid packet (ctb=39)gpg: [don't know]: invalid packet (ctb=07)gpg: WARNING: message was not integrity protectedgpg: [don't know]: invalid packet (ctb=63)gpg: block_filter: pending bytes!Maybe the file is corrupt... ill try again.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 10:35:36 pm
content: Yup thats what it was. Copied it to my Linux VM again and all ok this time.Thanks.Photos coming, uploading.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 10:38:28 pm
content: Ok here are all the photos I have taken.Sorry not the best, some are a bit blurry.Hope you get the gist.Hantek Scope Pictures zipped LARGECheersWanaGo

author: tinhead
author_rank: Super Contributor
timestamp: July 13, 2014, 11:33:18 pm
content: thanks for the pictures, they are great. I do have now raw picture how they made it. Unfortunately you haven't made any picture of what under the channel shielding, in case you get some time to shot one i would be really thankful.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 13, 2014, 11:54:21 pm
content: oh damn... does it just clip off?I've closed it all up now.However I might have to get back in there...Ill def get you a picture though.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 15, 2014, 05:27:18 am
content: I contacted Hantek and they promptly replied with this message to me:QuoteWith this file:http://www.taktik.co.nz/EEVBlog/packet.zip

author: WanaGo
author_rank: Regular Contributor
timestamp: July 15, 2014, 05:39:30 am
content: It looks like this contains fixes for the bad script before, but when I connected the USB drive with the packet folder and emerg.do files in the root of the USB drive, and started the scope up, it didnt seem to do anything differently.Running the update program in the scope doesnt work either as it cannot find any updates on the drive.So not 100% sure what to make of this.

author: tinhead
author_rank: Super Contributor
timestamp: July 15, 2014, 08:08:10 am
content: emerg.do (and all the even newer recovery tricks) are implemented intodsodfile. You remember, you renamed it to stop the boot loop. That file need to be there and loaded, and when the firmware is crashing (or not loaded or missing) the dsod will look for "magic" on flash drive. You can see the output/status mesages on uart.Btw., on my dev board when i follow the instruction the dsod is looking for system*.up and not doing what it should doSo who knows what your handheld is doing (that depends on version of dsod)

author: WanaGo
author_rank: Regular Contributor
timestamp: July 15, 2014, 08:31:31 am
content: OK interesting stuff.They replied again when I said it didnt work.Here is what they saidQuoteand sent me the file I put here:http://www.taktik.co.nz/EEVBlog/uart_update.rarHave an excuse to open it back up now and take that photo for you under the shield covers.Will do that nowRegardsWanaGo

author: WanaGo
author_rank: Regular Contributor
timestamp: July 15, 2014, 08:47:09 am
content: Photos from under the cover are here. Also all scrubbed apart from the one near the opening.Sorry if they are not very clearhttp://www.taktik.co.nz/EEVBlog/DSO1152S-UnderCover.zipRegardsWanaGo

author: WanaGo
author_rank: Regular Contributor
timestamp: July 15, 2014, 08:59:20 am
content: Followed their instructions...Even worse now...Display is now completely snow after the main start pages.Here is the logQuote

author: WanaGo
author_rank: Regular Contributor
timestamp: July 15, 2014, 09:15:09 am
content: Oh dear.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 15, 2014, 10:01:07 am
content: Im stuck.Cant get it working no matter what I try.Seems that first update has cleared out some essential files or something, it no longer knows how to use the LCD.

author: tinhead
author_rank: Super Contributor
timestamp: July 15, 2014, 12:51:26 pm
content: when you look exactly the "last" update copied some missing libs and the new dsod, everything else (meaning the "broken" dso.exe, which seems to be not broken btw.) is the same. A new rcS and /model (what are they doing with that? i see it is on latest benchtop model as well, hmm, will have to take look on that). Anyway, so far evrthing should be ok.I'm wondering about two things:1- the new rcS is loading run.sh, which starts then the dsod, but not dso.exe (so i assume the newest dsod is calling the dso.exe or dso_bin itself, haven't check that but i trust them here, a day old "B" model firmware is doing this exact the same way). I'm wondering only that they implemented this on such old "S" models as yours, but yeah, they should know what they doing.2-what is with the lib and lcd drivers on your handheld?Look your bootlog:insmod: can't insert '/lib/cfbcopyarea.ko': No such file or directoryinsmod: can't insert '/lib/cfbfillrect.ko': No such file or directoryinsmod: can't insert '/lib/cfbimgblt.ko': No such file or directoryinsmod: can't insert '/lib/s3c2410fb.ko': No such file or directory....Please press Enter to activate this console. cannot open lcdi did loaded "BV" model image, from 2011, so even older than your "S" model, then installed the first "S" model firmware - all working, and now used that manual update procedure - and everything works here. So it looks like the new dso.exe HAVE TO BE started by dsod (or manually, but not anymore from rcS, so that's why you got new one). Anyway, everything seems to be working (as far i can see on my dev board).I your older bootlog there is no such problem with lib directory, so i assumeyou wiped that directoryat some time (this is why i did checked myself if one of hantek's updates was responsibe for this, but it wasn't). I would say, send them that bootlog, they can easily compile for you zip file with all the missing files (i would do this for you, but i don't have any dump of "S" model and even if my dev board works, i can not guarante that my lib dir is complette, so better when Hantek compile for you this).

author: WanaGo
author_rank: Regular Contributor
timestamp: July 15, 2014, 09:22:45 pm
content: HmmI haven't wiped anything manually.I sent them the logs I posted here, will wait I suppose.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 16, 2014, 03:40:50 am
content: Fixed, they send another update.Attached.Quote

author: WanaGo
author_rank: Regular Contributor
timestamp: July 16, 2014, 05:04:53 am
content: Quote

author: tautech
author_rank: Super Contributor
timestamp: July 16, 2014, 05:11:58 am
content: Quote from: WanaGo on July 16, 2014, 05:04:53 amYour new title: WanaGo, Hantek Software Support Technician.But you had us wondering for a good while.

author: WanaGo
author_rank: Regular Contributor
timestamp: July 16, 2014, 05:15:48 am
content: Haha - glad we got to the bottom of it.Big thanks to everyone involved.I hope this has helped or will help someone with a Hantek scope. Hopefully no one else will fall into this trap now that Hantek is going to fix the updates.Now, back to what I was trying to measure...

author: rob77
author_rank: Super Contributor
timestamp: July 16, 2014, 07:45:47 am
content: i've upgraded my DSO1102B with the last FW from Hantek - and no issues. probably that bug was only for the S series you have.i was hoping i will have a excuse to play with the uart on my scope ... but no "luck" - the upgrade went smoothly

author: tinhead
author_rank: Super Contributor
timestamp: July 16, 2014, 08:51:34 am
content: Quote from: rob77 on July 16, 2014, 07:45:47 amit was combination of missing files in the update files and newer dsod, with mumore functionality than the one on other models. Actually on latest benchtop "B" models Hantek implemented exact the same large dsod with more functionality, so it seems they will move all models to that. For us it is good, one can use that dsod to restore/recover and maybe even backup functionality.Quote from: rob77 on July 16, 2014, 07:45:47 amthis is what fuses are for, shot them and you have to open the enclosureAs i was younger, i always tried like that, hehe.Now i'm old and wise, so i can open everything and play with everything, to get eventually even wiser.

author: tinhead
author_rank: Super Contributor
timestamp: July 16, 2014, 08:53:09 am
content: Quote from: WanaGo on July 16, 2014, 05:15:48 amand i have to thanks for the pics!

author: rob77
author_rank: Super Contributor
timestamp: July 16, 2014, 09:02:43 am
content: Quote from: tinhead on July 16, 2014, 08:51:34 amactually i'm a linux guy since '95 - '96 and did a lot of embeded stuff in the past... but now i'm too lazy to play with anything what is in working condition.. once something doesn't work - then i have to play with it

author: WanaGo
author_rank: Regular Contributor
timestamp: July 16, 2014, 09:32:40 am
content: This new update has quite a few new things... Would hope so too, coming from a factory 2012 update...Save waveform, you now seem to be able to save an animation, other than just an image or CSV etc... thats kinda cool... need to try that.The DMM readouts in the top right actually seem to work....The help looks much more comprehensive too. I think.No doubt more..Are there any update change logs, to say what has been updated?Now I am more comfortable with this scope physically.... Tinhead.... what upgrades can I do to it? Is this one capable of the 200Mhz upgrade, or does it not fall in the right range of serial numbers or whatever?Has mention of Video in the utility menu, which is greyed out. whats that?SD card - unsupported. whats that for? I saw the blank footprint for the uSD card socket.Video - unsupported.Net Card - supported - have used that before.Store depth - 1MCheersWanaGo

author: WanaGo
author_rank: Regular Contributor
timestamp: July 16, 2014, 09:40:04 am
content: Oh and now I can measure some signals on CH1 in MEAS as well as CH2 signals, at the same time.Before I suppose I couldnt select CH2 so knew no better! hah. this is going to be handy. Like a real scope or something, rather than a toy.

author: rob77
author_rank: Super Contributor
timestamp: July 16, 2014, 09:51:26 am
content: it's strange - my DSO1102B is apparently an older model tha your DSO1152S , but both DDM & frequency in the top right corner were working just fine before and after upgrade. and same for the CH1 & CH2 at the same time in the measurements it worked before the update and still works after the update .

author: commongrounder
author_rank: Frequent Contributor
timestamp: July 23, 2014, 02:40:15 pm
content: I noticed that Hantek has a firmware file (dso1kb_2.01.1_DSO1152S(140408.0).up) that is dated 7-14-2014. Can someone confirm that this is the fixed version of the firmware that WanaGo was having trouble with? I don't want to try it on my S series handheld until I'm sure it won't cause the same problems. I don't have the equipment to access the ports on the inside, nor the linux experience to do what WanaGo has done (Thanks for catching the problem, by the way!).When something like this happens, is there any way to force a firmware downgrade through the USB port?Thanks!

author: tinhead
author_rank: Super Contributor
timestamp: July 23, 2014, 04:04:37 pm
content: Quote from: commongrounder on July 23, 2014, 02:40:15 pmyou mean on their onedrive? this is the same version, only extracted on 7-14-2014, but the same content. They deleted allversions from web and onedrive, but seems that they forgot that extraced version.So no, don't use that.I will compile later today working version and post on my onedrive (it will be dated named custom_dso1kb_2.01.1_DSO1000S(140408.2).zip and only the up file dso1kb_2.01.1_DSO1000S(140408.2).up )Quote from: commongrounder on July 23, 2014, 02:40:15 pmas long the dso.exe (dso_bin) is running - yes - because one can connect over lan or usb with that tool from Peter Dreisiebnerhttp://peter.dreisiebner.at/dso-usb-tool/then go to shell tab and copy manually older files from flash drive to DSO. Then after reboot the DSO will use them.However, when the dso.exe (or dso_bin) is not working, then there was no other way than the physical uart.Now with the new dsod (watchdog) for benchtops and handhelds one will have a way to restore/downgrade DSO evenwhen dso.exe (or dso_bin) is crashing. It is somehow funny that the first firmware with the new dsod alread createdproblems, because of the dsod. But yeah, something like that can happens when one forgot to copy files into updateor run test twice (where the system does have already files which are missing in update ...).

author: commongrounder
author_rank: Frequent Contributor
timestamp: July 23, 2014, 05:29:36 pm
content: Thank you, tinhead. I will keep watch for it. This is an interesting problem. I'm so glad I saw this thread, as I check Hantek's onedrive regularly for firmware updates and would have blithely installed this defective one and ended up in the same boat as WanaGo, but without an easy way to fix it.

author: rob77
author_rank: Super Contributor
timestamp: July 23, 2014, 06:13:50 pm
content: Quote from: rob77 on July 16, 2014, 09:51:26 amups... early judgment.... the DMM & frequency in the top right corner are working... but only after pressing the measure button - but they keep working since then - even after menu off button pressed.. so not a big deal

author: tinhead
author_rank: Super Contributor
timestamp: July 24, 2014, 10:29:00 am
content: here we go, on my onedrivehttp://1drv.ms/1hf4SgOin firmware->hw1.00.4 there is the custom_dso1kb_2.01.1_DSO1000S(140408.2).zip file. Inside that file you will find dso1kb_2.01.1_DSO1122S(140408.2).up and extra.zip. Copy that dso1kb_2.01.1_DSO1122S(140408.2).up to empty flash drive. Then unzip that extra.zip to that flash drive, you will see then "packet" directory. This is necessary due the lack of NAND space, the update procedure need always twice the size of decrypted update. So my custom update is copying part of reqiered files directly from flash drive, so that it can work even on low space models (like my test unit from 2011). Remove that flash drive from PC and insert into handheld, run now the firmware update from utility->f2->f4. Due amount of files it can take some extra time, my script is doind 10sec. loop to ensure that all files has been written. So wait until the led stopped to lit and the "plaese reboot" pops up on display. Some models, and this depends on what fw version already installed, will anyway do an automaticaly reboot, so that's fine as well.After the reboot or power cycle you should see then 140408.0 as fw version.

author: commongrounder
author_rank: Frequent Contributor
timestamp: July 24, 2014, 01:26:43 pm
content: Thank you so much tinhead! Later on, after I finish work, I will give this a try on my DSO1122S unit and report the results. Once this is done, should the new DSOD functions work as Hantek had intended? It would be nice to think there is some way, other than cracking open the case, to recover a scope with issues.

author: tinhead
author_rank: Super Contributor
timestamp: July 24, 2014, 01:39:25 pm
content: Quote from: commongrounder on July 24, 2014, 01:26:43 pmyes, i did tested this already, meaning when i kill dso.exe (tested with broken one and with none) then the dso display stays black and after some time it does reboot. When i then insert flash drive with e.g. system_restore.up a message popups "firmware update", where of course one have to have an system*.up file encrypted with special password (in this case "dsoduse"). There is as well the emergency way, where one have to copy "emerg.do" file to flash drive. That file is nothing else than encrypted update shell script, which can then do restore or backups or what so ever. This script need to be then encrypted with special password (in this case "949307"). There seems to be small "model check" implemented, i think to prevent people from installing wrong firmware on wrong model, haven't tested yet how this works in detail, all i saw is that the systemxxx.up or hantek.up need to contain "model" file in which the model name is stored (and that name have to be the same as on the DSO already). In case o the isolated handhelds this model name is "dso1000s", so it is universal for all models in own model category. Sometimes i think they have too much time at Hantek

author: commongrounder
author_rank: Frequent Contributor
timestamp: July 25, 2014, 02:06:51 pm
content: Okay. I downloaded and extracted tinheads "custom_dso1kb_2.01.1_DSO1000S(140408.2).zip" file and followed the instructions earlier in this thread very carefully. Something unexpected happened, though. After starting the upgrade process through the menu (untility,>f2,>f4), things went as expected and the USB flash drive was blinking. This was going on for a few moments. I turned away to answer the phone and when I looked back, the screen was blank, but power was on. The USB drive was no longer flashing. To be certain it was hung, I left it go for 15 minutes, with no change. I had the unit fully charged and plugged in to the AC adapter. So, after nothing changed, I forced the unit off with the power button and restarted. Now I get a looping first screen, second screen, blank and restart. It seems similar to what WanaGo had happen. I can't think what I could have done wrong. I followed the procedure to a tee.I'm not panicking about this. I tried this with the full awareness that it is experimental. I use this scope for measuring bridged output audio power amplifiers, and I have my Fluke 199C that works for the purpose, so I can still do my testing. Screen and data captures are so much easier with the Hantek, which is why I got one (plus the screen is so much better). I know that there is a solution in this thread, but I am scratching my head as to what happened. I wish I hadn't turned away! As I said before, I'm not too well versed in the software aspects of this, but am willing to try, if I can get the proper hardware interface. Thanks for any suggestions!

author: tinhead
author_rank: Super Contributor
timestamp: July 25, 2014, 03:00:57 pm
content: how crap is that, i did the installation on total 3 boards with 3 different images - and that with fw level from 2011, 2012,2013 and even the latest 2014 to ensure that an ANY stage of better said with any version of hw/fw the update is running. Any then the first DSO in field is crashing :\Ok, i will help you with that. Copy dso1kb_2.01.1_DSO1122S(140408.2).up to empty fash drive and rename it to system1.upThen insert it into and tell me if you see something on screen and/or if then led is blinking. I need to know at what stage your DSO is now ...

author: commongrounder
author_rank: Frequent Contributor
timestamp: July 25, 2014, 03:43:59 pm
content: It was the FLASH DRIVEWhen I attempted to load the renamed firmware file onto the flash drive I've been using for this procedure, I got read/write errors. First time that has ever happened to me, but lesson learned. Don't use a $3.99 flash drive for firmware updates. The files looked fine when I had copied them on yesterday, so the failure could have occurred anytime.I loaded the renamed system1.up file to a fresh, name brand, flash drive and started the scope. I still get the first "picture" screen, then a firmware version screen for a moment, then blank for about 10 seconds before a recycle. The activity light on the flash drive flickers through all of the first cycle and part of the second and then goes out. Nothing but recycling of the scope after that. Does that mean some of the loading programs (like the DSOD) are corrupted?

author: tinhead
author_rank: Super Contributor
timestamp: July 25, 2014, 06:27:22 pm
content: What a crap. Did you remember what version was installed before the update? I will try then to find solution for you.I did removed that custom fw from my onedrive, i will have to implement crc check inside, without it is too risky.

author: commongrounder
author_rank: Frequent Contributor
timestamp: July 25, 2014, 06:46:46 pm
content: I was running the ver 2.01.1(140212.0) firmware previously. Thank you for your efforts, tinhead. I strongly suspect that the problem was hardware related at this end, rather than with any of your work. Your analysis and discussions of Hantek hardware and firmware have been totally outstanding!Should I start shopping around for one of those little USB to TTL interfaces? I only have a USB to RS-232 variety right now, which I know is not electrically compatible. Thanks!

author: tinhead
author_rank: Super Contributor
timestamp: July 27, 2014, 11:16:46 pm
content: i did tested everything i could test, but without success. The only way is now to work over UART. I will of course guide you as soon you bought/build such adapter. Sorry for that.

author: commongrounder
author_rank: Frequent Contributor
timestamp: July 27, 2014, 11:36:28 pm
content: I have a USB to TTL-serial interface on order. When I have the hardware set up, I'll drop back into this thread. Thanks so much!

author: commongrounder
author_rank: Frequent Contributor
timestamp: August 08, 2014, 08:07:07 pm
content: Greetings!The USB to TTL uart interface arrived today and I got it hooked up. When I started the scope, I received a string of messages exactly like the first one that Wanago received after his firmware update problem. I've read this thread through several times, and some of the Linux commands started making sense to me. The first thing I did actually accomplished two things: It fixed the problem, and proved that my defective USB flash drive caused my scope trouble, not tinheads fixed (dso1kb_2.01.1_DSO1122S(140408.2).up) firmware.Okay, so I monitored the scope as it ran through the initialization loop to the pausing point, just before the auto restart. I then hit enter to enable the console. After that, I typed "killall dsod". That stopped the restarts. I then simply entered "/dso.exe". I think I was lucky, and the main program file was not corrupted/lost, because the scope came to life. I wasted no time and inserted a good flash drive with tinheads modified firmware and files (as above, dso1kb_2.01.1_DSO1122S(140408.2).up) which I had kept. I ran the updater right from the scope Utility menu as you would normally do a firmware upgrade. It ran (a bit longer, as tinhead said it would with the extra files on the flash drive), and then restarted. Voila! The scope started normally and has been working ever since.To tinhead: Thank you so very much for your dedicated interest in the Hantek/Tekway gear. It saved me tons of grief. I believe you should repost the dso1kb_2.01.1_DSO1122S(140408.2).up fixed firmware on your onedrive site for others to use. It ultimately worked for me, and I have the benefits of the new firmware version, as Wanago has described. I do wish Hantek would take that last copy of the bad firmware off of their onedrive site. It sits like a land mine for unsuspecting "S" series scope owners (I wonder how many there are of us?).Wanted to add: My DSO1122S has a hardware version of 1.02 dated 9-2012

author: tinhead
author_rank: Super Contributor
timestamp: August 13, 2014, 07:17:58 am
content: you welcome! and of course good to hear that your handheld is back working.

author: aerra
author_rank: Contributor
timestamp: August 17, 2014, 08:34:32 pm
content: Hello. Here is my new DSO. The board is newer than posted in this topic, so attaching photos - may be interesting for anybody. FPGA is Cyclon IV, in WanaGo's held - Cyclon IIIWhat is strange - the shields of input circuits are not soldered - what a bullshit?UART has standart pinout

author: tinhead
author_rank: Super Contributor
timestamp: August 17, 2014, 09:05:21 pm
content: Quote from: aerra on August 17, 2014, 08:34:32 pmthanks for these great pictures (any chance to get originals with better resolution via PM?)Quote from: aerra on August 17, 2014, 08:34:32 pmand that's really surprise!Any chance that you made backup of the NAND and share with me ? (PM)

author: aerra
author_rank: Contributor
timestamp: August 18, 2014, 10:29:30 am
content: Yes, of'course. I outed the UART cable to battarey partition, so it's no problem to get backup (but i have to understand how to do it). Photos are 3MP, i'll sent them later.

author: tinhead
author_rank: Super Contributor
timestamp: August 18, 2014, 10:59:02 am
content: that's cool thanks!Knowing now that the latest "S" models (hw1.00.4) are S3C2416 SoC and Cyclone IV based no wonder that there was issues with latest firmware updates on older "S" models (hw 1.00.1 and hw 1.00.2).

author: aerra
author_rank: Contributor
timestamp: August 20, 2014, 05:21:03 am
content: Trying to calibrate the compensacion of probes using 1kHz scope's output . Problem: native probes don't want to make a right meandr, in end position of probe's capacitor the meantr is still not right. I tried another probes and they are better. And one more - the meandr is bit different in AC and DC modes, on both channels. So it seems that input capacistances in AC and DC are different. Is it possible to regulate this? There are two variable capacitors in input circuit under the shield, turn them?And is there a needence to solder the unsoldered sheelds of inputs?(bad english, learning)

author: aerra
author_rank: Contributor
timestamp: August 20, 2014, 04:37:06 pm
content: DC and ACBackup sent to PM.Maybe let's go to topic "Hantek - Tekway - DSO hack - get 200MHz bw for free" ?

author: tinhead
author_rank: Super Contributor
timestamp: August 20, 2014, 06:21:18 pm
content: as i don't have isolated model, i can't answer. But maybe the other ppl here with "S" models can check it.

author: commongrounder
author_rank: Frequent Contributor
timestamp: August 21, 2014, 08:29:56 pm
content: @aerraI set up my DSO1122S exactly the same way as your screen images (except I can't tell which averaging setting you were using, I chose 64). I set the probe compensation on the supplied probes as usual for the flattest tops with minimal over or undershoot. Below are screen shots of those, along with a couple using a faster timebase to show the leading edge a bit more clearly. I personally think this is quite acceptable, considering the noise floor of the inputs.Also, I would not touch the internal trimmers of the scope, or change anything about the shielding. You could easily throw your scope out of calibration and have no reference to depend on for measurements.The first two images are with DC coupling and the second two are with AC coupling. Hope this is helpful.

author: aerra
author_rank: Contributor
timestamp: August 23, 2014, 08:06:14 pm
content: Thanks

author: aerra
author_rank: Contributor
timestamp: January 06, 2016, 08:14:36 pm
content: good day all!On Hantek website there is last firmware for 1000s dated 01.2015. Is it good? Did anybody tried to update on it? My current versions in attached log

author: commongrounder
author_rank: Frequent Contributor
timestamp: January 07, 2016, 02:59:29 pm
content: I did install the "dso1kb_2.01.1_DSO1122S(150108.0).up" firmware on my DSO-1122S a while back. There were a few minor changes and spelling corrections. I *think* it improved stability (fewer lockups), although that can sometimes just be wishful thinking.One thing I need to figure out is memory handling. It won't allow setting the waveform memory over 512K unless certain conditions are met. I don't use long memory too often (slows down acquisition too much), so I can't remember what is required to enable the 1meg memory length.In any case the firmware upgrade process went without incident, so it seems safe to install.Good Luck!

author: aerra
author_rank: Contributor
timestamp: October 01, 2017, 11:31:27 am
content: Good day.Today the last update is dso1kb_2.01.1_DSO1152S(170801.0).up.Have anybody try it?

author: justincr83
author_rank: Newbie
timestamp: January 13, 2018, 01:19:41 am
content: my dso is dead, i have no idea what's wrong with it. i'm trying to figure out what is wrong with it but without luck...anyone knows where and if there is any uart port on this unit?here's the link to the started thread.https://www.eevblog.com/forum/chat/hantek-dso8060-dead-possible-fix/here's the pcb front and back pictures attached (DSO 8060)

author: WanaGo
author_rank: Regular Contributor
timestamp: January 24, 2019, 04:43:21 am
content: Greating again, Hi TinheadStill using my trusty DSO1152S, going well.I just replaced the Battery and got a new Fan from Hantek, as my battery was crap from day 1, only lasted a few minutes, but died about a year ago completely. Fan was noisy and spun slow and lumpy, and finally stopped spinning completely last year. New items are great, like having a new scope again. hah.Reason for digging up this post again. I don't believe I ever did the 200Mhz upgrade on this, I believe I left it at 150Mhz as stock.Reading through old posts again, I see mention of the linkhttp://peter.dreisiebner.at/dso-usb-tool/However it's not working.Is that tool still usable and available somewhere? Is it possible to do these mods without going via the UART?So reading back on my own posts, I have the following:DSO1152S2.01.1(170801.0) Software10010x555583e8 HardwarePCB is 2012-04 dated and 1.00.1 RevisionThe serial number is > 6000000, which seems hugely higher than instructions of Post 1 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/) which are > 15000 then use xyz, etc.If someone can point me in the right direction again, that would be a huge help. I will continue to read the hundreds of pages again to try and find the answers though.Quotefrom:https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg91877/Is this still the method to change to 200Mhz and to change the logo to show 200Mhz model?Thanks

author: WanaGo
author_rank: Regular Contributor
timestamp: January 24, 2019, 05:53:52 am
content: Turns out I did do this... except for the logotype.dis file, this is still on HANTEK_DSO1152SThe others are set to dst1202b and the dst1202b file is present in the / folderquestion though, whydst1202b and notdso1202b?and why Hantek_DSO1202Band not Hantek_DSO1202S?Just want to make sure im doing the right though.should in my case they be "dst1202b" file in /, and parameters in /logotype and /tmpdst files, and "Hantek_DSO1202S" in /logotype.dis file?

author: WanaGo
author_rank: Regular Contributor
timestamp: January 24, 2019, 07:54:25 am
content: Got the tool, thanks for the PM Peter. I couldnt reply to you though, i seem to be 'blocked' from doing so.Has anyone attempted to edit the /disp file to modify the logo?Any success?

author: WanaGo
author_rank: Regular Contributor
timestamp: January 24, 2019, 08:31:40 am
content: I had just spotted that too, thanks.So ive made the logo (640x480 in my case, 24 bit etc), made the ebm file with the tool, and now to do the disp stuff.I have the disp file on the computer, but unsure exactly what I am looking for to find this offset, and also how to split the file. I am guessing this is to make the disp1 and disp2 files from the original disp?Is there any information on that part available?Thank you

author: WanaGo
author_rank: Regular Contributor
timestamp: January 24, 2019, 11:15:47 am
content: OK, figured it out.The information for the DSO1152S didn't seem to work which is strange, so here is what I found out. No doubt a reason why.Instructions stated it was to be 24bit BMP, turns out this needed to be 16bit BMP. 24bit was too large.DSO1152S is 640x480, compared to the example which is 800x600 (but it did state this needed to change).Inside the /dso/app folder on my machine, is nothing but dsod and dsod.old files, there is no disp file in there. disp is only found in the root folder /.The tool required disp1 and disp2, which then get combined around the ebm file to form the new disp file.Comparing disp1 with my original disp file, part 1 ends ~ 0xb10 in with 0x0100 0x0200, so the equivalent in my file is at 0xb04.Comparing disp2 with my original disp file, part 2 starts ~0x96b04 with '/dev/fb0, just fount the equivalent in my file which is at 0x96b04 too.Therefore the 'ebm' is 0x96000 long, which corresponds to a 640x480x2=614400 ebm.In the Image2Lcd tool, there are actually 2 options for 16bit. Initially, I selected the 2nd one which resulted in a 900KB file (9821600 bytes) which I think was actually 24bit, and then I selected the first one which resulted in a 600KB file (614400 bytes) which was correctly 16bit.Combined them together resulting in a 608KB file the same as the original. The 24bit file resulted in a corrupt startup image and simply didn't work.I uploaded the file to /dso/app and nothing happened. Uploaded to / instead, and boom, the new logo appears. Lovely.Old and new images attached for reference.

author: WanaGo
author_rank: Regular Contributor
timestamp: January 24, 2019, 11:16:49 am
content: Yes, spot the typo

author: WanaGo
author_rank: Regular Contributor
timestamp: January 24, 2019, 08:03:25 pm
content: The next part of the puzzle is the EEPROM contents.Using Tinheads utility instructions from here:https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg467313/#msg467313I firstly had a look at the i2c.log file on the / folder of the scope.It is essentially blank. Anyone know why?Die Datei '/i2c.log' wurde gelesen. Größe: 8192 BytesDie ersten 256 Bytes:00000| 00 00 009F 0300 00 00 00 00 00 00 00 00 00 00 |................|00010| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|00020| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|00030| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|00040| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|00050| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|00060| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|00070| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|00080| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|00090| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|000A0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|000B0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|000C0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|000D0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|000E0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|000F0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|Die letzten 256 Bytes:01F00| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01F10| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01F20| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01F30| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01F40| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01F50| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01F60| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01F70| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01F80| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01F90| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01FA0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01FB0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01FC0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01FD0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01FE0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|01FF0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|Carried on anyway. Connected with USB and connected the Tool, and all the options were 'default', nothing specific looking for my scope at all.My PCB is my scope is 2012 dated and is Revision 1.00.1 yet is a DSO1152S. HW version is 10010x555583e8.Based on the Version file, selecting 1001 in the tool would be the wrong move. It suggests 1002 and 1004 are checked for by the firmware. Does anyone have any suggestion as to what mine should be?My Serial number is DSO06000xx, so is well above the 15000 threshold, even though its 2012 dated. I purchased it in 2013.I set the Language to English etc and clicked the write button for the centre section, hoping that it might trigger the scope to update the i2c.log file just from having the language items updated, however nothing happened. In the text box to the right of the tool, it came up with 'failed' shortly afterwards. Wondering if my model is just odd and the EEPROM is somehow different...?The end game is to try and install the SD and Video functions. I have LAN by default already installed and working.The next question is where do you obtain the video files to put on the SD card in the first place? I cannot find information on this yet.Does the card have to be a specific capacity and format?Another question is around the LAN IP address. Every time I power cycle the scope, my IP address is reset back to default. Is this normal? Is there any way to have it remember the IP address, as its a pain in the butt.Thanks

author: WanaGo
author_rank: Regular Contributor
timestamp: January 25, 2019, 09:08:06 am
content: I just acquired dso1kb_2.01.1_DSO1152S(180821.0).upNot game yet to upgrade, anyone interested?

author: WanaGo
author_rank: Regular Contributor
timestamp: January 26, 2019, 12:46:28 am
content: The manual states thisQuoteQuestion is where do you get the official videos from? And what do the videos even show? Or are there no videos officially? I thought these might be help videos or something, or is it just the generic ability to play a movie or something, for whatever reason...

author: lewiss66
author_rank: Newbie
timestamp: August 07, 2019, 07:35:30 pm
content: Quote from: WanaGo on January 24, 2019, 04:43:21 amHi WanaGo. Just bought the DSO1122S from ali and got the same issue as yours. The fan is noisy when I move the scope in certain positions. Did you have your fan replaced on warranty or did you have to order it and installed it by yourself? Thanks

author: WanaGo
author_rank: Regular Contributor
timestamp: August 07, 2019, 08:59:20 pm
content: Quote from: lewiss66 on August 07, 2019, 07:35:30 pmHi lewiss66I got the battery and the fan from Hantek directly, paid for the battery and they sent me the fan for free. I installed them both myself, easy job.

author: lewiss66
author_rank: Newbie
timestamp: August 25, 2019, 10:19:21 am
content: Ok Thanks WanaGo,I might check for a replacement aftermarket. But first I need to know how to open this scope.Could tel me how to open it?It seems that I first need to remove the rubbers on the sides by pulling them but not sure. They are pretty stiff.

author: WanaGo
author_rank: Regular Contributor
timestamp: August 25, 2019, 12:33:58 pm
content: Quote from: lewiss66 on August 25, 2019, 10:19:21 amPop the end caps on the rubbers off, which reveals a couple of screws.

author: Alfik
author_rank: Newbie
timestamp: February 03, 2021, 07:01:06 am
content: Quote from: WanaGo on January 24, 2019, 08:03:25 pmDid you solve this problem? I have DSO1062S, fw 2.01.1 (130129.0), hw 1.00.1 and my IP address is reset back to default also.Thanks

author: WH_Mike
author_rank: Newbie
timestamp: January 23, 2024, 09:56:31 am
content: Quote from: WanaGo on July 15, 2014, 05:27:18 amHello WanaGo!After update my DSO1152S I have loop reboot too.Do you still have "packet.zip" file from Hantek service?Previouse link is dead.If so, can you share it to me?Best wishes and thanks before.Mike

author: WH_Mike
author_rank: Newbie
timestamp: February 24, 2024, 01:00:42 pm
content: Hello friends.I was able to restore the functionality of my DSO1152S by analyzing the composition of the decrypted firmware archive 170801.In short, then:1) I recorded the decrypted and unpacked archive on a USB flash drive.2) at the end of the failed download, the oscillator closed the operation of the watchdog timer by issuing the killall dsod command3) created the /tmp folder in the root and copied all the files of the unpacked archive there4) launched the update script file from the root do_update.sh in the copied archive folder5) Restarted the oscilloscope.Voila, everything works!If you are interested, below is a complete, directed uart log of a single session, including both erroneous commands and correct ones with the results of their processing:

author: WH_Mike
author_rank: Newbie
timestamp: February 24, 2024, 01:08:42 pm
content: Quote from: WH_Mike on February 24, 2024, 01:00:42 pm