A 1Mpoint DSO will not mutate to 2Mpoint model only if you change license informations
in EEPROM - a physical chip will be necessary .. and few other things like e.g. kernel 2.6.30.4 (yeah, the firmware will
check this and if you don't on 2.6.30.4 the 2Mpoint will be not enabled even if you have license).
The kernel check (for 2.6.30.4) seems to be only cosmetic in nature for the 2Mpoint depth (appears to work with checks removed, with 120224.0). Also it seems unnecessary at first glance, that capture depth 1M/2M check is executed with changing timebase...
Can the debugmode be entered, something interesting there?
Sure, it can be removed. You need to check in few places as the firmware is checking also while accessing
device drivers (still in dso.exe), just look for "26304" string in disassembly.
Btw, did i mentioned already that exports are removed from current firmware? It make sense to leave copy of
2.06.3_120224.0 somewhere to have a chance to compare code from older (with exports) and current (w/o exports) versions.
Not that this is really necessary, but it makes quick checks easier.
regards debug mode, haven't tried anymore since a long time as it was nothing special there.
So this means that original "B" model users could save up to 2Mpoint?
What do you call exports? I've just saved a CSV to USB stick using 120430 firmware, so I guess exports are another thing.
Looks complex? No, it's not. Kernel and device drivers are since the published GPL code not an issue anymore
(so no need to wait for physical dump from someones BMV model). FPGA and CPLD designs are still what we
eventually looking for. I do have working FPGA and CPLD designs to support 2Mpoint, but they from
handhelds - in principle they runs on bench models too, but two SRAM traces need to be selfmade (even of hw1007 where
even 4Mpoint is already routed between CPLD, FPGA and SRAM). I do have all i need to run a test,
but no time for that (as i would need to solder all components from that board which i'm using to double check the
hw1007 schematics ...) so you see just too many tasks i'm working on.
Maybe someone can try to solder bigger SRAM - IS61LPS51236A-200TQLI(digikey 706-1100-ND ),
to patch fw (or install 2.6.30.4 kernel or patch uname) and to report back if the hw1007 boards and
their CPLD design are already good enought for 2Mpoint.
Now, I was thinking in adding extra features and it would be nice if we can organize ourselves to boost it up.
* Logic analyzer capability: let's start with I2C, SPI...
I would prefer connecting via LAN instead of serial connection.
However, it does not fix it. I suspect because the upgrade process is only incremental, reverting to an earlier upgrade can't fix it.
Anyone got suggestions how I have revert to the earlier software, or how to do a full install and upgrade to a less horrible version that the current one?
Frankly, I'm fed up with Hantek. I've had this scope one year now. I've made 'new product' excuses for Hantek a number of times, hoping they would improve their software and support. After one year, their new software upgrade wrecks the scope. They seem to have learned nothing.
Is there an easy way to fix this?
All i did was to patch out 3 bugs (this part works already with no issues), however i will try to patch 3 other
bugs (20, 22 and 24) before i post it here. In case i fail, i will of course post the latest working version.
Just give me a day or two
hi,
what can i do if i have this problem ? whithout installing this patch before ?
i have last firmware.
thanks.
marc
unfortunately you will have to connect via UART to the DSO (3.3V TTL UART converter is what you need)
and delete manualy the affected file, just execute on the shell rm -f /param/sav/run1kb*
or send the unit back to the shop where you bought it originaly.
Another reason why I would not believe in the rewritten software. The current codebase has a few years of QC, done by the customers. The fresh one, hacked together in two month, will not have any OC worth to mention.
EDIT: i've just got nice email from Hantek, the firmware will be revised not re-developed.This of course change the whole situation and make sense,
two months to re-develop
would be a typical chinese killer, but two months to revise the firmware is perfectly acceptable
hi,
what can i do if i have this problem ? whithout installing this patch before ?
i have last firmware.
thanks.
marc
unfortunately you will have to connect via UART to the DSO (3.3V TTL UART converter is what you need)
and delete manualy the affected file, just execute on the shell rm -f /param/sav/run1kb*
or send the unit back to the shop where you bought it originaly.
I assume this is what I have to do. I've got an iTeaduino v1.1 (Ardunio clone) which has a FT232RL chip on it, I asume I could talk to this chip over Putty / Hyperterminal. Will have to test it out later ...
Hi,
I am really impressed about the work of tinhead and others about Hantek "upgrades".
Recently I purchased a handheld DSO1102B.
After checking the PCB I have some questions:
It seems that the RJ45 socket connects not only to LAN but also to some kind of RS232 interface.
Do you have information how to populate/activate the RS232 option?
---> Edit/Add:
Hoppla, just saw some information about RJ45 UART in #1029.
Did you try this option in the meantime?
---
For SD card option: Is it sufficient just to populate the card holder or are some additional resistors etc. necessary?
Then I saw near to the UART connector an empty connector named "WLAN" Do you have information about this option?
anyone who knows if this is still the 1GSs 100MHz version?