-
Notifications
You must be signed in to change notification settings - Fork 917
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
I2C bus blocked when Pico I2C in slave mode #1519
Comments
This isn't something I know much about myself, but perhaps one of these other issues might have useful information for you? https://github.com/raspberrypi/pico-sdk/issues?q=is%3Aissue+i2c+slave And see also https://github.com/raspberrypi/pico-examples/tree/master/i2c/slave_mem_i2c in case that helps. |
Thank you very much for the answer. I will test tonight how it behaves when I flash the software via USB instead of via SWD. However, the I2C slave is running on core 0. I'll let you know when I know something new. |
Unfortunatly my problem has nothing to to with the mentioned isse. I thought there could be an problem, that the irq could not be enabled, but the irq is enabled. |
I was able to solve the problem. |
Can you show what code worked out for you?
|
Sorry for my late reply. In my code I divide between I think that a problem could be, when you write to the bus when there was no request for that. |
Hello,
I have a problem where I unfortunately do not get on.
I have a setup with a Raspberry Pi 3B+ as master, a Pico as master or slave and another slave. The Pico only acts as master when the Raspberry Pi is off.
Now I have the problem that when the Pico is switched as slave, I can't find any slaves via
i2cdetect -y 1
on the Pi and the processing of the command takes a very long time. If both Pico and Pi are test configured as master I find the second slave and the command is also processed very quickly. The values of the slave are now of course not interpretable because of the two masters.What I can also see is that the I2C interrupt handler is not called on the Pico. Other interrupts and also timers work correctly though.
Does anyone have an idea where my problem could be. Thank you very much.
Unfortunately I have the problem also in this trimmed down code variant:
Thank you very much for your help.
Many greetings,
Fabian
The text was updated successfully, but these errors were encountered: