Bad harddisc controller HD5 from Janich&Klass (Germany)

5 views
Skip to first unread message

ich.c...@gmail.com

unread,
6:42 AM (9 hours ago) 6:42 AM
to MFM Discuss
Hi, I have a CP/M system from  Janich & Klass (Germany) including a harddisc controller HD5. Sadly I have no manuals for the HD5 controller. 

I installed the CP/M from the original floppy disks and answered all questions
about the hardware correctly.

jk_mkc_hdc5_rev3_w01.jpg

Testing with a real harddisk only the 1st try worked correctly and the system
was booting from the harddisc. Sadly I did not made a image from this installation as while rading with the MFMEMU analysing endet correctly.
After this the harddisk controller goes bad.  

1st boot from HD was ok.

1-hd_only_1st_run_ok.jpg

Format ERROR:
2-bad-hd-format.jpg



#############
## ANALYSING##
#############

root@beaglebone:~# cd ~/mfm
root@beaglebone:~/mfm# ./setup_mfm_read
Rev B Board
root@beaglebone:~/mfm# ./mfm_read --analyze --transitions_file 1_raw_test-1
--extracted_data_file 1_extracted_test-1 --emulation_file  1_emufile_test-1
----note "JK HD5"
Board revision B detected
Found drive at select 1
Drive RPM 3569.5
Matches count 18 for controller WD_1006
Header CRC: Polynomial 0x1021 length 16 initial value 0xffff
Sector length 1024
Data CRC: Polynomial 0x1021 length 16 initial value 0xffff
Selected head 4 found 0, last good head found 3
Read errors trying to determine sector numbering, results may be in error
Number of heads 4 number of sectors 9 first sector 0
Interleave (not checked): 0 4 8 3 7 2 6 1 5
Drive supports buffered seeks (ST412)
No sectors readable from cylinder 615                                          
Stopping end of disk search due to two unreadable tracks in a row
Number of cylinders 615, 22.7 MB

Command line to read disk:
--format WD_1006 --sectors 9,0 --heads 4 --cylinders 615 --header_crc
--0xffff,0x1021,16,0 --data_crc  0xffff,0x1021,16,0 --sector_length 1024
----retries 50,4 --drive 1


Found cyl 0 to 614, head 0 to 3, sector 0 to 8                                
Expected 22140 sectors got 22140 good sectors, 0 bad header, 0 bad data
0 sectors marked bad or spare
0 sectors corrected with ECC. Max bits in burst corrected 0
Track read time in ms min 31.655542 max 1655.718042 avg 52.515619


##################################
## New empty image for testing: ##
##################################                              
mfm_emu –drive 1 --file test1 --initialize --cylinders 615 --heads 4 –note “J&K HD5”

Then I have to format with the HD5 controller but got an error. On real harddisk
I got "BAD SECTOR ID" from the controller.



Emulation started Wed Sep 17 16:24:46 2025
##########################################

PRU 0 pc 025b
00: 0031f3aa 00000190 0000001e 00000002 00c00f00 00140027 5f8f3d22 1409cfff
08: 06000000 07000000 6f3faf5b 0032de30 00009bf0 aeff3ff1 4f3b7f79 1727aa65
16: 00000000 0002200c 00000034 00000000 00000000 4fdfc6ff 00000016 9ca00000
24: 00010000 4804c194 000bc714 00000000 00000014 0000021a fd257ab7 40000080

0000: 9ca00000 000fffff 4a300000 00000000 00000000 00000000 00000000 00000000
0020: 5bd507fc c2270de9 5a2c8534 234ee7b8 000000ff 00000000 00000000 00000000
0040: 00000000 ccaf6452 00000000 00800f00 00000000 00000267 e5c89e28 00000004
0060: 00000000 00000000 00000000 00000000 00000000 00000016 00000000 00000c00
0080: 00000000 00000000 00000000 00000014 00000027 0032de30 00009bf0 0032de80
00a0: 1b5f6814 00000000 00000000 00800f00 8a69a152 9e476743 865abe14 783b27cc
00c0: 4f57d437 971b17bb 788fefb6 2f012f6b 1a878a2f ad3063ca a8ac90f1 c697837a
00e0: 00000034 0000041b 11947be7 e2d5f860 0032de76 000bbf78 000096c1 7ecb76b3

