View Single Post
Old 23 February 2018, 14:04   #819
ross
Defendit numerus
 
ross's Avatar
 
Join Date: Mar 2017
Location: Crossing the Rubicon
Age: 53
Posts: 4,476
Quote:
Originally Posted by kaffer View Post
https://github.com/keirf/FlashFloppy/issues/58

Quick read of the trackloader indicates a 33ms max latency from read-start to sync-found. This is in addition to a 15ms settle delay if any head-step occurred.

Worst-case to find a sync should be sector-latency + track-gap = (544*16 + 4256) * 2us ~= 26ms.

So there should be plenty to play with here. I will debug on real hardware next week.
EDIT: 33ms was an arbitrary decision, but I had made calculations similar to yours and I had abounded considering also
the possibility of hacked floppies for long track writing or "naturally" very slow.
So yes, is really plenty of time and if a device (drive or floppy) do not sync-respond after this time is sure bad.
Anyway I was really generous in terms of the number of retry attempts (see my code)


For all timing in loader you can check:
http://eab.abime.net/showthread.php?p=1183710

Ziriax loader is a modified and adapted version, but technically it's the same.

Last edited by ross; 23 February 2018 at 15:17.
ross is offline  
 
Page generated in 0.04477 seconds with 11 queries