Re: [Tinyos-help] Problem with crossbow motes
I tried to compile an application by the program notepad and I got some errors because I use some interfaces (Boot, Timer) that isn't recognized when compiled. So, I tried compile by the tinyos-2.1.1 installed in Ubuntu Linux. Later I tried to load by the Moteconfig program the executable (main.exe) generated from this compiling, so I got the following message: *platform N/A does not adapt with current MCU 128. Please check it. * Someone can help me? Best Regards, 2011/9/6 Rafael de Oliveira Costa rafaeldeoliveiraco...@gmail.com Marianna, this command only deploy the application to the mote plugged on the basestation. Rafael de Oliveira Costa M.Sc. Student PPGI / DCC - iNCE/ UFRJ Rio de Janeiro, RJ, Brazil The first step to getting the things you want out of life is this : decide what you want Ben Stein On Mon, Sep 5, 2011 at 9:17 PM, Marianna Araujo marianna.angel...@gmail.com wrote: Thanks for the reply. It worked to submit the Blink application, but I have a doubt. When I send this application only the base station receives it? Best Regards, 2011/9/5 Rafael de Oliveira Costa rafaeldeoliveiraco...@gmail.com Hi Marianna, here i'm using crossbow's motes and they works fine. to submit an application type make micaz install,1 mib510,/dev/ttyUSB0. Rafael de Oliveira Costa M.Sc. Student PPGI / DCC - iNCE/ UFRJ Rio de Janeiro, RJ, Brazil The first step to getting the things you want out of life is this : decide what you want Ben Stein On Mon, Sep 5, 2011 at 11:32 AM, Marianna Araujo marianna.angel...@gmail.com wrote: I started using the crossbow's motes (MTS420 platform - micaz/mica2) and I have been problem. I tried send an application for the sources and now one of them isn't been recognized in network. I rebooted the other sources and they were ok. However, exceptionally this source, did not work. I've tried to upload the firmware, but I really do not know which firmware suitable for him. Can you tell me what should I do? Another thing, I couldn't submit an application for the motes, for example the blink application. In the notepad, after to compiling, I made make micaz reinstall mib520 (because I use USB port), com3 (the lower port) and I got the following error MIB520 must be *defined, try make micaz help. Stop. * Best Regards, -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Marianna Araújo -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problem with crossbow motes
I started using the crossbow's motes (MTS420 platform - micaz/mica2) and I have been problem. I tried send an application for the sources and now one of them isn't been recognized in network. I rebooted the other sources and they were ok. However, exceptionally this source, did not work. I've tried to upload the firmware, but I really do not know which firmware suitable for him. Can you tell me what should I do? Another thing, I couldn't submit an application for the motes, for example the blink application. In the notepad, after to compiling, I made make micaz reinstall mib520 (because I use USB port), com3 (the lower port) and I got the following error MIB520 must be *defined, try make micaz help. Stop. * Best Regards, -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problem with crossbow motes
Thanks for the reply. It worked to submit the Blink application, but I have a doubt. When I send this application only the base station receives it? Best Regards, 2011/9/5 Rafael de Oliveira Costa rafaeldeoliveiraco...@gmail.com Hi Marianna, here i'm using crossbow's motes and they works fine. to submit an application type make micaz install,1 mib510,/dev/ttyUSB0. Rafael de Oliveira Costa M.Sc. Student PPGI / DCC - iNCE/ UFRJ Rio de Janeiro, RJ, Brazil The first step to getting the things you want out of life is this : decide what you want Ben Stein On Mon, Sep 5, 2011 at 11:32 AM, Marianna Araujo marianna.angel...@gmail.com wrote: I started using the crossbow's motes (MTS420 platform - micaz/mica2) and I have been problem. I tried send an application for the sources and now one of them isn't been recognized in network. I rebooted the other sources and they were ok. However, exceptionally this source, did not work. I've tried to upload the firmware, but I really do not know which firmware suitable for him. Can you tell me what should I do? Another thing, I couldn't submit an application for the motes, for example the blink application. In the notepad, after to compiling, I made make micaz reinstall mib520 (because I use USB port), com3 (the lower port) and I got the following error MIB520 must be *defined, try make micaz help. Stop. * Best Regards, -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] [tinyos-help] Problem with crossbow motes
I started using the crossbow's motes (MTS400 platform - micaz/mica2) and I have problem with them. I tried send a Blink application for the sources and now they aren't been recognized in network. In moteview program, the sources not been recognized, only the gateway. The sources, only the red and orange lights are lit. Is there any way to make them the way they came from the factory? Best Regards, -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] [tinyos-help] Problem with crossbow motes
I resolved the problem 2011/9/1 Marianna Araujo marianna.angel...@gmail.com I started using the crossbow's motes (MTS400 platform - micaz/mica2) and I have problem with them. I tried send a Blink application for the sources and now they aren't been recognized in network. In moteview program, the sources not been recognized, only the gateway. The sources, only the red and orange lights are lit. Is there any way to make them the way they came from the factory? Best Regards, -- Marianna Araújo -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problem with PowerTOSSIM-Z
Hello all, I'm trying to use the PowerTossimZ, but later that I downloaded the module and replaced the files according the README, I get error whenever I run any application, with make micaz sim For example: mkdir -p simbuild/micaz placing object files in simbuild/micaz writing XML schema to app.xml compiling RadioCountToLedsAppC to object file sim.o ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=10 -DIDENT_APPNAME=\RadioCountToLed\ -DIDENT_USERNAME=\marianna\ -DIDENT_HOSTNAME=\marianna-deskto\ -DIDENT_USERHASH=0x30315190L -DIDENT_TIMESTAMP=0x4dee76e9L -DIDENT_UIDHASH=0x548aa066L -Wno-nesc-data-race RadioCountToLedsAppC.nc -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml In file included from /opt/tinyos-2.x/tos/lib/tossim/MainC.nc:64, from RadioCountToLedsAppC.nc:47: In component `TossimActiveMessageP': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:82: conflicting types for `AMSend.getPayload' /opt/tinyos-2.x/tos/interfaces/AMSend.nc:135: previous declaration of `AMSend.getPayload' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: In function `AMSend.getPayload': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:83: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: At top level: /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:86: `getPayload' is not in interface `Receive' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: In function `Receive.getPayload': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:87: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: At top level: /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:90: `payloadLength' is not in interface `Receive' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:94: `getPayload' is not in interface `Snoop' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: In function `Snoop.getPayload': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:95: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: At top level: /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:98: `payloadLength' is not in interface `Snoop' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: In function `Model.receive': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:113: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: At top level: /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:187: conflicting types for `Packet.getPayload' /opt/tinyos-2.x/tos/interfaces/Packet.nc:126: previous declaration of `Packet.getPayload' In file included from RadioCountToLedsAppC.nc:47: In component `RadioCountToLedsC': RadioCountToLedsC.nc: In function `MilliTimer.fired': RadioCountToLedsC.nc:88: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast make: ** [sim-exe] Erro 1 Anyone knows tell me how I resolved this? Best Regards, -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problem with PowerTOSSIM-Z
rectified, I have just error in the RadioCountToLeds application. 2011/6/7 Marianna Araujo marianna.angel...@gmail.com Hello all, I'm trying to use the PowerTossimZ, but later that I downloaded the module and replaced the files according the README, I get error whenever I run any application, with make micaz sim For example: mkdir -p simbuild/micaz placing object files in simbuild/micaz writing XML schema to app.xml compiling RadioCountToLedsAppC to object file sim.o ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=10 -DIDENT_APPNAME=\RadioCountToLed\ -DIDENT_USERNAME=\marianna\ -DIDENT_HOSTNAME=\marianna-deskto\ -DIDENT_USERHASH=0x30315190L -DIDENT_TIMESTAMP=0x4dee76e9L -DIDENT_UIDHASH=0x548aa066L -Wno-nesc-data-race RadioCountToLedsAppC.nc -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml In file included from /opt/tinyos-2.x/tos/lib/tossim/MainC.nc:64, from RadioCountToLedsAppC.nc:47: In component `TossimActiveMessageP': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:82: conflicting types for `AMSend.getPayload' /opt/tinyos-2.x/tos/interfaces/AMSend.nc:135: previous declaration of `AMSend.getPayload' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: In function `AMSend.getPayload': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:83: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: At top level: /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:86: `getPayload' is not in interface `Receive' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: In function `Receive.getPayload': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:87: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: At top level: /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:90: `payloadLength' is not in interface `Receive' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:94: `getPayload' is not in interface `Snoop' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: In function `Snoop.getPayload': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:95: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: At top level: /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:98: `payloadLength' is not in interface `Snoop' /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: In function `Model.receive': /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:113: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc: At top level: /opt/tinyos-2.x/tos/lib/tossim/TossimActiveMessageP.nc:187: conflicting types for `Packet.getPayload' /opt/tinyos-2.x/tos/interfaces/Packet.nc:126: previous declaration of `Packet.getPayload' In file included from RadioCountToLedsAppC.nc:47: In component `RadioCountToLedsC': RadioCountToLedsC.nc: In function `MilliTimer.fired': RadioCountToLedsC.nc:88: warning: passing argument 2 of `Packet.getPayload' makes integer from pointer without a cast make: ** [sim-exe] Erro 1 Anyone knows tell me how I resolved this? Best Regards, -- Marianna Araújo -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Fwd: Fwd: [tinyos-help] Get the level energy in Wireless Sensor Network
-- Forwarded message -- From: Marianna Araujo marianna.angel...@gmail.com Date: 2011/5/18 Subject: Re: [Tinyos-help] Fwd: [tinyos-help] Get the level energy in Wireless Sensor Network To: Antonio Linan ali...@zolertia.com I'd like know how obtain the power level of the nodes in a WSN. I imagine that TinyOS provides that. Anyone know how? Regards, 2011/5/12 Antonio Linan ali...@zolertia.com Energy levels of a sensor or a mote? If you mean the sensor, oddly, for example the Sht1X has a register which can be read to know when VCC is below the recommended level. If you mean reading the mote's energy.. reading the battery level periodically? using the ADC ports? It would help a LOT if you specify at least which mote are you using... If you really want responses, at least provide useful information, and try doing your homework first (at least browsing other people code or googling) before asking for ideas. Antonio. On Thu, May 12, 2011 at 8:22 PM, Marianna Araujo marianna.angel...@gmail.com wrote: I need implement a algorithm to obtain the level of energy of each sensor. Anyone have any idea? Regards, -- Marianna Araújo -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- -- Antonio Liñan Colina R+D+I Engineer @: ali...@advancare.com @: ali...@zolertia.com -- Advancare T: +34 93 582 02 70 http://www.advancare.com http://www.zolertia.com -- Marianna Araújo -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] problem with project Octopus: A Dashboard for Sensor Networks Visual Control
Hi all, Anyone knows the project Octopus: A Dashboard for Sensor Networks Visual Control? And can someone help me? I'm trying to install it, but I get the following error when I type make micaz in /opt/tinyos-2.x/apps/OctopusDashboard/motes: mkdir -p build/micaz compiling OctopusAppC to a micaz binary ncc -o build/micaz/main.exe -Os -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=10 -I/opt/tinyos-2.x/tos/lib/net/ -I/opt/tinyos-2.x/tos/lib/net/ctp -I/opt/tinyos-2.x/tos/lib/printf -I/opt/tinyos-2.x/tos/lib/net/le -I. -DIDENT_APPNAME=\OctopusAppC\ -DIDENT_USERNAME=\marianna\ -DIDENT_HOSTNAME=\marianna-deskto\ -DIDENT_USERHASH=0x30315190L -DIDENT_TIMESTAMP=0x4dcee31fL -DIDENT_UIDHASH=0x6bdc18fdL -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, components)' -fnesc-dumpfile=build/micaz/wiring-check.xml OctopusAppC.nc -lm In file included from OctopusAppC.nc:47: In component `OctopusC': OctopusC.nc: In function `collectSendTask.runTask': OctopusC.nc:376: too few arguments to function `CollectSend.getPayload' OctopusC.nc: In function `serialSendTask.runTask': OctopusC.nc:387: too few arguments to function `SerialSend.getPayload' OctopusC.nc: In function `CollectReceive.receive': OctopusC.nc:536: too few arguments to function `SerialSend.getPayload' OctopusC.nc: In function `setLocalDutyCycle': OctopusC.nc:556: interface has no command or event named `setLocalDutyCycle' OctopusC.nc:566: interface has no command or event named `setLocalDutyCycle' In component `OctopusAppC': OctopusAppC.nc: At top level: OctopusAppC.nc:59: component HamamatsuS1087ParC not found OctopusAppC.nc:59: component `HamamatsuS1087ParC' is not generic /opt/tinyos-2.x/tos/chips/cc2420/lpl/DefaultLplC.nc:39:2: warning: #warning *** USING DEFAULT LOW POWER COMMUNICATIONS *** OctopusAppC.nc:114: component DisseminationC not found OctopusAppC.nc:115: component DisseminatorC not found OctopusAppC.nc:115: component `DisseminatorC' is not generic OctopusAppC.nc:68: no match OctopusAppC.nc:117: no match OctopusAppC.nc:118: no match OctopusAppC.nc:119: no match make: ** [exe0] Erro 1 Regards, -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Fwd: [tinyos-help] Get the level energy in Wireless Sensor Network
I need implement a algorithm to obtain the level of energy of each sensor. Anyone have any idea? Regards, -- Marianna Araújo -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Simulator with Graphical User Interface
Hi all, anyone knows a simulator with graphical user interface that provides the simulation the energy level of sensor node? I tried install the Octopus simulator, but I got error... Regards, -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] problem with telos
I'm trying tu use Tinyos in Ubuntu 10.10,when I try to compile Blink for micaz it goes ok. But when I try to compile for telosb I get the following error: /opt/tinyos-2.1.0/tos/system/ RealMainP.nc: In function `main': /opt/tinyos-2.1.0/tos/system/RealMainP.nc:68: interface has no command or event named `init' /opt/tinyos-2.1.0/tos/system/RealMainP.nc:69: interface has no command or event named `runNextTask' /opt/tinyos-2.1.0/tos/system/RealMainP.nc:75: interface has no command or event named `init' /opt/tinyos-2.1.0/tos/system/RealMainP.nc:76: interface has no command or event named `runNextTask' /opt/tinyos-2.1.0/tos/system/RealMainP.nc: At top level: /opt/tinyos-2.1.0/tos/system/RealMainP.nc:93: syntax error before `PlatformInit' In file included from BlinkC.nc:41, from BlinkAppC.nc:45: In interface `Timer': /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:53: syntax error before `dt' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:62: syntax error before `dt' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:81: only commands and events can be defined in interfaces /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:81: warning: return-type defaults to `int' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:81: syntax error before `isRunning' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:87: only commands and events can be defined in interfaces /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:87: warning: return-type defaults to `int' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:87: redefinition of `bool' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:87: syntax error before `isOneShot' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:103: syntax error before `t0' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:118: syntax error before `t0' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:125: only commands and events can be defined in interfaces /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:125: warning: return-type defaults to `int' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:125: syntax error before `getNow' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:133: only commands and events can be defined in interfaces /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:133: warning: return-type defaults to `int' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:133: redefinition of `uint32_t' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:133: syntax error before `gett0' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:140: only commands and events can be defined in interfaces /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:140: warning: return-type defaults to `int' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:140: redefinition of `uint32_t' /opt/tinyos-2.1.0/tos/lib/timer/Timer.nc:140: syntax error before `getdt' In file included from BlinkC.nc:44, from BlinkAppC.nc:45: In interface `Leds': /opt/tinyos-2.1.0/tos/interfaces/Leds.nc:106: only commands and events can be defined in interfaces /opt/tinyos-2.1.0/tos/interfaces/Leds.nc:106: warning: return-type defaults to `int' /opt/tinyos-2.1.0/tos/interfaces/Leds.nc:106: syntax error before `get' /opt/tinyos-2.1.0/tos/interfaces/Leds.nc:123: warning: declaration of `uint8_t' shadows global declaration /opt/tinyos-2.1.0/tos/interfaces/Leds.nc:106: warning: location of shadowed declaration /opt/tinyos-2.1.0/tos/interfaces/Leds.nc:123: syntax error before `val' In file included from /opt/tinyos-2.1.0/tos/system/LedsP.nc:39, from /opt/tinyos-2.1.0/tos/system/LedsC.nc:38, from BlinkAppC.nc:45: In interface `GeneralIO': /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:32: only commands and events can be defined in interfaces /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:32: warning: return-type defaults to `int' /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:32: syntax error before `get' /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:34: only commands and events can be defined in interfaces /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:34: warning: return-type defaults to `int' /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:34: redefinition of `bool' /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:34: syntax error before `isInput' /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:36: only commands and events can be defined in interfaces /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:36: warning: return-type defaults to `int' /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:36: redefinition of `bool' /opt/tinyos-2.1.0/tos/interfaces/GeneralIO.nc:36: syntax error before `isOutput' In component `LedsP': /opt/tinyos-2.1.0/tos/system/LedsP.nc:45: syntax error before `Init' LedsP: `Init.error_t' not implemented LedsP: `Leds.led0Off' not implemented LedsP: `Leds.led0Toggle' not implemented LedsP: `Leds.led1On' not implemented LedsP: `Leds.led1Toggle' not implemented LedsP: `Leds.led2Toggle' not implemented LedsP: `Leds.led2Off' not implemented LedsP: `Leds.led1Off' not implemented LedsP: `Leds.uint8_t' not implemented LedsP: `Leds.set' not implemented LedsP: `Leds.led0On' not implemented LedsP: `Leds.led2On' not implemented In file included from
[Tinyos-help] problem with telos
Hi, I have the following problem when try execute make telosb Couldn't execute msp430-gcc I'm using tinyos 2.1.0 in cygwin. Someone help me? Regards, -- Marianna Araújo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
