RE: [Tinyos-help] repeating tests,no free memory
I'll second this, no problems with just UART1 and radio. I'd still like to have some arbitration between the UART1 and Flash components (this could remedy the problem you're observing, too). I've made a Bluetooth module which communicates through UART1, and if I try to use the flash simultaneously, there's definitely a conflict. I haven't had enough time to figure out how this could be sorted. Without that, UART1 won't work with flash. Harri -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Moss Sent: Wednesday, October 04, 2006 8:02 PM To: 'Michael Schippling' Cc: tinyos-help@Millennium.Berkeley.EDU Subject: RE: [Tinyos-help] repeating tests,no free memory I'm not sure what's going on here with the micaz schematics or how it's implemented in software. I know on the mica2 schematics, the flash is controlled by USART1 and the CC1000 is controlled by the SPI_xyz lines: http://www.tinyos.net/hardware/design/ORCAD_FILES/MICA2/6310-0306-01ACLE AN.p df I assume the micaz is the same way - using PortB's SPI lines to control the radio and PortD's USART1 to control the flash. If that's the case, then they are two different ports and there shouldn't be a conflict with using the flash and the radio at the same time. Unless, of course, there's some low level component that enjoys starting conflicts between the two. Which - this is TinyOS 1.x remember - could be a plausible excuse. -Original Message- From: Michael Schippling [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 04, 2006 9:52 AM To: David Moss Cc: 'Munaretto, Daniel'; tinyos-help@Millennium.Berkeley.EDU Subject: Re: [Tinyos-help] repeating tests,no free memory Isn't SPI implemented with USART1? Or was I out behind the barn when they passed out? MS David Moss wrote: I think you're right - the flash is controlled by the UART not the SPI. So I'm not sure why it crashes on the micaz sometimes. I have gotten packets to come in over the radio and write to flash, and data from flash to go over the radio just fine on micaz's. Sounds like there's some other software issue going on here. -Original Message- From: Munaretto, Daniel [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 04, 2006 3:14 AM To: David Moss Cc: tinyos-help@Millennium.Berkeley.EDU Subject: RE: [Tinyos-help] repeating tests,no free memory Hi David, i would like to ask you a question: do you know if the way FlashBridge gets access to the flash, is controlled by SPI interface or UART1 interface (ATmega128)? because normally the external flash is controlled by UART1 interface of the ATmega128 processor (in this case there are not bus conflicts between flash and radio) and the radio in micaZ is controlled by SPI interface. thanks for your help, cheers Daniele ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-hel p ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-hel p ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Interface board for CMUcam and mica2 Mote
Respected sirI am Mtech student doing M.Tech. project on wireless sensor network.Actually i have to interface mica 2 mote with camera...i am using CMUcam Omnivision CMOS camera.For this i have designed interface board.. Which provide interfacing Between Mica2 Mote and CMUcam.how i can develope code for interfacing..please help me for sameThanksWarm RagardsRajeev KarothiaProject TraineeIIT Bombay ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] CC2420,micaz,energy consumption
Hi all, i looked for information on micaz's energy consumption but in the archive i didn't find complete answers. I need to measure the energy consumption in my motes while they're using the radio and while they're using the external flash to read and write data. This is in order to plan how to develop my future project. Is there an interface or commands to obtain automatically these values? or do i need external instruments to measure current and voltage? (but in this case it will be difficult to observe variations in really short time intervals..) this is for micaz, CC2420 chipcon, tinyos-1.x Thanks for any helps and feedbacks, they will be really appreciated cheers Daniele ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tmote as a I2C slave
Hi Steve, I have a couple of more questions regarding I2C slave. I used your code and it worked out of the box for tmotes. I tried to reproduce your code for tinyos-1.x using the primitives in MSP430I2CM.nc file. Actually my system is written in tinyos-1.x so I prefered using it. Though the writes from the master generates an interrupt at the slave, a read request doesnot generate any interrupt. Can you suggest what could be the possible cause for it. Do you know what the max speed of communication over I2C is that the MSP430 can support. How do we vary the speed ? Thanks a lot for your help, Nilanjan Quoting R. Steve McKown [EMAIL PROTECTED]: On Thursday 28 September 2006 03:42 pm, [EMAIL PROTECTED] wrote: Hi, Is there any code in the tinyos tree for the tmote to act as a I2C slave. I could find code (MSP430I2CPacket) for it to act as I2C master. You might want to check Boomerang; it apparently has features for the TMote platform not in vanilla TinyOS. I recently hacked on the current development snapshot of TinyOS-2.x to add I2C slave support for MSP430. It might work on TMote without changes. The code is ugly, put together quickly to help me understand some I2C mechanics. I'm not up to speed on I2C, and this code is surely not the right way to integrate slave support. But it might be useful as a guide. I've attached a tar.gz file with the code. I'm not sure it's kosher to send attachments to the list -- please send flames my way if not. The MSP430's I2C hardware peripheral is super easy to use as a slave. Just initialize slave mode by calling: Create an Msp430I2CConfigure component having the correct slave address in the msp430_i2c_config structure's i2coa field. call HplI2C.setSlaveMode(); call HplI2C.setReceiveMode(); call HplI2C.enableTransmitReady(); call HplI2C.enableReceiveReady(); I hacked the above into a copy of Msp430I2CP.nc as a new command I2CSlave.listen(). Then, in the same component, I2CInterrupts.fired() will call nextRead() and nextWrite() as the I2C hardware exposes requests from a master targeting the slave. These two functions can signal new I2CSlave events to either send I2C data from the bus to the app or vice versa, as required. Steve - This mail sent through IMP: http://horde.org/imp/ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] WSN in presence of dense WLAN
We have a dense WLAN (802.11g) running at our place (a closed room). When we try to run our micaz motes (working at 2.405 Ghz) - most of the packets are dropped midway. Is it because of the dense WLAN at the same place? If yes, then is there any solution (apart from switching off the WLAN, of course) Tarun ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] WSN in presence of dense WLAN
Hi, for the micaz, in the MakeXbowlocal file, in principle there are commented the frequencies that do not overlap the 802.11. So, compiling with the uncommented options will function without turning off your net. cheers, --marco. Quoting Tarun Bansal [EMAIL PROTECTED]: We have a dense WLAN (802.11g) running at our place (a closed room). When we try to run our micaz motes (working at 2.405 Ghz) - most of the packets are dropped midway. Is it because of the dense WLAN at the same place? If yes, then is there any solution (apart from switching off the WLAN, of course) Tarun ___ 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] CC2420,micaz,energy consumption
On Thursday 05 October 2006 02:53 am, Munaretto, Daniel wrote: I need to measure the energy consumption in my motes while they're using the radio and while they're using the external flash to read and write data. This is in order to plan how to develop my future project. The easiest solution is to use a digital sampling oscilloscope to measure the voltage drop across a small-ohm, precision resistor in series between the mote and its power source. Decent scopes are more than fast enough to capture useful power event information. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tmote as a I2C slave
On Thursday 05 October 2006 07:03 am, [EMAIL PROTECTED] wrote: I have a couple of more questions regarding I2C slave. I used your code and it worked out of the box for tmotes. Some days you get lucky, I guess. I tried to reproduce your code for tinyos-1.x using the primitives in MSP430I2CM.nc file. Actually my system is written in tinyos-1.x so I prefered using it. Though the writes from the master generates an interrupt at the slave, a read request doesnot generate any interrupt. Can you suggest what could be the possible cause for it. I'm not sure I'm clear on what you are seeing. Are you saying that a master write request triggers an operation at the slave but a master read request fails to trigger an operation at the slave? This would mean a master write triggers execution of nextRead() in the slave (via I2CInterrupts.fired()) and a master read fails to trigger execution of the slave's nextWrite() (both methods in Msp430I2CP.nc). If this is the case, it sounds like the I2CIE (I2C interrupt enable) register may not be set correctly. The Hpl12C.setXXXReady() methods are used to set the bits in this register. Do you know what the max speed of communication over I2C is that the MSP430 can support. How do we vary the speed ? Per the data sheet, the MSP430x15x, ...x16x and ...x161x microcontrollers support I2C spec v2.1 and only standard mode (up to 100kbps) and fast mode (up to 400kbps). To control the speed, you need to set the various bitfields in the msp430_i2c_config structure (see SlaveI2CConfC.nc as an example). These bitfields map a clock source with a prescaler, etc. to allow you to set the speed of the I2C clock. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TinyOS-2 Simulation err in g++
Can anyone tell me if there is an existing problem or if I have to install a fix for this? I ran tos-check-env. It worked fine. I recently installed TinyOS-2. I am trying to compile either Blink or Null in simulation mode. I am getting the following compiler (g++) errors on the sample code: declaration shadows global declaration -fPIC ignored for target (all code is position independent). This is followed by lots of compile-time errors. I get the following output make micaz sim 1out.txt 2err.txt .out.txt.. mkdir -p build/micaz placing object files in build/micaz writing XML schema to app.xml compiling NullAppC to object file sim.o ncc -c -shared -fPIC -o build/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -finline-limit=10 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -Wno-nesc-data-race NullAppC.nc -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml compiling Python support into pytossim.o and tossim.o g++ -c -shared -fPIC -o build/micaz/pytossim.o -g -O0 /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx -I/usr/include/python2.3 -I/opt/tinyos-2.x/tos/lib/tossim -DHAVE_CONFIG_H err.txt.. In file included from /opt/tinyos-2.x/tos/lib/tossim/sim_mac.c:34, from /opt/tinyos-2.x/tos/lib/tossim/tos.h:90: /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:14: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:98: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:20: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:98: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: In function `sim_gain_allocate_link': /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:134: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:98: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: At top level: /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:141: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:98: warning: location of shadowed declaration build/micaz/app.c:1: warning: -fPIC ignored for target (all code is position independent) ... followed by tons of compiler errors ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TinyOS-2 Sim error: Python.h not found.
Hello, I'm getting the following error when I compile Blink make micaz sim I'm runing under cygwin /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:30:20: Python.h: No such file or directory My PYTHONPATH is: .:/opt/ tinyos-2.x/support/sdk/python:/cygdrive/c/Python25/ Can you tell me what path I need to change or what I need to do? ...I'm listing the entire error log now: mkdir -p build/micaz placing object files in build/micaz writing XML schema to app.xml compiling NullAppC to object file sim.o ncc -c -shared -fPIC -o build/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -finline-limit=10 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -Wno-nesc-data-race NullAppC.nc -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml compiling Python support into pytossim.o and tossim.o g++ -c -shared -fPIC -o build/micaz/pytossim.o -g -O0 /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx -I/usr/include/python2.3 -I/opt/tinyos-2.x/tos/lib/tossim -DHAVE_CONFIG_H In file included from /opt/tinyos-2.x/tos/lib/tossim/sim_mac.c:34, from /opt/tinyos-2.x/tos/lib/tossim/tos.h:90: /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:14: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:98: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:20: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:98: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: In function `sim_gain_allocate_link': /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:134: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:98: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: At top level: /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:141: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:98: warning: location of shadowed declaration In file included from /opt/tinyos-2.x/tos/chips/atm128/timer/sim/HplAtm128Timer0AsyncC.nc:58, from /opt/tinyos-2.x/tos/platforms/mica/AlarmCounterMilliP.nc:30, from /opt/tinyos-2.x/tos/platforms/mica/sim/HilTimerMilliC.nc:41, from /opt/tinyos-2.x/tos/system/TimerMilliP.nc:41, from /opt/tinyos-2.x/tos/system/TimerMilliC.nc:40, from BlinkAppC.nc:46: In component `HplAtm128CompareC': /opt/tinyos-2.x/tos/chips/atm128/timer/sim/HplAtm128CompareC.nc: In function `timer0_compare_handle': /opt/tinyos-2.x/tos/chips/atm128/timer/sim/HplAtm128CompareC.nc:195: warning: declaration of `time' shadows global declaration /usr/include/time.h:49: warning: location of shadowed declaration build/micaz/app.c:1: warning: -fPIC ignored for target (all code is position independent) /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:1: warning: -fPIC ignored for target (all code is position independent) /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:30:20: Python.h: No such file or directory /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:375: error: ISO C++ forbids declaration of `PyObject' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:375: error: expected `;' before '*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:376: error: `PyObject' has not been declared /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:376: error: ISO C++ forbids declaration of `parameter' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:381: error: `PyObject_HEAD' does not name a type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:385: error: expected init-declarator before '*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:385: error: expected `,' or `;' before '*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:392: error: `FILE' has not been declared /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:392: error: ISO C++ forbids declaration of `fp' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function `int swig_varlink_print(swig_varlinkobject*, int*, int)': /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:395: error: `fprintf' undeclared (first use this function) /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:395: error: (Each undeclared identifier is reported only once for each function it appears in.) /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:396: error: 'struct swig_varlinkobject' has no member named 'vars' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: At global scope: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:404: error: expected init-declarator before '*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:404: error: expected `,' or `;' before '*' token
[Tinyos-help] Re: WSN in presence of dense WLAN
Hi,You can also check this manual from crossbow on how to avoid interference:http://www.xbow.com/products/Product_pdf_files/Wireless_pdf/ZigBeeandWiFiInterference.pdf Raghu-- Message: 1Date: Thu, 05 Oct 2006 15:46:34 +0200From: Marco Antonio Lopez Trinidad [EMAIL PROTECTED]Subject: Re: [Tinyos-help] WSN in presence of dense WLAN To: Tarun Bansal [EMAIL PROTECTED]Cc: tinyos-help@Millennium.Berkeley.EDUMessage-ID: [EMAIL PROTECTED]Content-Type: text/plain; charset=ISO-8859-1Hi,for the micaz, in the MakeXbowlocal file, in principle there are commented thefrequencies that do not overlap the 802.11.So, compiling with the uncommented options will function without turning offyour net.cheers,--marco.Quoting Tarun Bansal [EMAIL PROTECTED] : We have a dense WLAN (802.11g) running at our place (a closed room). When we try to run our micaz motes (working at 2.405 Ghz) - most of the packets are dropped midway. Is it because of the dense WLAN at the same place? If yes, then is there any solution (apart from switching off the WLAN, of course) Tarun ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- =Research AssistantDepartment of Computer ScienceUniversity of Illinois, Urbana-ChampaignIL-61801= ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
