Open salkinium opened 10 years ago
Can you generate a proper telos packet with mig?
Actually, I think this is a relic from TinyOS 1.x. According to TEP111, the TOS_Msg was replaced by the more generic message_t struct with (header, data, footer, metadata) starting with TinyOS 2.x.
Also, the only place this table is accessed is in packet/SerialSource.py, to get the baudrate (which is wrong, btw) and the factory (=TOS_Msg). However, the SerialSource.factory is never used for anything else.
So the python SDK is a little stuck somewhere between 1.x and 2.x.
To take the blow out of that last sentence: Apart from this little mishap the rest seems to be working fine :-)
Trying to open a serial connection via the python sdk on a telos mote fails.
The failure happens because in packet/Platform.py:83 the tinyos.packet.telos is tried to be imported, but since only tinyos.packet.avrmote is available, this fails.
I can change the look-up table to say
avrmote
instead oftelos
, but I assume there is a good reason (ie. 8 vs. 16 bit processor) that they are different:Any idea why tinyos.packet.telos is missing, and what it should be? Is it supposed to be generated by mig? (If so, why is it avrmote.py checked in, but not telos.py?)
Update: I think there is no reason why the avrmote.py should not work on other platforms as well. It does on the TelosB.
Update2: The baudrate of the telos is also false, the default is 115200 (/tos/lib/platforms/telosa/TelosSerialP.nc).
As far as I am concerned, this quickfix solves this issue: