Products > Test Equipment

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

<< < (644/645) > >>

Gregorio:
I thought those files were applications. I'll have to look into using them. Do you know the application that handles them?
Thanks a lot Morris6.

Gregorio:
I thought those files were applications. I'll have to look into using them. Do you know the application that handles them?
Thanks a lot Morris6.

morris6:
This post of member Tinhead is about restoring the firmware. AFAIK The supervivi bootloader is used here to be able to use USB serial in stead of a JTAG connection to upload a complete image. It's a slow process, some nail biting and finger crossing needed.


--- Quote from: tinhead on November 29, 2011, 09:07:09 pm ---How to restore original firmware/NAND

imagine you screwed something up and wish to restore the firmware to the original version
(which you of course saved before wth the backup tools from this thread ... you don't? Well do it now.
If it's already too late then send me PM, i can help you to restore your DSO)

There are two ways :
- over JTAG
- over UART/USB

As most ppl don't have a nice H-JTAG USB (or whatever ARM JTAG) i will skip here the restore over JTAG part,
because if you have one you know how to use it
(all you need in principle is to flash in raw mode, so with OOB blocks the combined backup file fw_backup.bin and reboot)

Restore over UART/USB
You need some tools:
- dnw.exe
- supervivi.bin
- vivi.bin (just in case, see later why)

These tools are attached already here:
https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=4153

The dnw.exe need a device driver and inf file, you can find them here:
(from http://www.friendlyarm.net/downloads page)
http://www.friendlyarm.net/dl.php?file=usb-downloaddr-setup_20090421.zip
http://www.friendlyarm.net/dl.php?file=usb-downloaddr_20090421.zip

The first one is complette setup program, the second just inf/device drive, use the one you like, both works
For Win64 users: i know there are some dnw.exe/drivers out there for Win64, search for them or use Win32 to restore

Now the first step is to create a complette restore file, the backup tool from this thread is creating 3 dumps:
boot.bin
kernel.bin
root.bin

They are only MTD partitions backups (with NAND OOB blocks), what missing is some empty space
which has been not saved during backup and NAND MTD endblock.
You can find them here:

(https://www.eevblog.com/forum/index.php?topic=1571.msg26930#msg26930)

https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=4903
https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=4904

Download these two files, put them into a folder with boot.bin, root.bin and kernel.bin
and run from dos prompt following:
copy /B boot.bin + blank.bin + kernel.bin + root.bin + mizi_tag.bin fw_backup.bin

The resulting fw_backup.bin is the full backup wich we need to proceed with restore.

Now connect your DSO over UART to your PC, open the terminal application, connect to whatever com port your
DSO is connected to (set 115200, 8n1) and power up your DSO.

While powering up try multiple times to hit space key, if the boot process have not stopped at following screen power off DSO
and try again until you see something like that :



This is the bootload prompt. Unfortunately the original Tekway/Hantek bootloader have NO USB support
so we have first to upload another one bootloader (with USB support) - that's the supervivi.bin

IMPORTANT: use only the supervivi.bin provided by me, if you use different version the restore might not work properly
or you screw up the MTD patritions.

To do this type in the bootloader prompt following:

load flash vivi x

and click enter. Now in your terminal application (i'm using hyperterm, sure not the best solution but it works)
chose "Transfer->send file", select the supervivi.bin, select Xmodem as protocol
(the x in what you typed in bootloader prompt means Xprotocol too).

Now you should see somehing like this picture:



After this step reboot your DSO, hit again during boot multiple times space key until the DSO stop at such screen:





The next step is to connect the DSO over USB and to install the device drivers to allow dnw.exe to communicate
with DSO. After you installed drivers run the dnw.exe, if everything worked you should see
in the dnw.exe top status line something like USB:OK



If you see this you can continue with fw/NAND restore, if not close dnw.exe, reconnect USB cable and try again.

Now type in the supervivi bootloader menu "r" - this means restore, immediately after that in dnw.exe menu
chose "Usb Port->Transmit/Restore" and chose the previously created full backup fw_backup.bin
Don't wait too long, dnw.exe is sometimes really bitchy with timeouts.

You should see now in the dnw.exe and your terminal application the transfer/flashing progress:






After the supervivi bootloader flashed the NAND with your fw_backup.bin the menu will be shown again, just
scroll back to see the flashing status, here my example (note, my NAND have one bad block, not a bog deal):



That's all, now close dnw.exe, disconnect USB cable from DSO and reboot DSO - you will have
now your original firmware restored.


Note: if you have too many bad NAND sectors the restore might not work, then you will have to buy new empty NAND chip,
solder it and repalce the broken one and of course use ARM JTAG to program the NAND backup (or at least the bootloader).

Extra note: after restore the bootloader is again the original HanTekway vivi.bin (the same as the attached),
if you lazy you can remove it of course by the supervivi.bin - the DSO will still work and you will have
nice way (over USB/dnw.exe) to backup/restore NAND (if you hacking often and have no JTAG cable this is the fastest way)

--- End quote ---

Juen:

--- Quote from: RavenSpy on October 13, 2014, 07:15:10 pm ---
--- Quote from: richardbb on October 13, 2014, 02:27:57 pm ---The driver doesn't seem to be getting loaded at all. Try running insmod /dso/drivers/dm9000.ko and see if anything shows up in the log

--- End quote ---
Hello, do it, this is the output:

--- Code: ---[root@Hantek ~]# 
[root@Hantek ~]# insmod /dso/drivers/dm9000.ko
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: dm9000a at c4976300,c4978308 IRQ 48 MAC: ba:97:89:4e:f1:22 (random)
[root@Hantek ~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr BA:97:89:4E:F1:22 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:48 Base address:0x6300

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


--- End code ---

But leds still doesn't turn on... =(

--- End quote ---
I'm on the same boat. The driver does not load at boot time, I have to load it manually using insmod. Moreover, I'm unable to bring the interface up, the link always stays down (no carrier), even though I've assigned an IP to the device. No errors are shown on dmesg upon loading the driver.

The scope is a 5102P unlocked to 5202P. Board 1.01, manufactured in 2015.
I have installed the DM9000, the transformer, the two 22pf caps, the 25MHz crystal, and removed the 0 Ohm resistor.
I performed all the i2c file editing by hand.


--- Code: ---[root@Hantek ~]# insmod /dso/drivers/dm9000.ko
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: dm9000a at c4982300,c4984308 IRQ 48 MAC: 16:56:94:19:87:6a (random)

[root@Hantek ~]# ip addr add 192.168.1.88/24 dev eth0
[root@Hantek ~]# ip addr show eth0
3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 16:56:94:19:87:6a brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.88/24 scope global eth0
[root@Hantek ~]# ip link set dev eth0 up
dm9000 dm9000: eth0: link down
[root@Hantek ~]# ip link show eth0
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 16:56:94:19:87:6a brd ff:ff:ff:ff:ff:ff

--- End code ---

--- Code: ---[root@Hantek ~]# cat i2c.log
[--LOG0--]
[serial number]<redacted>
[operation time]2018-12-24 13:02:00
[operator]hantek
[pcb]101
[lcd]3
[front]3
[usb]0
[touch]0
[net]1
[iso]0
[buf]1
[sd]1
[vei]0
[dds]0
[key]0
[bw]200

--- End code ---

I have an another question, despite of allegedly having the lan feature enabled, I have not found where the LAN related options should appear in the configuration menus. So... is it enabled? I have not yet calibrated the scope, but I guess that shouldn't matter...

Inspecting the rcS script, the network related stuff is commented out


--- Code: ---[...]
#insmod /dso/drivers/dm9000.ko

insmod /dso/drivers/tq2416_backlight.ko
insmod /dso/drivers/tq2416_beep.ko

#ifconfig eth0 192.168.1.127 up
#sleep 10;mount 192.168.1.126:/home/nfsroot /mnt/nfs -o nolock &
[...]

--- End code ---

Find attached the whole bootlog.

Thanks!

Jarek8:
Hello,
after update firmware my Hantek DSO5202P scope didn’t boot succesfully.

I have connected to internal UART and i find that machine is alive.
Only the filesystem is corrupted.

Could you send me anybody a backup please?
Thanks

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod