How use altera_avalon_fifi_xxx with a .cpp file ? - Intel Community

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++

How use altera_avalon_fifi_xxx with a .cpp file ?

1,006 Views

Hi,

I try to use altera_avalon_fifo_init() function in .cpp file extension.

The compilation is OK but the linker does't find the function defined in bsp (in library libhal_bsp.a). The error is :

c:\dev\e111\fpga\fit\software\test06/other1.cpp:9: undefined reference to `altera_avalon_fifo_init(unsigned long, unsigned long, unsigned long, unsigned long)'

But, when I rename the file with .c extension, all is ok.

Is it possible to use altera_avalon_fifo_init() (or any functions in BSP) into .cpp file ?

I use Eclipse Indigo. My project is created with "Nios II Application and BSP from Template"

Best regards

Eric

Link Copied

2 Replies

320 Views

I remember that if you define a function (i.e. testcpp() ) in a cpp file, you must declare it with the extern "C" directive in order to call it from a .c files.

extern "C" int testcpp (int n);

int testcpp (int n)

{

/* function body */

}

I think you must use something similar for calling .c functions from .cpp source files.

Copy link

320 Views

Hi Cris72,

Thanks a lot. Now all is OK.

Best regards

Eric

Copy link

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). 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.