This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

RTC1 Initialisation with soft device

I am building my application up on the blinky free rtos. I want to use RTC and ble stack. i am initialising RTC1 first and ble stack stact.

The problem is that I am getting 0x1001 error code (which stands for "Incorrect interrupt configuration") from softdevice_handler_init() if I initialize soft device after the nrf_drv_rtc_init().

I didn't face any problem with the nRF5_SDK_11.0.0-2.alpha_bc3f6a0, problem is coming with nRF5_SDK_11.0.0_89a8197 only.

Thanks in advance!

Parents
  • We are using FreeRTOS, BLESTACK and RTC.

    FreeRTOS uses SystemCore Clock,RTC0 is blocked by the Soft-device.

    We are trying to use RTC1/RTC2 for tick events. When we try to enable the tick event for RTC1 or RTC2 we are getting below shown error. Below Error was displayed by enabling DEBUG.

    ID=4097 pc=121272 info=2048,

    I am assigning RTC2_CONFIG_IRQ_PRIORITY

  • Systick won't work - not if you sleep the chip at all, you should use one of the nRF52 ports if you want FreeRTOS to work properly.

    What is the numerical value of the IRQ priority, what actual number are you using? I keep asking you this, I can't see your nrf_drv_config.h file.

    Similarly what priorities has the RTOS set for other peripherals, if it's set Systick to a high interrupt priority - that won't work either. I suggest dumping the contents of the NVIC enabled and priority registers just before the softdevice enable call and finding what's enabled and what priorities they have. The error message is pretty clear - one of your interrupt priorities at least is wrong, you just need to look at them all and find out which one.

Reply
  • Systick won't work - not if you sleep the chip at all, you should use one of the nRF52 ports if you want FreeRTOS to work properly.

    What is the numerical value of the IRQ priority, what actual number are you using? I keep asking you this, I can't see your nrf_drv_config.h file.

    Similarly what priorities has the RTOS set for other peripherals, if it's set Systick to a high interrupt priority - that won't work either. I suggest dumping the contents of the NVIC enabled and priority registers just before the softdevice enable call and finding what's enabled and what priorities they have. The error message is pretty clear - one of your interrupt priorities at least is wrong, you just need to look at them all and find out which one.

Children
No Data
Related