Pico flash size bytes #159
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!159
Loading…
Reference in a new issue
No description provided.
Delete branch "pico-flash-size-bytes"
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?
Looking at the other
#definevalues inplatform_defs.h, shouldXOSC_MHZalso be moved elsewhere? The RP2040 datasheet says "The RP2040 supports 1MHz to 15MHz crystals" so I guess XOSC_MHZ might be a board-level thing rather than a platform-level thing?@ -44,6 +33,22 @@* \include flash_program.cIs -1 the correct default value? E.g. see here in
hardware_flash.cSeems this would give a mixed sign comparison if the board header doesn't define flash size. Maybe it should be left undefined, or set to 16M?
Yeah the initial clock setup needs more thought in general, e.g. we should be able to support systems with no crystal at all, but currently that requires you to modify or roll your own
runtime_init. It should also be hoisted up over the data init in crt0 to speed that up. I'll open an issue for itfixes #134
Probably ought to remove the default from this line too?
(I've just checked, and all the scripts/programs dealing with
pico_configs.tsvcope fine withdefaultbeing absent)#183 enforces this 🙂
You still need to fix the PICO_CONFIG line to remove the
default, i.e.