RP2040 and RP2350 have different maximum watchdog delays #2500
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!2500
Loading…
Reference in a new issue
No description provided.
Delete branch "lurch-patch-1"
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?
RP2040-E1 doesn't apply to RP2350 😉 I spotted this whilst investigating #2497
@ -74,6 +74,13 @@ void watchdog_update(void);* \note If \ref watchdog_start_tick value does not give a 1MHz clock to the watchdog system, then the \p delay_msspelling
@ -74,6 +74,13 @@ void watchdog_update(void);* \note If \ref watchdog_start_tick value does not give a 1MHz clock to the watchdog system, then the \p delay_msditton
@ -74,6 +74,13 @@ void watchdog_update(void);* \note If \ref watchdog_start_tick value does not give a 1MHz clock to the watchdog system, then the \p delay_msMaybe reference the errata?
@ -74,6 +74,13 @@ void watchdog_update(void);* \note If \ref watchdog_start_tick value does not give a 1MHz clock to the watchdog system, then the \p delay_ms🤦♂️ I guess that's what happens when I make late-night PRs!
@ -74,6 +74,13 @@ void watchdog_update(void);* \note If \ref watchdog_start_tick value does not give a 1MHz clock to the watchdog system, then the \p delay_msIn fairness, I'd made the typo by copy'n'pasting an existing typo in the same header-file 😂
Updated and force-pushed
@kilograham Do you know which hardware bug this is referring to? The RP2040 datasheet lists RP2040-E1 (which doesn't cover this) as the only watchdog-related errata.
Seems like I'd forgotten about #1492 🤦
This seems a bit better