-
Notifications
You must be signed in to change notification settings - Fork 12
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
RTC not implemented #51
Comments
RTC0 is used by softdevice. |
Ahh ok, thanks for the information. Might be a stupid question, but what is a softdevice? As the LFTimer is already in use for us_ticker it is not possible to use it for RTC also. I mean in the way that rtc_api.c is implemented, correct? Edit: I think of some changes that may enable the usage of the rtc interrupt for both rtc_api.c and us_ticker.c BR |
ARM Internal Ref: IOTSFW-2522 |
I think I found a way to implement the rtc without having huge changes, but my question is where to make sure that the DEFINE has to be set that the implementation get recognized? |
softdevice info : https://www.nordicsemi.com/eng/Products/S110-SoftDevice-v7.0 there're some RTC1 channels left, so you might get it working to provide rtc time functionality. You can describe more in detail, or just send a pull request for review. |
Within my fork you can see or review the changes. If I will do a pull request again, I thing it's going to the blenano one again. That is not correctly I think. I have a problem compiling my rtc changes, because the compiler outputs:
For me that seems as, the include of "rtc_api.h" won't work. Because for my target the blenano I already activated the Edit: By left rtc channels you mean something like the CC register based solution within lp_ticker.c? BR Daniel |
I changed the way of implementation today. Now I can compile but all of my functions (I added an rtc_int.h and rtc_int.c file) are not accessible, yotta says there is no reference. You can have a look to the changes at my fork!
|
Finally I got it working, just have a look at PullRequest #52 |
Can anyone explain the reasons why the RTC of the nrf51822 is not usable with mbed? I read some comments within us_ticker.c that show that the RTC1 is in use for regular ticker and scheduling due to power consumption (Low frequency timers compared to High frequency ones).
But I haven't found that RTC0 is already in use by one of the library implementations! Is it therefore possible to use this for the rtc_api.c implementation?
BR Daniel
The text was updated successfully, but these errors were encountered: