if somebody else has this error..
i found my mistake, i had a special character (not ascii) in a comment
that Nesdoc can't handle.
best regards!
Hello,
when I try to make documentation of my project an error occurs.
I checked out the newest TOSROOT/tools folder today but the problem
Hello,
when I try to make documentation of my project an error occurs.
I checked out the newest TOSROOT/tools folder today but the problem
continues...
Had somebody else this problem?
Can somebody give a hint?
I use tinyos 2.1.1, iris motes and blip 1..
Best regards!
Sebastian
Hi Andris,
Unfortunately it doesn’t seem to solve the problem.
Maybe I have some time in the next weeks to do some
more tests on that.
First of all I have to do the bit-banging workaround..
I think it is a bug in the sensor. It seems that sometimes
the ack is not handled right, maybe because
Hi Andris,
Yesterday I continued with my i2c problems and discovered the following:
The debug values:
20:03:44 cmd 0x00 0x00
20:03:44 ir read done..
20:03:44 init 255 3
20:03:44 cmd 0x04 0x01
20:03:44 cmd 0x25 0x01
20:03:44 int 0x08 0x01
20:03:44 cmd 0x45 0xb5
20:03:44 int 0x40 0xb5
20:03:44
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…)
Hallo,
unfortunately I wasn’t successfully in reading out the i2c_status..
I successfully included the dbgmsg-components but on the pc-side
I can’t receive dbg-messages.
(I use blip‘s ipbasestation ..does it work together?)
If you want to reconstruct the i2c error you can manually pull
scl
Unfortunately I have never worked with moteworks
and T1 (T1 = tinyos 1.X ?)
I work with tinyos-2.1.1 and the standard i2c component of atmle128L (iris)
which uses the under laying twi (two wire interface)
of the atmel128L chip but it seems that with this
special co2-sensor (with long reaction
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
Hello!
I have a problem with the Atmel128 i2c environment.
I want to read out the k30 co2-sensormodul from senseair.
On this sensor the i2c communication is implemented in software.
Because of that there is an advice in the datasheet
that it might come to problems during the i2c communication
Thank you for your quick reply!
Yes I see my workaround isn't such a good idea.
With other I2C-Sensors (tsl2561 light sensor) I also hadn't any problems
and all worked fine. But with the k30 co2 sensor in particular something
doesn't work.
I also tried to slow down the i2c clock but it
10 matches
Mail list logo
