RC2014 Z80 RomWBW HBIOS v3.0.1 unable to detect floppy "FD"

[Jo Ga]

I build the floppy controller from :

http://www.smbaker.com/wordpress/wp-content/uploads/2016/12/rc2014-floppy-wd-sch.png

RC2014 boot after adding the FD controller. Is not detecting the FD device when  already in the slot and floppy connected.

Current RC2014 with the FD card installed: Is not detecting the FD 

RomWBW HBIOS v3.0.1, 2021-10-17

RC2014 Z80 @ 7.372MHz

0 MEM W/S, 1 I/O W/S, INT MODE 1

512KB ROM, 512KB RAM

SIO0: IO=0x80 SIO MODE=115200,8,N,1

SIO1: IO=0x82 SIO MODE=115200,8,N,1

DSRTC: MODE=STD IO=0xC0 NOT PRESENT

MD: UNITS=2 ROMDISK=384KB RAMDISK=384KB

IDE: IO=0x10 MODE=RC

IDE0: 8-BIT LBA BLOCKS=0x0003D400 SIZE=122MB

IDE1: NO MEDIA

PPIDE: IO=0x20 PPI NOT PRESENT

Unit        Device      Type              Capacity/Mode

----------  ----------  ----------------  --------------------

Char 0      SIO0:       RS-232            115200,8,N,1

Char 1      SIO1:       RS-232            115200,8,N,1

Disk 0      MD1:        RAM Disk          384KB,LBA

Disk 1      MD0:        ROM Disk          384KB,LBA

Disk 2      IDE0:       CompactFlash      122MB,LBA

Disk 3      IDE1:       Hard Disk         --

RC2014 Boot Loader

SURVEY status with the card installed. Address 50 show in the report when card is present, If I remove the card , the 50… LINE doesn’t report.

B>SURVEY

                *** System Survey (December 17) ***

Drive A: 24K bytes in 0 files with 360K bytes remaining

Drive B: 380K bytes in 58 files with 4K bytes remaining

Memory map:

0       8       16      24      32      40      48      56      64

|       |       |       |       |       |       |       |       |

 TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTCCCBBBBBBB

T=TPA   C=CPM   B=BIOS or unassigned    R=ROM or bad

BIOS at E603    iobyte 94       drive 01        BDOS at D806

65535 Bytes RAM         0 Bytes ROM             55302 Bytes in TPA

0 Bytes Empty           65535 Total Active Bytes

Active I/O ports:

10 11 12 13 14 15 16 17 

50 51 52 53 5C 5D 5E 5F 

80 81 82 83 84 85 86 87 

90 91 92 93 94 95 96 97 

32 Ports active

B>

FDU tool show the drive is accessible, I Can change the floppy light and I can listen to the motors, and floppy spinning.

 (H) RC2014 WDC (SMB)

  (I) SmallZ80 Expansion

  (J) Dyno-Card FDC, D1030

  (X) Exit

=== OPTION ===> RC-WDC

CONFIGURING TRACE AND THE 1.44MB IN POLL

===== RC-WDC ==========<< FDU MAIN MENU >>======================

(S)ETUP: UNIT=00  MEDIA=1.44MB   MODE=POLL        TRACE=01

————————————————————————————————

READING RAMDOM:

=== OPTION ===> VERIFY (S)ECTOR, (T)RACK, (D)ISK, (R)ANDOM ===> RANDOM

RESET DRIVE...

SENSE INTERRUPT: 08 --> C0 00 [DISK CHANGE]

SENSE INTERRUPT: 08 --> C1 00 [DISK CHANGE]

SENSE INTERRUPT: 08 --> C2 00 [DISK CHANGE]

SENSE INTERRUPT: 08 --> C3 00 [DISK CHANGE]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SPECIFY: 03 D0 11 --> <EMPTY> [OK]

RECALIBRATE: 07 00 --> <EMPTY> [OK]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 20 00 [OK]

PROGRESS: TRACK=11 HEAD=01 SECTOR=07

SEEK: 0F 04 11 --> <EMPTY> [OK]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 20 11 [OK]

READ: 46 04 11 01 07 02 07 1B FF --> 44 04 00 11 01 07 02 [NO DATA]

CONTINUE? (A)BORT, (R)ETRY, (I)GNORE ===> 

FORMAT A TRACK

=== OPTION ===> FORMAT (T)RACK, (D)ISK ===> TRACK

ENTER TRACK [00-4F] (11): 44

ENTER HEAD [00-01] (01):   

ENTER INTERLEAVE [01-12] (02):   

RESET DRIVE...

SENSE INTERRUPT: 08 --> C0 00 [DISK CHANGE]

