Hantek - Tekway - DSO hack - get 200MHz bw for free

[lemon]

Please, can someone to feedback us about this test?

Set a waveform to screen (triangle, sinusoidal).
Move the waveform to up or down so to cut the edge of the screen.
Now invert the waveform.
What is appearing? Is it normal or the bottom of waveform is also cutting?

Here is a short video about this. https://www.dropbox.com/s/gzstblo60y50d7z/2013-11-07%2000.02.43.mp4

[primsam]

@lemon

i think this is the wrong section  for your problem, in the video is a owon brand device that has nothing to do with hantek/teckway/voltraft and so on ...

[n8ddd]

updating...here's attached log console.the mtd size of "rootfs"is 121Mb,then why the nunddump is dumping 124Mb?
without -b option is dumping forever

[tinhead]

updating...here's attached log console.the mtd size of "rootfs"is 121Mb,then why the nunddump is dumping 124Mb?

this is because you dumped the data with OOB blocks (which is necessary for restore over JTAG or the method i've published)
Eaach every (and that depends n flash size and structure) about of byte there is OOB block data, so the 121Mb together with OOB block will larger, in your case 124Mb.

[vmpn]

I also see some errors about linuxrc not starting. I need to double check config for my busybox build. Meanwhile please do not replace the one on the DSO.  You can put it in another folder and run it as:

{Path}/busybox nanddump ....

[tinhead]

Please, can someone to feedback us about this test?

Set a waveform to screen (triangle, sinusoidal).
Move the waveform to up or down so to cut the edge of the screen.
Now invert the waveform.
What is appearing? Is it normal or the bottom of waveform is also cutting?

there are not such issues on Tekway/Hantek, nor these others nown from Owon (with inverted and moved to top signal).
This must be firmware bug in Owon firmware, you should tell that Owon (or rf-loop, he is collecting bugs as well).

[n8ddd]

i've noticed that with busybox from vmpn the dump files are like this

boot.bin-1.03mb
logo.bin-2.06mb
kernel.bin-4.12mb
root.bin-124mb

and the dumped files with original busybox

boot.bin-1mb
logo.bin-2mb
kernel.bin-4mb
root.bin-dumping forever

[vmpn]

i've noticed that with busybox from vmpn the dump files are like this

boot.bin-1.03mb
logo.bin-2.06mb
kernel.bin-4.12mb
root.bin-124mb

and the dumped files with original busybox

boot.bin-1mb
logo.bin-2mb
kernel.bin-4mb
root.bin-dumping forever

Are you using -o command line parameter? In the newest busy box this flag flipped meaning. In the old version -o means exclude oob blocks. In the new version (that I built) -o means include the oob blocks.

[JeffD]

I was wondering what the current hardware revision is for a Hantek DSO5102BM model?  Is it 10070x555583e9?  Couldn't find the info on the Hantek site and still waiting for a their response to my email.

Still reading through this thread.  Huge amount of great info here.

[n8ddd]

yes,i'm using -o

[vmpn]

yes,i'm using -o

Please create dumps without using "-o" and they should come out same size as original ones

[tinhead]

Still reading through this thread.  Huge amount of great info here.

JeffD,

the best is to skip the first 130-140 pages Really. Lots of the informations are already lightyears outdated. On the first page, there are shortcuts to important topics, as well the last pages contains siome newer infomations as well.

I was wondering what the current hardware revision is for a Hantek DSO5102BM model?  Is it 10070x555583e9?  Couldn't find the info on the Hantek site and still waiting for a their response to my email.

there are no any models left with old SoC, so current BM/BMV will be for sure not hw1007 but hw101 which is alreay S3C2416 SoC based. Between B and BM/BMV models, it is only bigger SRAM and different design in CPLD (address counter with higher range. BM\BMV design does works however with B\MSO models with no issue - i'm using MSO with 2M SRAM, so can during boot chose between MSO and BMV DSO), and between B and MSO models it is only the additional PCB mounted to i/o port on the B model mainbaord (and some few passive parts necessary to enable int , etc on the extra PCB).

Only P models does use different PCB design, so they can't be upgrated to higher memory nor MSO functionality (however it seems they does have kind of i/o header, which could allow other extensions, but up to now nothign really prooved).

[JeffD]

Thanks for the info tinhead.  That is what I figured once I got up to page 120 trying to figure out what was current hardware revision for different models.

[at2]

Is it possible to use  the DSO-BW-Changer for the DSO 5102P to change the bandwith to 200 MHz?

[tinhead]

Is it possible to use  the DSO-BW-Changer for the DSO 5102P to change the bandwith to 200 MHz?

yes it should be

[lemon]

@lemon

i think this is the wrong section  for your problem, in the video is a owon brand device that has nothing to do with hantek/teckway/voltraft and so on ...

Please, can someone to feedback us about this test?

Set a waveform to screen (triangle, sinusoidal).
Move the waveform to up or down so to cut the edge of the screen.
Now invert the waveform.
What is appearing? Is it normal or the bottom of waveform is also cutting?

there are not such issues on Tekway/Hantek, nor these others nown from Owon (with inverted and moved to top signal).
This must be firmware bug in Owon firmware, you should tell that Owon (or rf-loop, he is collecting bugs as well).

That is exactly answering, that I wanted.
The purpose of my question was to examine the phenomenon in another DSO oscilloscope so as to exclude the possibility to be issue of DSO scopes.

Tinhead, thanks for the respond.

[at2]

Thank you tinhead for your fast reply. I`m going to try out and let you know.

AT2

[at2]

  It works great. Thank you for your Support.

AT2

[miljume]

Hi all,

I ordered a DSO1062B just to upgrade it to 200Mhz but I get stuck at the first step when trying to do a backup

I get "firmware update failed, error: 0xfe no upgrade files detected on USB device!" 

I have the following setup

[model] DSO1062B
[sw version] 2.01.1 (130129.0)
[hw version] 10020x555583e8
[serial number] DS00503381

Can someone please help me getting through?

Regards,
Mikael

[kafachan]

Hi all,
     Thank you  . 

Regards,
Kafa.

[at2]

Hello Kafachan,

i can only tell with my DSO, as i did the change and it works fine .
See on YouTube. There did Cooking Engineer the change with his voltcraft from 60 to 200 MHz.


AT2

[miljume]

Hi all,

I am still stuck with unlocking 200Mhz for my DSO1062B, is there a way to unlock a unit with the data below?


[model] DSO1062B
[sw version] 2.01.1 (130129.0)
[hw version] 10020x555583e8
[serial number] DS00503381

Thankful or all help I can get

Regards,
Mikael

[tinhead]

where you stuck? still in backup? well, then skip backup. Or stuck in the hack tool? then do it manually. Everything one need to know is on the first page of this thread.

[mobiletester]

I have a Hantek DSO5072P. SW 3.40.0 (130717.0)
Works the BW-Changer also on this model?

[artag]

This thread is way too long ! Is anybody running a forum with the topics a bit more searchable ?!

I'm looking at buying one of the hantek scopes but having trouble working out the tradeoffs. I don't think there's any saving in buying the DSO1062, and I'm not convinced 1GS/s is enough for 200Mhz mode, so I'll probably stick with 100MHz bandwidth. I've got faster analog scopes anyway.

But there's the choice of B, BM, P and MSO5120D.   

B is a bit cheaper
BM has 2M memory (but does that make it really slow update ?)
MSO is useful but only 1M memory.
P is really cheap but only 40K memory (or maybe 24k?)

Of course, I'd really like the best of everything ! It seems the MSO option isn't that great and can be added fairly easily. So maybe the 2M is the best choice ?

Are there any options now with ethernet already fitted ? There seem to be some add-in boards, or I can put a wifi adapter in the USB.