lte_lc_connect() function error

[vchhabra]

Calling the lte_lc_connect() function eventually leads to the code breaking on:

fault_s.S line 104

#elif defined(CONFIG_ARMV7_M_ARMV8_M_MAINLINE)
    /* force unlock interrupts */
    eors.n r0, r0
    msr BASEPRI, r0

It never connects to the LTE tower. I am not using the nrf9160 board but a custom board config.

My question would be if there are any config settings which might cause the LTE to not connect?

[Didrik Rokhaug]

Hi.

Do you know what exactly causes your device to hard-fault?

Do you see the same behavior if you are running the same application on a DK?

Or one of our samples on your device?

Are you building your application as non-secure?

Best regards,

Didrik

[vchhabra]

Not sure if it is a hard fault. In case of multiple polling threads the other threads still work. But whenever I call lte_lc_connect() this Happens

I have been testing on a DK.

I dont see the problem when I use other projects I made for testing.

Yes, the application is non secure.

EDIT: By board I mean the files located at zephyr/boards/arm/nrf9160_pca10090 

We have a custom package for our eval board which we are using here.

[Didrik Rokhaug]

Have you initialized the lte_lc  library (lte_lc_init()) and the bsdlib (bsdlib_init()) before calling lte_lc_connect()?

Have you checked that the bsdlib and lte_lc libraries did not return any errors when they were initialized?

Are you able to find the place that leads you to the fault handler, either by stepping through the code with a debugger or by adding debug prints?

[vchhabra]

The Issue was something to do with SPI0 and UART0 both being active and used at the same time in the project. When the code reached the connect function it probably could not resolve it and threw the fault.