• Please review our updated Terms and Rules here

Kaypro 2/84 issues.. need insight and help.

Patrick.B (TTR)

Patrick.B (TTR)

Experienced Member
Joined
May 11, 2011
Messages
496
Location
Houston, Texas, USA
So I opened this Kaypro 2/84 (discovered it was by board images on https://retrocmp.de/kaypro/kay-p2_hrdw.htm#mb-284
and quickly realized the A: drive doesn't "spin at all, so I took it out and made drive B: as drive A: (yes I changed the jumper to DS0)
and I get a "cannot read your diskette" error, so I tried K2-22G and K2-BLNK Images on http://www.retroarchive.org/maslin/disks/kaypro/index.html lists
which is TD02IMD conversion to IMD then converted using HxCSoftware to HFE format then utilizing CPM2.2 TRS-80 Model 4 configuring both drives as Kaypro 2 SSDD 40T formats I ran DUP to copy HFE to Actual Diskette.
Now I have converted before TD0to IMD to HFE on the K10 and know how to verify the images so I am pretty certain the images are good to Use (but if someone wants to double-check them for me on their K2-gotek ask away for images)
So I figured the drive isn't "actuating/moving the head, so I slapped my gotek on it as I have done on my previous Kaypro 10
It does access the gotek drive (led turns on) but doesn't try to read the drive, in the image below the T-000 tells me when the drive is changing tracks. I still get the same error.
lastly, I did change the WDC9216 ICX on a whim thinking.... same results.

thoughts, insights?
images attached if someone wants to double check images for gotek
 

Attachments

  • 20230619_143526.jpg
    20230619_143526.jpg
    824.5 KB · Views: 11
  • 20230619_204841.jpg
    20230619_204841.jpg
    620.4 KB · Views: 14
  • 20230619_204845.jpg
    20230619_204845.jpg
    2.1 MB · Views: 13
  • K2 Disk Images.zip
    271.2 KB · Views: 0
Have you confirmed the disk select is active and present at the Gotek? With a multimeter? If the Gotek is being accessed, it's possibly accessing Track 0 and not getting good data... But I am not that familiar with Kaypro yet to be certain.

There's a full video with links in the description to working Gotek files and configurations that you may be looking for on Youtube - It maybe useful for sanity checking your steps.



Regards
David
 
Note that all of the Kaypro CP/M image resides on track 0 (sides 0 and 1), so the head won't move until you get the CP/M prompt and load a file (or run a program). However, it sounds like the reads during boot are failing, but we don't have enough information about why. Looks like you have the 81-292 ROM (missing the label), have you verified that it has not been corrupted?

If you can burn a ROM, and hook up the serial port, you could try the debug monitor and floppy procedures described in the document http://sebhc.durgadas.com/kaypro/diags.pdf and get more information.
 
Patrick,
Having had a very similar problem with a Kaypro 4/84, I'd suggest the following tests
in order.

1. Veryify the following Clock Signals for:
84MHz, 4MHz, 2MHz, 1MHz, and CLK at Pin 24 of the FDC.

2. Verify VDC on Pins:
21 = +5VDC
22 = +5VDC
40 = +12VDC


3. Verfiy the INPUTS to the FDC from the Floppy's Pins on J8-xx
NOTE: Floppy Must be Selected for these Inputs to be Active to FDC.
Also Verify the PULLUP Resistors R45, R46, and R47.
/INDEX J8-8 Input thru U61 to FDC Pin 35
/TRK00 J8-26 Input thru U61 to FDC Pin 34
/WPRTCT J8-28 thru U61 to FDC Pin 36

4. Verify the /RD and /WR thru U52 to FDC Pins:
Pin 2 = /WE
Pin 4 = /RD


The Motherboard I was working on would step to track 0 on powerup, but would not step
IN towards the Hub when trying to read. This was because a gate was stuck at about
1.8 VDC for U52 Pin 10. Replacing the 74LS32 (U52) fixed the problem.

It won't take long to locate the problem if you use Doug's Diagnostic Monitor.

REF: https://forum.vcfed.org/index.php?threads/the-dead-kaypros-society.1243241/

Larry
 
Last edited:
durgadas311 said:
If you can burn a ROM, and hook up the serial port, you could try the debug monitor and floppy procedures described in the document http://sebhc.durgadas.com/kaypro/diags.pdf and get more information.
Click to expand...

yeah something deeper than just internal I think in this case when I test teeh flpy it hangs on most commands.
see below log from terminal

I noted with * text descriptions*


Kaypro Monitor v2.2

: N CRTC
: *NOTE MONITOR TURNED ON
?
: T CRTC
Wait... UpdateAbort
: * TEST LOCKS UP PRESED ESC TO ABORT
?
: T VRT
E0 016A
C0 01CF
E0 07FE
C0 0863
E0 0E92
C0 0EF6
E0 1525
C0 158A
E0 1BB9
C0 1C1E

:
Kaypro Monitor v2.2

: * TESTING FLOPPY WHEN NOT SELECTED
?
: T FLPY
01 0002
00 0003

: * NOTE 00 FFFF NEVER SHOWED UP ON THIS TEST AS PER MANUAL
?
: O 10 03

: I 10
Input 10 = 01

: T FLPY 53
01 0002
00 09AF

: T FLPY 03
01 0002

: T FLPY
01 0002
00 0003

: T FDRD 00
** This test hangs the machine completely. no key command makes it quit hard reset required.

Suggestions?
 
ldkraemer said:
Patrick, Having had a very similar problem with a Kaypro 4/84, I'd suggest the following tests in order.

1. Verify the following Clock Signals for: 84MHz, 4MHz, 2MHz, 1MHz, and CLK at Pin 24 of the FDC.
2. Verify VDC on Pins: 21 = +5VDC, 22 = +5VDC, 40 = +12VDC

Larry
Click to expand...

Hey Larry I assume your asking from motherboard pins? not the floppy pins
RE test 1, and your testing clock signal changes on pin 24 of the FDC in what manner? Scope settings set to auto ?

RE test 2, pin 21, 22 and pin 40 ? fdc only has 34 pins. please explain.
 
I'm a bit surprised that the display lit up, but the T CRTC did not work. We might need to revisit that.

The floppy tests are looking like TRK00 from the drives is not working, although it looks like maybe you didn't select a drive? Maybe make certain you followed the notes on the SysPort for the */84 models. I probably need to add more to the Floppy Diagnosis section to remind the reader to select a drive.
 
Patrick.B (TTR) said:
I will admit I read it in a diagonal will re read it when I am rested, 5 hours of driving made my brain mush
Click to expand...
I did update the diags.pdf doc just now, as it was a bit "skinny" regarding that. I also put a frequently-used example value in the SysPort Usage section.
 
it was great to be able to "show you whats going on over discord" now to attack all the things Larry suggested to find why the data isnt getting to the drive.
 
You must log in or register to reply here.
Back
Top