a07ac72cc5
To me, it made more sense to track which boards go together in a cluster; when reviewing a request to actually use a duplicate vid/pid, you want to know what board(s) it is aliasing. I also revamped the detection of non-USB boards so that a board .mk file that couldn't be parsed by the code here would raise a problem instead of just being skipped for the purposes of checking. There were some lines with comments on the end, and some variation in capitalization of the IDs. These are all normalized and a (sometimes unfriendly!) error printed when it's incorrect. Before this, here were some ways to trick the duplicate vid/pid checker: ``` USB_PID = 0XABCD USB_PID = 0xAbCd USB_PID = 0xABCD # harmless comment? ``` None of these things were ever done on purpose. |
||
|---|---|---|
| .. | ||
| bluetooth | ||
| boards | ||
| common-hal | ||
| device/nrf52 | ||
| freeze | ||
| nrfx@3f55e49eb1 | ||
| peripherals/nrf | ||
| supervisor | ||
| .gitignore | ||
| background.c | ||
| background.h | ||
| fatfs_port.c | ||
| gccollect.c | ||
| ld_defines.c | ||
| Makefile | ||
| mpconfigport.h | ||
| mpconfigport.mk | ||
| mphalport.h | ||
| nrfx_config.h | ||
| nrfx_glue.h | ||
| nrfx_log.h | ||
| qstrdefsport.h | ||
| README.md | ||
| sd_mutex.c | ||
| sd_mutex.h | ||
CircuitPython Port To The Nordic Semiconductor nRF52 Series
This is a port of CircuitPython to the Nordic Semiconductor nRF52 series of chips.
Note
: There are board-specific READMEs that may be more up to date than the generic board-neutral documentation below.
Flash
Some boards have UF2 bootloaders and can simply be flashed in the normal way, by copying firmware.uf2 to the BOOT drive.
For some boards, you can use the flash target:
make BOARD=pca10056 flash
Segger Targets
Install the necessary tools to flash and debug using Segger:
note: On Linux it might be required to link SEGGER's libjlinkarm.so inside nrfjprog's folder.
DFU Targets
run follow command to install adafruit-nrfutil from PyPi
$ pip3 install --user adafruit-nrfutil
make flash and make sd will not work with DFU targets. Hence, dfu-gen and dfu-flash must be used instead.
- dfu-gen: Generates a Firmware zip to be used by the DFU flash application.
- dfu-flash: Triggers the DFU flash application to upload the firmware from the generated Firmware zip file.
When enabled you have different options to test it:
- NUS Console for Linux (recommended)
- WebBluetooth REPL (experimental)