SENSE INTERRUPT: 08 --> C1 00 [DISK CHANGE]

SENSE INTERRUPT: 08 --> C2 00 [DISK CHANGE]

SENSE INTERRUPT: 08 --> C3 00 [DISK CHANGE]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SPECIFY: 03 D0 11 --> <EMPTY> [OK]

RECALIBRATE: 07 04 --> <EMPTY> [OK]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 20 00 [OK]

PROGRESS: TRACK=44 HEAD=01 SECTOR=01

SEEK: 0F 04 44 --> <EMPTY> [OK]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]

SENSE INTERRUPT: 08 --> 20 44 [OK]

FORMAT TRACK: 4D 04 02 12 6C E5 --> 04 00 00 44 04 12 02 [OK]

NOTES:

  a)-I did try with /DACK enable. Same results.

  b)-Change the card position in the 8 back plane to different slot.

  c)- survey don’t show the port 50 without the card in the slot

B>survey

                *** System Survey (December 17) ***

Drive A: 24K bytes in 0 files with 360K bytes remaining

Drive B: 380K bytes in 58 files with 4K bytes remaining

Memory map:

0       8       16      24      32      40      48      56      64

|       |       |       |       |       |       |       |       |

 TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTCCCBBBBBBB

T=TPA   C=CPM   B=BIOS or unassigned    R=ROM or bad

BIOS at E603    iobyte 94       drive 01        BDOS at D806

65535 Bytes RAM         0 Bytes ROM             55302 Bytes in TPA

0 Bytes Empty           65535 Total Active Bytes

Active I/O ports:

10 11 12 13 14 15 16 17 

80 81 82 83 84 85 86 87 

90 91 92 93 94 95 96 97 

24 Ports active

B>

[Tadeusz Pycio]

Build a RomWBW with FDD support.

FDENABLE    .EQU    TRUE      

FDMODE        .EQU    FDMODE_RCWDC

[Jo Ga]

Thank you very much for quick response. I do appreciate.

I'm relative new to the RC2014 build and never have done the RomWBW, for what I was reading is going to be process.

I need to get familiar with the process, the tools, and the methodology, after that I will have to see where are those flags ( what module and what flag/file)

Any help is welcome, will be great if someone can provide with any information.

No sure but I was under the understanding that the FD was enable as default as per I read. 

How I do know if the current romWBW the FD is enable. Any address that I can check from the monitor, a flag to check?

Before I do replace my romWBW

I'm not 100% that the hardware if perfect, is a board I just build, and I have not easy way to test in other machine.

Jose.

[Tadeusz Pycio]

Supported, key elements are displayed on the start screen, even if they are not present in the configuration (example below).

Changes can be made in the configuration files for a given configuration, in your case it would probably be "RCZ80_std.asm" in the /Source/HBIOS/Config folder, and then a new RomWBW should be built.

[Wayne Warthen]

The current Development Snapshots on the RomWBW Releases page do have floppy support enabled by default.  You could download the current snapshot and try that.

Based on your FDU results, the card is generally working.  Seeking and formatting are working.  Reading data seems to be failing.  You definitely want everything to work under FDU before worrying about getting it to work under CP/M.  Focus on FDU until everything works there.  Make sure your media and drive are good.  Make sure your media is correct for 1.44MB (high density).  If you have a PC with a 1.44MB floppy, then format and test a floppy on the PC.  Then try to read that floppy on your RC2014 using FDU.

Thanks,

Wayne

[Wayne Warthen]

Wanted to clarify a couple things I just said.

On Sunday, July 24, 2022 at 7:08:37 AM UTC-7 Wayne Warthen wrote:

The current Development Snapshots on the RomWBW Releases page do have floppy support enabled by default.  You could download the current snapshot and try that.

The current official release of RomWBW (v3.0.1) that you are using does NOT have floppy support enabled by default.  That is why you do not see it reflected in the boot messages.  The current Development Snapshot (v3.1.1) does have it enabled by default.  You can download the development snapshot from the RomWBW Releases page and use the RCZ80_std.rom binary from that.  You do NOT need to have floppy support enabled in RomWBW for FDU.COM to work.  FDU.COM is a completely standalone test tool that talks directly to the hardware.

I want to go back and double check the correct jumper settings for this board.  I will send another message a little later when I can do that.

Thanks,

Wayne

[Jo Ga]

Wow, you guys are so great, in answering the questions, great support. Thank you 

Now I understand why I was reading that FD was enable. That explain a lot and simplify what I need to do.

Plan:

Just in case I will wait for a new rom chip , I just purchased, program the new one and keep the original just in case.

