Bottom Page

Thread Rating:
  • 1 Vote(s) - 1 Average
  • 1
  • 2
  • 3
  • 4
  • 5
 smbus contention handling
I have several threads needing to use the Raspberry Pi3 single I2C bus. The threads aren't called all that frequently, the fastest being one per second and the slowest once every 10 minutes. Since the Pi3 has four processors I believe that there will be times when two (or more) threads will try to access I2C at the same time and mess things up.

What I've done is created a global variable: i2c_busy and in each called thread I do the following before actually attempting to use the bus.

while i2c_busy

i2c_busy = True
some_value = some_i2c_call()
i2c_busy = False
First question: Is there actually going to be a bus contention problem? I think yes but I could be wrong - not an expert.
Second question: Does this seem like a reasonable way of dealing with said contention?

Well it looks like doing it this way isn't a good idea. Hadn't thought of it but "i2c_busy" has the correct value when the thread is created but it doesn't update while the thread is running (makes sense now that I think of it). TOP shows threads piling up whenever it actually hits the While statement and they don't go away until I kill the program.

Guess I'll redo this a bit and put the check in the main loop just before creating the thread.

Top Page

Possibly Related Threads...
Thread Author Replies Views Last Post
  SMBUS Support RWP 1 1,890 Nov-06-2017, 08:45 PM
Last Post: Larz60+

Forum Jump:

Users browsing this thread: 1 Guest(s)