hi, For the first question, i tried looking at some sample platform implementations. It looks like i got it all wrong. 1) Capture Interface is used just to include timing info associated with an interrupt event. Capture interface in no way does emulation. TEP 126 gives info on how to emulate a normal pin as an interrupt.
2) For the second, this link was useful http://www.ece.ncsu.edu/netwis/sensor_networks.php Thanks, Prasanna Karthik >> >> >> >>(moved to tinyos-help) >> >>Only pins connected to port 1 or port 2 on the msp430 are capable of >>being interrupts. >> >>-Joe >> >>On 4/11/06, Dan Steingart <steinda at berkeley.edu> wrote: >>> While many of the pins on the 6 pin header (1,2,3,4,5,9) and on the >>> 10 pin header (2,3,4,5) can be set to be inputs or outputs (via >>> MSP430GeneralIOC), only pins 3,4 and 5 on the 6-pin and pins 8 and 9 >>> on the 10 pin are addressed in MSP430InterruptC. Before I start >>> hacking to change this, is there a reason why any pin that can do I/O >>> can't also be an interrupt? >>> >>> Thanks in advance, >>> >>> Dan >> > > hi, > The usability of the pins available in the 16 pin-extension has been > discussed earlier in this thread. > I seek a few clarifications: > > 1) Pins connected to Port1 or Port2 of the MSP430 can only be used as > interrupt pins directly. Pins belonging to other Ports[3...6] can be used > as interrupts by emulating them using Capture interface. Right? > > 2) Addressability of pins. For. example, take pin 7 of the 10-pin > Extension. It can act as a GPIO or ADC. Namely, P2.1 or P6.2. Do i have to > explicitly state somewhere in the code, for it to be recognized as a GPIO > and not as an ADC? > > Thanks, > -Prasanna Karthik > > _______________________________________________ > 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
