Products > Test Equipment
Hantek DSO1152S - Wont boot after firmware update
tinhead:
--- Quote from: commongrounder on July 24, 2014, 01:26:43 pm ---Once this is done, should the new DSOD functions work as Hantek had intended?
--- End quote ---
yes, 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 >:D
commongrounder:
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! :-BROKE
tinhead:
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.up
Then 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 ...
commongrounder:
It was the FLASH DRIVE |O When 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?
tinhead:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version