@Grysia, post #1
Drive Identification
Amiga hosts expect a drive ID sequence from external and Amiga-high-density drives on pin 34 of the floppy interface when the drive motor is disabled (pin 34 carries the Ready/RDY signal when the drive motor is enabled). In contrast, FlashFloppy's default interface mode (interface = shugart) permanently attaches RDY to pin 34, regardless of motor.
This default behaviour usually works fine:
Drive ID signalling is not required for double-density DF0 operation
External drive enclosures often implement the drive-ID circuitry
A mounted disk image asserts RDY which happens to match the Amiga ID sequence for a double-density drive anyway
However, there are a couple of cases where this default behaviour may not suffice:
Using high-density disk images (1760kB formatted capacity)
Using as an external drive with a passive interface cable, if FlashFloppy does not assert RDY during boot (eg. eject-at-power-on, no USB stick, or too slow to initialise)
In the above cases FlashFloppy can be configured to emulate the drive ID in several ways:
1. Basic identification (any Gotek)
The following line in FF.CFG will force FlashFloppy to emit the drive ID on pin 34 at all times:
interface = amiga
When high-density images are not being used, and when FlashFloppy is being used as DF0 or without problems as DF1-DF3, then the default interface type (interface = shugart) is preferred as this gives more accurate behaviour on pin 34 when the drive motor is on.
@Grysia, post #7
The following line in FF.CFG will force FlashFloppy to emit the drive ID on pin 34 at all times:
interface = amiga
@Grysia, post #7
@Grysia, post #11