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++
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.
12748 Discussions

How to test the Avalon MM interface in C?

Altera_Forum
Honored Contributor II
‎11-26-2011 11:04 PM
1,323 Views

Hello, 

 

I have written a program in VHDL which is compatible with the Avalon MM slave interface and i have generated it in SOPC-builder. 

 

I would like to write a small test program in C to see if it works as it should but I don't know how to communicate with it (how to write and read from it). Should I use IOWR and IORD in some kind of way or do someone have a better suggestion? I am kind of new with this so I would really appreciate an answer.
0 Kudos

Link Copied

2 Replies
Altera_Forum
Honored Contributor II
‎11-28-2011 08:42 AM
574 Views

Yes, just use the IORD and IOWR macros in a software uploaded to a Nios CPU to access your component. When generating the BSP you should get a system.h file that contains the base address of your component. 

Another alternative if you want to test it from your PC without using a Nios CPU is the system console tool.
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎11-29-2011 10:43 PM
574 Views

Thank you for your answer!

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.