Re: [Tinyos-help] SendMsg and Send Interfaces?
I believe Send interface is used for Multihop routing transmission and has a pre-defined destination address of 0, which is the base station address. SendMsg is a one-hop transmission interface which allows you to specify any destination addr, AM group, etc. I don't quite understand what you mean by "block messges to neighbor nodes" though. If you want to block incoming msgs, shouldn't a receive interface be used in stead? - Dongyan On 9/16/06, Sumit Gupta <[EMAIL PROTECTED]> wrote: Hi, I would like to know basic difference between these two interfaces. I am also wondering that If I want to block certain messges to neighbor nodes (or in network) should I do it at SendMsg or Send. I know it might sound a little stupid question but please adivce. Regards, Sumit ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge: Nodes won't reboot over the air
You might want to check your battery voltage. I ran into the same problem a while ago and it turns out that when the battery voltage is less than a certain value (I remember it's 2.7V) the flash in the MCU can't be re-programed. - Dongyan On 8/7/06, R Gartz <[EMAIL PROTECTED]> wrote: Hello, I'm having problems with Deluge. I've done everything the deluge-manual said, but the nodes won't reboot over the air through TOSBase. The nodes do seem to receive some commands over the air, but they do not reboot, however they are saying (through the commandline output) that they shall reboot from image A to image B... but when checking againg with deluge --ping, the nodes still execute image A However, when I plug in one node at the programmer and issue the reboot command, the node reboots When I issue an inject command, all the nodes install the new image.. I'm using the correct makerules from /tools/make and I'm using the correct TOSBoot from: /lib/Deluge/TOSBoot/build/micaz/main.ihex (all updated from CVS) Anyone knows what the problem could be? greetings, R. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] just started
You might want to look at contrib/xbow and search for mda300.c, which is part of xlisten, to see how the conversion is done. - Dongyan On 7/21/06, karthik Bollepalli <[EMAIL PROTECTED]> wrote: Hello, I have just started working on the MDA 300CA Data acquisition board. My project aim is to connect a finger clip sensor and a pressure sensor to the MDA 300 CA DAQ board and using the micaz send the information on a wireless channel to the base station. I have just started and so i am nt averse with the complete functioning of the system.My question is The analog o/p of the finger clip sensor wen connected to the ADC channels of the(A0-A6) DAQ board will be converted to a digital signal.This when transfered over the micaz must be decoded on a PC.How do we decode that and wats the bit length of the digital output. Please guide me step wise, as i am new to this. Thanks, Karthik ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Weird results...
When you program your motes, have you programmed them with different node ids like make tmote reinstall,NODE_ID? - Dongyan On 7/6/06, Jose L. Ponce <[EMAIL PROTECTED]> wrote: Hello all, My question is very simple: I have 5 motes with the same program installed. This program receives an instruction from the computer and executes it (i.e. "dac output to 2 volts"). I am sending the instruction using moteif.send(MOTEID, message), so theoretically just the mote MOTEID should receive the message. This is not the case, though, and all motes seem to receive the message and execute it. And what's more strange: if I have two motes and I send "set dac to 0x" (which should be the maximum, 3 volts) both motes receive the message and each of them has an output of 1.5 volts!! The nodes are connected to the computer through USB and communication is made using this means, not radio. The DAC outputs are connected to an inverter amplifier and this amplifier is connected to a DC-Controlled Dimmer. Could the problem be related to impedances??? Any thoughts on what could be causing this anomaly and how to solve it? Thanks, - Jose. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] #ifdef support in nesc.
You need to also wire the components' interface together. For example,
do you have in your configuration sth like
#ifdef CHIRP_ENABLE
SurgeM.StdControl -> Sounder;
#endif /* CHIRP_ENABLE */
- Dongyan
On 6/29/06, Tehn Yit Chin <[EMAIL PROTECTED]> wrote:
Philip Levis wrote:
> On Jun 29, 2006, at 5:33 PM, Tehn Yit Chin wrote:
>
>> Hi,
>>
>> Does anyone know if #ifdef is supported in nesc?
>
>
> The full C preprocessor is supported. Your bug is that you are not
> wiring the Sounder. You need to include it in the configuration.
>
In Surge.nc, I was wiring Sounder as
implementation {
components Main, SurgeM, TimerC, LedsC, NoLeds, Photo as Sensor,
RandomLFSR,
GenericCommPromiscuous as Comm, Bcast, MultiHopRouter as multihopM,
QueuedSend;
#ifdef CHIRP_ENABLE
Components Sounder;
#endif /* CHIRP_ENABLE */
}
Is this valid? Must all components be specify in one statement?
thanks,
tyc
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] How does event implemented in tinyos?
I believe there is no event queue and when you signal an event, the event handler is executed immediately. An async event can preempt other events but a regular event cannot. On 6/15/06, Aditya Bhave <[EMAIL PROTECTED]> wrote: in tinyos, events can be preempted by other events. So i think the event sendone() is called immediately, On 6/15/06, Shiyuan < [EMAIL PROTECTED]> wrote: > When we say "signal Send.sendDone(...)", does this put an event in an event > queue - like windows mechnism? Or it will excute the event handler "event > result_t SendMsg.sendDone()" function body immediately? > > Thanks. > > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- regards, Aditya Bhave ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] error when upgrading to tinyos-2.0
Jonny, You may need to add the --ignoreos option to the rpm command. - Dongyan On 4/14/06, Jonny.Ma <[EMAIL PROTECTED]> wrote: > hi, > > I have come across error when tried to upgrade to tinyos-2.0 following > the step of its docs. The problem happened when I tried to install > tinyos-tools-1.2.1-3.cygwin.i386.rpm package. Could anyone help me and > thanks a lot. By the way, I'v already upgraded to tinyos1.1.15 before > tinyos2.0 upgrading.(Upgraded cygwin as > http://www.tinyos.net/scoop/special/howto_upgrade_cygwin showed) > > $ rpm -ivh --force tinyos-tools-1.2.1-3.cygwin.i386.rpm > Preparing...### [100%] > package tinyos-tools-1.2.1-3 is intended for a cygwin operating system > If I try the final step to upgrade the tinyos2.0 source tree, I failed too. : > ( > > $ rpm -ivh tinyos-2.0.0beta1-3.cygwin.noarch.rpm > error: Failed dependencies: > tinyos-tools >= 1.2.1 is needed by tinyos-2.0.0beta1-3 > > Looking forward to your replay, and thanks for advancing again ! > > - > Jonny.Ma > > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] help on running ../contrib/xbow/apps/XMesh/XMDA300
The red LED is on because the MDA300 sensor board is not connected to your mote on the mib 510. On 4/12/06, chandresh parekh <[EMAIL PROTECTED]> wrote: > > Hi all, > > I am trying to run XMDA300 app under ../contrib/xbow/apps/XMesh/. > > Here is what I did and what I observed. > > I programmed three motes with > opt/tinyos-1.x/contrib/xbow/apps/XMesh/XMDA300 application > ,using command > make mica2 install,0 (for base station) 10 (second mote)11 (third mote) > mib510,com1 > > the screen shot of installation is given below: > [EMAIL PROTECTED] > /opt/tinyos-1.x/contrib/xbow/apps/XMesh/XMDA300 > $ make mica2 install,0 mib510,com1 > mkdir -p build/mica2 > compiling XMDA300 to a mica2 binary > ncc -o build/mica2/main.exe -Os > -I%T/../contrib/xbow/tos/platform/mica2 -I%T/../ > contrib/xbow/tos/CC1000RadioAck > -I%T/../contrib/xbow/tos/lib/ReliableRoute -I%T/ > lib/Queue -DTEN_X -I%T/../contrib/xbow/tos/interfaces > -I%T/../contrib/xbow/tos/s > ystem -I%T/../contrib/xbow/tos/lib > -I%T/../contrib/xbow/tos/sensorboards/mda300 > -I%T/lib/Broadcast -I%T/../contrib/xbow/tos/lib/XLib > -finline-limit=10 -W > all -Wshadow -DDEF_TOS_AM_GROUP=0x88 -Wnesc-all -target=mica2 > -fnesc-cfile=build > /mica2/app.c -board=mda300 > -DCC1K_DEFAULT_FREQ=RADIO_916BAND_CHANNEL_00 -DRADIO_ > XMIT_POWER=0xFF -I%T/lib/Deluge > -DIDENT_PROGRAM_NAME=\"XMDA300\" -DIDENT_USER_I > D=\"Administrator\" -DIDENT_HOSTNAME=\"piloo\" -DIDENT_USER_HASH=0x0a75adf5L > -DI > DENT_UNIX_TIME=0x443cd8c4L -DIDENT_UID_HASH=0xbc772c55L XMDA300.nc -lm > C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/sensorboards/mda300/SamplerM.nc > :515: warning: `Sample.dataReady' called asynchronously from > `Battery.dataReady' > C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/CC1000RadioAck/CC1000RadioIntM. > nc:187: warning: non-atomic accesses to shared variable `usRSSIVal': > C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/CC1000RadioAck/CC1000RadioIntM. > nc:953: warning: non-atomic read > C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/CC1000RadioAck/CC1000RadioIntM. > nc:183: warning: non-atomic accesses to shared variable `bTxPending': > C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/CC1000RadioAck/CC1000RadioIntM. > nc:454: warning: non-atomic read > XMDA300M.nc: In function `XMDA300M$StdControl$init': > XMDA300M.nc:236: warning: unused variable `i' > C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/lib/ReliableRoute/MultiHopEWMA. > nc: In function `MultiHopEWMA$SendRouteTask': > C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/lib/ReliableRoute/MultiHopEWMA. > nc:444: warning: unused variable `sortTbl' > C:/tinyos/cygwin/opt/tinyos-1.x/tos/system/RealMain.nc: In function `main': > C:/tinyos/cygwin/opt/tinyos-1.x/tos/interfaces/StdControl.nc:63: > warning: `resul > t' might be used uninitialized in this function > XMDA300M.nc: In function `XMDA300M$Sample$dataReady': > XMDA300M.nc:480: warning: unused variable `i' > compiled XMDA300 to build/mica2/main.exe >28284 bytes in ROM > 2402 bytes in RAM > avr-objcopy --output-target=srec build/mica2/main.exe build/mica2/main.srec > avr-objcopy --output-target=ihex build/mica2/main.exe build/mica2/main.ihex > writing TOS image > set-mote-id build/mica2/main.srec build/mica2/main.srec.out-0 0 > installing mica2 binary using mib510 > uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128 > --wr_fuse_e=f > f --erase --upload if=build/mica2/main.srec.out-0 > Firmware Version: 2.1 > Atmel AVR ATmega128 is found. > Uploading: flash > Fuse High Byte set to 0xd8 > Fuse Extended Byte set to 0xff > rm -f build/mica2/main.exe.out-0 build/mica2/main.srec.out-0 > installing mica2 bootloader using mib510 > uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128 > --wr_fuse_e=f > f --upload > if=/opt/tinyos-1.x/tos/lib/Deluge/TOSBoot/build/mica2/main.ihex > Firmware Version: 2.1 > Atmel AVR ATmega128 is found. > Uploading: flash > Fuse High Byte set to 0xd8 > Fuse Extended Byte set to 0xff > > Next, I changed ran the xlisten applicatin and the screen shot of running > xlisten is below: > > [EMAIL PROTECTED] > /opt/tinyos-1.x/contrib/xbow/beta/tools/src/xlisten > $ xlisten -r -p -c -b=mica2 -s=com1 > xlisten Ver:$Id: xlisten.c,v 1.13 2004/08/22 23:20:30 mturon Exp $ > Using params: [baud=0x1001] [raw] [parsed] [cooked] > com1 input stream opened > 7e427d5e0033881d0a000c81060a00b1014206741caa090e08a3073692 > [ > 39] > mda300 error: unknown packet_id (6) > MDA300 Error: unknown packet id (6) > 7e427d5e000388100a000d0200990b00ff004aa2 [26] > 7e427d5e0033881d0a000e81060a00b1014206731cfe08c8081b094b24 > [ > 39] > mda300 error: unknown packet_id (6) > MDA300 Error: unknown packet id (6) > 7e427d5e0033881d0b000f81060b0aa0013506711c860868082a08e1f3 > [ > 39] > mda300 error: unknown packet_id (6) > MDA300 Error: unknown packet id (6) > 7e427d5e0033881d0a001081060a00b2014206741c820
Re: [Tinyos-help] ice-gdb error under tinyos 2.0 toolchain
I see. My avarice is version 2.3 and that must be the reason. Thanks David. - Dongyan On 4/10/06, David Gay <[EMAIL PROTECTED]> wrote: > On 4/5/06, Dongyan Chen <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I was using GDB with mkII JTAG ICE to debug my programs under > > tinyos2 toolchain. However when starting ice-gdb there are the > > following errors: > > That command is not in the gdb-avarice-script distributed with avarice > 2.4. Use avarice 2.4 (it seems the stuff it was trying to enable has > disappeared from current gdb's - it improved the performance of the > step and next commands). > > David Gay > > > > > $ ice-gdb > > JTAG config starting. > > Found a device: JTAGICEmkII > > Serial number: 00:a0:00:00:35:89 > > Reported JTAG device ID: 0x9702 > > ... > > Waiting for connection on port 6423. > > GNU gdb 6.3 > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain > > conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "--host=i686-pc-cygwin --target=avr". > > /usr/share/avarice/gdb-avarice-script:3: Error in sourced command file: > > Undefined set remote command: "step-over-range-packet enable". Try "help > > set re > > mote". > > > > I deleted the trouble-making line from gdb-avarice-script and > > everything seems to be working fine. But who can tell me what the "set > > remote step-over-range-packet enable" really means and what's the > > consequence of deleting it from the script? Any help is greatly > > appreciated. > > > > - Dongyan > > > > ___ > > Tinyos-help mailing list > > Tinyos-help@Millennium.Berkeley.EDU > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Help on installing XMesh/XMDA300 on mica2 motes
Chandresh, You need to copy the entire contrib/xbow folder to your windows machine rather than just the xbow/apps folder. The XMesh app uses interfaces & modules under contrib/xbow/tos/. - Dongyan On 4/10/06, chandresh parekh <[EMAIL PROTECTED]> wrote: > > Hi all, > > I tried to download tinyos-1.x/contrib from my windows machine and got the > following errors: > > [EMAIL PROTECTED] /opt > $ cvs > -d:pserver:[EMAIL PROTECTED]:/cvsroot/tinyos > login > Logging in to > :pserver:[EMAIL PROTECTED]:2401/cvsroot/tinyos > CVS password: > cvs [login aborted]: end of file from server (consult above messages if any) > > > $ cvs -z3 > -d:pserver:[EMAIL PROTECTED]:/cvsroot/tinyos co > -P tinyos > 1.x/contrib > cvs checkout: warning: failed to open /home/Administrator/.cvspass for > reading: > No such file or directory > cvs [checkout aborted]: end of file from server (consult above messages if > any) > > After this failure, I managed to download the folder on a linux machine. > Then, I copied the entire folder to ../tinyos-1.x/contrib/xbow/apps/ and > hoping it should work. > But I got the followng sequence of erros: > > [EMAIL PROTECTED] > /opt/tinyos-1.x/contrib/xbow/apps/XMesh/XMDA300 > $ make mica2 install,10 mib510,com1 > mkdir -p build/mica2 > compiling XMDA300 to a mica2 binary > ncc -o build/mica2/main.exe -Os -finline-limit=10 -Wall -Wshadow > -DDEF_TOS_A > M_GROUP=0x7d -Wnesc-all -target=mica2 -fnesc-cfile=build/mica2/app.c > -board=mda3 > 00 -DCC1K_DEFAULT_FREQ=RADIO_916BAND_CHANNEL_00 > -DRADIO_XMIT_POWER=0xFF -I%T/lib > /Deluge -DIDENT_PROGRAM_NAME=\"XMDA300\" > -DIDENT_USER_ID=\"Administrator\" -DIDE > NT_HOSTNAME=\"piloo\" -DIDENT_USER_HASH=0x0a75adf5L > -DIDENT_UNIX_TIME=0x443a8612 > L -DIDENT_UID_HASH=0x280bd6ccL XMDA300.nc -lm > XMDA300M.nc:122: C file XCommand not found > XMDA300M.nc:125: C file sensorboard not found > XMDA300M.nc:139: interface XCommand not found > C:/tinyos/cygwin/opt/tinyos-1.x/tos/interfaces/RouteControl.nc:42: > expected inte > rface `XCommand', but got interface 'RouteControl' > XMDA300M.nc:143: interface Sample not found > C:/tinyos/cygwin/opt/tinyos-1.x/tos/interfaces/RouteControl.nc:42: > expected inte > rface `Sample', but got interface 'RouteControl' > XMDA300M.nc:150: interface Relay not found > C:/tinyos/cygwin/opt/tinyos-1.x/tos/interfaces/Timer.nc:42: expected > interface ` > Relay', but got interface 'Timer' > XMDA300M.nc: In function `StdControl.start': > XMDA300M.nc:285: interface has no command or event named `getSample' > XMDA300M.nc:285: `TEMPERATURE' undeclared (first use in this function) > XMDA300M.nc:285: (Each undeclared identifier is reported only once > XMDA300M.nc:285: for each function it appears in.) > XMDA300M.nc:285: `SAMPLER_DEFAULT' undeclared (first use in this function) > XMDA300M.nc:287: interface has no command or event named `getSample' > XMDA300M.nc:287: `HUMIDITY' undeclared (first use in this function) > XMDA300M.nc:289: interface has no command or event named `getSample' > XMDA300M.nc:289: `BATTERY' undeclared (first use in this function) > XMDA300M.nc:293: interface has no command or event named `getSample' > XMDA300M.nc:293: `ANALOG' undeclared (first use in this function) > XMDA300M.nc:293: `EXCITATION_33' undeclared (first use in this function) > XMDA300M.nc:295: interface has no command or event named `getSample' > XMDA300M.nc:297: interface has no command or event named `getSample' > XMDA300M.nc:299: interface has no command or event named `getSample' > XMDA300M.nc:299: `DELAY_BEFORE_MEASUREMENT' undeclared (first use in this > functi > on) > XMDA300M.nc:301: interface has no command or event named `getSample' > XMDA300M.nc:303: interface has no command or event named `getSample' > XMDA300M.nc:305: interface has no command or event named `getSample' > XMDA300M.nc:307: interface has no command or event named `getSample' > XMDA300M.nc:307: `AVERAGE_FOUR' undeclared (first use in this function) > XMDA300M.nc:307: `EXCITATION_25' undeclared (first use in this function) > XMDA300M.nc:309: interface has no command or event named `getSample' > XMDA300M.nc:311: interface has no command or event named `getSample' > XMDA300M.nc:313: interface has no command or event named `getSample' > XMDA300M.nc:315: interface has no command or event named `getSample' > XMDA300M.nc:317: interface has no command or event named `getSample' > XMDA300M.nc:319: interface has no command or event named `getSample' > XMDA300M.nc:319: `EXCITATION_50' undeclared (first use in this function) > XMDA300M.nc:319: `EXCITATION_ALWAYS_ON' undeclared (first use in this > function) > XMDA300M.nc:324: interface has no command or event named `getSample' > XMDA300M.nc:324: `DIGITAL' undeclared (first use in this function) > XMDA300M.nc:324: `RESET_ZERO_AFTER_READ' undeclared (first use in this > function) > XMDA300M.nc:324: `FALLING_EDGE' undeclared (first use in this function) > XMDA300M.nc:326: interface has no command or event named `getSample' > XMDA300M.nc:326:
Re: [Tinyos-help] GIO -- Output Voltage.
Pinky,
You may use the MSP430GeneralIO interface for telosb/tmote. Suppose
you are using P6.3 to control your sensor:
In your module:
...
uses {
interface MSP430GeneralIO as P63;
...
}
...
call P63.selectIOFunc();
call P63.makeOutput();
call P63.setHigh();
...
In your configuration, wire YOUR_COMPONENT.P63 -> MSP430GeneralIOC.port63.
- Dongyan
On 4/6/06, pinky tejwani <[EMAIL PROTECTED]> wrote:
> Hi all,
>Thanks for all the help with Digital output voltage.
>
> I recently moved from 1.1.13 version to 1.1.15 version and now the
> same code does not work. I looked in to the hardware.h file under
> telosb platform, it says TOSH
> command are not used anymore. Instead use the commands like P2OUT =
> 0x01 to toggle the output.
> I tried this, and unfortunately it does not work either. I am still
> debugging the code, but would like to know any thoughts or facts from
> the members here.
>
> Also can anyone help me with using MSP430GeneralIO interface ? Can
> this be used with TelosB Platform or does it needs some changes in the
> makerules or download some more binary utilities ?
>
> I appreciate the effort. Hope to hear from someone soon.
>
> Thanks,
> Pinky Tejwani.
>
> On 2/15/06, Robert Szewczyk <[EMAIL PROTECTED]> wrote:
> > Look at the page 29 of MSP430 datasheet -- it has the data about how
> > much current the MCU can source and sink through the IO pins
> > (http://focus.ti.com/lit/ds/symlink/msp430f169.pdf).
> >
> > Rob
> >
> > On 2/15/06, Michael Schippling <[EMAIL PROTECTED]> wrote:
> > > also, once all that is settled, make sure that you are not
> > > trying to draw too much current from the pin to turn on your
> > > sensor. The ATMEGA specs say 40mA max, I don't have the telos
> > > chip specs but it's probably similar. Anyway I think that is
> > > pushing it, I'd be more comfortable with <10mA.
> > > MS
> > >
> > > Matthew J Whelan wrote:
> > > > The output voltage of the GIO set high should be the about same as your
> > > > battery voltage. Do you have the P2.0 pin setup right?
> > > > P2SEL &= ~(0x01);//Sets P2.0 to GIO
> > > > P2DIR |= 0x01; //Sets P2.0 to output
> > > > P2OUT |= 0x01; // Sets P2.0 high
> > > > What about the P6.3 (since the ADC3 input is wired to pin 10 as well)?
> > > > P6SEL &= ~(1<<3); //Sets P6.3 to GIO
> > > > P6DIR |= ~(1<<3); //Sets P6.3 to input
> > > >
> > > > Is there some significant load on your signal which is causing it to
> > > > drop in voltage?
> > > >
> > > > Regards,
> > > > Matt
> > > >
> > > >
> > > > [EMAIL PROTECTED] wrote: -
> > > >
> > > > To: Tinyos-help@Millennium.Berkeley.EDU
> > > > From: pinky tejwani <[EMAIL PROTECTED]>
> > > > Sent by: [EMAIL PROTECTED]
> > > > Date: 02/15/2006 02:21PM
> > > > Subject: [Tinyos-help] GIO -- Output Voltage.
> > > >
> > > > Hello All,
> > > > I have written a code for bit-banging using the TOSH macros for
> > > > General I/O pins.
> > > > Platform - TelosB/TmoteSky
> > > > The voltage that I get on the pin 10 of U2 connector is 1.3 or 1.5 V
> > > > maximum.
> > > >
> > > > The aim of the exercise is to use one of the digital output pins to
> > > > switch on/off a sensor. Can someone tell me if there is a way to
> > > > make
> > > > the digital output voltage to be above 2 V ?
> > > > ( I am trying to avoid using an external circuit to do that )
> > > >
> > > > Hope to hear from someone.
> > > >
> > > > Thanks,
> > > > Pinky Tejwani.
> > > > Clemson University.
> > > >
> > > > ___
> > > > Tinyos-help mailing list
> > > > Tinyos-help@Millennium.Berkeley.EDU
> > > >
> > > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ___
> > > > Tinyos-help mailing list
> > > > Tinyos-help@Millennium.Berkeley.EDU
> > > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> > > ___
> > > Tinyos-help mailing list
> > > Tinyos-help@Millennium.Berkeley.EDU
> > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> > >
> >
> > ___
> > Tinyos-help mailing list
> > Tinyos-help@Millennium.Berkeley.EDU
> > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
>
>
> --
> Pinky Tejwani
> Graduate Student
> Clemson University
> [EMAIL PROTECTED]
> #864-650-7835
>
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/list
[Tinyos-help] ice-gdb error under tinyos 2.0 toolchain
Hi all, I was using GDB with mkII JTAG ICE to debug my programs under tinyos2 toolchain. However when starting ice-gdb there are the following errors: $ ice-gdb JTAG config starting. Found a device: JTAGICEmkII Serial number: 00:a0:00:00:35:89 Reported JTAG device ID: 0x9702 ... Waiting for connection on port 6423. GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i686-pc-cygwin --target=avr". /usr/share/avarice/gdb-avarice-script:3: Error in sourced command file: Undefined set remote command: "step-over-range-packet enable". Try "help set re mote". I deleted the trouble-making line from gdb-avarice-script and everything seems to be working fine. But who can tell me what the "set remote step-over-range-packet enable" really means and what's the consequence of deleting it from the script? Any help is greatly appreciated. - Dongyan ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Help on multi-hop with XsensorMDA300
You can try WMEWMAMultihopRouter under tos/lib/MintRoute. On 3/31/06, chandresh parekh <[EMAIL PROTECTED]> wrote: > > Hi All, > > I am a masters student. I have been using Mica2+MDA300 to collect strain > readings from strain sensor to PC. I program base station (gateway- the mote > connected to PC ) with TOSBase. The node with strain sensor is programmed > with XsensorMDA300. This works fine for single hop communication. But I want > to incorporate multi-hop in my application. Any idea on how can I achieve > this? > > > Regards, > Chandresh > > > > > > New Yahoo! Messenger with Voice. Call regular phones from your PC and save > big. > > > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems switching from Tinyos 2.x to Tinyos 1.x
Thanks Phil. I'll try that. In fact I'm switching back and forth from T2 to T1, so my current solution is to use two separate .bashrc files for T2 and T1. When working with T1 code, I use make tmote, then source ~/T2.bashrc, then make tmote reinstall so I can still use the new bsl. As of the serial forwarder, the following is the error message after the upgrade: $ java.lang.NoClassDefFoundError: javax/comm/SerialPortEventListener at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:537) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at net.tinyos.packet.BuildSource.makeSerial(BuildSource.java:360) at net.tinyos.packet.BuildSource.makeArgsSerial(BuildSource.java:349) at net.tinyos.packet.BuildSource.makePacketSource(BuildSource.java:147) at net.tinyos.packet.BuildSource.makePhoenix(BuildSource.java:87) at net.tinyos.sf.SFListen.run(SFListen.java:84) Serial Forwarder Exited Normally I thought it is the incorrect classpath specified in T2, but after changing it back things remain the same. Thanks, - Dongyan On 12/6/05, Philip Levis <[EMAIL PROTECTED]> wrote: > On Mon, 2005-12-05 at 14:13 -0600, Dongyan Chen wrote: > > Dear all, > > > > When switching back to Tinyos-1.x tree, I changed the environment > > variables as instructed in > > http://www.tinyos.net/dist-2.0.0/tinyos-2.0.0pre2/doc/html/upgrade-tinyos.html. > > While my programs compile, I can't upload them to TMote. The following > > is the error: > > > > $ make tmote reinstall > > cp build/telosb/main.ihex build/telosb/main.ihex.out > > found mote on COM5 (using bsl,auto) > > installing telosb bootloader using bsl > > msp430-bsl --telosb -c 4 -r -e -I -p > > /opt/tinyos-1.x/tos/../beta/Deluge/Deluge/T > > OSBoot/build/telosb/main.ihex > > MSP430 Bootstrap Loader Version: 2.0 > > > > USAGE: /opt/msp430/bin/msp430-bsl [options] [file] > > Version: 2.0 > > > > If "-" is specified as file the data is read from the stdinput. > > A file ending with ".txt" is considered to be in TI-Text format, > > '.a43' and '.hex' as IntelHex and all other filenames are > > considered as ELF files. > > > > General options: > > -h, --helpShow this help screen. > > ... > > > > I believe it's coz the msp430-bsl has been upgraded by T2 and the > > options are changed. I can get by this with changing the environment > > variables back to 2.0 version and do a make tmote reinstall, which > > works. However, is there any cleverer way to do this? > > The 2.x install process replaces a few elements of the toolchain. E.g., > ncc has been moved out of the nesC compiler and into TinyOS (as it's > what has some TinyOS-specific options). > > So switching back to 1.x require that you replace those changed tools > with the 1.x versions. In the case of bsl, it's in 1.x/tools/src/mspgcc- > pybsl. Just be sure to check that when you reinstall it, it's the one > that the make system is calling (it's possible to get into a situation > where you install the 1.x version, but in a different place so the make > system continues to call the 2.x one). > > > I also found that the SerialForwarder stopped working after the > > upgrade. Anyone has the same experience? > > How did it stop working? > > Phil > > > ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problems switching from Tinyos 2.x to Tinyos 1.x
Dear all, When switching back to Tinyos-1.x tree, I changed the environment variables as instructed in http://www.tinyos.net/dist-2.0.0/tinyos-2.0.0pre2/doc/html/upgrade-tinyos.html. While my programs compile, I can't upload them to TMote. The following is the error: $ make tmote reinstall cp build/telosb/main.ihex build/telosb/main.ihex.out found mote on COM5 (using bsl,auto) installing telosb bootloader using bsl msp430-bsl --telosb -c 4 -r -e -I -p /opt/tinyos-1.x/tos/../beta/Deluge/Deluge/T OSBoot/build/telosb/main.ihex MSP430 Bootstrap Loader Version: 2.0 USAGE: /opt/msp430/bin/msp430-bsl [options] [file] Version: 2.0 If "-" is specified as file the data is read from the stdinput. A file ending with ".txt" is considered to be in TI-Text format, '.a43' and '.hex' as IntelHex and all other filenames are considered as ELF files. General options: -h, --helpShow this help screen. ... I believe it's coz the msp430-bsl has been upgraded by T2 and the options are changed. I can get by this with changing the environment variables back to 2.0 version and do a make tmote reinstall, which works. However, is there any cleverer way to do this? I also found that the SerialForwarder stopped working after the upgrade. Anyone has the same experience? Thanks a lot in advance. - Dongyan ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems upgrading to TinyOS2.0
Kristin and David: Thanks for the suggestion. The operating system is xp. However, even if the error message is ignored, there is error at the last step when installing tinyos-2.0.0pre2-1: $ rpm -Uvh nesc-1.2-1.cygwin.i386.rpm Preparing...### [100%] package nesc-1.2-1 is intended for a cygwin_nt-5.1 operating system [EMAIL PROTECTED] /cygdrive/c/downloads $ rpm -ivh --force tinyos-tools-1.2.0-2.cygwin.i386.rpm Preparing...### [100%] package tinyos-tools-1.2.0-2 is intended for a cygwin_nt-5.1 operating s ystem [EMAIL PROTECTED] /cygdrive/c/downloads $ rpm -ivh tinyos-2.0.0pre2-1.cygwin.noarch.rpm error: Failed dependencies: tinyos-tools >= 1.2.0 is needed by tinyos-2.0.0pre2-1 nesc >= 1.2 is needed by tinyos-2.0.0pre2-1 avr-binutils >= 2.15 is needed by tinyos-2.0.0pre2-1 avr-gcc >= 3.4 is needed by tinyos-2.0.0pre2-1 [EMAIL PROTECTED] /cygdrive/c/downloads $ rpm -ivh --force tinyos-2.0.0pre2-1.cygwin.noarch.rpm error: Failed dependencies: tinyos-tools >= 1.2.0 is needed by tinyos-2.0.0pre2-1 nesc >= 1.2 is needed by tinyos-2.0.0pre2-1 avr-binutils >= 2.15 is needed by tinyos-2.0.0pre2-1 avr-gcc >= 3.4 is needed by tinyos-2.0.0pre2-1 On 11/9/05, Kristin Wright <[EMAIL PROTECTED]> wrote: > If your cygwin dll is out-of-date, another error pops up: an error box > that indicates windows can't find the correct dll to execute the > program (I forget exactly what point this box comes up) . > > The error that you have pops up if you're on a non-xp system. What > version of windows are you running? > > In my experience, giving the --ignoreos argument to rpm (as David > mentioned) will allow the rpms to be installed with no ill effects > during or after. > > -kw > > On 11/9/05, David Gay <[EMAIL PROTECTED]> wrote: > > On 11/9/05, Dongyan Chen <[EMAIL PROTECTED]> wrote: > > > package msp430tools-python-tools-1.0-1 is intended for a > > > cygwin_nt-5.1 o > > > perating system > > > > > > Does this mean the cygwin version is out of date? Any input is > > > appreciated. > > > > I'm unclear on the exact cause (Kristin?), but you can add --ignoreos > > to shut it up... > > > > David Gay > > > > ___ > > Tinyos-help mailing list > > Tinyos-help@Millennium.Berkeley.EDU > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problems upgrading to TinyOS2.0
Hi, When upgrading to T2, we met the following errors: [EMAIL PROTECTED] /cygdrive/c/downloads $ ls avarice-2.3.20041206cvs-1.cygwin.i386.rpm avr-binutils-2.15tinyos-3.cygwin.i386.rpm avr-gcc-3.4.3-1.cygwin.i386.rpm avr-insight-6.3-1.cygwin.i386.rpm avr-libc-1.2.3-1.cygwin.i386.rpm msp430tools-base-0.1-20050607.cygwin.i386.rpm msp430tools-binutils-2.16-20050607.cygwin.i386.rpm msp430tools-gcc-3.2.3-20050607.cygwin.i386.rpm msp430tools-libc-20050308cvs-20050608.cygwin.i386.rpm msp430tools-python-tools-1.0-1.cygwin.noarch.rpm [EMAIL PROTECTED] /cygdrive/c/downloads $ rpm -Uvh --force *.rpm Preparing...### [100%] package msp430tools-base-0.1-20050607 is intended for a cygwin_nt-5.1 op erating system package msp430tools-binutils-2.16-20050607 is intended for a cygwin_nt-5 .1 operating system package msp430tools-gcc-3.2.3-20050607 is intended for a cygwin_nt-5.1 o perating system package avarice-2.3.20041206cvs-1 is intended for a cygwin_nt-5.1 operat ing system package avr-binutils-2.15tinyos-3 is intended for a cygwin_nt-5.1 operat ing system package avr-gcc-3.4.3-1 is intended for a cygwin_nt-5.1 operating system package avr-insight-6.3-1 is intended for a cygwin_nt-5.1 operating syst em package avr-libc-1.2.3-1 is intended for a cygwin_nt-5.1 operating syste m package msp430tools-libc-20050308cvs-20050608 is intended for a cygwin_n t-5.1 operating system package msp430tools-python-tools-1.0-1 is intended for a cygwin_nt-5.1 o perating system Does this mean the cygwin version is out of date? Any input is appreciated. - Dongyan ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
