Respected Sir
i tried to do byte level communication between ATmega128 and CC1000 radio in MICA2 mote.
I found that there is a problem with SPI interface.
I send a single byte to SPDR register and i read it back.
Displayed it using UART.
But I got some unknown data.
what may be the reason.
please help me.
If you have any module for SPI communication send it.
thanking You
Regards
S.Sankar
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Send Tinyos-help mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."
Today's Topics:
1. Re: WSN in presence of dense WLAN (Marco Antonio Lopez Trinidad)
2. Re: CC2420,micaz,energy consumption (R. Steve McKown)
3. Re: Tmote as a I2C slave (R. Steve McKown)
4. TinyOS-2 Simulation err in g++ (Marguerite A Doman)
----------------------------------------------------------------------
Message: 1
Date: Thu, 05 Oct 2006 15:46:34 +0200
From: Marco Antonio Lopez Trinidad <[EMAIL PROTECTED]>
Subject: Re: [Tinyos-help] WSN in presence of dense WLAN
To: Tarun Bansal <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1
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
> [email protected]
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
------------------------------
Message: 2
Date: Thu, 5 Oct 2006 08:04:48 -0600
From: "R. Steve McKown" <[EMAIL PROTECTED]>
Subject: Re: [Tinyos-help] CC2420,micaz,energy consumption
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="utf-8"
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.
------------------------------
Message: 3
Date: Thu, 5 Oct 2006 08:41:54 -0600
From: "R. Steve McKown" <[EMAIL PROTECTED]>
Subject: Re: [Tinyos-help] Tmote as a I2C slave
To: [EMAIL PROTECTED]
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
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.
------------------------------
Message: 4
Date: Thu, 5 Oct 2006 12:07:22 -0400 (EDT)
From: Marguerite A Doman <[EMAIL PROTECTED]>
Subject: [Tinyos-help] TinyOS-2 Simulation err in g++
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8
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 1>out.txt 2>err.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=100000 -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
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
End of Tinyos-help Digest, Vol 42, Issue 15
*******************************************
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
