• State Verified Answer
  • Locked Locked
  • Replies 15 replies
  • Subscribers 25 subscribers
  • Views 372 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289340
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LWM2M Carrier Library and date_time library hard fault

user106788

I'm trying to integrate my application with the LWM2M Carrier library, and experiencing a hard fault when calling date_time_update_async(). This happens even if I call the function after I receive the event LWM2M_CARRIER_EVENT_LTE_READY. Anything obvious I'm missing? 

Parents Reply Children
  • 0 in reply to user77062

    When I get to work today, I’ll recreate it. The fault was not printing to the logs so I’ll have to enable it in prj.conf

  • 0 in reply to user77062

    I tested with running NCS v1.7.0 lwm2m carrier sample, adding date time library. 

    2022-05-20T10:14:39.955Z DEBUG modem << *** Booting Zephyr OS build v2.6.99-ncs1  ***
2022-05-20T10:14:39.958Z DEBUG modem << Flash regionsDomainPermissions
2022-05-20T10:14:39.962Z DEBUG modem << 00 01 0x00000 0x10000 Securerwxl
2022-05-20T10:14:39.965Z DEBUG modem << 02 31 0x10000 0x100000 Non-Securerwxl
2022-05-20T10:14:39.971Z DEBUG modem << Non-secure callable region 0 placed in flash region 1 with size 32.
2022-05-20T10:14:40.022Z DEBUG modem << SRAM regionDomainPermissions
2022-05-20T10:14:40.025Z DEBUG modem << 00 07 0x00000 0x10000 Securerwxl
2022-05-20T10:14:40.029Z DEBUG modem << 08 31 0x10000 0x40000 Non-Securerwxl
2022-05-20T10:14:40.031Z DEBUG modem << PeripheralDomainStatus
2022-05-20T10:14:40.035Z DEBUG modem << 00 NRF_P0               Non-SecureOK
2022-05-20T10:14:40.038Z DEBUG modem << 01 NRF_CLOCK            Non-SecureOK
2022-05-20T10:14:40.042Z DEBUG modem << 02 NRF_RTC0             Non-SecureOK
2022-05-20T10:14:40.045Z DEBUG modem << 03 NRF_RTC1             Non-SecureOK
2022-05-20T10:14:40.048Z DEBUG modem << 04 NRF_NVMC             Non-SecureOK
2022-05-20T10:14:40.052Z DEBUG modem << 05 NRF_UARTE1           Non-SecureOK
2022-05-20T10:14:40.055Z DEBUG modem << 06 NRF_UARTE2           SecureSKIP
2022-05-20T10:14:40.058Z DEBUG modem << 07 NRF_TWIM2            Non-SecureOK
2022-05-20T10:14:40.062Z DEBUG modem << 08 NRF_SPIM3            Non-SecureOK
2022-05-20T10:14:40.065Z DEBUG modem << 09 NRF_TIMER0           Non-SecureOK
2022-05-20T10:14:40.069Z DEBUG modem << 10 NRF_TIMER1           Non-SecureOK
2022-05-20T10:14:40.072Z DEBUG modem << 11 NRF_TIMER2           Non-SecureOK
2022-05-20T10:14:40.075Z DEBUG modem << 12 NRF_SAADC            Non-SecureOK
2022-05-20T10:14:40.079Z DEBUG modem << 13 NRF_PWM0             Non-SecureOK
2022-05-20T10:14:40.082Z DEBUG modem << 14 NRF_PWM1             Non-SecureOK
2022-05-20T10:14:40.086Z DEBUG modem << 15 NRF_PWM2             Non-SecureOK
2022-05-20T10:14:40.089Z DEBUG modem << 16 NRF_PWM3             Non-SecureOK
2022-05-20T10:14:40.092Z DEBUG modem << 17 NRF_WDT              Non-SecureOK
2022-05-20T10:14:40.096Z DEBUG modem << 18 NRF_IPC              Non-SecureOK
2022-05-20T10:14:40.099Z DEBUG modem << 19 NRF_VMC              Non-SecureOK
2022-05-20T10:14:40.103Z DEBUG modem << 20 NRF_FPU              Non-SecureOK
2022-05-20T10:14:40.106Z DEBUG modem << 21 NRF_EGU1             Non-SecureOK
2022-05-20T10:14:40.109Z DEBUG modem << 22 NRF_EGU2             Non-SecureOK
2022-05-20T10:14:40.113Z DEBUG modem << 23 NRF_DPPIC            Non-SecureOK
2022-05-20T10:14:40.116Z DEBUG modem << 24 NRF_REGULATORS       Non-SecureOK
2022-05-20T10:14:40.120Z DEBUG modem << 25 NRF_PDM              Non-SecureOK
2022-05-20T10:14:40.123Z DEBUG modem << 26 NRF_I2S              Non-SecureOK
2022-05-20T10:14:40.126Z DEBUG modem << 27 NRF_GPIOTE1          Non-SecureOK
2022-05-20T10:14:40.129Z DEBUG modem << SPM: NS image at 0x10000
2022-05-20T10:14:40.131Z DEBUG modem << SPM: NS MSP at 0x20020838
2022-05-20T10:14:40.134Z DEBUG modem << SPM: NS reset vector at 0x1da89
2022-05-20T10:14:40.138Z DEBUG modem << SPM: prepare to jump to Non-Secure image.
2022-05-20T10:14:40.146Z DEBUG modem << *** Booting Zephyr OS build v2.6.99-ncs1  ***
2022-05-20T10:14:40.148Z DEBUG modem << LWM2M Carrier library sample.
2022-05-20T10:14:40.157Z DEBUG modem << DATE_TIME_NOT_OBTAINED 
2022-05-20T10:14:40.359Z DEBUG modem << LWM2M_CARRIER_EVENT_MODEM_INIT
2022-05-20T10:14:40.392Z DEBUG modem << Certificate found, tag 411: [0;32mmatch
2022-05-20T10:14:40.422Z DEBUG modem << [0mCertificate found, tag 412: [0;32mmatch
2022-05-20T10:14:40.438Z DEBUG modem << [0mLWM2M_CARRIER_EVENT_CONNECTING
2022-05-20T10:14:42.542Z DEBUG modem << LWM2M_CARRIER_EVENT_CONNECTED
2022-05-20T10:14:43.584Z DEBUG modem << LWM2M_CARRIER_EVENT_LTE_READY

  • 0 in reply to user77062

    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

  • 0 in reply to user106788

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

  • 0 in reply to user77062

    [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? 

Related
Terms of service