ble/softdevice: add ble_nordic_softdevice feature#11769
ble/softdevice: add ble_nordic_softdevice feature#11769aabadie merged 1 commit intoRIOT-OS:masterfrom
Conversation
This may also work: introduce a |
|
Yes, I thought about that option too, but found it a little overkill at first. But thinking about it now, its probably the cleanest solution after all -> will adapt. |
The softdevice is only verified to be working on nrf52832-based boards. This feature prevents the softdevice from being build for other, similar targets (e.g. nrf52840-based boards).
9fd194f to
03153ac
Compare
|
pushed the fix. Due to further complications through the |
aabadie
left a comment
There was a problem hiding this comment.
Code changes are ok for me.
Also tested on nrf52dk and nrf52840dk and no problem found. The testing procedure described in this PR is not totally valid since softdevice is not pulled in for nrf52840 based board => no feature missing warning (these boards now use the nrf802154 driver directly).
Let's merge this.
ACK
I found out about this PR while rebasing #11477. The migration was not started due to being close to the release, and it will be announced on the mailing list too. As it appears to be |
Contribution description
This PR is a minor step on the path to make NimBLE the default solution for IP-over-BLE in RIOT, e.g. making it the default when building the
gnrc_networkingexample.But currently the softdevice is broken and there was some confusion about testing it also for the
nrf52840, for which it was never verified to be working. This PR should clarify this situation once and for all :-)Note about the approach: apparently the
CPU_MODELvariable is not set when parsing theMakefile.features. At least I have not seen a more generic way in setting this feature explicitly for allnrf52832-based boards. Anything nicer is welcome :-)Testing procedure
Build the gnrc networking example for the e.g.
nrf52dk(-> should be all good), and for the e.g.nrf52840dk(-> should complain about the missing feature).Issues/PRs references
partly related to #11559 and subsequently #11091