Stack Overflow Asset Tracker

I added some code for events of an external device. The external device is configured to Listen and Submit events as other Modules do. When, the generated Hex is burnt in nRF9160DK and tested using LTE LINK Monitor, there are the error / fatal errors as shown in attached log file.

Please, guide how to rectify.   

  

  • Hello, 


    Would you mind providing more information i.e. what specifically did you add/change, and what version of nRF Connect SDK are you running?

    Kind regards,
    Øyvind

  • Hi, the nRF connect is 3.10.0. How may I send the whole project to you to test at at your end.

  • mexco said:
    the nRF connect is 3.10.0

    No, this is the nRF Connect for Desktop is a cross-platform tool framework for assisting development on nRF devices. 

    The nRF Connect SDK is installed either using the Toolchain Manager app in nRF Connect for Desktop, and the version of your nRF Connect SDK is found inside here. Or if you have installed nRF Connect SDK manually, you will need to provide what version you are running. 

    You can use VS Code, opened from Toolchain Manager, to generate support information running nRF Connect: Generate Support Information from the Command Pallette (CRTL+SHIFT+P).

    Kind regards,
    Øyvind

  • I tried using nRF SDK 1.7.1 and 1.9.1 both in SES, but same results.

  • You will need to debug your project using the tool arm-none-eabi-addr2line to translate addresses into file names and line numbers. 

    2022-05-09T05:23:30.233Z DEBUG modem << [00:00:00.278,930] [1;31m<err> os: ***** USAGE FAULT *****[0m
    2022-05-09T05:23:30.242Z DEBUG modem << [00:00:00.284,576] [1;31m<err> os:   Stack overflow (context area not valid)[0m
    2022-05-09T05:23:30.249Z DEBUG modem << [00:00:00.291,870] [1;31m<err> os: r0/a1:  0x0c060050  r1/a2:  0xfb7f97f7  r2/a3:  0x0e009420[0m
    2022-05-09T05:23:30.260Z DEBUG modem << [00:00:00.300,598] [1;31m<err> os: r3/a4:  0x5df7bfff r12/ip:  0x000214ee r14/lr:  0x61000200[0m
    2022-05-09T05:23:30.263Z DEBUG modem << [00:00:00.309,356] [1;31m<err> os:  xpsr:  0x00000000[0m
    2022-05-09T05:23:30.275Z DEBUG modem << [00:00:00.314,636] [1;31m<err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000[0m
    2022-05-09T05:23:30.289Z DEBUG modem << [00:00:00.325,134] [1;31m<err> os: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000[0m
    2022-05-09T05:23:30.294Z DEBUG modem << [00:00:00.335,662] [1;31m<err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000[0m
    2022-05-09T05:23:30.309Z DEBUG modem << [00:00:00.346,160] [1;31m<err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000[0m
    2022-05-09T05:23:30.311Z DEBUG modem << [00:00:00.356,658] [1;31m<err> os: fpscr:  0x01410408[0m
    2022-05-09T05:23:30.324Z DEBUG modem << [00:00:00.361,907] [1;31m<err> os: Faulting instruction address (r15/pc): 0x00000000[0m
    2022-05-09T05:23:30.327Z DEBUG modem << [00:00:00.369,903] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0[0m
    2022-05-09T05:23:30.333Z DEBUG modem << [00:00:00.377,838] [1;31m<err> os: Current thread: 0x2000d2b0 (unknown)[0m

Related