Add board definition for the RP2040 Stamp Round Carrier #837
No reviewers
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk!837
Loading…
Reference in a new issue
No description provided.
Delete branch "round_carrier_board"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The file modifies a few pins and then includes the stamp board file.
Details about the board available here: https://www.solder.party/docs/rp2040-stamp/round-carrier/
@ -0,0 +38,4 @@// --- Neopixel Ring ---#ifndef PICO_DEFAULT_WS2812_PIN#define PICO_DEFAULT_WS2812_PIN 24Looking at the product-page you mentioned, I guess the on-board NeoPixel doesn't stop working when the Stamp is on the Carrier Board, so perhaps the Carrier Board NeoPixel pin should get its own
#define, rather than overriding thePICO_DEFAULT_WS2812_PINfromsolderparty_rp2040_stamp.h? 🤷@ -0,0 +34,4 @@#endif#ifndef PICO_DEFAULT_UART_RX_PIN#define PICO_DEFAULT_UART_RX_PIN 17#endifGiven that this is redefining all the UART pins, perhaps it's worth specifying the
PICO_DEFAULT_UARTdefinition, just to be on the safe side?@ -0,0 +55,4 @@#endif#ifndef PICO_DEFAULT_I2C_SCL_PIN#define PICO_DEFAULT_I2C_SCL_PIN 1#endifGiven that this is redefining all the I2C pins, perhaps it's worth specifying the
PICO_DEFAULT_I2Cdefinition, just to be on the safe side?@ -0,0 +38,4 @@// --- Neopixel Ring ---#ifndef PICO_DEFAULT_WS2812_PIN#define PICO_DEFAULT_WS2812_PIN 24I thought about it, but I think I'd rather have the Carrier NeoPixel ring take priority over the single NeoPixel on the Stamp 😅
@ -0,0 +34,4 @@#endif#ifndef PICO_DEFAULT_UART_RX_PIN#define PICO_DEFAULT_UART_RX_PIN 17#endifSure, will do :)
@ -0,0 +38,4 @@// --- Neopixel Ring ---#ifndef PICO_DEFAULT_WS2812_PIN#define PICO_DEFAULT_WS2812_PIN 24Okay, so perhaps you want to add an additional define to the carrier's header-file with the definition of the stamp's neopixel pin, so that code written to target the carrier can write to both (defined) neopixel pins? 🙂
@ -0,0 +33,4 @@#define PICO_DEFAULT_UART_TX_PIN 16#endif#ifndef PICO_DEFAULT_UART_RX_PIN#define PICO_DEFAULT_UART_RX_PIN 17This should probably be something like
SOLDERPARTY_RP2040_STAMP_...rather thanPICO_STAMP_..., as it's a feature specific to this board and not to any other Pico boards.@ -0,0 +33,4 @@#define PICO_DEFAULT_UART_TX_PIN 16#endif#ifndef PICO_DEFAULT_UART_RX_PIN#define PICO_DEFAULT_UART_RX_PIN 17Gotcha 👍
LGTM! And hopefully @kilograham agrees with all my suggestions 😉