-
Notifications
You must be signed in to change notification settings - Fork 152
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
Update nrf-connect SDK to 2.7 #218
Conversation
In [018dbcfd6679c273842084ce34c167295bc6f354](zephyrproject-rtos/zephyr@018dbcf), Zephyr introduced the -Wdouble-promotion compiler flag. We have some debugging logs that implicitly promote floats to double, and it generates a lot of warnings. This commit fixes it.
This relic of the past was briefly used when I first wrote the nrf-connect firmware and tested it against the nrf52840dk_nrf52840 dev board.
It looks like ZBOSS's macro fiesta introduced a new argument in `ZB_ZCL_SET_ATTR_DESC_*` -- see [git blame](https://github.com/nrfconnect/sdk-nrfxlib/blame/11a7add841663509a20b51c0e208ad8091fe1132/zboss/production/include/zcl/zb_zcl_illuminance_measurement.h#L129)
Some pointers:
|
I started migrating |
I've been testing the |
Some changes are required to make the samples compile against the 2.7 nRF Connect SDK (release notes). Most notably:
-Wdouble-promotion
. Some of our debug logging implicitly promotes float -> doublenrf52833
andnrf52840
) and all their versions (1.0.0
to2.0.0
), they are now unified under a singlebparasite
board with multiple supported SoCs and versions. This seem to be the new encouraged way to do things based on docs and existing Zephyr boards.Breaking Changes
Board Identifier
In the Hardware Model V2, boards have different identifiers. While before we referred to a board as:
bparasite_nrf52840@2.0.0
(deprecated)We now must say
bparasite@2.0.0/nrf52840
This applies mostly to build scripts. For example, building with
west
(and Docker) is now done with: