1 reply to this topic

[Tobias Lange]

Hi,

I'm using a co_uint50 in the software part of my project.
As there was no problem in compiling the software simulation and generating the hardware I wanted to validate my design in ModelSim.
When I want to create the Hardware Simulation Executable I get the following error message:


make[1]: Entering directory `/cygdrive/o/projects/impulse/fft/smd'
"C:/Impulse/CoDeveloper3/MinGW\bin\gcc" -g -O -I"C:/Impulse/CoDeveloper3/StageMaster\include" -o sw/fft_sw.o -c sw/fft_sw.c
sw/fft_sw.c: In function `Producer':
sw/fft_sw.c:29: error: `co_uint50' undeclared (first use in this function)
sw/fft_sw.c:29: error: (Each undeclared identifier is reported only oncesw/fft_sw.c:29: error: for each function it appears in.)
sw/fft_sw.c:29: error: parse error before "testValue1"
sw/fft_sw.c:51: error: `testValue1' undeclared (first use in this function)
sw/fft_sw.c: In function `Consumer':
sw/fft_sw.c:64: error: `co_uint50' undeclared (first use in this function)
sw/fft_sw.c:64: error: parse error before "testValue_buf"
sw/fft_sw.c:80: error: `testValue_buf' undeclared (first use in this function)
make[1]: *** [sw/fft_sw.o] Error 1
make[1]: Leaving directory `/cygdrive/o/projects/impulse/fft/smd'
make: *** [smd/fft.exe] Error 2

======== Build of target 'build_smd' complete ========


There is no problem when using co_uint32 or co_uint64. It seems that datatypes from co_uint33 to co_uint63 don't work.
The "co_math.h" file is included.
You will get the same error message when trying to generate the Hardware Simulation Executable for the crc_40bit example.
In this case a co_uint40 is used in the software testbench.

Thanks in advance,
Tobias

[etrexel]

Hi,
The Hardware Simulation Executable is using a different co_math.h that is not up to date with the one used for desktop software simulation and hardware generation. Please try copying the 'co_math.h' from 'C:\Impulse\CoDeveloper3\Include'
to 'C:\Impulse\CoDeveloper3\StageMaster\include' to bring them into sync.

Best Regards,
Ed