Thanks to visit codestin.com
Credit goes to github.com

Skip to content

rp2/pio: Fix the RP2350 (PICO2) Port PIO2 prog data structure #17519

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

IntergalacticMicrosystems

Summary

The RP2350 PIO2 State Machines ( 8, 9, 10, 11 ) did not work.
The data structure used to pass the PIO arguments was missing an entry for PIO2, thus causing the PIO2 instances to write wrong data to wrong locations.
Fixes issue #17509

Testing

RP2530 Pico 2 board - Tested a modified pio_1hz.py, now works on all 12 RP2350 state machines at once or 1 at a time.
RP2040 Pico board - still works, tested a modified pio_1hz.py, works on all 8 state machines at once or 1 at a time.

Copy link

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

@IntergalacticMicrosystems IntergalacticMicrosystems marked this pull request as draft June 18, 2025 04:35
@IntergalacticMicrosystems IntergalacticMicrosystems changed the title Fix the RP2350 (PICO2) Port PIO2 prog data structure rp2/pio: Fix the RP2350 (PICO2) Port PIO2 prog data structure Jun 18, 2025
@IntergalacticMicrosystems IntergalacticMicrosystems marked this pull request as ready for review June 18, 2025 13:37
@dpgeorge dpgeorge added this to the release-1.26.0 milestone Jun 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants