Working with A GPS got Error on SUPL session nrf9160 stack over Flow and nrf9160dk reboot again

[Waqar Ahmed]

Hi
I want to Integrate GPS(with A GPS assistance needed)with AWS iot example. when i start GPS on aws connect event ready .SUPL is initialized successfully and even SUPL socket is created successfully .inside SUPL session function i got error stack overflow and my nrf9160 dk reboot .I am using nRF Connect Sdk 1.5.0

I am using SUPL client library version 0.7.0 download from Nordic provided link and extract to the path  mention in nordic website.

[Håkon Alseth]

Hi,

 

Which thread is located at address 0x20014d30? You should check the .map file to see which thread this is, and adjust the stack size to it. If this is the main stack, you can adjust it with CONFIG_MAIN_STACK_SIZE in prj.conf.

 

Kind regards,

Håkon

[Waqar Ahmed]

i already try to found this thread in .zephyr.map file in my buid directory \ncs\v1.5.0\nrf\samples\nrf9160\aws_iot\build_nrf9160dk_nrf9160ns\zephyr\zephyr.map but i got nothing of this thread type.

i had also increased the CONFIG_MAIN_STACK_SIZE  to double the CONFIG_MAIN_STACK_SIZE=8192 but the issue. remain the same.

I am attaching the zephyr.map 

0412.zephyr.map

[Waqar Ahmed]

i have forwarded you most recent zephyr.map file

[Håkon Alseth]

But, which thread is faulting now? When you recompile and re-flash the addresses will change.

[Waqar Ahmed]

The thread address remain same. Even i complied the code. Dozen of time

[Waqar Ahmed]

0x20014d30

[Håkon Alseth]

Could you please post the full fault print that corresponds to the latest .map file?

There is no thread on this RAM address, it's the RAM for the nrf9160_gps driver.

 

What you can also do is to try to resolve the faulting flash mapped addresses (from 0x0 to 0x10 0000) using arm-none-eabi-addr2line:

arm-none-eabi-addr2line -e build-folder/zephyr/zephyr.elf 0xFAULTING_ADDRESS

 

Kind regards,

Håkon

[Waqar Ahmed]

2021-11-05T14_31_23.396Z-log.txt