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

[Loafdude]

Thanks Tin for all the work and information you have put forward here.
Very much appreciated.

Just modded a Hantek DSO5062BM

Tin,
Are you still needing copies of BM models backups? If so let me know. I can supply

The first post is a bit confusing with so much information strikethrough'ed
I appreciate its better to not delete the information though, maybe we can move it
The BM model backup firmware script is very difficult to find for new users (as you link to the B version in the instructions)

For everyones information here is the chk_base_volt from my unit

Code: [Select]

[8mv]167
[20mv]359
[400mv]403
[2000mv]1999
Here is the bootlog

Code: [Select]

*** Warning - bad CRC or NAND, using default environment



##### EmbedSky BIOS for SKY2440/TQ2440 #####
Press Space key to Download Mode !
Booting Linux ...
Copy linux kernel from 0x00200000 to 0x30008000, size = 0x00200000 ... Copy Kernel to SDRAM done,NOW, Booting Linux......
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.30.4 (root@rain-fc4) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #9 Mon Dec 12 11:50:21 CST 2011
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: TQ2440
ATAG_INITRD is deprecated; please update your bootloader.
Memory policy: ECC disabled, Data cache writeback
CPU S3C2440A (id 0x32440001)
S3C24XX Clocks, (c) 2004 Simtec Electronics
S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0
NR_IRQS:85
irq: clearing subpending status 00000002
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttySAC0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61316KB available (3116K code, 333K data, 100K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 199.47 BogoMIPS (lpj=498688)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 296 bytes
NET: Registered protocol family 16
S3C2440: Initialising architecture
S3C2440: IRQ Support
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c4808000, irq 33
DMA channel 1 at c4808040, irq 34
DMA channel 2 at c4808080, irq 35
DMA channel 3 at c48080c0, irq 36
S3C244X: Clock Support, DVS off
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
yaffs Sep 21 2011 16:15:16 Installing.
msgmni has been set to 119
alg: No test for stdrng (krng)
io scheduler noop registered (default)
s3c2440-uart.0: tq2440_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440
s3c2440-uart.1: tq2440_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: tq2440_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2440-nand s3c2440-nand: Tacls=2, 20ns Twrph0=3 30ns, Twrph1=2 20ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
Scanning device for bad blocks
Creating 4 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x000000000000-0x000000040000 : "EmbedSky_Board_uboot"
0x000000200000-0x000000400000 : "EmbedSky_Board_kernel"
0x000000400000-0x000003ff8000 : "EmbedSky_Board_yaffs2"
0x000000100000-0x000000200000 : "EmbedSky_Board_logo"
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
mice: PS/2 mouse device common for all mice
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
Linux video capture interface: v2.00
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: starting watchdog timer
s3c2410-wdt s3c2410-wdt: watchdog active, reset abled, irq enabled
mapped channel 0 to 0
s3c2440-sdi s3c2440-sdi: powered down.
s3c2440-sdi s3c2440-sdi: initialisation done.
Advanced Linux Sound Architecture Driver Version 1.0.18a.
No device for DAI UDA134X
No device for DAI s3c24xx-i2s
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: UDA134X <-> s3c24xx-i2s mapping ok
s3c2440-sdi s3c2440-sdi: powered down.
ALSA device list:
  #0: S3C24XX_UDA134X (UDA134X)
TCP cubic registered
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
lib80211: common routines for IEEE802.11 drivers
s3c2410-rtc s3c2410-rtc: setting system clock to 2013-06-05 11:33:53 UTC (1370432033)
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 100K
__init s3c24xxfb_probe
setting vert: up=29, low=13, sync=3
setting horz: lft=40, rt=40, sync=48
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1
Console: switching to mono frame buffer device 100x30
fb0: s3c2410fb frame buffer device
var.xres=800
var.yres=480
var.bits_per_pixel=8
var.xres_virtual=800
var.yres_virtual=480
fix.id=s3c2410fb
fix.smem_start=866123776
fix.smem_len=768000
fix.type=0
fix.type_aux=0
fix.xpanstep=0
fix.ypanstep=0
fsetting vert: up=29, low=13, sync=3
setting horz: lft=40, rt=40, sync=48
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1
ix.ywrapstep=0
fix.line_length=800
argv[1]=16
var.xres=800    var.yres=480    var.bits_per_pixel=16
show logo,video_buf_size = 768000
bwscon:0x2201d110
fpga bank 221422
dso-fpga: install ok
dso-spi initialized
Init spi success!
New Log Write OK Length:21
open spi error
dm9000 Ethernet Driver, V1.31
dm9000 dm9000.0: read wrong id 0x002a0028
dm9000 dm9000.0: read wrong id 0xffffffff
dm9000 dm9000.0: read wrong id 0xffffffff
dm9000 dm9000.0: read wrong id 0xffffffff
dm9000 dm9000.0: read wrong id 0x2b2a2928
dm9000 dm9000.0: read wrong id 0xff2a2928
dm9000 dm9000.0: read wrong id 0x2b2a2928
dm9000 dm9000.0: read wrong id 0xffffffff
dm9000 dm9000.0: wrong id: 0xffffffff
dm9000 dm9000.0: not found (-19).
Try to bring eth0 interface up ...
Hantek GPIO(buzzer/speaker),(c)20110309
gpioG11 initialized
speaker on
Beep
ifconfig: SIOCGIFFLAGS: No such device
dso-buzzer initialized
ifconfig: SIOCSIFHWADDR: No such device
ifconfig eth0 hw ether 10:23:45:67:89:ab
ifconfig: SIOCSIFADDR: No such device
ifconfig eth0 192.168.1.55 netmask 255.255.255.0 up
/sbin/net_set: line 5: route: not found
add default gw 192.168.1.2
Done
i2c /dev entries driver
s3c2440-i2c s3c2440-i2c: slave address 0x10
pdata->frequency=6000
s3c2440-i2c s3c2440-i2c: bus frequency set to 9 KHz
s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
s3c2410_udc: debugfs dir creation failed -19
s3c2440-usbgadget s3c2440-usbgadget: S3C2440: increasing FIFO to 128 bytes
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$4s3c2410_udc_disable()
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c2440_clkcon=00FF7FF0
fpga download file_name :/dn.rbf
status: 0x1
fpga_down_load file name : /dn.rbf.
data DOWN finish.
dso-spi:FPGA_DOWNLOAD ok.
release
no update file to foud
now run app .....
var.xres=800
var.yres=480
var.bits_per_pixel=16
var.xres_virtual=800
var.yres_virtual=480
fix.id=s3c2410fb
fix.smem_stasetting vert: up=29, low=13, sync=3
setting horz: lft=40, rt=40, sync=48
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1
rt=866123776
fix.smem_len=768000
fix.type=0
fix.type_aux=0
fix.xpanstep=0
fix.ypanstep=0
fix.ywrapstep=0
fix.line_length=1600
argv[1]=8
var.xres=800    var.yres=480    var.bits_per_pixel=8

Please press Enter to activate this console. s3c2440_clkcon=00FF7FF0
cannot open lcd
: No such file or directory
cannot open lcd
: No such file or directory

[root@Hantek /]#

There was no watchdog on my unit

[tinhead]

Thanks Tin for all the work and information you have put forward here.
Very much appreciated.
Just modded a Hantek DSO5062BM

you welcome

Tin,
Are you still needing copies of BM models backups? If so let me know. I can supply

no, i got few days ago latest dump from another user, but thanks for asking.

The first post is a bit confusing with so much information strikethrough'ed
I appreciate its better to not delete the information though, maybe we can move it
The BM model backup firmware script is very difficult to find for new users (as you link to the B version in the instructions)

yeah, i will edit it, or probably better write from scratch.

[sparkybg]

Hi,

I have just updated my Hantek DSO1062B handheld with the newest firmware from hantek's site 2.01.1 (130129.0) and discovered several bugs (when beep is on and you move cursor, it beeps even if you push and hold the direction buttons, trigger level is erratic - it sets lower trigger level than indicated), and I want to go back to the older firmware.

Does anyone have a firmware older than 2.01.1 (130129.0)? My older was 2.01.1 (12xxxxx.x), and it was OK, more or less, but I don't have it anymore and I cannot revert back to it.

Thanks.

[tinhead]

2.01.1_DSO1202B(121229.0)

[tinhead]

2.01.1_DSO1202B(121109.0).zip

[tinhead]

and finally 2.01.1_DSO1202B(120701.0)


To downgrade you will have to
 -downlad these file,
 -unzip the *.up file
 -decrypt the *.up file by "gpg -d --passphrase 111111"
 -guzip the content
 - untar the content
 - unatar again the content
 - copy manally the dso.exe to your handheld root dir (/dso.exe)
 - replace the language files (e.g. /OurLanguages/English.lan) with these from the downgrade firmware

To copy files you can simply use that tool directly

http://peter.dreisiebner.at/dso-usb-tool/

or indicrect together with flash drive (e.g. copy iles to flash, use that tool shell tab to cpy from flash drive,
which is then /mnt/udisk/ to DSO )

[sparkybg]

WOW! Very helpful. Thanks!

[sparkybg]

I have changed the BW to 200Mhz and upgraded to 1202 latest firmware (130xxxx). Everything is fine now. Thanks again.

And one more question - when I turn on the unit and it is still cool, the fan starts blowing for some time, and then stops despite that the unit heats up. The BNC connectors becomes hot enough that it is hard to keep my finger on them for more than 3-4 seconds, and the fan is still off.

Is this a normal behaviour?

Fan test works (the fan blows when "open" and does not blow when "close).

[mikett]

Hi All,

I have a 2 year old Hantek DSO5102B moded for 200MHz.
This machine used to work fine but has been unused for about 6 months until yesterday when I switched it on
and the screen froze on 200ms/1volt and the only front panel leds on are AUTO SET, RUN/STOP and
CH1 MENU.
No keys are responsive and the terminal Linux boot up is attached.
Any one experienced this before and could it be the hardware or possibly NAND flash corruption.
Thanks.

[tinhead]

I have changed the BW to 200Mhz and upgraded to 1202 latest firmware (130xxxx). Everything is fine now. Thanks again.

And one more question - when I turn on the unit and it is still cool, the fan starts blowing for some time, and then stops despite that the unit heats up. The BNC connectors becomes hot enough that it is hard to keep my finger on them for more than 3-4 seconds, and the fan is still off.

Is this a normal behaviour?

Fan test works (the fan blows when "open" and does not blow when "close).

no, i don't think so. Do default setup first, then let the fan better in "open" position, wait a minute (to ensure setup saved)
and power cycle DSO. I think it will work then properly (i hope).

[tinhead]

Any one experienced this before and could it be the hardware or possibly NAND flash corruption.

it seems that the /dso.exe is crashing. Maybe is a good idea to copy manually /dso.exe and at least
/OurLanguages/English.lan from a latest firmware to the DSO, then reboot and run regular firmware update.

To copy manually you can use flash drive (and remote shell over uart or that DSO tool http://peter.dreisiebner.at/dso-usb-tool/)
You will need of course to decrypt/unpak the firmware:
 - decrypt the *.up file by "gpg -d --passphrase 0571tekway"
 - guzip the content
 - untar the content
 - unatar again the content

[mikett]

Thank's tinhead.
I have no idea how to:

decrypt the *.up file by "gpg -d --passphrase 0571tekway"
 - guzip the content
 - untar the content
 - unatar again the content

Where do I get the "gpg.exe" and "guzip.exe" from. Can it done on a Windows platform
Better still does anyone have all the components already extracted from the latest released software.

[tinhead]

Where do I get the "gpg.exe" and "guzip.exe" from. Can it done on a Windows platform

wow, that must be hard to get .. is it?

Honestly, it is really that hard to google for "gpg windows" or "gunzip windows" ?
e.g. http://gpg4win.org/

and untar/unzip/gunzip can be doe for example with TotalCommander (it will autodetect content and unpack,
so yuo can click, and click and click once again to gunzip/untar/untar )

Better still does anyone have all the components already extracted from the latest released software.

you need to do something on your own, even if i give you these file, i can't copy them for you, nor install device driver
nor the software to be able to connect to DSO.

[tinhead]

i've uploaded newest firmware for following 1M models

 - Tekway DST1062B, DST1102B, DST1202B
 - Hantek DSO5062B, DSO5102B, DSO5202B
 - Voltcraft DSO3062C, DSO1062D
 - PCE DSOs: PCE-DSO5062B, PCE-DSO5102B, PCE-DSO5202B

here : http://www.mikrocontroller.net/attachment/181556/dst1kb_2.06.3_15202b_fact_130425.0_.up

and for following 2M models

 - Hantek DSO5062BM, DSO5102BM, DSO5202BM
 - Hantek DSO5062BMV, DSO5102BMV, DSO5202BMV

here : http://www.mikrocontroller.net/attachment/181558/dst1kb_2.06.3_5202bmv_f_130425.0_.up

[sparkybg]

Everything can be done with 7zip or winrar.

I've used cryptophane for decryption. It is very easy to use software:
https://code.google.com/p/cryptophane/downloads/list

Tinhead, the fan still does not work properly. Maybe I will have to make small fan controller to make it work as it should work or just turn on the fan on constantly.

[tinhead]

there is a driver running, which controls - based on temp sensor - the fan. I propose you check if the driver is running properly it might be bug as well, who knows, i don't have any handheld anymore).

[sparkybg]

I will check it. If there is a driver/sensor, it is on the front side of the pcb. I will have to dismantle the unit completely to check out.

Thanks.

[mikett]

Thank you tinhead and others. The process wasn't  too bad afterall.

I fixed the Hantek by replacing the dso.exe, language and two files in the /lib/ directory.
I then updated the firmware as usual with a flash disk.

I used this gpg command:
gpg2 -d --passphrase 0571tekway dst1kb_2.06.3_15202b_fact_130425.0_.up >> bbb
Then (winrar bbb) to  get the (tekwayup_client) directory.

[brainwash]

This does not quite fit into the firmware thread but I have regular problems with the supply connector: every three months or so I have to open the scope and refit the connectors. I've bent the odd and even pins a little in the opposite ways and tightened the female plugs a bit but I'm not sure how well this will hold up. Is there any other way to avoid the regular 'white screen' problem?

[Mike Warren]

This does not quite fit into the firmware thread but I have regular problems with the supply connector: every three months or so I have to open the scope and refit the connectors. I've bent the odd and even pins a little in the opposite ways and tightened the female plugs a bit but I'm not sure how well this will hold up. Is there any other way to avoid the regular 'white screen' problem?

With mine, the white screen was caused by the flex cable (FPC) not being seated properly. Are you sure that's not the case with yours? You may just be bumping it each time you reseat the power supply connector.

[brainwash]

Not consciously, but probably when taking the shield off it is moved a bit. But I think when I tried powering it on with the shield off it also presented the white screen, some time ago, so I'm putting my money on one of the connectors.
I'm already thinking of putting some hot glue or other similar fixing stuff there but I don't bang my scope on the bench so see no reason for that. The funny thing is that it usually stops working after a long period of non-usage, not when using it.
Edit: with this problem, all of the time it starts up fine but then the screen stops working after 1-10 minutes. Cycling power solves the issue for another minute or so.

[Mike Warren]

I would still be inclined to disconnect and reconnect the FPC to the screen. It's quite common for faults to behave exactly as you describe. The connection is only just being made and broken by movement caused by small temperature changes, and can cause the fault to be intermittent.

[tinhead]

"white screen" is coming from the 5V rail, which is used for TFT backlight (when there is not enought current display goes white).
So it can be the FPC (on both sides of course) but as well the power supply connector (JST XH 5S plug/socket) ... these used in DSO
are one hung low brand, that could be the reason.

[tinhead]

XY "Easter Egg" (undocummented XY color mode):

set mode to XY, Persistency to Auto, go to Utility -> Page3/3 -> Option and push F5 to change XY color

[Hydrawerk]

I am still looking forward to Dave's review of this Tekway scope... https://pbs.twimg.com/media/BMI6-1sCMAEse4e.jpg