nrf523840 with softdevice and app_timer and hfclk timer -> fault

RE: nrf523840 with softdevice and app_timer and hfclk timer -> fault

Einar Thorsrud — Mon, 04 Jan 2021 14:03:44 GMT

Hi Ziv,

[quote user="ziv123"]so instead of using "NRF_TIMER_CC_CHANNEL0" i should be using "NRF_TIMER_CC_CHANNEL1" ?[/quote]

That should not be needed, though it also should not matter.bEach timer have a set of CC channels, so channel 0 on timer 1 has nothing to do with channel 0 on timer 0.

[quote user="ziv123"]if i understand correct the RTC0 is LFCLK and the TIMER0 is HFCLK ?[/quote]

Yes. The RTCs are clocked by the LFCLK (32.768 kHz) and the timers are clocked by the HF clock (specifically a 16 MHz peripheral clock which is the HF clock divided by 4).

RE: nrf523840 with softdevice and app_timer and hfclk timer -> fault

ziv123 — Mon, 04 Jan 2021 13:52:52 GMT

great, it seems to compile, soon i will run it and test how it works.. but before, just to be sure .. do i need to change the channel in the timer creation as well:

so instead of using "NRF_TIMER_CC_CHANNEL0" i should be using "NRF_TIMER_CC_CHANNEL1" ?

nrf_drv_timer_extended_compare(&m_timer, NRF_TIMER_CC_CHANNEL0, TICS_FOR_32KHZ, NRF_TIMER_SHORT_COMPARE0_CLEAR_MASK, false);
    nrf_drv_timer_enable(&m_timer);

// samling event configurations - get handlers address: 
    uint32_t timer_compare_event_addr = nrf_drv_timer_compare_event_address_get(&m_timer, NRF_TIMER_CC_CHANNEL0);
    uint32_t saadc_sample_task_addr   = nrf_drv_saadc_sample_task_get();

also, if i understand correct the RTC0 is LFCLK and the TIMER0 is HFCLK ?

best regards

Ziv

RE: nrf523840 with softdevice and app_timer and hfclk timer -> fault

Einar Thorsrud — Mon, 04 Jan 2021 13:42:57 GMT

Hi Ziv,

[quote user="ziv123"]well for some reason i thought that the softdevice uses the LFCLK and not the HFCLK (which right now seems less logic with BLE operations)[/quote]

The SoftDevice reserve both RTC0 and TIMER0. Neither can be used by the application.

[quote user="ziv123"]so what am i defining wrong in the sdk_config.h file or the notorious apply_old_config.h file (which i did not touch yet)[/quote]

You do not need to (nor should you) touch apply_old_config.h, but you need to ensure that you enable TIMER1 properly in sdk_config.h. That would be by setting TIMER1_ENABLED to 1 (with that, apply_old_config.h would automatically set NRFX_TIMER1_ENABLED to 1).

Einar

RE: nrf523840 with softdevice and app_timer and hfclk timer -> fault

ziv123 — Mon, 04 Jan 2021 13:36:54 GMT

hi Einar

well for some reason i thought that the softdevice uses the LFCLK and not the HFCLK (which right now seems less logic with BLE operations), but anyway, so i set the instance of the timer i create with 1 instead of 0 and then i get compilation error here (in file nrfx_timer.h) :

/** @brief Macro for creating a timer driver instance. */
#define NRFX_TIMER_INSTANCE(id)                                   \
{                                                                 \
    .p_reg            = NRFX_CONCAT_2(NRF_TIMER, id),             \
    .instance_id      = NRFX_CONCAT_3(NRFX_TIMER, id, _INST_IDX), \
    .cc_channel_count = NRF_TIMER_CC_CHANNEL_COUNT(id),           \
}

saying that :

'NRFX_TIMER1_INST_IDX' undeclared here (not in a function); did you mean 'NRFX_TIMER0_INST_IDX'?

so what am i defining wrong in the sdk_config.h file or the notorious apply_old_config.h file (which i did not touch yet) 🙂

hope to read from you soon

best regards

Ziv

RE: nrf523840 with softdevice and app_timer and hfclk timer -> fault

Einar Thorsrud — Mon, 04 Jan 2021 12:51:29 GMT

Hi Ziv,

As this fails immediately when you initialize the timer I suspect you may be using timer 0? If so, this is expected as that is reserved for the SoftDevice and cannot be used by the application when a SoftDevice is used. You need to use another timer instance in that case.

Einar