It's teardown time! Since none of has the hardware at the moment, let's take a look at the firmware. As to be expected, this scope runs linux as well as Tek's other non-windows scopes. Looking at the firmware update, things are a bit different than they used to be. Instead of some ext2 image, you now get a "TBS2KB.TEK" file.
Binwalk tells us that there's a Cramfs at offset 340 in there, looks interesting. Unfortunately, mounting the cramfs image doesn't work as does using fsck.cramfs for unpacking. After staring at the blob and the cramfs documentation I figured out that tek for some reason decided to hack cramfs in interesting ways. Instead of the standard 12 byte inodes, this one's got 16 byte inodes, 4 bytes more! I couldn't patch fsck.cramfs to understand tek's crazy format, so I came up with this
http://pastebin.com/BW7nYDWi minimum-brains python script that doesn't understand paths and simply extracts every file it finds in one directory.
Some notable things on the extracted files:
- There are two monster executables, ULPP and tekapp, totalling over 40MB. Fore some reason, they left the map file for the ULPP binary in the image.
- It really seems to be based on the AM33xx, there's a programm called gpmcdma
- There are many libraries referring to other tek instruments,
- There's a 16MB big Opentype font, seems a bit like an overkill
I don't have the time to take a closer look at the extracted files right now, maybe someone of you is interested...
There's no indication whatsoever on the tek website of them integrating GPL'ed software in there products
I had hoped that tek would do better than some random chinese CCTV camera manufacturer...