Talk:Debugging / Architecture Changes for transceiver / hostmote - in progress
From CSL Wiki
Question by Karen March 15 2005
- What is the relationship between the code in the hostmote directory and in mote/nic/ and mote/libmote? Is the code in one of these directories superseded by the other? Is the mote/nic/ and mote/libmote code eventually called by the hostmote code?
Answer by Thanos March 15 2005
mote/hostmote: contains all related code for the hostmoted module (PC side hostmote daemon). Creates hostmoted binary
mote/nic: contains all related code for the motenic module. Creates motenicd binary, which needs hostmoted to run
mote/libmote: contains helper functions for both hostmoted and motenicd AS WELL AS THE EMTOS PC SIDE LIBRARY. Emtos should probably be moved into its own dir under mote; this was planned but never done unfortunately... --thanos
Re: The tiny-os side hostmote code does not have a good seperation of radio specific / radio agnositic code, meaning it contains many #ifdef statements, greatly reducing code clarity, and limiting future extensibility to other radio platforms
It used to be clean but it became dirty for political reasons (smac, hostmoap). Ben cleaned it up and suggested moving ifdefs to a platform dir, which is a good idea. A better idea is to have radio modules (originally planned) and to have transceiver just be a connector application.
Re: Tiny-OS side files:
HostMotePacketM.nc is the hostmote LOW LEVEL UART module.
- the tos-contrib/hostmote directory contains all the hostmote modules and some test drivers (there are 3 hostmote clients, data, conf and debug, and a server module, as well as the low-level uart one)
- the tos-contrib/transceiver directory contains the transceiver application. Transceiver uses hostmote, but it's not the only app that does (emtos uses it as well, for debugging purposes. --thanos)
