Support for the nRF52833

crownstone / bluenet

Bluenet is the in-house firmware on Crownstone hardware. Functions: switching, dimming, energy monitoring, presence detection, indoor localization, switchcraft.

https://crownstone.rocks

91 stars 62 forks source link

Support for the nRF52833 #90

Closed mrquincle closed 4 years ago

mrquincle commented 4 years ago

There's new hardware worked on (not available soon) that will likely have an nRF52833 chip. To support this chip we will have to bump the SDK version and the SoftDevice.

There are bugs / fixes that have to be applied:

FDS_SUCCESS becomes NRF_SUCCESS
The way symbols are introduced in generic_gcc_nrf52.ld doesn't work.
Add the PCA10100 dev. board (which has an nRF52833).
Adjust SOFTDEVICE_MAJOR=7 etc. in CMakeBuild.config.default.
They didn't introduce more SECTIONS, but ram/flash is adjusted. It has 512 kB flash, 128 kB ram. Thus in CMakeBuild.config.default adjust APPLICATION_START_ADDRESS etc. accordingly.
Link to /tools/nrf5_sdk/modules/nrfx/mdk/gcc_startup_nrf52833.S.

To do:

Make sure APPLICATION_START_ADDRESS are properly updated when changed and not somewhere cached by cmake.

mrquincle commented 4 years ago

The branch https://github.com/crownstone/bluenet/tree/nrf52833 takes most of these things into account. Tested with the PCA10100 board. A connection can be made and (fake) switch command can be sent with the dev app. The symbols are now done through an include/third/nrf/nrf_symbols.ld.in file that is populated by cmake with the right address information.

All sizes etc. need to be checked! It can very well be the case that some values can be bumped to make truly use of e.g. the 128 kB ram. Changes have been at the absolute minimum.

They can be found in the branch https://github.com/crownstone/bluenet/tree/nrf52833.

mrquincle commented 4 years ago

PCB ACR01B11A has arrived. It is programmed. There was something funny with the JLink programmer setup made by Bart which only allowed a single nrfjprog a time. The second always failed. Regardless of this, it has been programmed and shows up in the "dev app" (give or take a few hardware errors which make complete sense because the temperature and current thresholds have not been calibrated for this board yet). This finishes the work on this branch. It can be merged into master when this board becomes officially supported.

One task that has to be done then is adding a subdirectory with chipset family on https://github.com/crownstone/bluenet-release and https://github.com/crownstone/bluenet-release-candidate. You can push the same firmware to different devices with the same chipset, but you can't push the same firmware to devices with a different chipset.