> By the way: How do you use blip on iris? It's not
> supported yet (see the thread "IRIS support on current Blip Version")
I don’t use the current (blip 2.0) version… I use the first version of blip
which works fine on iris nodes (the only thing that made problem was to use
iris as ipbasestation…)
> Now you say I should pull the SCL line low, and use the i2c bus. This
> means HOLD MASTER. This is a signal generated by the slave, becouse it
> isn't ready for communication. The driver should wait with the first
> job while the SCL is low (and sends EBUSY to any new request), and as
> soon as the SCL is released it should do the first job.
> Do you say that the i2c is still busy after releasing the SCL?
Yes…when I hold scl long enough in low state and release the line it still
returns EBUSY...
I don’t know if this is the same problem as the one that occurs while the
communication with the co2 sensor..
I recognized that because I guessed that the problem is caused by the long time
period in that the co2 sensor hold scl low when it does a measurement. This
period can be up to 160 ms! So maybe this time is just too long for the twi..?
> It still be much easier to resolve this bug, if you could send me the
> debug output of the low level communication, and it might be easier
> than writing a bit-banging driver.
Ok, I will try it…
Sebastian
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
