You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was confirmed by that in Core 1.3.2 NRF_TIMER_1 could be used to trigger an interrupt, but that functionality was broken with the transition to Core 2.0.0.
Can NRF_TIMER_1 availability be brought back?
If not, documentation needs to be changed to indicate that it is not available for timer interrupts.
The text was updated successfully, but these errors were encountered:
Hi,
Thank you for your post. I also have a problem after changing from Core 1.3.2 to a higher version. The IMU on Nano 33 BLE has no interrupt pins connected to the processor. It can only poll to check the register whether there is data available in loop(). In this way, there is serious data loss if I use a high Core version. Do you know is it related to the NRF_TIMER_1? Many thanks.
This issue was noted when using Khoi Hoang's NRF52_MBED_TimerInterrupt library
https://github.com/khoih-prog/NRF52_MBED_TimerInterrupt
and was reported here
https://github.com/khoih-prog/NRF52_MBED_TimerInterrupt/issues/6
It was confirmed by that in Core 1.3.2 NRF_TIMER_1 could be used to trigger an interrupt, but that functionality was broken with the transition to Core 2.0.0.
Can NRF_TIMER_1 availability be brought back?
If not, documentation needs to be changed to indicate that it is not available for timer interrupts.
The text was updated successfully, but these errors were encountered: