Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
12603 Discussions

Why qsys doesn't report error when Avalon-MM data width mismatch?

Altera_Forum
Honored Contributor II
1,881 Views

I have a design which I want to connect a DDR3 controller (DDR3 SDRAM Controller with UniPHY) to an Avalon-MM Pipeline Bridge, then the bridge connects with the nios II. (Nios <-----> Bridge <-----> DDR3) 

 

After I configure the DDR3 controller, the data width in the avalon MM interface is 256. But the bridge data width I set is 32. It is obvious their data width doesn't match, but the qsys still allows me to connect them and after I connect them, there is no error appear to say their width is mismatch. I am confused why? Why the bridge can accept the slave which has the different data width? 

 

Thanks in advance.
0 Kudos
3 Replies
Altera_Forum
Honored Contributor II
622 Views

Read this document to gain a better understanding of what you are telling Qsys to do: 

http://www.altera.com/literature/hb/qts/qsys_interconnect.pdf 

 

Adapting mismatched widths is a feature.
0 Kudos
Altera_Forum
Honored Contributor II
622 Views

 

--- Quote Start ---  

Read this document to gain a better understanding of what you are telling Qsys to do: 

http://www.altera.com/literature/hb/qts/qsys_interconnect.pdf 

 

Adapting mismatched widths is a feature. 

--- Quote End ---  

 

 

Thanks. I did skim the file quickly but I didn't notice it. I will read it carefully again.
0 Kudos
Altera_Forum
Honored Contributor II
622 Views

One can suspect that, behind the scenes, QSYS will connect the lower order address bits of the 32 bit wide interface to the byte enable signals on the 256 bit interface. However, it might be a good idea to look at the generated files and verify what is actually occurring.

0 Kudos
Reply