So the reading of the floppy , they are old, better to get new ones, and get an USB floppy drive for my laptop, that way I can read/write/format the floppy and take a variable from the issue reading the floppy from the card using FD,  and will help moving stuff from to the pc.

The address is configured in the pin 3 from left to right (40) but the others 2 pin are not connected, I left them unconnected.

I will update the results as I go.

Thank you so much for helping,

Jose,

[Wayne Warthen]

I have attached a picture of my board.  This shows the jumper configuration I am using.  I just confirmed this board is working.

WARNING: It appears that the numbering of JP1 and JP2 pins on the silkscreen is backwards from the schematic.  I suggest using the attached picture as a reference to set the jumpers properly.

Thanks,

Wayne

[Richard Deane]

If you plan on buying a floppy drive, do consider a gotek floppy emulator as an alternative. I have two used with my zeta2 under romwbw. It uses floppy images stored on USB stick. They are quite cheap through aliexpress. 

Richard

--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/01b24896-c058-411c-a927-950e7cdeb974n%40googlegroups.com.

[Jo Ga]

I think it will be ok with the  77061102P ( 6 pin bussed 1k), do you have the part number you use ?

In the picture I only see two resistors. My card has a resistor next to the capacitor next to the oscillator, but it could be the picture angle, so I don't see the resistor.

Jose.

--
You received this message because you are subscribed to a topic in the Google Groups "RC2014-Z80" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rc2014-z80/gCsIBhLqLSA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rc2014-z80+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/5bcc3ad8-8ca9-4b76-9f37-80018df879f8n%40googlegroups.com.

[Wayne Warthen]

On Mon, Jul 25, 2022 at 4:59 PM Jo Ga <jlgv...@gmail.com> wrote:

I think it will be ok with the  77061102P ( 6 pin bussed 1k), do you have the part number you use ?

I don't have the specific part number, but the 77061102P should be equivalent and fine.

In the picture I only see two resistors. My card has a resistor next to the capacitor next to the oscillator, but it could be the picture angle, so I don't see the resistor.

The third resistor is not visible in the picture, but all 3 resistors on my board (R1-R3) are identical.

Thanks.

Wayne 

[Jo Ga]

Thank you so much for your time and clarifications. So , now I need to wait for the new rom, the resistor , the new floppy and the usb floppy drive. 

I'm not sure about you but I'm nostalgic about the sound of the floppy drive. I will keep adding more to the RC2014, it has been a great project and great people like you

helping and supporting the newcomers.

After the floppy I'm thinking of adding a  sound. I have an AY-3-8910A . Any recommendations?

Thank you.

Jose.

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CADQpb5OwAydUWXkURAQpVS7YPvTeSdTajEfz7DCVTwJh%2BqFbFQ%40mail.gmail.com.

[Wayne Warthen]

On Mon, Jul 25, 2022 at 5:28 PM Jo Ga <jlgv...@gmail.com> wrote:

Thank you so much for your time and clarifications. So , now I need to wait for the new rom, the resistor , the new floppy and the usb floppy drive. 

I'm not sure about you but I'm nostalgic about the sound of the floppy drive. I will keep adding more to the RC2014, it has been a great project and great people like you

helping and supporting the newcomers.

I absolutely love the sound/experience of real floppy drives.  I even have some 8" drives that I hook up on occasion!

After the floppy I'm thinking of adding a  sound. I have an AY-3-8910A . Any recommendations?

Yes, the AY-3-8910A will work great in Ed Brindley's RC2014 Sound Card.   You can get a kit with everything but the AY-3-8910 sound chip from Spencer's store: https://z80kits.com/shop/ym2149-sound-card/.

-Wayne

[Jo Ga]

I tested the floppies , in my PC with an usb floppy drive and format them out. When reading from the board , same messages.

Im waiting for pet to rebuild the board, the resistors are the correct one. 

Notes: the floppies are ok

Floppy drive still posible problem, card also a posible problem. 

RomWbW is detecting the FD 

That one is fixed, but still not properly working. 

I found a module to attach to an usb drive and will be able to connect to the FD cable while removing the usb cable from the floppy.  I have to open the usb drive . I will be able to determine if is the drive.

I think I will get the virtual drive if still having issues.

I will keep updating the process. Any ideas are welcome.

Jose

On Jul 24, 2022, at 10:31 AM, Wayne Warthen <wwar...@gmail.com> wrote:

Wanted to clarify a couple things I just said.

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/63083e5b-75c1-4cb3-9a58-2bdda0248a21n%40googlegroups.com.

[Alan Cox]

