The main step is to make something that works... I usually start with whatever hacked up bit of hardware poking I can find which does sort of what it should. Then I try to figure out what kind of semi-rational interface I should provide, keeping in mind that there may be other bits of hardware or platforms that might want to use this interface in the future. Then make it look nice. Then DOCUMENT what it is and what it does.
The "driver" concept in TOS is a bit different from higher level OS's because drivers don't get loaded separately. TOS usually implements some kind of upper/ lower level split, where the upper level is as generic as it can be and the lower level works with the specific hardware. For an example, trace through how the Voltage component works, on top of the ADC, on top of specific chip and platform code. Was that what you were looking for? MS fabrice fothe wrote: > > Hi every body, > > I'm working on Mica2 for my Bachelor thesis.I have the > original node for sending and receiving i also have one Sniffer (MIB > 520) like Base Station. > My supervisor make a new component MICA2 using the piece from The > Crossbow Technology. Now my job it to make the driver of this new > component using NESC. > > There is some one who can tell me the mains steps to follow > to write a driver of the MICA2?? > > Thank a lot for responding!!! > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
