• Please review our updated Terms and Rules here

Tektronix 4052/54 diagnostic ROM pack remade.

Hi Bob,

Use this link to see all the files in that folder including my microcode zip (should match the microcode ROMs in Jos' zip) and my doc on reading the old Motorola ROMs:
http://www.bitsavers.org/pdf/tektronix/405x/4052_4054/firmware/

The MAS ROMs zip are the BASIC EPROMs on the MAS board. The 4052A/4054A updated the MAS board to replace the ROMs and Patch ROMs with EPROMs and replaced the discrete GPIB circuit with a TI 9914 GPIB IC.

I just noticed the MAS ROMs zip is shuffled pairs of EPROMs into a single binary file which can be examined with a binary editor like HxD.

When you get your 4054A to pass the power on self test - you should be able to use the Option 1 serial interface (or manually enter the program) to load in my Checksum test program which will check your BASIC ROMs against my version 1.5 BASIC ROMs.

Here is a 4052/4054 Microcode Power Up Test Sequence service bulletin that I posted on my repo that may help:
https://github.com/mmcgraw74/Tektronix-4051-4052-4054-Program-Files/blob/master/4051-4052-4054_ServiceNotes/4052-4054%20Powerup%20Microcode%20Tests%20-%20May%201980.pdf

And the System Test Fixture doc link I posted is from a microfiche that contains the original 4052/4054 microcode disassembly listing with comments! It also contains even more details on the PCB LEDs and Connectors with detailed power up steps!
 
We really ought to have a separate Tektronix-genre.....

Things that were wrong in my 4052 :

- Analog powersupply : a defective opamp pulled down the supplyvoltage for all other powersupply-opamps, rsulting in all analog power levels to be way off.
- defective ROM's
- defective DRAM ( the somewhat notorious 4116)
- and I also found out thet the machine will not boot if the tapeuinit is not present....

DRP module : be aware a full set of tests takes several minutes, with nothing much happening in between. It might be worthwhile to try just to run the CRC tests.
 
nikola-wan said:
Bob,

Check out this 4052/4054 System Test Fixture manual pdf pages 10 and 11:
github.com

Tektronix-4051-4052-4054-Program-Files/4052-4054_SystemTest/Tek_067-0942-99_System_Test_Fixture_instructions.pdf at master · mmcgraw74/Tektronix-4051-4052-4054-Program-Files

Archive of Tektronix 4051 4052 4054 and A series computer programs - mmcgraw74/Tektronix-4051-4052-4054-Program-Files
github.com github.com

All lights on indicates ALU, MCP Handshake, or I/O issue with your 4054A.

ALU issues could be due to bad microcode - here is a link to Jos' ALU ROMs:

My ALU ROMs are also in the same folder with my doc on how to read those ROMs with a DATA I/O programmer.

Monty
Click to expand...
Hi Monty,

Based upon the pages 10 and 11 you sent, I get the following indicator lights: 101111 111 which indicates "Write I/O handshake works. If halted, read I/O handshake failure has occurred."

Do you think that could still be a micro code issue?

Bob
 
nikola-wan said:
Hi Bob,

Use this link to see all the files in that folder including my microcode zip (should match the microcode ROMs in Jos' zip) and my doc on reading the old Motorola ROMs:
http://www.bitsavers.org/pdf/tektronix/405x/4052_4054/firmware/

The MAS ROMs zip are the BASIC EPROMs on the MAS board. The 4052A/4054A updated the MAS board to replace the ROMs and Patch ROMs with EPROMs and replaced the discrete GPIB circuit with a TI 9914 GPIB IC.

I just noticed the MAS ROMs zip is shuffled pairs of EPROMs into a single binary file which can be examined with a binary editor like HxD.

When you get your 4054A to pass the power on self test - you should be able to use the Option 1 serial interface (or manually enter the program) to load in my Checksum test program which will check your BASIC ROMs against my version 1.5 BASIC ROMs.

Here is a 4052/4054 Microcode Power Up Test Sequence service bulletin that I posted on my repo that may help:
https://github.com/mmcgraw74/Tektronix-4051-4052-4054-Program-Files/blob/master/4051-4052-4054_ServiceNotes/4052-4054%20Powerup%20Microcode%20Tests%20-%20May%201980.pdf

And the System Test Fixture doc link I posted is from a microfiche that contains the original 4052/4054 microcode disassembly listing with comments! It also contains even more details on the PCB LEDs and Connectors with detailed power up steps!
Click to expand...
Super helpful, thanks!
 
jdreesen said:
We really ought to have a separate Tektronix-genre.....

Things that were wrong in my 4052 :

- Analog powersupply : a defective opamp pulled down the supplyvoltage for all other powersupply-opamps, rsulting in all analog power levels to be way off.
- defective ROM's
- defective DRAM ( the somewhat notorious 4116)
- and I also found out thet the machine will not boot if the tapeuinit is not present....

DRP module : be aware a full set of tests takes several minutes, with nothing much happening in between. It might be worthwhile to try just to run the CRC tests.
Click to expand...
Thanks, and I was wondering the same thing - I keep posting in the DRP thread, but it is kind of more general troubleshooting going on. Should I start a new thread? Bob
 
Bob,

I think you should start a separate thread on this forum for your 4054A repair.
I'll bet some forum users (like me) only look at the thread title and assume they know what's going on if they have read the thread before.

Dave Roberts has been great at helping others diagnose their vintage computer problems.


BJeffway said:
Based upon the pages 10 and 11 you sent, I get the following indicator lights: 101111 111 which indicates "Write I/O handshake works. If halted, read I/O handshake failure has occurred."

Do you think that could still be a micro code issue?

Bob
Click to expand...

I don't think it is a microcode issue - I think Write I/O handshake works and Read I/O handshake failed.

I would try again without the DRP installed.

And if it halts again at this same spot - you have a Read I/O handshake failure.

But also if it gets this far, you might be able to use the DRP with the switches set to test the ALU.

Looking at page 19 of the microcode listing I see the begin I/O tests which are testing a PIA at FF0F.

My 4051/4052/4054 color address map indicates that is the 4054 MAG Tape DATA PIA:
http://www.bitsavers.org/pdf/tektronix/405x/4051_vs_4054_Address_Maps_-_colored.png
 
Last edited:
nikola-wan said:
Bob,

I think you should start a separate thread on this forum for your 4054A repair.
I'll bet some forum users (like me) only look at the thread title and assume they know what's going on if they have read the thread before.

Dave Roberts has been great at helping others diagnose their vintage computer problems.




I don't think it is a microcode issue - I think Write I/O handshake works and Read I/O handshake failed.

I would try again without the DRP installed.

And if it halts again at this same spot - you have a Read I/O handshake failure.

But also if it gets this far, you might be able to use the DRP with the switches set to test the ALU.

Looking at page 19 of the microcode listing I see the begin I/O tests which are testing a PIA at FF0F.

My 4051/4052/4054 color address map indicates that is the 4054 MAG Tape DATA PIA that the microcode powerup is using for the I/O Tests:
http://www.bitsavers.org/pdf/tektronix/405x/4051_vs_4054_Address_Maps_-_colored.png
Click to expand...
 
Excellent idea on starting a new thread - I was going to do that yesterday, but I have been using a new logic analyzer to gather more detailed data on what the micro-code is doing. I need to re-capture that at a higher sample rate tomorrow, and then take a close look at it. Everything I see so far says you are right about it being the I/O tests. I am trying to narrow it down as much as possible before making a new post. Yikes looks like troubleshooting that could be interesting. The technical data provided by you, Jos and others is incredibly valuable, I really appreciate it. You guys must have spent a good effort and a lot of time collecting it. That memory map you just sent is great! It even ties you to the schematic page.

The "4052/4054 Microcode Power Up Test Sequence service bulletin" is incredibly valuable, thanks much for that! That PDF only has pages 29 and 30. Is the entire document available somewhere?

I tried running the ALU test, but its not getting far enough in the start up to run anything on the DRP.

One embarrassing question - I can't seem to figure out how to start a new thread????

I hope to have some good detailed info tomorrow for me post to the new thread.

Thanks again to all for the help.
 
This is the link to the complete microfiche I found on Tek Wiki: https://w140.com/tekwiki/wiki/067-0942-99

This is the 4052/4054 System Test Fixture Personality Board instructions.

I converted the microfiche images to this pdf:
github.com

Tektronix-4051-4052-4054-Program-Files/4052-4054_SystemTest/Tek_067-0942-99_System_Test_Fixture_instructions.pdf at master · mmcgraw74/Tektronix-4051-4052-4054-Program-Files

Archive of Tektronix 4051 4052 4054 and A series computer programs - mmcgraw74/Tektronix-4051-4052-4054-Program-Files
github.com github.com

To start a new thread navigate back to https://forum.vcfed.org/index.php?forums/other/

Click in the box above the list of threads called "Thread Title" and type your new thread title.

Then you will be editing the first page of the new thread.

I assume you have downloaded the latest 4054A service manuals from the links I posted?

http://www.dvq.com/tektronix/Tek_070-2839-03_4054-4054A_parts_and_schematics.pdf
http://www.dvq.com/tektronix/Tek_070-2840-03_4052-4054A_technical_data.pdf
http://www.dvq.com/tektronix/Tek_070_2289_02_4054Opt30and31_operators.pdf

last one includes the Option 30 Service Manual and the Quick Reference Guide.
I donated to vintagetek.org for those microfiche manual scans to repair my 4054A and Bob at dvq.com posted the manuals as they are huge!
 
Last edited:
nikola-wan said:
Actually the 4054 Opt 30 and 31 link above is only the Option 30/31 Operators manual.

Here is the vintagetek.org scan posted on w140.com/tekwiki/wiki/4052 of the 4054 operator, service manual and quick reference guide (all three in one pdf):
070-2289-02_Opt30_Operators__070-2601-02_Opt30_Service__and_070-2586-01_Opt30_QuickRef
Click to expand...
OK, thanks to your help I started a new thread. The address data I grabbed from the microcode is very interesting, I think you and Jos will find it interesting, as well. Hopefully someone can help shed some light on where to look next.

This will be my last post here for a while, may be back once I get to the point where the DRP is running. Thanks to both you and Jos for all the super valuable help and links.

How on earth did you convert that poor quality microfiche JPG to a readable PDF??

One last question: These 2 pages are great that you posted here. Do you have the rest of that document?
github.com

Tektronix-4051-4052-4054-Program-Files/4051-4052-4054_ServiceNotes/4052-4054 Powerup Microcode Tests - May 1980.pdf at master · mmcgraw74/Tektronix-4051-4052-4054-Program-Files

Archive of Tektronix 4051 4052 4054 and A series computer programs - mmcgraw74/Tektronix-4051-4052-4054-Program-Files
github.com github.com

Best,
Bob
 
BJeffway said:
OK, thanks to your help I started a new thread. The address data I grabbed from the microcode is very interesting, I think you and Jos will find it interesting, as well. Hopefully someone can help shed some light on where to look next.

This will be my last post here for a while, may be back once I get to the point where the DRP is running. Thanks to both you and Jos for all the super valuable help and links.

How on earth did you convert that poor quality microfiche JPG to a readable PDF??

One last question: These 2 pages are great that you posted here. Do you have the rest of that document?
github.com

Tektronix-4051-4052-4054-Program-Files/4051-4052-4054_ServiceNotes/4052-4054 Powerup Microcode Tests - May 1980.pdf at master · mmcgraw74/Tektronix-4051-4052-4054-Program-Files

Archive of Tektronix 4051 4052 4054 and A series computer programs - mmcgraw74/Tektronix-4051-4052-4054-Program-Files
github.com github.com

Best,
Bob
Click to expand...
Bob - it was just those two pages in: https://w140.com/tekwiki/images/8/88/Wizards_workshop_issue_10-9_may_2_1980.pdf
This info was likely taken from the 4052/4054 microcode doc.
 
As I di not want to create yet another new 4052 thread I'll add it here.
Gents, please be aware of the WSI 57C49 Eprom, 8Kx8 in a 24 pin DIP, which can go low as 25nS access time. It could potentially be used for both the 82s181 in the ALU board, or the MK36xxx's in the MAS board.
Note that addresslines A10,A11 and A12 are swapped, so the contents needs to be moved accordingly.
If someone wants to try it : here are 5.1 MAS roms for the 4052, with transposed contents so that you can program those eproms directly, then they should be dropins for the ROM's in the MAS board. Not tested yet !
 

Attachments

jdreesen said:
As I di not want to create yet another new 4052 thread I'll add it here.
Gents, please be aware of the WSI 57C49 Eprom, 8Kx8 in a 24 pin DIP, which can go low as 25nS access time. It could potentially be used for both the 82s181 in the ALU board, or the MK36xxx's in the MAS board.
Note that addresslines A10,A11 and A12 are swapped, so the contents needs to be moved accordingly.
If someone wants to try it : here are 5.1 MAS roms for the 4052, with transposed contents so that you can program those eproms directly, then they should be dropins for the ROM's in the MAS board. Not tested yet !
Click to expand...
Now tested and confirmed to work for the MAS board. So that is a convenient drop-in replacement, but remember to use the transposed rom contents as posted above! Or transpose yourself with the quick hack below.
Jos
 

Attachments

@jdreesen, vcfed.org is trying to repair their Tektronix 4054 and suspect ROM rot.

They have a Tektronix 4052 Diagnostic ROM Pack - and I sent them the EPROM image you posted for your clone of the Diagnostic ROM pack - but apparently the 4054 ALU must not be working to run Diagnostic ROM Pack code.

I have pointed them to your WSI 57C49 solution post above for the MAS ROMs.

You mentioned in that post that it would also work for the ALU board 82S161 - have you got a transposed ALU ROM image that can be used? Also - for the 82S161 ROM replacement - the 57C49 plugs in directly with no need for a socket adapter?
 
Never got around to transpose the ROM images for the ALU, but you can do that with the above C-program. After transposing the 57C49 will drop right in, no need for a socket adaptor.
 
I built @nikola-wan 's GPIB drive and ran into random failures on some (but not all) program, which prompted me to realize there's likely some faulty RAM in my 4052 despite fully booting up and being able to load the GPIB drive without trouble. I obtained a DRP from @jdreesen, which has been very useful. The ROM CRC test identified my ROMs as version 2.1 without patches, and the RAM test found faulty RAM in the upper 16K, so I proceeded to pull the boards and pulled all the socketed 4116's that I ran through a little DRAM tester I found on ebay. Found 1 out of 18 RAMs were faulty. That was the easy part.

Now the hard part, on my 4052 the DRP appears to randomly fail or post an "ERROR HANG" message on the screen when running the RAM test, so I'm pretty certain there's at least another failing 4116 in the lower 16K that is affecting the DRP operation. Those chips are soldered on the board so I would like to pinpoint the failing chip rather than blindly desolder all 18 chips and risk great damage to the board. The DRP user guide pointed me to Appendix A. Did anyone run into this situation and understand how to use the microcode power-up memory test to pinpoint the failing RAM? I have already attached a logic analyzer to MB0-15 and the MCP program counter, but am trying to make sense of what exactly I'm looking for. Or has anyone figured out a better and easier way to narrow down RAM tests in the lower 16K?
 
Philcogrump said:
I built @nikola-wan 's GPIB drive and ran into random failures on some (but not all) program, which prompted me to realize there's likely some faulty RAM in my 4052 despite fully booting up and being able to load the GPIB drive without trouble. I obtained a DRP from @jdreesen, which has been very useful. The ROM CRC test identified my ROMs as version 2.1 without patches, and the RAM test found faulty RAM in the upper 16K, so I proceeded to pull the boards and pulled all the socketed 4116's that I ran through a little DRAM tester I found on ebay. Found 1 out of 18 RAMs were faulty. That was the easy part.

Now the hard part, on my 4052 the DRP appears to randomly fail or post an "ERROR HANG" message on the screen when running the RAM test, so I'm pretty certain there's at least another failing 4116 in the lower 16K that is affecting the DRP operation. Those chips are soldered on the board so I would like to pinpoint the failing chip rather than blindly desolder all 18 chips and risk great damage to the board. The DRP user guide pointed me to Appendix A. Did anyone run into this situation and understand how to use the microcode power-up memory test to pinpoint the failing RAM? I have already attached a logic analyzer to MB0-15 and the MCP program counter, but am trying to make sense of what exactly I'm looking for. Or has anyone figured out a better and easier way to narrow down RAM tests in the lower 16K?
Click to expand...

Can you post a photo of the DRP ERROR message you are getting?

v2.1 ROMs are apparently the first 4052/4054 ROM release and super old. You indicated your ROM CRCs are version 2.1 without patches - do you not have patch ROMs on your board?

Since your 4052 boots - I do NOT expect you to have any remaining bad DRAM, but hanging while running BASIC programs sounds like BASIC ROM errors (since you have such an old ROM set). I have never had my 4052 hang running any of my Flash Drive programs with v5.1 ROMs.

I think you should program up a set of WSI 57C49 EPROMs with Jos' zip file of 4052/4054 v5.1 which does not need patch ROMs. His zip has the bytes moved to correct for the difference in order on a couple of the address pins on the WSI 57C49 - see his link above in this thread:

https://forum.vcfed.org/index.php?threads/tektronix-4052-54-diagnostic-rom-pack-remade.63974/post-1315932

They can be programmed with a Data I/O Unipak 2 or 2B

​

 
Last edited:
nikola-wan said:
Can you post a photo of the DRP ERROR message you are getting?

v2.1 ROMs are apparently the first 4052/4054 ROM release and super old. You indicated your ROM CRCs are version 2.1 without patches - do you not have patch ROMs on your board?

Since your 4052 boots - I do NOT expect you to have any remaining bad DRAM, but hanging while running BASIC programs sounds like BASIC ROM errors (since you have such an old ROM set). I have never had my 4052 hang running any of my Flash Drive programs with v5.1 ROMs.

I think you should program up a set of WSI 57C49 EPROMs with Jos' zip file of 4052/4054 v5.1 which does not need patch ROMs. His zip has the bytes moved to correct for the difference in order on a couple of the address pins on the WSI 57C49 - see his link above in this thread:

https://forum.vcfed.org/index.php?threads/tektronix-4052-54-diagnostic-rom-pack-remade.63974/post-1315932

They can be programmed with a Data I/O Unipak 2 or 2B

​

Click to expand...
There are no patch ROMs on the MAS board, here's a photo: https://www.electronixandmore.com/resources/teksystem/boardbottom.jpg

I'll try Jos's WSI 57C49 ROM upgrade. Unfortunately in the process of debugging my 4052, the repeated power cycling killed the deflection power supplies so now I get a dot in the center of the screen and have a new problem to fix. 😅

Meanwhile, I ordered a set of 57C49's and will need to find or build a programmer for them.

I'm not 100% convinced there isn't a failing DRAM on the board because the nature of the errors and hangs with the diagnostics pack or even running programs off the GPIB drive are random and not repeatable.
 

Attachments

  • boardbottom.jpg
    boardbottom.jpg
    238.7 KB · Views: 5
You must log in or register to reply here.
Back
Top