Products > Test Equipment
Hantek DSO1152S - Wont boot after firmware update
<< < (4/26) > >>
WanaGo:
>cat sys.inf

[DST type]dst1202b
[soft version]2.01.1(121207.1)
[fpga version]0x555583e8
[start time]-1
[update time]0
WanaGo:
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).up
dso1kb_2.01.1_DSO1152S(140408.0).up

Its that 2nd one that I tried today which got me into this mess.

Looks like I was running 121207.1 prior to that.
WanaGo:
now thats interesting...

./dso.exe

scope 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 140408

Turned it off again.
will wait for instructions
tinhead:
i'm on windows, so some steps might be different on windows:

1- go to Hantek OneDrive http://1drv.ms/1cA9vjg and download firmware for your model (DSO1152S_Firmware.zip)
2- unzip that file, you will get dso1kb_2.01.1_DSO1152S(140408.0).up
3- get gnupg, run in command prompt from directory with the *.up file like
 gpg -o fw.tar.tar.gz dso1kb_2.01.1_DSO1152S(140408.0).up
4- when asked type password: 111111
5- now you should have that file fw.tar.tar.gz created in this directory
6- open it with winrar, then the content again with winrar - you will see "tekwayup_client" directory, unpack it to harddrive
7- in that directoy there will be "update" script, in my opinion there is bug, there should be

[cmd] mv /tmp/tekwayup_client/dso.exe   /dso_update.exe

and not

[cmd] mv /tmp/tekwayup_client/dso.exe   /dso.exe

I 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 that  :palm: One can see in the bootlog "no update file to foud" which
is 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 boards
with 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 DSO
2- 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 dsod

and then arrow key up (to reply last command) and ENTER, and again :) Until 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 with

 ls /mnt/udisk/

You should see that copied before dso.exe. Copy it now to root of the DSO, like

 cp /mnt/udisk/dso.exe /dso.exe

then flush the cash with

 sync
 sync

and give executo rights

 chmod 777 /dso.exe

No 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 need
to copy other files from that "tekway_client" directory. In case you applied different update, let me know this, then
you will have to copy other files as well.
WanaGo:
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 shortly

Thank you!
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod