Some Pictures:
https://ibb.co/album/xqNvf6Some stuff I found out: (With help of other people on the Forum)
- After you Disconnect / Change the NVRAM Lithium battery, the trace wents to the top of the LCD in full span mode.
Solution: You have to turn off the analyzer and hold the "." dot key, while turning on, during the whole bootup process. This initializes the NVRAM, and everything is back to normal.
- When you want to use a new CF card, you need a 8 or 16MB card, and format it with this tool:
https://www.sdcard.org/downloads/formatter/Then copy the files on it. Nothing else worked for me.
- After pressing: "Shift + Format + 882323 + Hz", you can reset "ATT switch count" and "Power ON switch count".
- After pressing: "SHIFT + WINDOW + 882323 + Hz", you enter the calibration menu, where you can read/write/tweak every calibration value. So you dont need some unobtainium PC Software like with R&S Machines. (Thank you Advantest
When you want to save the changes to the EEPROM, you need to remove the small backplate assembly, with the 4 screws. There is a DIP Switch, where you can turn EEPROMWRITE on.
- Pressing SHIFT + TRANSIENT will also ask for a password, but it is not known yet. I think this is the access to the debug mode. I found some interesting strings in the firmware:
DFM.txt: --- Read memory ----------------
DFM.txt:
DFM.txt: DEBUG MODE
DFM.txt: TBC SEND 595
DFM.txt: TBC SEND DAC
DFM.txt: TBC SEND DAC 500
DFM.txt: TBC SEND CXD
DFM.txt: TBC SEND 87086/16
DFM.txt: TBC SEND 87086/20
DFM.txt: TBC SEND AD7008
DFM.txt: TBC READ 0831
DFM.txt: TBC EEPROM WRITE
DFM.txt: TBC EEPROM READ
DFM.txt: TBC SRAM WRITE
DFM.txt: TBC SRAM READ
DFM.txt: DEBUG MODE
DFM.txt: Standard
DFM.txt: TBC|Send xxx
DFM.txt: TBC|Read 0831
DFM.txt: TBC|EEPROM xxx
DFM.txt: TBC|D.P.M xxx
DFM.txt: return
DFM.txt: STANDARD
DFM.txt: ACTIVE
DFM.txt: address| write
DFM.txt: FORMAT
DFM.txt: Hex|Dec
DFM.txt: SIZE TYPE
DFM.txt: 8|16|32
DFM.txt: Read Loop
DFM.txt: Write Loop
DFM.txt: return
DFM.txt: SEND 1/2
DFM.txt: TBC|Send 595
DFM.txt: TBC|Send DAC
DFM.txt: TBC|Send DAC5
DFM.txt: TBC|Send CXD
DFM.txt: TBC|Send 7008
DFM.txt: next menu
DFM.txt: return
DFM.txt: SEND 2/2
DFM.txt: TBC|Send 87086|/16
DFM.txt: TBC|Send 87086|/20
DFM.txt: prev menu
DFM.txt: TBC EEPROM
DFM.txt: TBC|EP Write
DFM.txt: TBC|EP Read
DFM.txt: return
DFM.txt: LOCAL BUS
DFM.txt: TBC|SRAM Write
DFM.txt: TBC|SRAM Read
DFM.txt: return
DFM.txt: DEBUG TBC
DFM.txt: ACTIVE
DFM.txt: address| write
DFM.txt: Write Loop
DFM.txt: return
DFM.txt: DEBUG TBC
DFM.txt: ACTIVE
DFM.txt: address| write
DFM.txt: Read Loop
DFM.txt: return
DFM.txt: DEBUG TBC
DFM.txt: ACTIVE
DFM.txt: ID |sorc|dest|size
DFM.txt: Execute
DFM.txt: return
I searched all firmware files for the passwords, but could not even find "882323", which is the same as for the R3131A.
I wonder how they are encoded?
- There even exist a tool on the cf card (TBC.X), to read/write the calibration values as .csv files. But I dont know how to execute it. (Maybe through Debug Mode)
I attached my CF-Card content, and I even Read out the TSOP Flash-EPROM on the CPU Board. Maybe anyone can find the Debug mode password.
The Operating System is called VRTX-32 from Mentor Graphics. I think the kernel runs on the Flash-Eprom, and the executables are on the CF-Card.
Also VRTX runs the Hubble Space Telescope.
CF Card Content:
https://drive.google.com/file/d/1XZMoc3Zd86UlXWMjUhN6VH5KTtQ_qpTr/viewAlso: Broken TG Fix:
Oh Boy....