LWM2M Carrier Library and date_time library hard fault

Gotcha, good to know it’s just an issue on my end. I’ll reproduce in a little bit and get back to you with a better log. Thanks for your help

Sounds good. Make sure to add CONFIG_DATE_TIME=y in prj.conf and add #include <date_time.h>

[00:01:15.316,497] <err> os: Exception occurred in Secure State
[00:01:15.316,497] <err> os: ***** HARD FAULT *****
[00:01:15.316,497] <err> os: Fault escalation (see below)
[00:01:15.316,497] <err> os: ***** BUS FAULT *****
[00:01:15.316,528] <err> os: Precise data bus error
[00:01:15.316,528] <err> os: BFAR Address: 0x50008158
[00:01:15.316,528] <err> os: r0/a1: 0x2002a4a0 r1/a2: 0x00000000 r2/a3: 0x80850000
[00:01:15.316,528] <err> os: r3/a4: 0x0005ca5b r12/ip: 0x00036d04 r14/lr: 0x61060000
[00:01:15.316,558] <err> os: xpsr: 0x40028000
[00:01:15.316,558] <err> os: s[ 0]: 0x00000000 s[ 1]: 0x00000000 s[ 2]: 0x00000000 s[ 3]: 0x00000000
[00:01:15.316,589] <err> os: s[ 4]: 0x00000000 s[ 5]: 0x00000000 s[ 6]: 0x00000000 s[ 7]: 0xffffffff
[00:01:15.316,589] <err> os: s[ 8]: 0x00000000 s[ 9]: 0x00000003 s[10]: 0x00000000 s[11]: 0x00000000
[00:01:15.316,589] <err> os: s[12]: 0x00000000 s[13]: 0x00000000 s[14]: 0x00000000 s[15]: 0x00000000
[00:01:15.316,589] <err> os: fpscr: 0x00000000
[00:01:15.316,589] <err> os: Faulting instruction address (r15/pc): 0x00000000
[00:01:15.316,619] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:01:15.316,619] <err> os: Current thread: 0x200223f8 (time_thread)
[00:01:15.839,660] <err> fatal_error: Resetting system

This is the hard fault. I had put some of my own prints in the date_time library functions to try to trace it down. It seems like this is the critical section:

static void new_date_time_get(void)
{
	int err;

	while (true) {
		k_sem_take(&time_fetch_sem, K_FOREVER);

		LOG_DBG("Updating date time UTC...");
		err = current_time_check();
		if (err == 0) {
			LOG_DBG("Time successfully obtained");
			initial_valid_time = true;
			date_time_notify_event(&evt);
			continue;
		}

		LOG_DBG("Current time not valid");

and is failing after it receives the semaphore from the date_time_update_async function here:

int date_time_update_async(date_time_evt_handler_t evt_handler)
{
	if (evt_handler) {
		app_evt_handler = evt_handler;
	} else if (app_evt_handler == NULL) {
		LOG_DBG("No handler registered");
	}

	k_sem_give(&time_fetch_sem);

	return 0;
}

The relevant variables in prj.conf are:

# Date Time library
CONFIG_DATE_TIME=y
CONFIG_DATE_TIME_NTP=n
CONFIG_DATE_TIME_UPDATE_INTERVAL_SECONDS=0

I tried non-zero values for CONFIG_DATE_TIME_UPDATE_INTERVAL_SECONDS and used to have CONFIG_DATE_TIME_NTP enabled but disabled it to try the other option and the fault occurs in all scenarios. Scratching my head a little bit since this call worked fine before integrating LWM2M Carrier, but it may just simply be a stack overflow? 

Are you able to test with the nRF9160:LwM2M carrier sample on your side? I.e. adding date_time to the sample alone. That worked for me. 

esisk said:

[00:01:15.316,497] <err> os: Exception occurred in Secure State

What board are you building for? seems to be an issue with secure, not non-secure. Can you confirm?

When I get to work today I can test on the bare-bones sample. I always build my project for <custom_board>ns. I can always double check though. Would you mind adding a call to date_time_update_async(handler) in your test? I saw your log say DATE_TIME_NOT_OBTAINED which was before the LWM2M library had connected to the network, but I’d like to see what happens if you call the function I mentioned after the LTE link is ready.