Products > Test Equipment
Hantek - Tekway - DSO hack - get 200MHz bw for free
frank_d:
Hello Tatel, I'm sorry I gave the impression to be lazy. The truth is that I'm not good at english writing and just tried to write as little as possible and went straight to what I supposed could be the solution to my situation. Here is all the story: after intalling the Voltcraft update, the scope was stuck and after a restart it was just showing a black screen and emitting a continous sound from the inner buzzer. Going through this thread (belive me, I read all of it) I aquired tons of useful information and was able to find the uart port on the pcb (thanks to pictures and schematics), connect the scope to my PC and I discovered that many scopes has the same hardware with different names. I got the Blindelinx experience and after serching the Hantek equivalent model I got the firmware from Hantek web site. After installing the new firmware (via uart) I went to the situation I wrote in my post. Any oder attempt failed. At this point, I tried to ask for the original Voltcrat files beliving it could be the only way to resuscitate the scope.
Anyway, I'm going to send the scope to the local Voltcraft dialer for a software repair tomorrow.
Bye
Francesco
tatel:
--- Quote ---ls: /mnt/udisk/system*.up: No such file or directory
--- End quote ---
The system can't find any file called system(anything).up in the /mnt/udisk directory.
/mnt/udisk seems to be the directory where your system expects to find firmware upgrade files. When you put your USB stick on the scope, the contents of the USB stick should appear in that directory.
It doesn't find any file callled "system(probably a number or reference).up", which would be the firmware update. * is a wildcard that means "anything".
So probably your USB stick doesn't have any FW update file. It could be that the system doesn't take your USB but I think you would get a mount error should that be the case. Having the complete output from teraterm/putty would help. Maybe your USB stick is too big (>4 GB) or is not FAT32 formatted. But I think probably that firmware upgrade file just is not there.
Using teraterm/putty you could give this command
ls /mnt/udisk
This should return a list with the files/directories under /mnt/udisk. Maybe your system*.up file is under a directory or still compressed or...
I don't know what. It should be on the first level of your USB stick
I think you probably don't have any linux experience and screwed some command or some procedure step. Please follow the instructions found in this post:
https://www.eevblog.com/forum/repair/voltcraft-dso-1102d/msg2036896/#msg2036896
These are the instructions that Blindelinx followed. He also claimed not having any linux experience. Please note that these instructions, as Blindelinx said, seem to be using a not-so-good firmware update file. You have to use the original firmware from Hantek instead as he did. Probably having that original firmware update systemXXXXXX.up in the first level of a good USB stick is all that is needed.
Please note that if you screw some command and give instead a command that will delete, say, anything, linux will not ask "Are you sure?" before executing that screwed up command. So be careful, and, if not sure you can do it, please go to the dealer.
If your system is able to return a "file not found" error it means that Linux is running so you'll have a functional oscilloscope as soon as a good firmware update is loaded into it.
Good luck
sim_v:
Deep review of DSO5202p by a french guy (Cyrob)
I hope the youtube translator make a good job.Measures start at 14 minutes 14 seconds
Jelmer9888:
I tried to restore my DSO5102P to default values, but it seems my backups were wrong to begin with.
There is some serious outdated information in this topic, that's a bummer.
I also have 4 backup NAND partitions, I should have had 8 partitions. Sizes are boot 1024, kernel 2048, logo 512 and root 512 KB.
So I did a restore of all partitions (because my serial nr was suddenly gone) in the process.
the scope seems to be working fine, but my question is, can I have demolished something hidden what I don't see right now?
In the end my scope is now showing all the correct data again, serial no. and it shows it is a DSO5202P and it is calibrating.
But I don't trust my own restore action with a way to small root partition I did somewhere in the proces.
Btw, it is showing a "*** Warning - bad CRC, using default environment" booting up, don't know if that was there before.
atoll:
Hi! I need Nand flash for DSO-5102B for JTAG. Boot only recovery.
sw 3.30.0 (140902.0)
hw 1010x 5555830F
s/w T1G/012 01xxx
mail to atoll(@)tut.by
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version