Cleanup/clarification of PIO behavior with >32 pins #2085
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!2085
Loading…
Reference in a new issue
No description provided.
Delete branch "pio_hipins"
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?
@ -72,0 +80,4 @@** On RP2350B, there are 48 pins but each PIO instance can only address 32 pins (the PIO* instance either addresses pins 0-31 or 16-47 based on \ref pio_set_gpio_base). The* `pio_sm_` methods that directly affect the hardware always take _real_ pin numbers in the full range, however:Is it worth saying that sm_ methods also take real pin numbers?
@ -72,0 +80,4 @@** On RP2350B, there are 48 pins but each PIO instance can only address 32 pins (the PIO* instance either addresses pins 0-31 or 16-47 based on \ref pio_set_gpio_base). The* `pio_sm_` methods that directly affect the hardware always take _real_ pin numbers in the full range, however:ah - you've said that below - ignore
Looks good to me, and fixes the uart_rx example!
ah - I think pio_sm_set_pindirs_with_mask64 is shifting twice. It shifts by pio_get_gpio_base then calls pio_sm_set_pindirs_with_mask_internal which shifts again. Removing the shift from pio_sm_set_pindirs_with_mask_internal fixes this. uart_tx can be used to test this.
These lines need to be removed?
Seems to work nicely
@ -265,4 +274,4 @@}pio->sm[sm].pinctrl = pinctrl_saved;pio->sm[sm].execctrl = execctrl_saved;}I'm sure this must be a stupid question, but why is line 243 doing
when line 221 says
?