[En-Nut-Discussion] Nut/OS configurator Floating point activation leads to compiler error (.elf file)

Harald Kipp harald.kipp at egnite.de
Mon Jul 30 12:59:39 CEST 2012


Hi Philipp,

On 29.07.2012 17:40, Philipp Drey wrote:

> I'm working with an EtherNut 2.1B board. As in my program code floating
> point operations are needed, I activated  floating point in the Nut/OS
> configurator, like discribed in the NutWiki. Afte compiling with the new
> config file, I get an error (I think while building the .elf file, or
> somewhere after line 33).

First of all: You do not need to enable this feature in the Configurator to use floating points:

http://www.ethernut.de/en/documents/ntn-4_floats.html

It is only required to read and write floats via stdio.

>   15.
> 
>       NutTracker.c: In function 'ProcessRequests':
> 
>   16.
> 
>       NutTracker.c:232: warning: implicit declaration of function 'NutSleep'
> 
>   17.
> 
>       NutTracker.c:233: warning: implicit declaration of function 'NutReset'
> 
>   18.
> 
>       NutTracker.c:287:4: warning: "/*" within comment
> 
>   19.
> 
>       NutTracker.c:308: warning: implicit declaration of function 'ScanAtXY'
> 
>   20.
> 
>       NutTracker.c:312: warning: implicit declaration of function 'tracker'
> 
>   21.
> 
>       NutTracker.c:166: warning: unused variable 'i'
> 
>   22.
> 
>       NutTracker.c:165: warning: unused variable 'sinus'
> 
>   23.
> 
>       NutTracker.c:164: warning: unused variable 'kR'
> 
>   24.
> 
>       NutTracker.c:162: warning: unused variable 'z_rad'
> 
>   25.
> 
>       NutTracker.c: At top level:
> 
>   26.
> 
>       NutTracker.c:332: warning: conflicting types for 'ScanAtXY'
> 
>   27.
> 
>       NutTracker.c:308: warning: previous implicit declaration of 'ScanAtXY' was here
> 
>   28.
> 
>       NutTracker.c:389: warning: conflicting types for 'tracker'
> 
>   29.
> 
>       NutTracker.c:312: warning: previous implicit declaration of 'tracker' was here
> 
>   30.
> 
>       NutTracker.c: In function 'NutAppMain':
> 
>   31.
> 
>       NutTracker.c:479: warning: implicit declaration of function 'fdevopen'
> 
>   32.
> 
>       NutTracker.c:502: warning: implicit declaration of function 'NutDhcpIfConfig'

Before looking any further, you should fix these warning first.


 
>       c:/programme/winavr/bin/../lib/gcc/avr/4.3.3/../../../../avr/lib/avr51\libc.a(fp
> 
>   38.
> 
>       _powsodd.o): In function `__fp_powsodd':
> 
>   39.
> 
>       (.text.avr-libc.fplib+0x10): relocation truncated to fit: R_AVR_13_PCREL against
> 
>   40.
> 
>        symbol `__mulsf3' defined in .text section in c:/programme/winavr/bin/../lib/gc
> 
>   41.
> 
>       c/avr/4.3.3/avr51\libgcc.a(_mul_sf.o)
> 
>   42.
> 
>       c:/programme/winavr/bin/../lib/gcc/avr/4.3.3/../../../../avr/lib/avr51\libc.a(fp
> 
>   43.
> 
>       _powsodd.o): In function `__fp_powsodd':
> 
>   44.
> 
>       (.text.avr-libc.fplib+0x20): relocation truncated to fit: R_AVR_13_PCREL against
> 
>   45.
> 
>        symbol `__mulsf3' defined in .text section in c:/programme/winavr/bin/../lib/gc
> 
>   46.
> 
>       c/avr/4.3.3/avr51\libgcc.a(_mul_sf.o)
> 

Looks to me like an avr-libc problem. Did you mix up libs/compilers? Anyway, as long as we have these warnings above, we may speculate endlessly.

If the problem still exists after fixing this, create a simple example, similar to app/uarts.

Best regards,

Harald






More information about the En-Nut-Discussion mailing list