Hi,

Can you find out what's in the state variable when the i2c stops working?

By the way: when we had problems with the i2c drivers, I modified the
hpls to print every low level communication:
http://dl.dropbox.com/u/363226/munka/I2CDriver.zip
Don't forget to change the Clk/Data pins in the HplAtm128I2CBusC
(there might be other things to change back), we used it with
atm128rfa1 (ucmini platform).
If you don't familiar with DiagMsg, check its readme in $TOSDIR/lib/DiagMsg

Andris

On Thu, Nov 24, 2011 at 4:16 PM, "Sebastian Dölker"
<[email protected]> wrote:
> Sorry I was imprecise.. I started with tinyos 2.1.1
> but work with a check out from the googlecode repository.
> (Downloaded in august 11)
>
> Anyway i downloaded the newest source today..
> but the problem seems to continue!
>
> Because the I2C-Funktions returned EBUSY I thought,
> that there was a problem with the arbiter so I tried it
> without arbiter an wired experimentally direct to the Atm128I2CMasterPacketP 
> (via I2CPacket-interface),
> but the Problem continued…
>
> I discovered that while the I2C-components returned EBUSY the
> software runs through the else-block at the beginning of the
> read-function in Atm128I2CMasterPacketP, because of that I tried
> to „reset“ the i2c component with the i2c_abort() function..
> but as you mentioned this isn’t a good idea..
>
> Have you an idea what can cause such a bad state
> in Atm128I2CMasterPacketP and how it can be corrected?
>
> Thanks in advance,
> Sebastian
>
> --
>
>
>
>
>
>
>
>
>
>
>
> NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
> Jetzt informieren: http://www.gmx.net/de/go/freephone
>

_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to