Support Opus Discovery Disks

[gnulnulf]

I have an Opus Discovery drive.
It has 2 formats:
single sided 40 tracks, 18 sectors, 256 sector size, index 0 (sectors 0-17)
double sided 80 tracks, 18 sectors, 256 sector size, index 0 (sectors 0-17)

The double sided version overlaps size with other 720k disks.
Would it be an option to use the extension (OP1/OP2) to specify disk options?

In FloppyDisk.cpp I expect to add something like:
case (uint16_t) (40118/2): //40 track 1 sided Opus image 180k
numTrack = 40;
numSec = 18;
bitLength = BIT_LENGTH_DD;
flags.seclen = 1; //256b sectors
break;

How can I set the number of heads?
Do you know where the sector number is set?

[gnulnulf]

I tested it for the single sided and most of the data looks OK.
(In my fork/branch opus1)
I see quite a lot crc errors but that could be my breadboard.

I used fddemu-> greaseweasle (scp) -> HxCfloppyemulator track analyzer.

[acemielektron]

Thanks, since I don't have relevant hardware I appreciate your comments.

…

On Wed, Jun 28, 2023, 18:16 Arco van Geest ***@***.***> wrote: I tested it for the single sided and most of the data looks OK. (In my fork/branch opus1) I see quite a lot crc errors but that could be my breadboard. I used fddemu-> greaseweasle (scp) -> HxCfloppyemulator track analyzer. — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAM2CIRGPWJJ74MWUSPH6OLXNRDDTANCNFSM6AAAAAAZUUHTIQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[acemielektron]

I should look at CRC code for 256 byte sectors. As I mentioned I don't have such hardware to test so your comments are appreciated. Edit: I have looked at CRC generation code and it should work ok. I wonder if there is a timing error, which would corrupt data. Did you check if data read from emulator is corrupted ?

…

On Thu, Jun 29, 2023, 16:09 Acemi Elektron ***@***.***> wrote: Thanks, since I don't have relevant hardware I appreciate your comments. On Wed, Jun 28, 2023, 18:16 Arco van Geest ***@***.***> wrote: > I tested it for the single sided and most of the data looks OK. > (In my fork/branch opus1) > I see quite a lot crc errors but that could be my breadboard. > > I used fddemu-> greaseweasle (scp) -> HxCfloppyemulator track analyzer. > > — > Reply to this email directly, view it on GitHub > <#29 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAM2CIRGPWJJ74MWUSPH6OLXNRDDTANCNFSM6AAAAAAZUUHTIQ> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

[gnulnulf]

It works in the ZX spectrum. I tried several 180k and 720k(18s) images. I guess the real hardware is more flexible regarding to timing.

[acemielektron]

Thanks for letting me know. I haven't found anything wrong in CRC code. Just that, it has been so long since I've written it, I have forgotten about my 256byte sector hack.

…

On Wed, Jul 26, 2023, 18:49 Arco van Geest ***@***.***> wrote: It works in the ZX spectrum. I tried several 180k and 720k(18s) images. I guess the real hardware is more flexible regarding to timing. — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAM2CIVJT35PA6PYZOF3DZ3XSE4CDANCNFSM6AAAAAAZUUHTIQ> . You are receiving this because you commented.Message ID: ***@***.***>