[riot-notifications] [RIOT-OS/RIOT] board suggestion: nRF52840-dongle (#12189)
notifications at github.com
Fri Sep 13 16:47:45 CEST 2019
The abovementioned branch can now be used to run examples like nimble_gatt or usbus_minimal, and `make flash` orchestrates all the required `nrfutil` incantations.
Unless someone tries this out and places more trust in it than I do, I'll leave this sitting around until #11085 can be used to work with its console. With that, I can get a better impression of whether things work as they should, and prep it for an actual PR.
A few questions popped up so far that may help get this into better shape even before it enters the PR phase:
* Is there a checklist of things a new board should be able to do, or general "new board" tips?
* What's the naming guidance between the vendor's marketing name ("nRF52840-Dongle") vs. its PCB identifier ("PCA10059")?
* The nRF chips appear to be quite flexible in their pinout, and as there're neither on-PCB devices that use SPI or I2C nor designated headers for use with those protocols. Is there any point in this board providing the feature `periph_i2c` with arbitrary pins like those in `boards/common/nrf52/include/cfg_spi_default.h`? Any application of those would need to redefine them anyway, pratically creating a fork/copy of the board with an explicit peripheral device for whichever purpose.
* Due to the flashing tool / bootloader involved, there is currently a bespoke linker script and a number of custom definitions in `Makefile.include` that orchestrate the use of the flasher. Does that need to be generalized into its own tool makefiles or can that stay here until something else (hint: Thingy:52 OTA bootloader) uses it?
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications