Skip to content
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

Fix Issues: Pixel and Status Pixel #708

Merged
merged 5 commits into from
Mar 7, 2025
Merged

Fix Issues: Pixel and Status Pixel #708

merged 5 commits into from
Mar 7, 2025

Conversation

brentru
Copy link
Member

@brentru brentru commented Mar 5, 2025

Fixes #691 and #684 via resolving a bug in Adafruit_NeoPixel and adding additional code in the application to handle RMT de-initialization.

This pull request requires the following pull request to be approved, merged, and released before merging:
adafruit/Adafruit_NeoPixel#424

This pull request resolves:

@brentru brentru requested a review from tyeth March 5, 2025 20:08
Copy link
Contributor

@tyeth tyeth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Serial wait slipped into example, and not sure of we want to use updateLength as deprecated, but all good if we do.

// to INPUT.
#ifdef ARDUINO_ARCH_ESP32
// Release the rmtPin for use by other peripherals
statusPixel->updateLength(0);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure this works on all platforms [updateLength 0 then show], and the docs mention it is deprecated but left for old projects that may be calling it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This access to the RMT is only for ESP32 and is guarded, am I missing something?

Copy link
Contributor

@tyeth tyeth Mar 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I guess my brain was still coming from the perspective of the neopixel repo when making those comments.
I'm happy (actually extremely grateful) for this fix, but also wonder if the docs comments in neopixel repo suggest not using updateLength and using new NeoPixel(length, instead then is this the right move. Let's merge it and keep the neopixel repo issue to that repo.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't merge til neopixel repo is merged fwiw

@brentru
Copy link
Member Author

brentru commented Mar 6, 2025

@tyeth Can I re-request a review for this?

Copy link
Contributor

@tyeth tyeth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, nice one resolving it all

@brentru brentru merged commit afd0e86 into main Mar 7, 2025
39 checks passed
@brentru brentru deleted the fix-neopixel-bug-c6 branch March 7, 2025 15:07
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.

C6 Feather can't use onboard neopixel as user component
2 participants