Floating point exception on nrf9160

[Danny Zadok]

Hi,

 I have a problem with floating point types on nrf9160.

I get an exception when I get to a simple floating point assinment:

 void f(int i)

{

     float x;

     x = (float)i;

}

The disasemmbly is: vldr s15, r0

here is my prj.conf

CONFIG_PRINTK=y
CONFIG_HEAP_MEM_POOL_SIZE=256
CONFIG_ASSERT=y
CONFIG_GPIO=y
CONFIG_ADC_NRFX_SAADC=y
CONFIG_ADC=y
CONFIG_SERIAL=y
CONFIG_STDOUT_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_ADC_ASYNC=y
CONFIG_TRACING=y
CONFIG_SEGGER_SYSTEMVIEW=y
CONFIG_SPI=y
CONFIG_CMSIS_DSP=y
CONFIG_NEWLIB_LIBC=y
CONFIG_FPU=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_CMSIS_DSP_BASICMATH=y
CONFIG_CMSIS_DSP_TRANSFORM=y
CONFIG_CMSIS_DSP_STATISTICS=y
CONFIG_CMSIS_DSP_COMPLEXMATH=y
CONFIG_CMSIS_DSP_SUPPORT=y

I've also added 

CONFIG_FLOAT=y

but it did not help.

Would you please help?

Thanks

Danny

[Danny Zadok]

Additional information:

If I disable the compiler optimizations in prj.conf by

CONFIG_NO_OPTIMIZATIONS=y

It stops happening.

But I need the optimizations.

Does any one knows why GCC optimizations causes exceptions?

Thanks

Danny

[Vidar Berg]

Hi Danny,

Are you doing float operations from multiple threads by any chance? The help text for CONFIG_FPU says that:

"When this option is enabled, by default, threads may use the floating point registers only in an exclusive manner, and this usually means that only one thread may perform floating point operations.

If it is necessary for multiple threads to perform concurrent floating point operations, the “FPU register sharing” option must be enabled to preserve the floating point registers across context switches."

Please try to build with CONFIG_FPU_SHARING=y and see if it makes any difference.

Best regards,

Vidar

[Danny Zadok]

Hi Vidar,

 No. I do not do floating point operation from multiple threads. Only from one thread.

Besides, I did add this ONFIG_FPU_SHARING=y  config parameter, but it did not help.

The only workaround was to disable the compiler optimizations with CONFIG_NO_OPTIMIZATIONS=y

Danny

[Vidar Berg]

Hi Danny,

Have you enabled the FPU exception handler in your app? In that case, I think I've misunderstood the problem. I thought the float instruction was causing a fault exception at first. Assuming it's indeed a FPU exception, can you read the control register to check what the reason for the exception is (Floating-point Status Control Register)? Most likely it is going to be the IXC bit, which indicate that the result of a FP computation has been rounded. There is a similar thread about this here: https://devzone.nordicsemi.com/f/nordic-q-a/57519/mask-fpu-ixc-exception

Best regards,

Vidar

[Danny Zadok]

Hi Vidar,

 No. I did not  enable the FPU exception handler in my app.

I do I enable/disable it? Please let me know if it is enabled.