Add more defines related to partition tables #2581
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#2581
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
It would be good to add some of the defines from https://github.com/raspberrypi/pico-examples/pull/627#pullrequestreview-3042818651 into the SDK, including adding defines for the family names (which can also be used by picotool).
punting this to 2.3.0 as we should probably add a library related to all this
Should raspberrypi/pico-examples#627 also be bumped until that library is added, or is it fine to merge it without the library and fix it up to use the library later?
yeah, i think it is fine - it shows you how to do it for now
Hi @will-v-pi As a part of this work, would it be possible to add a size definition for the
workarearequired when using the bootrom's flash API please?We can then replace some hardcoded instances.
Thanks.
Whilst I'm here, is there any appetite for adding something like:
#define UF2_BLOCK_SIZE 512?I realise there's a
static_assert(...)inuf2.hto guard against this struct being sized other than 512 but it would be nice if source could use a common definition - this must be immutable by now.Apologies if I've missed something I could use.
Thanks.
This probably isn't what you'e looking for! 🤣
i.e. No, there doesn't seem to be anything you've missed.
@lurch Thanks. Yes, "... that was not the droid I was looking for" :)