Products > Test Equipment
MSO2000 Application module hack
drsurfer:
Thanks for your info.
So it's confirmed that the PCB published (and the SIM socket choosen) is simply too big. :palm:
The center of SIM connector on it is at ~15 mm from the edge, so it's mandatory to file it as much as possible to have a reliable contact with the scope pads.
I did a little investigation on the strings inside the last firmware, hoping to find a "magic" string that will enable at same time all the three features available. It seems this does not exist, but there are five strings that could enable some undocumented/abandoned/<whatever> features.
--- Code: ---DPO2EMBD Embedded Serial Triggering and Analysis
DPO2AUTO Automotive Serial Triggering and Analysis
DPO2COMP Computer Serial Triggering and Analysis
DPO2AUTOMAX Extended Auto Serial Triggering and Analysis
DPO2VID Extended Video
DPO2AUDIO Audio Serial Triggering and Analysi
DPO2PWR Power Analysis
DPO2BTA Beta Enabled
--- End code ---
DPO2VID is the only string I've found referenced in some Tek docs related to our scopes.
I hope that someone finds the time to do a little experimentation on these. 8)
Lunasix:
Thanks !
I will try asap.
Lunasix:
AUTOMAX and VID are correctly detected. But I can't see any difference between AUTO and AUTOMAX, probably none, and video trigger (SECAM/PAL/NTSC) is now useless, and is already available without any key.
Others have no effect, except warning.
drsurfer:
May be deeper in the firmware there are hidden other exploits, but I feel satisfied of the results I got and I will not spend more time on it.
BTW, the binary format of firmware is straightforward, and even a linux beginner (like me) can easily find the way to do some investigations on it, so I will not disclose any details on the process.
Ciao
DrSurfer
Dreamster:
--- Quote from: Lunasix on September 22, 2014, 09:22:21 pm --- Reading starts at address 04, find the string (terminated with 0) and reads 3 more bytes at FF (thus, ending on a 16 bytes boundary). If the scope reads garbage (or 0xFF), it will say it needs a software update, since value in the key isn't recognized (but supposed to be valid).
--- End quote ---
Hi.
Can you elaborate on this? I see the request for software update but I am already at 1.56. Apart from the bytes set to DPO2COM\0 or EMBED, what should the rest of the eeprom be set to.
Regards
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version