Realization MFM de/en-Coder via MAXII

Reinhard,

just had a look at your web page, good old days :-) i personaly started with a PET 2001 i guess it was 1979 ...

first MaxII is a CPLD not a FPGA

i could give you some help, prefered in our native laguage :-) via PM

Do you have more information about the MFM ? a single ton or multiple tones at the same time ?

implementing ram rom is easy, depending upon the HDL language you use.

Grüße aus der Südpfalz

Michael

Hallo Michael,

I will send you a PM and many thanks for the offered help.

Reinhard

P.S. Can't reach you via PM/E-Mail, sorry

Anyway, the MFM ( Magnetic Recording system with Peak shift compensation) architecture ist based on US Patent Nr. 4,553,178. I can't include a link here, but on my hompage , chapter 1.2 is a link included to the engineering drawing. On page 23 , You will find the MFM ENCODER and on page 24 the MFM DECODER.. The challenge is to rebuild this part of the circuit diagram in MAXII architecture.

Sorry Reinhard,

PM was closed but should be open now ... give it a try, it works some else mailed me ...

had a quick look at page 23

the lower part seems pretty straight foreward

a shift register which taps are the adr of that prom.

the upper part is good old fashioned "digital" logic :-)

the 50ns delay with taps each 5 nsec is some kind of shift register with a 5nsec clock what means 200MHz and that is fast ... if a MaxII can handle that ... were is the datasheet ..

--- Quote Start ---

MaxII is a CPLD not a FPGA

--- Quote End ---

By it's technology, MAX II is a simple FPGA with built-in configuration flash. The logic elements are SRAM based in contrast to a EEPROM based CPLD cells. You'll also notice, that MAX II uses the Quartus FPGA related tools, while MAX 3000 and 700 are using a different compiler/fitter.

But anyway, it's capable of performing at 200 MHz clock frequency. As a disadvantage, it hasn't any PLL or clock multiplier, so you must supply a 200 MHz clock input (or at least 100 MHz when using both edges). A full featered FPGA with PLL could use a convenient 10 or 20 MHz clock.

MAX II has no internal RAM or ROM, but 32x8 can be made in MAX II logic cells.

Hello and many thank for the upgrade infos

@ MSchmitt : I have no datasheet, only the old engineering drawings and I only know the logic was based on 74S... chips, 0.4ns.

@ FvM : No good news for me. I am using the MAXII-MICRO.Kit-Board

because in my opinion it should be easy for use for beginners ( included USB blaster), but runs only at 50MHz and I see no change for upgrading to 200MHz. ( soldering ?) At least, I also have to implement a 10240 byte track-holding-FIFO ... and MAXII has no internal RAM?

Do you have any recommendations which development board would fulfilling this request ? Regards, Reinhard

Well if MaxII runs @ 200MHz what i haven't tried yet there are some other points to consider. if the design runs with 200MHz and 8.2MHz then some kind of clock crossing must be taken into account. but it is also possible to run the design at 200MHz and have some kind of clock enable that has 1 200MHz clock pulse every 8.2MHz (too keep the design fully synchronous)

another question what needs to be implemented inside the fpga except page 23 ?

you talked about 10240 byte fifo that could be implemented with 20 M4K memory blocks cyclone II fpga offers.

as you are new to the quartus world and fpga as well, did you had a look at the schematic entry possabilities quartus offers ? if you look at your page 23 there are some 7474 at the bottom, you can also draw such a logic with quartus. this tool is capable to handle hdl and schematic entry in a mixed combination.

i had converted a couple of old schematics (like some arcade classics) into pure verilog designs and sometimes the asyncron design to fully synchrnous conversion was a heavy task, but what worries me in your design are the two signal delay lines one 50ns with a tap each 5ns and the other one i have seen with 100ns delay and a tap each 10ns. they can be seen as shift registers with a high clock rate.

so what amount of logic do you want to transfer to a fpga and what kind of help could be give to you ?

Reinhard,

just to give you an example how the conversion from your schematic to verilog could look like here are some few code snippets ...

--- Quote Start ---

--- Quote End ---

Lets starts with the toggle DFF from the lower left corner

--- Quote Start ---

reg E128;

always @ ( posedge Clk_8_2Mhz )

E128 <= ~E128;

wire RLVA_SYS_1H;

wire RLVA_SYS_0H;

assign RLVA_SYS_1H = E128;

assign RLVA_SYS_0H = ~E128;

--- Quote End ---

now the shift register E117

--- Quote Start ---

// The shift register from Page 23 at the bottom;

reg [4:0] E117;

always @ ( posedge Clk_8_2Mhz or negedge RLV9_INIT_0L )

if ( !RLV9_INIT_0L )

E117 <= 4'd0;

else

E117[4:0] <= { E117[3:0] , RLV_MUX_DATA_H };

--- Quote End ---

now the ROM E120 82S123

implemented as priority encoded wires .... well at 8.2MHz i don't worry about timing here

