Skip to content

Fix using stdio_usb and other interrupts from encrypted binaries #588

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

Closed
wants to merge 2 commits into from

Conversation

will-v-pi
Copy link
Contributor

@will-v-pi will-v-pi commented Dec 17, 2024

This is a fix for #584, to enable the interrupts in the encrypted binary, which then allows use of stdio_usb if desired

@kilograham kilograham added this to the 2.1.2 milestone Feb 13, 2025
@kilograham
Copy link
Contributor

ah yes, @will-v-pi we should probably do this in the regular binary startup as you commented elsewhere (runtime_init_per_core_irq_priorities for simplificity)

will-v-pi added a commit to will-v-pi/pico-sdk that referenced this pull request May 30, 2025
kilograham added a commit to raspberrypi/pico-sdk that referenced this pull request May 30, 2025
* Call enable_interrupts when initialising IRQs

Fixes raspberrypi/pico-examples#584, supercedes raspberrypi/pico-examples#588

* move enable_interrupts to the end though it doesn't make much difference

* guard enable_interrupts by !RP2040 as it isn't needed there

---------

Co-authored-by: Graham Sanderson <[email protected]>
@kilograham
Copy link
Contributor

raspberrypi/pico-sdk#2491 merged which supersedes this

@kilograham kilograham closed this May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants