FPGA Intellectual Property
PCI Express*, Networking and Connectivity, Memory Interfaces, DSP IP, and Video IP
Announcements
Intel Support hours are Monday-Fridays, 8am-5pm PST, except Holidays. Thanks to our community members who provide support during our down time or before we get to your questions. We appreciate you!

Need Forum Guidance? Click here
Search our FPGA Knowledge Articles here.
5884 Discussions

For the life of me, I cannot find the document that describes byte-write limitations in Arria 10 DDR3 hard ip emif. I'm looking for the table that describes how the DM lines can and cannot be grouped in a x64 interface. Thank you.

TTewalt
Beginner
481 Views
 
0 Kudos
3 Replies
NurAida_A_Intel
Employee
88 Views

Hi Sir,

 

Unfortunately, we don’t have the descriptions about byte-write limitations in Arria 10 DDR3 IP and I apologize for the inconvenience caused.

 

 In general, one data mask (DM) pin exists per DQS group. Below is the example for x8 DDR3 interface.

 

emifDM.PNG

 

So, for x64 interface, you will have total of 8 DM pins/bits. DM needs to be a differential pin-pair with a DQ pin due to the FPGA architecture. This pinout requirement is documented in the EMIF pinout guidelines. In the EMIF Handbook Volume 2, chapter 1.2.1 on page 40, it states :

"13.Ensure that DM/BWS pins are paired with a write data pin by placing one in an I/O pin and another in the pairing pin for that I/O pin. It is recommended—though not required—that you follow the same rule for DBI pins, so that at a later date you have the freedom to repurpose the pin as DM." => https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/hb/external-memory/emi_plan...

 

I sincerely hope this helps.

 

Thanks

 

Regards,

NAli1

TTewalt
Beginner
88 Views

My mistake... the question I had is Avalon related, not hard memory controller. I was looking for the following:

 

-begin

When more than one bit of the byteenable

signal is asserted, all asserted lanes are adjacent.

The number of adjacent lines must be a power

of 2. The specified bytes must be aligned on an

address boundary for the size of the data. For

example, the following values are legal for a 32-

bit slave:

• 1111 writes full 32 bits

• 0011 writes lower 2 bytes

• 1100 writes upper 2 bytes

• 0001 writes byte 0 only

• 0010 writes byte 1 only

• 0100 writes byte 2 only

• 1000 writes byte 3 only

-end

 

My Avalon interface is 256-bits wide (32 byte enables) and I was looking for the rules on how to use them correctly.

 

Thanks for replying,

Tim

NurAida_A_Intel
Employee
88 Views

Hi Sir,

 

Basically the concept is the same for 256 bits. If you need to write full data the set all the byte enable to '1' . It depends on which data you want to write. I demonstrate it in below table for example.

 

byteenablee.PNG

Thanks.

 

Regards,

NAli1

Reply