Hi I'm using T2.1 on an IRIS mote with an addon.
This addon sometimes generates a pulse (1ms length) and I want to generate an interrupt in the 0 to 1 transition. If I attached the addon to Int5 or Int7 it works perfectly. On Int6 it doesn´t. But the strange behavior happens when touch the Int6 pin (on the IRIS connector) with a VCC line and it works. Using a scope I discovered that the Int6 pin is driving to much mA (25.4) and because of that the pulse maximum voltage drops too much. So I would like to know if Int6 is internaly used for something on the IRIS or if I'm doing something wrong? I should note that this behavior was replicated in 3 motes with a few diffente addons. Best regards, André Rodrigues ----- Original Message ----- From: "Michael Schippling" <[email protected]> To: "Faisal Aslam" <[email protected]> Cc: "tinyos-help" <[email protected]> Sent: Tuesday, August 25, 2009 4:58 PM Subject: Re: [Tinyos-help] c-stack gets corrupted: TinyOS error? > If you can't find any likely source of wild pointers > then you may "just" be blowing your stack. I think there > is stack monitor code for TOS somwplace...try some searching. > You can also try reducing your stack usage by eliminating > functionality, cutting down function call levels (recursion > anyone?) and reducing large automatic variables to see > if it makes any difference. Pay a bit of attention to the > RAM usage reported during the build as well. > > MS > > Faisal Aslam wrote: >> Hi, >> >> We have an application that sends packets. It also print the packets on >> the serial port. There are also some other complex tasks carried out by >> the application. We have debug that application throughly and found out >> that TinyOS function CC1000SendReceiveP$listenData somehow overwrites >> the c-stack. It leads to the application get halt as a return method of >> a function now points to an invalid address. >> We have checked our code and was not able to find any mistake. Please >> guide us how can we fix this or give us any ideas? >> Is that errror could be called because of non-atomic regions accessing >> data? However, we have no asyn functions. What could be the reason of >> this? >> >> I will be very thankful with some replies. >> > _______________________________________________ > 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
