Sorry i was not clear.
oh yes, you was.
I tell you something, your DSO is hw1007, with max. firmware 2.x, and not 3.x as you said. So that here is wrong
>> The correct BIOS from Hantek looks to be "dso5kb_func_dso5202b20140111.up"
and this corrent:
>> but I also have "dst1kb_2.06.3_15202b_fact(130814.0).up"
The DSO 3.x fw is using "dso5000b" as password, the DSO 2.x fw "0571tekway".
Anyway, MSO - and that means 2.x and 3.x fw - is using "0571tekway" as well. But on Hantek (and as wel Voltcraft website) there are information WHAT fw can be uised on WHAT hardware (talking about MSO). And of course there is absolutely no reason to use MSO firmware on DSO (one can do this only when knowing what to do first, but even then, without mso hardware there is no benefot of using the MSO firmware on DSO. Actually the DSO firmware is better, sure no MSO functionaliuty but DSO is stable).
nothing to the scope since since then.
sure, this is because MSO is using differnet libs, drivers, root fs and kernel. So once installed the dso.exe (from MSO formware) will crash, and even worse, the atchdog (dsod process) might reboot your DSO over and over again (until you kill it).
I need some help!
oh well, you do. So let's take a look on what the fw update did to your DSO. The "update" script looks like:
[cmd] mv /tmp/tekwayup_client/lcd.ko /dso/driver/- so you need lcd.ko from an DSO
[cmd] rm /protocol.inf
[cmd] mv /tmp/tekwayup_client/protocol.inf /protocol.inf- and protocol.inf
[cmd] mv /tmp/tekwayup_client/rcS /etc/init.d/rcS
[cmd] chmod 777 /etc/init.d/rcS- and rcS
[cmd] mv /tmp/tekwayup_client/dso.exe /dso.exe- the dso.exe as well
[cmd] mv /tmp/tekwayup_client/dsod /dso/app/dsod- the watchdog executable
[cmd] rm /help.db
[cmd] mv /tmp/tekwayup_client/help.db /- help files from DSO
[cmd] rm /OurLanguages/*
[cmd] mv /tmp/tekwayup_client/*.lan /OurLanguages/- language files
[cmd] mv /tmp/tekwayup_client/icon/* /icon/- and maybe even icons, but normally not.
Now let's take a look what of these files is included in e.g. DSO fw dst1kb_2.06.3_15202b_fact(130814.0):
rcS
dso.exe
dsod
protocol.inf
help.dband finally folder "OurLangauges" are all withinn that update file. The lcd.ko is missing, but when you look inside rcS you will find out that the lcd.ko is not in use on DSO, but only MSO. So you can ignore it. That said all you have to do is do decrypt/untar/untar/unzip the dst1kb_2.06.3_15202b_fact(130814.0).up file, copy all these files to usb flash drive, insert it into your DSO, connect via UART (yes, you need physical connection here, and of course converter etc. UART<->USB) and then first kill the "dsod" and copy/overwirte all the MSO files with DSO version again. And then finally you have to change permission in root directory to +x, something like "chmod 777 *" is for sure ok. T
That's all .. almost. Now you have to replace the /param/sav/r* file and reboot DSO. Now your DSO should work again.