0400: 1e631873 9d7f0327 0f7c9297 eacce54a 656500ec b9ae0ece f7c18c4f c433d340
0420: 3f2808c3 8eaa7e40 4c374fe5 1a59a9f4 048ff049 486ab05a 908a0c92 e01b09f0
0440: 5f4a34a4 77a887a6 0e15271c 3848763c a675f805 dad177ab 9ad688cd ea716386
0460: 8a65217a a7afa4e4 0548f729 0135a1aa 585105ba 08a9b8ef d3e5c68d f8b1f376

PRU 1 pc 0116
00: aaaaaaaa aaaaaaaa 00000440 00000400 0000001e 0002200c 00000001 20a30004
08: 07000000 07000000 00000010 00001458 ffb90000 00000410 ffffffff 00000000
16: 3f6aaf85 00005164 00000034 f5620105 00000000 000b141e 0000000c 9ca00000
24: 00000030 00002210 49000000 49004100 00000007 0000000c d7a97a12 40000000

0000: 9ca00000 000fffff 4a302000 00000000 00000000 00000000 00000000 00000000
0020: 223f303a 9f6921bc 07de11af 82b3d43d 00000001 00000000 00000000 19f5cc6a
0040: 2a525556 ae67a2a1 7fff333b 808106ce 0000000c 1add1e50 00005164 74c17761
0060: 0ccccccd 0000001e 00000014 00000007 00000440 00000040 3d861855 3680448b
0080: 02000027 0300003b 02000027 02000027 02000027 0300003b 02000027 02000027
00a0: 02140027 0314003b 02140027 02140027 02140027 0314003b 02140027 02140027
00c0: 30374272 99c98a9c 58ee10ef 4e81b00a 0001000c 9ca05164 048e9d48 18d04d2b
00e0: 0032bcfa 003294f2 0032bd48 000bc163 8174902f 000bc183 0000040f 000bbf9a

0400: aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa
0420: aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa
0440: aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa
0460: aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa

0000: 02140027 02140027 02140027 02140027 02140027 02140027 02140027 02140027
0020: 59bcb641 b005d8b7 a3a50565 cca9d02d 222e9ce8 088f0545 360f926d fcc8b343
0040: fbaaa69d 65c1e2db b7e4f80b 4375d599 0b2e8f72 f6aa0cec 1429b426 150ba617
0060: 52f4db9e 660a82b6 0432cb53 ee18e41d 608d8e23 68939584 23a1a707 1a0f0942



ich.c...@gmail.com

unread,
6:47 AM (9 hours ago) 6:47 AM
to MFM Discuss

David Gesswein

unread,
8:06 AM (7 hours ago) 8:06 AM
to mfm-d...@googlegroups.com
The emulator dump shows that the controller activated the write signal
but didn't generate any transitions on the data lines on the 20 pin
connector pins 13,14. This would be consistent with getting bad sector ID
when you tried formatting with real disk.

You showed emulator reading the disk. Was that the bootable CP/M copy? You
said you didn't get an image of the bootable CP/M though.

The SN75118N near the 20 pin connector is the transmitter and receiver for
the drive data. If you have a scope would be a good place to start checking.
Should see transistions with 200, 300, and 400ns separation when write line
goes low.

If you have another 20 pin cable may want to try it first and make sure its
plugged in with the correct orientation. Cable backward could cause this
problem.

The pictures you linked to in the other post I get access denied. Probably
not important for me to see them.
> --
> You received this message because you are subscribed to the Google Groups "MFM Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to mfm-discuss...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/mfm-discuss/f4ecd1b3-edeb-4a7b-ba2f-49e4959c88bdn%40googlegroups.com.




Reply all
Reply to author
Forward
Message has been deleted
0 new messages