Add board definition for RP2040 Stamp #696
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!696
Loading…
Reference in a new issue
No description provided.
Delete branch "rp2040-stamp"
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?
More details about the board available here: https://rp2040-stamp.solder.party/
@ -0,0 +1,83 @@/*Change the copyright date to 2021?
My version of this was:
I decided not to set 'LED PIN' because it's only on the carrier, not the stamp itself.
@ -0,0 +1,83 @@/*TBH most of these are specific to the Carrier, the Stamp itself can use any pin for any function (that the RP2040 allows), but the defaults are those that are used by the Carrier cause for many people that will be their entry point :)
@ -0,0 +1,83 @@/*r you sure you want this?
@ -0,0 +1,83 @@/*I would personally think that this board definition should be specific to the stamp on its own; if the carrier adds useful things to that then IMO it should be another board.
While I am aware that the stamp can use any pin, the point of these definitions is to provide sane defaults for the various examples and a good basis for building a project on top of it, so defining things which are not available unless you have a carrier board is not helpful.
@ -0,0 +1,83 @@/*I noticed this difference from the version I made (copied from another board) and presumed it was intended. Can you elaborate on what the difference actually means?
@ -0,0 +1,83 @@/*Yes, there should probably be a separate header for the carrier board that (pre) overrides anything it needs to, and includes the stamp header at the end to pick up the rest of the defaults
@ -0,0 +1,83 @@/*This select the slow generic flash stage2 boot, which is probably only what you want if a faster specific variant does not work. I'm pretty sure the stage2 boot used on the pico worked on the stamp too (when i tried it), but @arturo182 would know better
@ -0,0 +1,83 @@/*I was not able to get any other variant working for the production GD25Q64 flash. IIRC I sent you one stamp with that flash and one with Winbond, which did you use? I will retest all other defs one more time to verify.
hello.zip
Yeah i tried with the GDw5q64 version.. here is a little UF2 i just tried with (which for my test purposes both has boot2_w25q080 and ups the clock speed to 270Mhz)... it prints stuff to USB console
@kilograham you were right, it works with w25q080, not sure what I did wrong last time :)
Thank you :)