Clock configuration fail in application with secure bootloader (uart mbr)

RE: Clock configuration fail in application with secure bootloader (uart mbr)

Narek Aleksanyan — Tue, 22 Feb 2022 13:05:03 GMT

I found what was causing my application to crush.

It was the fact that I didn't change RAM placement addresses and my application most likely was trying to access function at an address which was allocated for bootloader and giving hardfault in the result .

RE: Clock configuration fail in application with secure bootloader (uart mbr)

Narek Aleksanyan — Mon, 21 Feb 2022 12:12:51 GMT

Here is what happens when it crushes, and you can see the main function here as well.

RE: Clock configuration fail in application with secure bootloader (uart mbr)

Sigurd — Mon, 21 Feb 2022 10:44:04 GMT

1) What happens when it crashes? Hardfault? or does it go to the app_error handler? Are you able to debug further after the crash?

2) How does your main() function look like?

RE: Clock configuration fail in application with secure bootloader (uart mbr)

Narek Aleksanyan — Wed, 16 Feb 2022 13:23:58 GMT

[quote userid="15146" url="~/f/nordic-q-a/84411/clock-configuration-fail-in-application-with-secure-bootloader-uart-mbr/353051#353051"]I assume you did this, NRF_SDH_CLOCK_LF_SRC to 0, NRF_SDH_CLOCK_LF_RC_CTIV to 16, NRF_SDH_CLOCK_LF_RC_TEMP_CTIV to 2, and NRF_SDH_CLOCK_LF_ACCURACY to 1. Perhaps also CLOCK_CONFIG_LF_SRC to 0.[/quote]

Yes, I have these settings in my application sdk_config

[quote userid="15146" url="~/f/nordic-q-a/84411/clock-configuration-fail-in-application-with-secure-bootloader-uart-mbr/353051#353051"]

Does it passes nrf_drv_clock_lfclk_request() as well?

Are you able to debug, and figure out where it crashes?

[/quote]

My application crashes inside nrf_drv_clock_lfclk_request() when it calles CRITICAL_REGION_EXIT()

here is the function below.

void nrf_drv_clock_lfclk_request(nrf_drv_clock_handler_item_t * p_handler_item)
{
    ASSERT(m_clock_cb.module_initialized);

    if (m_clock_cb.lfclk_on)
    {
        if (p_handler_item)
        {
            p_handler_item->event_handler(NRF_DRV_CLOCK_EVT_LFCLK_STARTED);
        }
        CRITICAL_REGION_ENTER();
        ++(m_clock_cb.lfclk_requests);
        CRITICAL_REGION_EXIT();
    }
    else
    {
        CRITICAL_REGION_ENTER();
        if (p_handler_item)
        {
            item_enqueue((nrf_drv_clock_handler_item_t **)&m_clock_cb.p_lf_head,
                p_handler_item);
        }
        if (m_clock_cb.lfclk_requests == 0)
        {
            nrfx_clock_lfclk_start();
        }
        ++(m_clock_cb.lfclk_requests);
        CRITICAL_REGION_EXIT();//this call results in crush <=============
    }

    ASSERT(m_clock_cb.lfclk_requests > 0);
}

RE: Clock configuration fail in application with secure bootloader (uart mbr)

Sigurd — Tue, 15 Feb 2022 10:19:53 GMT

Hi,

Does it passes nrf_drv_clock_lfclk_request() as well?

Are you able to debug, and figure out where it crashes?

...

I assume you did this, NRF_SDH_CLOCK_LF_SRC to 0, NRF_SDH_CLOCK_LF_RC_CTIV to 16, NRF_SDH_CLOCK_LF_RC_TEMP_CTIV to 2, and NRF_SDH_CLOCK_LF_ACCURACY to 1. Perhaps also CLOCK_CONFIG_LF_SRC to 0.

RE: Clock configuration fail in application with secure bootloader (uart mbr)

Narek Aleksanyan — Mon, 14 Feb 2022 13:52:26 GMT

The only log that I get in my application is the one that I wrote

<info> app: inside app main

the other instance of logging before crushing is in the function nrf_drv_clock_init(), which is not getting processed even if I call NRF_LOG_FLUSH() or NRF_LOG_FINAL_FLUSH()

but the returned value of nrf_drv_clock_init() passes the APP_ERROR_CHECK

ret_code_t ret= nrf_drv_clock_init();
APP_ERROR_CHECK(ret);
nrf_drv_clock_lfclk_request(NULL);

[quote userid="15146" url="~/f/nordic-q-a/84411/clock-configuration-fail-in-application-with-secure-bootloader-uart-mbr/352854#352854"]From your "NRF_LIBUARTE_ASYNC_DEFINE", you seem to be using RTC instance 0. This is used by the SoftDevice as well. Try using RTC instance 2 instead.[/quote]

I changed the RTC instance to 2, also changed the timer instance to 3, but the problem still persists.

Is it possible that the address of the modules in use are misplaced in ram?

EDIT::

So I stumbled across bunch of parsing errors in output Source Navigator, which neither were showing in Target tab, nor they were indicated in any way during build, and all of these errors are complaining about "unknown register name 'vfpcc' in asm" in the cmsis_gcc.h header.

Which according to this https://devzone.nordicsemi.com/f/nordic-q-a/35481/source-navigator-in-segger-embedded-studio-reports-unknown-register-name-vfpcc-in-asm

is not an issue

However I include this for you to have full information regarding the issue.

RE: Clock configuration fail in application with secure bootloader (uart mbr)

Sigurd — Mon, 14 Feb 2022 11:31:44 GMT

Do you have any logs from your application as well?

[quote user=""]Also I use a timer instance in libuarte if it is relevant.[/quote]

From your "NRF_LIBUARTE_ASYNC_DEFINE", you seem to be using RTC instance 0. This is used by the SoftDevice as well. Try using RTC instance 2 instead.

RE: Clock configuration fail in application with secure bootloader (uart mbr)

Narek Aleksanyan — Tue, 08 Feb 2022 12:53:15 GMT

I ran the debug variant of the bootloader project(pca10040_uart_debug), and here is the log of the bootloader.

00> <info> app: Inside main
00>
00> <debug> app: In nrf_bootloader_init
00>
00> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
00>
00> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
00>
00> <debug> nrf_dfu_settings: Using settings page.
00>
00> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
00>
00> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
00>
00> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
00>
00> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
00>
00> <debug> app: Enter nrf_bootloader_fw_activate
00>
00> <info> app: No firmware to activate.
00>
00> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
00>
00> <debug> app: App is valid
00>
00> <warning> nrf_dfu_settings: No additional data erased
00>
00> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
00>
00> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
00>
00> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
00>
00> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
00>

RE: Clock configuration fail in application with secure bootloader (uart mbr)

Sigurd — Mon, 07 Feb 2022 13:16:06 GMT

Hi,

[quote user=""]

After bootloader starts my application I initialize the clock module, however my application crushes and causes the device to reset.

[/quote]

Could you test with the debug variant of the bootloader project(pca10040_uart_debug), and see if you get any errors or warnings printed in the log(Segger RTT logger backend)?