cpu/nrf9160: add Kconfig dependencies#17291
Conversation
.murdock
Outdated
| microbit | ||
| native | ||
| nrf52840dk | ||
| nrf59160 |
There was a problem hiding this comment.
| nrf59160 | |
| nrf9160 |
There was a problem hiding this comment.
I guess I was still asleep this morning...
Should be nrf9160dk...
9e09545 to
a016eee
Compare
| Indicates that the current cpu is 'nrf9160'. | ||
|
|
||
| rsource "vectors/Kconfig" | ||
|
|
There was a problem hiding this comment.
I think you are missing: source "$(RIOTCPU)/nrf5x_common/Kconfig". As that one already includes the cortexm_common Kconfig you can remove it from here.
There was a problem hiding this comment.
@leandrolanzieri The problem here is that nRF9160 doesn't fully reuse nrf5x_common for now because some work is still needed on the driver side. That's why this CPU defines by itself which features it has instead of relying on nrf5x_common.
If this is problem, I can have a look to fix the remaining issues with the shared drivers first, then let nRF9160 fully relies on nrf5x_common. What do you think ?
There was a problem hiding this comment.
But if we don't select CPU_COMMON_NRF5X its features should not be provided, right? This is currently failing because MODULE_NRF5X_COMMON_PERIPH is missing (defined in cpu/nrf5x_common/periph/Kconfig.nrf5x)
|
Its green now, should I squash @leandrolanzieri @dylad? |
|
Go ahead ! |
9847661 to
4aaf8f1
Compare
|
Here we go ! |
|
Thanks! |
Contribution description
These models modules for nrf9160 CPU and the only BOARD using it.
Testing procedure
Issues/PRs references
Part of #16875