Repository navigation
Conversation
Collaborator
|
Tested on CLUE and ItsyBitsy nRF52840. Works: buses, CIRCUITPY read/write, CLUE display and all 5 sensors. Doesn't work: on CLUE, Note: the adaboot bump is missing adaboot #9, which #11570 needs for the Picos. Whichever merges second needs both. |
STATUS_DOTSTAR_DATA and STATUS_DOTSTAR_CLOCK name board pins and emit MICROPY_HW_APA102_MOSI/SCK with CIRCUITPY_BITBANG_APA102 into the generated mpconfigboard.h. Setting only one, or combining them with STATUS_NEOPIXEL, is an error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pin names come from the ports/nordic board. The header pins are named by a new adafruit-itsybitsy-header connector in the overlay, with a binding in dts/bindings and names in CONNECTORS, which gives board.I2C(), board.SPI() and board.UART() on SCL/SDA, SCK/MOSI/MISO and TX/RX. Pins off the header (SWITCH, the LED and the status DotStar) are named in [pins]. All I2C, SPI, UART and PWM instances are dynamic. The status DotStar is bit-banged, so the upstream apa102 node on SPI2 is dropped. Changes from the upstream board: - QSPI runs at 16 MHz, not 32 MHz. The GD25Q16C fails with I/O errors at 32 MHz, as found for ports/nordic in adafruit#1418. - The user LED is labeled blue, not red. CONSOLE=1 puts the Zephyr console on TX/RX. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dhalbert
force-pushed
the
zephyr-cp-itsybitsy-nrf52840
branch
2 times, most recently
from
October 19, 2026 23:43
7590571 to
e35154c
Compare
dhalbert
changed the title
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dhalbert
force-pushed
the
zephyr-cp-itsybitsy-nrf52840
branch
from
October 20, 2026 03:24
e35154c to
102225e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR note written by @dhalbert; code and tests by Claude, guided by me.
The CLUE changes that were here moved into #11576, and the adaboot update is no longer needed:
mainalready has a newer adaboot that includes adafruit/adaboot#8, which added the ItsyBitsy.circuitpython.tomlfor APA102/DotStar status LED.adafruit-itsybitsy-headerconnector: a binding indts/bindings, a node in the board overlay, and aCONNECTORSentry inzephyr2cp.py. It names the header pins, including the standard pins forboard.I2C(),board.SPI()andboard.UART(). It covers only the ItsyBitsy nRF52840's pins for now; the other ItsyBitsy boards have extra pins such as D3 and D4 (see the TODO).CONNECTORSentries alphabetically, in a separate commit. Will make future additions easier and the code easier to read.Testing
On an ItsyBitsy nRF52840:
board.I2C(), before and afterdeinit().board.SPI()MOSI-MISO loopback, 250 kHz to 16 MHz. 32 MHz fails, as on the Feather nRF52840 in both ports (MISO sample delay).board.UART()TX-RX loopback at 9600 and 115200 baud.