On Tue, 9 Aug 2022 at 10:58, Jo Ga <jlgv...@gmail.com> wrote:
>
> Summary:
> The card I made I did so with all resistors at 4.6K, when the RN1 resistor should be at 1K. After the change I have the GoTEk working in the RC214. But the original Floppy Drive still has issues. Im blaming that to the old hardware.


1K should work with most PC era drives but it's actually still too big
for some of the old clunkers and way to big for 8" and very early
5.25". Also never assume "the floppy is OK". It's ok for a particular
drive and alignment. Hopefully the USB drive is properly aligned but
your other drive may not be if I'm understanding the email chain
right.

My normal workflow is

- If it's 3" change the drive band unless it has a new one already

- inspect the heads, clean them if need be

- Check the disks you are using have no mould patterns on them as that
indicates trouble and will gunk up the head and probably means the
disk is useless anyway

- Format a test disk with that drive starting at track 0 and watch and
listen to the head movement. Old 5.25" often need a tiny bit of
lubrication. Some of the full height drives like the Trash80 ones need
a fair bit.

- Try to get the point I can format and read back an entire disk
reliably. If a couple of test disks persistently error at the same
point you may need to look at the alignment and movement much harder.

Only at that point try and use a disk from another system and then use
that to re-align the heads if needed. Properly this is done with a
scope aligning the pattern. Improperly but usually it is done with a
sample disk from another device and a bit of tweaking back and forth
to find the middle of the range it reliably reads.

[Wayne Warthen]

Hi Jose,

You provided a lot of information and I'm not sure I understand all of it.  I strongly concur with all of Alan's comments about floppy media and hardware.  I have tried to address your questions below.

Thanks,

Wayne

On Tue, Aug 9, 2022 at 2:58 AM Jo Ga <jlgv...@gmail.com> wrote:

Question:  I have tried to open/export the image in the windows 10 usb under windows 10. I don’t have a GotEk in the windows 10.

 

Should I still be able to still open the images that are working in the RC2014?

If you mean that you are removing the USB stick from the GoTek and putting it in your Windows 10 PC, then yes, you should see the image files on the USB stick from Windows 10.  I'm not quite sure what you mean by open/export them.  What are you using to open or export?

 

My two questions:

Any idea why the CPM/Z is telling me the disk is FULL?

If the floppy was "preformatted" for IBM PC or formatted on an IBM PC, then you will need to use CLRDIR on the RC2014 to "clear" the CP/M directory area.  If not, CP/M will report no space available.  If you format the floppy using FDU on the RC2014, it should be fine without needing to use CLRDIr.

 

Should I still be able to still open the images that are working in the RC2014?

Sorry, I still don't know what you mean by "open the images".

TESTING 

 But the original Floppy Drive still has issues. Im putting that into the old Drive.

Question:  I have tried to open/export the image in the windows 10 usb under windows 10. I don’t have a GotEk in the windows 10.

 

Should I still be able to still open the images that are working in the RC2014?

Are you saying that you connect the USB floppy drive to Windows and you are trying to read the floppy that works in the RC2014 from Windows using the USB floppy drive?  Windows does not understand a CP/M filesystem at all, so it won't natively read a floppy containing a CP/M floppy filesystem.  However, you should be able to read the raw data using a tool like rawwritewin.

It sounds to me like the GoTek and the modified USB floppy are both working fine on our RC2014.  The DATA MISMATCH errors are probably  because you have not written a specific test pattern to all sectors of the disk.  Review the FDU documentation with respect to how the VERIFY function works.  You must write a known sector prior to using the VERIFY function.  Truthfully, the VERIFY function is almost useless.  If you can FORMAT, WRITE, and READ to an entire floppy using FDU, then everything should be fine.

Thanks,

Wayne

[Jo Ga]

Thank you again for the quick answers and clarifications.   The good news is the Floppy Card is working after fixing the resistors RN1 to 1K.

The Gotek:

I have never used a GoTek before, so i'm not sure how i should be able to see the partitions from a windows 10 pc. 

The Gotek is not having any issues in the CM/P, I'm able to read and write to the Gotek. When I tried to open the USB in a Windows PC (without the Gotek drive), it didn't open, and was asking to format the USB drive,

In the Gotek software there is an option to export an image from the USB, i also was trying that option, but in reality I don't know how it is supposed to work.

The USB drive converted to 34 pins:

I was able to read from the floppy, and when writing , was telling it was full, so now I know what to do.

I will update after the re-test with the information provided, and I will try to better present the problem and the test that was done.

Jose.

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CADQpb5Ovob8FBBK4P4ku12uo%3DAB%3DkWtZBAdKgWr4ywAKKecZTA%40mail.gmail.com.