about Merlin Burst Adapter

--- Quote Start ---

Now I'm writing an interface between Avalon bus and a LSI, changing Avalon bus signals(read, write,ect) to LSI control signals. An interface can deal with burst transfer is preferred.

--- Quote End ---

Are you sure you need burst? Does the LSI interface use a start address followed by multiple data phases like a DDR, or can it just accept data on every cycle? If the latter is the case, then the Avalon components can post writes and prefetch reads on every clock cycle, so a burst interface is not required.

Can you post a part number for the LSI device. I'll take a look.

Cheers,

Dave

Thanks for you answer, Dave.

The LSI need many clock cycles to return readdata, and also need many cycles to complete a write transfer.

If the interface doesn't support burst transfer, what'll happen when the Nios starting a burst transfer? The Merlin Burst Adapter will translate burst transfer into individual salve transfers?

regards,

feng

If your LSI (I've NFI what it is - but I assume some serial bus) needs a lot of clocks to perform an action, it may be better to perform the LSI transfer completely asynchronously and have the Avalon master (eg nios) either poll for completion or (if very very slow) take an interrupt.

That way you don't completely stall the nios cpu while your slow LSI transfer takes place, and you'll have complete control of the number of words read/written from the LSI slave in one transfer.

The nios cpu can only do burst transfers for cache line fill/write, but doesn't normally have that enabled because it isn't necessary for internal memory or SDRAM/DDR.

Thanks, dsl.

I implemented the custom component between Avalon master and the LSI synchronously. Did you mean that if the custom component don't support burst transfer, then burst transfers shouldn't happen?

regards,

feng