Updated and added new board headers for Pimoroni RP2040 boards #191
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 milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk!191
Loading…
Reference in a new issue
No description provided.
Delete branch "board-headers"
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?
Lets try this again
@ -0,0 +1,139 @@/** Copyright (c) 2020 Raspberry Pi (Trading) Ltd.Should this be "Copyright (c) 2021 Pimoroni Ltd." ? 🤷
@ -0,0 +1,139 @@/** Copyright (c) 2020 Raspberry Pi (Trading) Ltd.Not got a clue! Both are valid, but it's on your repo, so...
Cool; we're getting there
Thanks for the merge @kilograham .
Yes, both Tiny and PicoSystem have a regular LED, although in our case it's active low rather than high.
We don't have any products with a WS2812 as the LED at this time. Instead we have separate R, G and B LEDs, so for now I've set the G to be the
PICO_DEFAULT_LED_PIN, and included separate defines for each LED element. E.g.Keybow 2040
(no SPI used)
PicoSystem
(no I2C used)
Tiny2040 is a weird case, as it's very much like the Pico in that any pins can be used, just from a smaller subset, so we haven't discussed specific pins to use as defaults. See pinout:

I suppose defaulting to SPI0 and I2C0 would be sufficient?
Oh and yes active low makes sense as a setting too, although it won't be used for now