Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17267 Discussions

Qsys and multiple slave SPI

Altera_Forum
Honored Contributor II
‎07-27-2011 06:57 PM
1,083 Views

I am trying to move a design from SOPC to QSYS mainly to allow software to read which device in the FPGA is interrupting through PCIe.  

 

I have one SPI master that has two slaves, that isn't moving over because QSYS isn't generating SSn as a vector. In Qsys the spi core is set to 2 slaves, but the QSYS system inspector shows the SSn as being 1 bit wide. When I look in the verilog generated for the SPI core is it two bits wide, but the verilog generated for the system is one bit wide. 

 

Is this fixed in SP1, did I do something wrong, or do I tell software they are stuck with prioritized interrupts and all the reads? 

 

Rob
0 Kudos

Link Copied

2 Replies
Altera_Forum
Honored Contributor II
‎07-27-2011 07:51 PM
381 Views

This is a known bug and it has not been fixed yet. The SPI core itself is generated correctly but when it gets wired up to the top level it is only done for a single bit so for now the only workaround is to hack up the top level file manually to make sure the other bits get connected.

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎07-27-2011 08:33 PM
381 Views

Well that sucks, but what it is what I suspected I would have to do. It does leave room for error if something changes. 

 

Thanks, 

 

Rob
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.