I just verified that this does in fact disable the bandwidth limit option in the Ch2 (modified) menu.
So the next step is to take it apart again and check those vias to see what kind of signals they're giving. One of them should respond only to the bandwidth limit select, the other is likely the 50 MHz limit, and perhaps there's a way to bypass the other without cutting the trace.
Otherwise, fiddling with the software may be the only choice.
To each his own -- I'd see fiddling with the software as the first choice, not the last one. Much cleaner.
Sadly, IDA Pro can't handle Blackfin DSP code, leaving me to deal with objdump.
In the hopes of seeing something useful, I yanked off the 24LC04 I2C EEPROM attached to the Blackfin DSP, in the hopes of finding something obvious -- I was disappointed with what I found:
0000000: 0104 ffff 1700 0000 00ff ffff 8025 0000 .............%..
0000010: 0009 0001 0001 0100 a086 0100 1900 0000 ................
0000020: 0000 803f 0000 0001 a086 0100 e7ff 0000 ...?............
0000030: 0000 803f 0000 0000 0000 0100 0000 0700 ...?............
0000040: 0000 0000 0000 0000 cdcc cc3d 1400 b5ff ...........=....
0000050: 0300 9600 0000 0000 0100 0000 0000 0000 ................
0000060: 0000 ffff 4042 0f00 0000 0000 0000 0000 ....@B..........
0000070: 0000 0000 a086 0100 0000 0000 0000 0000 ................
0000080: 0000 0000 0000 0800 0020 0000 0000 0000 ......... ......
0000090: 0800 0010 0500 0000 bd37 0635 5c8f c23e .........7.5\..>
00000a0: 0000 0000 0000 0000 0002 1900 e7ff 0000 ................
00000b0: bd37 8635 0000 0000 bd37 8635 0000 0000 .7.5.....7.5....
00000c0: 0000 0000 0000 0000 0100 0000 0000 0100 ................
00000d0: cdcc 4c3e cdcc 4c3e 0100 0000 0100 0000 ..L>..L>........
00000e0: 0100 0000 0000 0003 0101 07ff 4042 0f00 ............@B..
00000f0: 0000 0000 4042 0f00 0000 0000 0000 0000 ....@B..........
0000100: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000110: 0000 0000 0000 0000 0000 ffff bd37 8635 .............7.5
0000120: 00ff ffff bd37 8635 0000 0000 0000 0000 .....7.5........
0000130: 0100 01ff 0000 0000 0101 0101 0101 0101 ................
0000140: 0101 0001 0000 0000 0100 ffff 3aa3 14a9 ............:...
0000150: 00ff 0000 0001 0203 0405 0607 0001 0203 ................
0000160: 0405 0607 0000 0000 0000 0000 0007 0700 ................
0000170: 0007 0708 0202 0202 0202 0202 0202 0202 ................
0000180: 0202 0202 0000 0202 0202 0202 0202 0202 ................
0000190: 0202 0202 0202 0000 8ded b5a0 f7c6 b03e ...............>
00001a0: 0100 00ff 0000 0000 ffff ffff 0000 0000 ................
00001b0: ffff ffff 0000 0000 ffff ffff 0000 0000 ................
00001c0: ffff ffff 0000 0000 ffff ffff 0000 0000 ................
00001d0: ffff ffff 0000 0000 ffff ffff 0000 0000 ................
00001e0: ffff ffff 0000 0000 ffff ffff 0000 0000 ................
00001f0: ffff ffff 0000 0000 ffff ffff 0000 0000 ................
I'm not seeing anything that looks remotely like a model number or serial number. This was from a DS1052E -- anyone else care to do the same so we can compare?
The firmware images don't appear to be signed, so they could be modified easily -- they are 4194325-byte files, which seems to me like a 21-byte header plus a 4MB firmware image. The header is:
0000000: 4453 3130 3030 4520 2020 3032 2e30 322e 3032 2e30 30 DS1000E 02.02.02.00
There's no room for a hash, so you could do whatever you want to the file. Unfortunately, this means that there's no sort of bootloader which could recover corrupted firmware, so your options would be to desolder the NOR flash holding the firmware and reprogram it using a chip programmer, or try to get the 13-pin JTAG-looking connector working.