Products > Test Equipment
Reverse engineering Tektronix TDS3GV module for TDS3000 series oscilloscopes?
ArcticGeek:
@pmercier
Nice work.
Can you clarify what the wires you soldered on were connected to? I assume these were the serial connections that you soldered: TX, RX, CTS, and RTS....is that correct? And these wires were then connected to some sort of TTL/RS232 level translator IC?
Mike
james_s:
Woohoo!
Would have saved me $250 (well, $230 by the time I bought a connector) to know that but somebody had to do it. Glad to hear it works and is really that simple.
The wires are soldered to TXD, RXD, CTS and RTS, refer to my screenshot of the bottom of the board where it is labeled.
The signals are 3.3V logic so you will need something like a MAX232 or one of those USB to LVTTL serial modules. They go direct to the CPU or one of the ASICs so I highly recommend some ESD protection as was incorporated in the original comm module.
Downgrade to firmware 3.39 and then send the following:
PASSWORD PITBULL
MCONFIG TDS3054
Power cycle and it should boot up saying it's a TDS3054B. Run SPC and you should be good to go.
You can then update to the latest firmware and run SPC again.
Actually I believe the B models can go all the way up to TDS3064 which is 600MHz 5GS/sec. Mine is a TDS3014 (no letter) so I was "only" able to upgrade it to 500MHz.
pmercier:
Hi,
some update. I received my pcb order to have the connector available outside to play with this saturday.
I just tried to use the serial port of my TDS3000(A) but with no success.
Seem like the A model, we must use the hardware RTS/CTS control flow (don't have anything to test against for the moment) or the serial port is disabled by default (fuxxored).
I would more easyli go for the second idea as there is nothing about a serial port in the menus (my 3032C has serial port config event without an extension card).
So getting a Floppy emulator to downgrade the firmware seem now less urgent :P
BTW for the screen as it's connected "directly" to the lcd connector the signal is present as soon as the scope is on.
pin 2, 11: DotClock 25MHz
pin 3 : HSync 31.5Khz (lonw 31,72us)
pin 4 : VSync 60,16Khz (low 16,62ms)
Pin 6-9 : Red [0-3]
Pin 51,52,54,55 : Green [0-3]
Pin 56,57,59,60 : Blue [0-3]
I have mapped the datalines and some of the address lines too but for the moment i can't confirm their axact assignation(just some guess).
After some more playing i think like james_s that some pins are used to detect the type of extension card. But it seem more tricky than some lines to ground.
I have a bunch of pins that have no signal on them :
High state : 13, 15, 24, 65, 66
Low state : 14, 16, 18, 19, 20, 22, 23, 25, 61, 62, 63, 64
Given the position of the pins i suspect the LC00A and LC08A to have something to to with the identification of the module.
They're probably only for the logic to enable/disable the 245's of the GPIB controller, but it can be a possibility that one of thoses is used to act as a "ROM" on the data bus for a byte to identify the module.
Edited to add pins 61 to 64.
james_s:
Hey that breakout board is a cool idea!
If you want to work on reverse engineering this further, I can open mine up again and trace out pins that you're wondering about. The scope is definitely able to identify the module that is plugged in, it may do so by detecting the GPIP or ethernet chips on the bus, it could also be something simple like connecting specific pins to other pins.
pmercier:
Yes am actually working on reverse engineering it based on the image only and I must say it's limited.
I'll gladly accept any help on this matter ^_^
The breakout board (thanks for the term) for this type of work is a must have !
For the pin to pin i thought so to and forgot to write it. it's on my test list for tonight if am not too tired to leave my eyes open.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version