this could also be implemented as a memory and initialised from a file

but strictly implemented from original schematic without 1 clock delay a register would give

it is done this way ... without propper values

--- Quote Start ---

wire [4:0] PROM_E120;

assign PROM_E120 = ( E117 === 5'H00 ) ? 5'b00000 :

( E117 === 5'H01 ) ? 5'b00000 :

( E117 === 5'H02 ) ? 5'b00000 :

( E117 === 5'H03 ) ? 5'b00000 :

( E117 === 5'H04 ) ? 5'b00000 :

( E117 === 5'H05 ) ? 5'b00000 :

( E117 === 5'H06 ) ? 5'b00000 :

( E117 === 5'H07 ) ? 5'b00000 :

( E117 === 5'H08 ) ? 5'b00000 :

( E117 === 5'H09 ) ? 5'b00000 :

( E117 === 5'H0A ) ? 5'b00000 :

( E117 === 5'H0B ) ? 5'b00000 :

( E117 === 5'H0C ) ? 5'b00000 :

( E117 === 5'H0D ) ? 5'b00000 :

( E117 === 5'H0E ) ? 5'b00000 :

( E117 === 5'H0F ) ? 5'b00000 :

( E117 === 5'H10 ) ? 5'b00000 :

( E117 === 5'H11 ) ? 5'b00000 :

( E117 === 5'H12 ) ? 5'b00000 :

( E117 === 5'H13 ) ? 5'b00000 :

( E117 === 5'H14 ) ? 5'b00000 :

( E117 === 5'H15 ) ? 5'b00000 :

( E117 === 5'H16 ) ? 5'b00000 :

( E117 === 5'H17 ) ? 5'b00000 :

( E117 === 5'H18 ) ? 5'b00000 :

( E117 === 5'H19 ) ? 5'b00000 :

( E117 === 5'H1A ) ? 5'b00000 :

( E117 === 5'H1B ) ? 5'b00000 :

( E117 === 5'H1C ) ? 5'b00000 :

( E117 === 5'H1D ) ? 5'b00000 :

( E117 === 5'H1E ) ? 5'b00000 :

5'b00000 ;

// now we assign the output bits of the PROM the names as used by the schematics

wire RLVA_B0_H;

wire RLVA_B1_H;

wire RLVA_B2_H;

wire RLVA_B3_H;

wire RLVA_B4_H;

assign RLVA_B0_H = PROM_E120[0];

assign RLVA_B1_H = PROM_E120[1];

assign RLVA_B2_H = PROM_E120[2];

assign RLVA_B3_H = PROM_E120[3];

assign RLVA_B4_H = PROM_E120[4];

--- Quote End ---

last but not least the counter at the lower right

--- Quote Start ---

reg [3:0] E125;

always @ ( posedge Clk_8_2Mhz or negedge RLV9_INIT_0L )

if ( !RLV9_INIT_0L )

// async nCLR

E125 <= 4'd0;

else

if ( RLVA_SYS_0H ^ RLVA_R0_H )

// nLOAD

E125 <= { RLVA_B4_H , RLVA_B3_H , RLVA_B2_H , RLVA_B0_H };

else

// normal count operation

E125 <= E125 + 4'd1;

// again assign output bits the name of used by schematics

wire RLVA_R0_H;

wire RLVA_R1_H;

wire RLVA_R2_H;

wire RLVA_R3_H;

assign RLVA_R0_H = E125[0];

assign RLVA_R1_H = E125[1];

assign RLVA_R2_H = E125[2];

assign RLVA_R3_H = E125[3];

--- Quote End ---

Hello Reinhard,

Need for FIFO memory is a sufficient reason to use a full featured FPGA for the design. I would recommend Cyclone III, Terasic DE0 is a possible hardware platform.

Hello,

many many thanks for all your effort and information you provided !

Based on your good explanations and examples, I think , this is feasible for me. Concering the other issues, I have no plan yet. Speed up the MAXII or use another FPGA development board. Best regards, Reinhard

Reinhard,

as FvM already said i would also go for a FPGA like Cyclone III instead of a MaxII.

Cyclone FPGA have some PLLs you can use to create required clocks out of other clocks. the created clocks can be faster and / or slower than the input clock. also they offer on chip memories you can use for the fifos and these memories run as fast as the fmax of the design can be in that FPGA. also you have enough resources for clock crossing and other stuff. the designs i had done with cyclone II and cyclone III (same sources) were faster compiled for the cyclone III target and had higher fmax. also the cyclone II has only the EP2C20Q240 as a device that is "hand solderable" and the cyclone III family offers a bigger range of devices were you can starte with a smal device and if needed and you have obeyed the migration rules, replace by a bigger device. the smalest "hand solderable" footprint is a TQFP144 if you would go for your own target pcb. there are some dev kits out there like the bemicro or the ebv dev kit that have usb blaster like jtag support on board and some user io pins. both with a cyclone III fpga. do you know how many IOs you will need ?