is this normal or is there something wrong? I dont want to turn it off unless you say its okay.
no, for some reason this didn't work properly on your DSO. There is problem with nanddump, even with proper params it does read on some DSO forever, looks for me as cloned bad partition. When i do the backup on virgin NAND, it works.
All you can do now is to backup your device specific files, use that tool http://peter.dreisiebner.at/dso-usb-tool/
go to virtual shell, insert flash drive and copy files from / to /mnt/udisk/
my question on the serial number of mine. is it a newer model or older model? 035000xxx
but I'm getting the dreaded fe error on the3.40 firmwares you posted. not sure whats going on there..
but I'm getting the dreaded fe error on the3.40 firmwares you posted. not sure whats going on there..
don't worry, the DSO you ("P" model) have is complettly new design. There is no other firmware version than 3.x for your DSO.
Other models (like "B" and "MSO", "BM/BMV" not yet confirmed but probably the same problem) have multiple hardware
revisions:
- hw0, hw1005, hw1007 with Samsung S3C2440 SoC - with firmware 2.x
- hw??? with Samsung S3C2416 SoC - with firmware 3.x
For both, ppl with 2.x or/and 3.x firmware installed, when then install different firmware the DSO/MSO will get bricked.
So they have to watch out what they installing. For you as already said, didn't matter, your DSO is new, based on
S3C2416 and there only existing firmware is already 3.x. You can't install 2.x because there was never 2.x for your DSO,
you can't install firmware from other models because they using different naming cnvention for update files and different
firmware encryption pwd.
alright, anything else you want me to do?
anyway, I tried to run all the commands that your tool runs from the serial console.. and it seems to get stuck on this line.
nanddump -o -b -l 0x7900000 -f /mnt/udisk/dump/root.bin /dev/mtd3
so what kind of command do I need to run to backup the scope then? or just some files?
Hello,
I wonder if it is possible to reset the "bout count" and "upgrade count" counters?!
THX
Now i must solder the pins in order to connect the uart adaptor...
it still displays the 5072p logo on booting..
I edited the logotype (I think that displays the proper model # in the system info) and logotype.dis and the boot logo still reports 5072p
oh well, it is not really complex. You have to compile kernel and the frame buffer driver - where the boot logo is located.
You need of course the GPL source for these DSOs, check here (there are two version, to get all you need, you need to download both)
https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg266507/#msg266507