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

nrf52: Make target MCU and LFCLK source selection as a choice #1654

Merged

Conversation

andrzej-kaczmarek
Copy link
Contributor

This is proposed change to use choice settings to select target MCU and LFCLK source for nRF52xxx BSP-s. It requires new newt feature implemented here: apache/mynewt-newt#270. The advantage here is that we do not need separate values for each option and newt will take care of proper value being set for those settings (and there will be only one value). The disadvantage is that it breaks compatibility with earlier newt version and possible with some external code that uses those settings.

@sterlinghughes
Copy link
Contributor

This would require a new version of newt to build *-core, correct? We should probably upgrade the satisfies dependency for newt.

@andrzej-kaczmarek
Copy link
Contributor Author

dependency for newt will be updated for next release
we probably do not do this for master since newt version does not change (perhaps we should bump patchver for such cases?)

@sjanc
Copy link
Contributor

sjanc commented Mar 8, 2019

master is expected to be used with master newt
as mentioned, if needed deps will be updated when next release is done

@andrzej-kaczmarek andrzej-kaczmarek changed the title [DONOTMERGE] nrf52: Make target MCU and LFCLK source selection as a choice nrf52: Make target MCU and LFCLK source selection as a choice Mar 22, 2019
@andrzej-kaczmarek andrzej-kaczmarek merged commit 6b80304 into apache:master Mar 25, 2019
@andrzej-kaczmarek andrzej-kaczmarek deleted the nrf52-syscfg-choice branch March 25, 2019 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants