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

Potential lock up with many rapid keypresses. #18

Closed
caternuson opened this issue Jan 10, 2019 · 3 comments
Closed

Potential lock up with many rapid keypresses. #18

caternuson opened this issue Jan 10, 2019 · 3 comments

Comments

@caternuson
Copy link
Contributor

https://forums.adafruit.com/viewtopic.php?f=8&t=144551

@ladyada
Copy link
Member

ladyada commented Jan 10, 2019

replied to thread, the code is not easy to debug, so not sure if/when i'll get to it. delays may solve the problem

@griv
Copy link

griv commented Apr 16, 2020

I've just hit this issue.
I've got a single Neotrellis wired to a D1 Mini. My app connects to an MQTT broker using the PubSub library and subscribes to 16 topics. As the subscription messages come in the Neotrellis locks up after 4 messages. I'm not pressing any Trellis buttons, just writing the LED colours. The D1 mini continues as I can still see more messages coming in in the serial console.

Loading the example code of basic and interrupt I can press buttons for about 10 seconds and then it locks up. I've tried powering it with 5v and 3.3v with similar results.

Update: also tried cutting the 3v Vi2c trace and soldering to Vin. Same results (tried both 3.3 & 5v).

Update: seems it is a D1 Mini issue. Works fine on a Mega. I rebuilt my app on a D32 and it's solid. Not sure if it is a library conflict (I have heaps of libraries installed). I did try a few D1 Minis all with the same result.

@ladyada
Copy link
Member

ladyada commented Apr 3, 2021

found this bug, adafruit/seesaw#48
i think disabling IRQ support helps/fixes - ironically :(
so comment out ss.setGPIOInterrupts(button_mask, 1); or whatever is enabling GPIO irqs
closing for now because im pretty sure its fixed - have been smashing these MX keys

@ladyada ladyada closed this as completed Apr 3, 2021
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

No branches or pull requests

3 participants