Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Core 1.3.2 > 2.0.0 broke ability to use NRF_TIMER_1 #320

Open
cattledogGH opened this issue Sep 10, 2021 · 1 comment
Open

Core 1.3.2 > 2.0.0 broke ability to use NRF_TIMER_1 #320

cattledogGH opened this issue Sep 10, 2021 · 1 comment
Labels
nrf52 question Further information is requested

Comments

@cattledogGH
Copy link

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.

@tangtangdn
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nrf52 question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants