nRF9160 modem_shell example code crashes when connecting to CMW500

[bc_metco]

 SDK1.9.1 with example of modem_shell. 

modem fw is up to date, version 1.3.2

the fw crashes as soon as CMW500 trying to establish a connection.

[helsing]

Here is something else to try:

The stack overflow happens inside the time_tread. Could you try to increase the stack size for this thread and see if it helps? The stack size is defined by CONFIG_DATE_TIME_THREAD_STACK_SIZE and the default value is '1152'. Try adding this CONFIG to your prj.conf file and increase the stack size. Try for example to double the size to '2304' to begin with. Does the device still crash?

Documentation, for reference:

• https://github.com/nrfconnect/sdk-nrf/blob/v1.9.1/lib/date_time/date_time_core.c#L104
  
• https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/kconfig/CONFIG_DATE_TIME_THREAD_STACK_SIZE.html#std-kconfig-CONFIG_DATE_TIME_THREAD_STACK_SIZE

[helsing]

You could also try to add

CONFIG_DATE_TIME_THREAD_STACK_SIZE=2048

to your prj.conf file.

[bc_metco]

the attachment is in red circle. as I mentioned, this web page portal doesn't allow me upload the file (.dfl).

[helsing]

There is no attachment visible on my side. Could you perhaps try to rename the file to '.txt', and then try upload the file again?

In any case, do you need us to reproduce this, or do you consider the problem solved?

[bc_metco]

SaveFile000.txt

Here is the setting file.

can you reproduce this issue and make sure that increase stack size isn't a quick dirty fix?

[helsing]

Thank you for submitting the file.

Increasing the stack size is usually not to dramatic. However, we will now try to reproduce this. 

[helsing]

Hi Bo,

Regarding the stack size, this issue was identified and fixed in later versions of nRF Connect SDK: https://github.com/nrfconnect/sdk-nrf/commit/da8d172763815205ac279dff9e91177cd05945ae

The recommended new stack size is '1280'.

Regarding this:

It looks like you need to enter an DNS. You could enter something like "8.8.8.8" or "1.1.1.1" instead of "0.0.0.0".

If this works we probably do not need to reproduce the issue.