Added some waveshare boards definition #619
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!619
Loading…
Reference in a new issue
No description provided.
Delete branch "develop"
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?
Added some waveshare boards definition
RP2040-LCD-0.96
The other boards are not on the shop yet, but I've got them.
This is my first time to pull request. I may have made a mistake in several operations. Please forgive me
@ -0,0 +1,104 @@/*@kilograham As I mentioned in one of the previous iterations of this PR, I dunno if we ought to be allowing this to introduce a
PICO_LCD_SPIdefine (which IMHO feels a bit generic), or requesting that it instead uses a more board-specific name e.g.WAVESHARE_RP2040_LCD_SPI?One comment, but otherwise LGTM.
@ -0,0 +1,104 @@/*I think it's a good idea. I'll change some macro names.
Do I need to click the Resolve button?
@ -0,0 +1,104 @@/*Thanks @EngineerWill 👍
do any of these boards have RP2040-B1 chips on them? if not probably best to have PICO_FLOAT_SUPPORT_ROM_V1 and friends be 0. It is not critical though, so I will merge without it for now if I don't hear back before 1.3.0 release which is imminent
Note, that you should now just set use PICO_RP2040_B0_SUPPORTED = 0 instead of the two old flags
hi kilograham .There is no problem. I have submitted it. Please check whether it is right