HANTEK DSO5102B self bricking oscilloscope - Page 1
Forum section: electronics / general

author: ChrisMe
author_rank: Newbie
timestamp: March 04, 2012, 10:31:43 pm
content: Hey guys,funny thing happened today:Turned on my Hantek and it just went exactly like the one in that vid:I browsed quite a while here, used google, even commented on that video as you might see, which led me here in the first place, but I couldn't find a pratical solution, does anyone have an idea?If possible I want to spare myself the pain of returning this to china...

author: nordiste
author_rank: Newbie
timestamp: March 05, 2012, 07:32:40 am
content: hi,i tell you on the video page who you can read that thread to solve your problemhttps://www.eevblog.com/forum/general-chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/you must to see 879th post to see where is CMOS UART PORT (3.3V max)(you can use bus pirate or other systems who works on 3.3V UART)i think you don't have pin header but only PCB holes to make connectionsafter connected, power up DSO and you will see a linux boot.you must delete (or rename) a file :rm -f /param/sav/run1kb*you can see reply #1121after that, DSO works fine, ou just have to restart it.don't forget to update firmware with newest version just after solving your problem.

author: user12
author_rank: Newbie
timestamp: March 05, 2012, 11:08:09 am
content: Hi,yesterday I had the same problem on a tekway. Here is what I did:during boot I repeatedly pressed Default Setup (period less than a second)after several trials I managed to get the device responsive againHope this helps, good luck.Walter.

author: tinhead
author_rank: Super Contributor
timestamp: March 05, 2012, 11:42:56 am
content: i recommend to install this :https://www.eevblog.com/forum/general-chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg93999/#msg93999Currently is a bit crazy, DSOs produced in December are loaded with firmware which is crashingwith exact the problem you got - not responding to anything.Hantek released new firmware few days ago after massive message flood from users,however in hurry they not tested long memory in dual channel mode (which is producing nice artifacts).When you don't care about two channels bug you can install the firwmare from Hantek website (2.06.3 12 - 120224.0),if you need two channels but can work with your current firmware (even if it's crashing) consider no updating,There will be soon new firmware fixing this two channels artifacts problem.

author: grenert
author_rank: Frequent Contributor
timestamp: March 05, 2012, 11:55:43 am
content: Quote from: tinhead on March 05, 2012, 11:42:56 amJust wondering: How did new firmware break something that used to work? Did they revise the hardware in December?

author: tinhead
author_rank: Super Contributor
timestamp: March 05, 2012, 12:54:01 pm
content: Quote from: grenert on March 05, 2012, 11:55:43 amFPGA design has been changed as part of jitter reduction fix.Quote from: grenert on March 05, 2012, 11:55:43 amfirmware is just a piece of code, in this case linux application therefore there are bilionsof ways how to produce overflow and crash that application.In principle not a big deal, in such case reboot would fix it, but not this time ...This time the application is writing current configuration while crashing, and of course as theconfiguration is broken after reboot the application is not able to startup.Hantek was pushed by the community to fix 16 bugs, they fixed 12 of them within 3 months,one of the next of the list was jitter reduction so they changed FPGA design.Additionaly (this was never asked, becaue in principle everybody accepted that chinese are cheatting a bit)they changed the sample rate to 500MSs per channel when in long memory mode instead of 400MSsand rewrote complettly the timebase and sampling buffers. this is really nice move, however theyprobably oversaw that a combination (especialy) of the new FPGA design and new timebase is producingfunny buffer overflows.What they released is firmware which is not crashing anymore killing these DSOs (well, imagine i would nothack this DSO and nobody would be aware of how to connect over uart of fix it? right, such DSO would be killed!)but in hurry the probably oversaw that dual channel works only with small memory and single window goodRight, good QC would ... but anyway they working on that now.Nevertheless, the fix i posted in link above will help users to default the DSO to default settingevery time they need it - and no need to open the DSO and play with UART/linuxa anymore.

author: ChrisMe
author_rank: Newbie
timestamp: March 05, 2012, 06:37:53 pm
content: Allright, at first: HUGE THANKS TO ALL OF YOU FOR YOUR HELPFUL REPLIES.Then @ Nordiste, yes that was me posting on that utube vid, i also checked the hantek hack topic, but it didn't manage to read all 1140 posts, so i didn't exactly know which uart settings i would need and awhich file to delete. then if possible i'd like to avoid soldering a 10pin header into the pcb for warranty reasons. Anyhow thanks for telling me which file's the troublemaker@user12: i love you man: your tip did the trick!!!@tinhead: im using 111226.1; so no suprise there... Furthermore, i've been lurking around here quite a bit and you sir appear to be a f*cking genious. It seems that there are few here who understand these oscis as good as you to. So with respect to you, thanks for the link and the update files themselves.Basically I'll stick to what I've got, as I often need two channels to check timings on my Atmega UART/SPILastly, again, thank you very much!