[
https://issues.apache.org/jira/browse/MYNEWT-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055732#comment-16055732
]
Andrzej Kaczmarek commented on MYNEWT-785:
------------------------------------------
I created initial pull request for this:
https://github.com/apache/incubator-mynewt-core/pull/341
Open issue here is how we should handle configuration since default
configuration is for 1MHz so controller won't work (I added explicit error for
this emitted during build). Depending on HW used we need different
configuration - changing OS_CPUTIME_FREQ to 32768 is not enough. We also need
to enable TIMER5 for nRF52 or TIMER3 for nRF51.
- should we leave this to user (in target configuration)?
- should we configure this in application (how to handle different HWs)?
- should we change default configuration to use 32768 instead of 1M (something
could break)?
[~wes3] any idea?
> Remove support for 1MHz clock in nimble. We stick to Low Power RTC
> ------------------------------------------------------------------
>
> Key: MYNEWT-785
> URL: https://issues.apache.org/jira/browse/MYNEWT-785
> Project: Mynewt
> Issue Type: Sub-task
> Security Level: Public(Viewable by anyone)
> Components: Nimble
> Reporter: Łukasz Rymanowski
> Assignee: Andrzej Kaczmarek
> Fix For: v1_1_0_rel
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
