Pico sync sw spinlock fix #3040
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!3040
Loading…
Reference in a new issue
No description provided.
Delete branch "pico_sync-sw-spinlock-fix"
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?
Related to #1812? Or is that just coincidentally similar?
@ -0,0 +6,4 @@cc_binary(name = "pico_sync_test_hw",testonly = True,srcs = ["pico_sync_test.c"],This needs a:
along with
load("//bazel:defs.bzl", "compatible_with_rp2")at the top@ -0,0 +6,4 @@cc_binary(name = "pico_sync_test_hw",testonly = True,srcs = ["pico_sync_test.c"],thx
related - however the previous fix did not cover all cases
This PR breaks the hardware tests on Arm -
pico_thread_local_testandpico_thread_local_test_cppare failing, they seem to be getting stuck in the firstsem_acquire_blockingAnd on Risc-V, the new
pico_sync_test_swtest fails withModule SYNC: Section check low power lock_core wait loop with timeout : Failed testshould fix #3052
pico_sync_test_swis still failing on Risc-V - the full test output was:When running it locally it also fails, although with a slightly different number of times:
All hardware tests passing now