Products > Test Equipment

Reverse Engineering TDS2CM/TDS2MM

<< < (3/8) > >>

sd_tony:
Awesome, oPossum! can you quickly double check that P45 is really left open or it is actually pulled to ground (or to VCC, very unlikely though) through a 5K or 10 resistor? this pin is the only one which can be used as card detection signal, or else how does scope know the extension module is connected? by reading RPOM directly? it's possible, but not a typical design.

sd_tony:

--- Quote from: daisizhou on March 03, 2022, 09:59:59 am ---Sir, is TDS-2012C supported?

--- End quote ---

No, looks like TDS2CM/MM is for TDS210/220/224 only, TDS2012 has different extensions to support GPIB and other interface

oPossum:
Pin 45 is open - does not go anywhere. Checking for a signature in the PROM is a much more robust way to detect the presence of firmware than just looking at a single pin. The PROM can be validated with a checksum/crc to ensure the entire contents are accessible and valid.

The HP 5465X series modules for many early 90's HP DSOs have 0x5A5A in the first word. An A series DSO will see this signature and then use the firmware in the module. The later B and D series DSOs will see the signature and then enable supporting firmware within the DSO. They don't use any of the firmware in the modules. This allowed modules that where already in production to be used with the newer DSOs.

Tektronix revised the TDS2CM firmware to create the TDS2CMA for the new TDS1000/TDS2000 series. The later B & C series eliminated the module slot and added USB. There isn't a TDS2MMA because the measurement capabilities became a standard feature.
 

sd_tony:
according to Tek programmer manual, looks like TDS2CM works for TDS200, TDS1000 and TDS2000 series, but not 1000/2000 B and C series. By the way, what are the difference exactly between TDS2CM, TDS2CMA and TDS2CMAX? only firmware different? they all look similar physically.

TDS2CM already works with TDS1000/2000, why they created TDS2CMA and TDS2CMAX?

sicco:
There was something similar with the tds3000 and the TDS3EM ethernet module: the -b and -c tds3000 scopes cannot accommodate a tds3em plugin because the scope resident PHY hardware was added to the -b and -c mainboard / power supply. The ttl level i/o pins for Ethernet PHY chip on the plugin module were thus already occupied in the later -b and -c  scopes. A plugin module in a -b or -c scope that tries to drive those pins, will end up battling the logic output that is already wired internally to that pin. So neither driver will win and both Ethernet sockets will no longer work when plugging in that module. (actually, -b and -c. scope will refuse to boot when it sees that plugin module is inserted).

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod