nRF52833 support WIP #698
nRF52833 support WIP #698
Conversation
|
I am really interested in this. I made sure that CircuitPython support was working fine for the 833 but have been hoping for Arduino support for the 833 to come. Debugging on CP pointed me to update the bootloader SD. The UF2 device family is also different with the 833 (see bootloader repo) Couple of comments: |
|
Per the compatibility matrix, the nRF52833 requires S140 7.0.1 or later. The current bootloader included in this fork was built with S140 6.1.1 for compatibility with the rest of the core since I think some function signatures change between versions (but I could be wrong). A softdevice update would probably be the last major thing needed to get board support working. |
| @@ -0,0 +1,155 @@ | |||
| /* | |||
There was a problem hiding this comment.
file has not been double checked, it just follows the same structure as the other dev kit variants.
| @@ -0,0 +1,55 @@ | |||
| /* | |||
There was a problem hiding this comment.
file has not been double checked, it just follows the same structure as the other dev kit variants.
| @@ -26,7 +26,7 @@ | |||
| #define NRFX_TIMER2_ENABLED 0 | |||
| #define NRFX_TIMER3_ENABLED 0 | |||
|
|
|||
| #ifdef NRF52840_XXAA | |||
| #if defined(NRF52840_XXAA) | |||
There was a problem hiding this comment.
the nRF52833 does not have a QSPI peripheral
Runs on device hardware (not yet tested on pca10100). Flashing with nrfjprog 10.12.1 manually installed into BSP.
Current issue: Bluefruit.begin() breaks when bond_init() calls InternalFS functions.
Implementation borrows from work done by @LokiMetaSmith in PR #659.