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]

"Stack overflow" is a keyword here. Try using addr2line using LR in order to find out what caused the crash. It looks to be related to something in the time_thread in date_time_core.c.

For 0x41000000/lr, type the following into the command line:

arm-none-eabi-addr2line -e <path to build\zephyr\zephyr.elf> 0x41000000

This will return a the line in the code related to the crash. Looking it up might give you some hints regarding the crash. This line would also be a good start for setting a break point.

[bc_metco]

what's the command line you are referring to? Do you mean the dev kit? No, I got the message from the UART port which is on our customized board build up with nRF9160 chipset. We don't have the resource to hook our customized board and debug it on the fly. I was hoping you, Nordic team, could replicate the error and updated the example code and I can test it from there. 

[helsing]

You could read out your revision by either AT command: AT%HWVERSION or look on the nRF9160 SIP for marking "B1".

"B1" -> Revision 2

"B0" -> Revision 1 

Only revision 2 is supported by modem firmware v1.3.2.

[bc_metco]

Here is the SiP, HW version should be B1. I will upload CMW500 configuration file later.

[helsing]

Thank you for confirming the SIP version. It would be great if you could also comment on the DK HW version. This can be found on the back of the DK there should be a sticker, below 'PCA10090'. The version could be for example '1.0.0'.

Please also let us know if you have tried increasing DATE_TIME_THREAD_STACK_SIZE.

[bc_metco]

It seems the solution is to increase 

helsing said:

DATE_TIME_THREAD_STACK_SIZE

is working. 

The 2nd screenshot shows the HW version

I try to upload the configuration file of CMW500. but the ".dfl" file is block by the system. I change the extension to ".jpg" remember to change it back after you downloaded it.

[helsing]

Great to hear that it is now working.

I am not able to see any attachment. Would you be able to resend the file? Is there still any need for us to reproduce the issue, or are you happy with increasing the stack size?