I don't think ESDI is possible with the beaglebone. Data rate is 20 MHz or
so which you could do with a SPI port but there were other signals such as
sector start that needed to be accuratly generated relative to the data
stream. I couldn't figure out any way to do that with beaglebone. Details are
fuzzy now since I looked at it 9 years ago when I started this project. Didn't
think it had been that long. Time flies when your involved in too many things.
PRU isn't fast enough to deal with 20 MHz data without using SPI port.
On Mon, Jul 10, 2023 at 10:13:47AM -0700, e2k wrote:
> So, the RLL should work, it is "just" a matter of the right software.
> Looking at ESDI, it also has the clock signal on the connectors, drivers
> are faster, but it is similar/upgrade to the ST506 interface?
> So one could upgrade the existing HW by few signals and also support ESDI?
> Am I completely wrong, or too naďve?
>
> Cheers
>
> On Monday, 10 July 2023 at 12:21:49 UTC-4
a...@bitsavers.org wrote:
>
> > On 7/10/23 8:02 AM, e2k wrote:
> > > Could it work for RLL and ESDI too?
> > > I see that there were some experiments with RLL, and once ESDI got
> > mentioned, ...
> >
> > I have samples of RLL and MFM encoding here if someone wants to look at
> > writing an RLL decoder
> > One of the problems is there is little documentation on how various
> > chipsets did RLL encoding
> >
http://bitsavers.org/projects/hd_samples
> >
> > ESDI drives use a different physical interface so the existing board
> > cannot work with 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 on the web visit
https://groups.google.com/d/msgid/mfm-discuss/a879f3db-8695-461c-b832-ba697743b953n%40googlegroups.com.