Dear Micheal,
First of all, thanks for your interest.
I listed my actions below in T2;
1. I modified nx_int16_t line of oscilloscope.h
typedef nx_struct oscilloscope {
nx_uint16_t version; /* Version of the interval. */
nx_uint16_t interval; /* Samping period. */
nx_uint16_t id; /* Mote
looks like nx_int16_t is defined as a short (int)
and Java don't know from shorts...this may be a bug
in the T2 mig impl vis the nx types. The error is
kind of weird as I would have thought it would complain
about short not being defined anywhere...but who knows.
The Java update() method, as
I don't understand the relationship between send() and receive() here
but it's possible that the intermediate put() fails because the UART
is busy. I think put() just starts a uart xmit, and like the radio
send() you need to wait for a done() before successfully posting
another char.
MS
i'm doing my final project but i have some trouble.
i'm making wireless sensors. i'm using cc1000 and AVR
ATMega 8 or 16 to make my final project.
These are my trouble n i need:
1.layout of PCB AVR+cc1000.
2.the library of cc1000 from codevision.
3.Schematics of RF Modem.
i have found some PCB
Edgy packages work on feisty. You just have to install udev. Have a look at
the archives.
On 5/18/07, Micfox Micfox [EMAIL PROTECTED] wrote:
I think you can install tinyos from source code(checkout the source code
from CVS), which is Ubuntu-version independent.
The relevant installation
Hi,
I managed to use the CPU cycle count from PowerTOSSIM to measure the
possible difference.
It seems that ROM is roughly about 50% slower.
Here are the numbers showing the difference in three of my functions. RAM
access was coded with table[addr], ROM access was coded with PRG_RDB().
Function
Hi,
I have made a TLV packet with the following declaration :
typedef nx_struct sensing_msg {
nx_uint8_t flags;
nx_uint8_t length;
nx_uint8_t value[];
} sensing_msg_t;
I used [] instead of a pointer, because I need to mig the packet in
java and a pointer won't work. In my nesC application,
Actually, the copy does not work either.
When I access sm-value[1] at different times, it seems to have random
values, I guess I'm accessing the data of some other component.
I quite clueless now...
Romain
On 5/18/07, Romain Thouvenin [EMAIL PROTECTED] wrote:
Hi,
I have made a TLV packet
You can use CC2420Control.setRFpower.
On 5/18/2007, Shuo Xiao [EMAIL PROTECTED] wrote:
Hi all,
I tried to use the command CC2420Packet.getPower to get the current
transmission power, and the application wires the component CC2420PacketC.
But why the data I got is 0, not the default tx power
On May 17, 2007, at 9:50 PM, Shuo Xiao wrote:
Hi all,
I tried to use the command CC2420Packet.getPower to get the current
transmission power, and the application wires the component
CC2420PacketC. But why the data I got is 0, not the default tx
power 31? And how to use the command
unfortunately
nx_uint8_t value[];
is just another way to say
nx_uint8_t *value;
The packet definition must contain the actual data because
the lower levels treat the message as a single char array.
When you do the assignment, whatever is at payload[2] and [3]
is treated as a
Actually, there was a stupid mistake in my code where I access the
data. With the mistake fixed, it works!
I mean this works:
receive(message_t * msg, void * payload, uint8_t length){
sensing_msg_t * sm = payload;
do_something_with(sm-value[0]);
...
}
I have to say I don't really
Hi All,I am searching for simulator for energy consumption in MicaZ,but i
can\'t find one.I also can\'t find energy model for MicaZ in
Avrora,PowerTOSSIM.Does ns-2,omnett++ simulate energy consumption for any
application in MicaZ( as micaZ uses CC2420 chip).I also tried nesct in Omnet++
The difference between flash and RAM accesses stems from the
architecture of AVR. You can load a byte from RAM on AVR8 into an
arbitrary register in a two clock cycles. Loading a byte from program
memory (in your labeling ROM, technically flash) takes 3 cycles,
because the microcontroller needs
ah ha, so there is a hidden wait-state...
I couldn't find any pipelining diagrams in the datasheet that
I have but now I see the issue. Looks like one uses LD to get Sram
and LPM to get Flash contents, where LD takes 2 cycles and LPM 3.
So it's not even roughly 50% overhead, it's exactly 50%...
Thanks guys for all the information and help.
I'm happy that the results I got roughly match the 50% overhead You pointed
out.
One last thing - this is surely a stupid question but how can one estimate
the execution time based on clock cycles ? Suppose I have a block of code
which needs 1000 CPU
No hidden wait states, LPM needs to arbitrate with the loading of the
regular instruction stream from program memory. If you're looking at
atmega 128 datasheet, look at figure 6 and think what happens on the
program memory bus. Then, consider what happens when you perform data
access like the
Hello,
We've tried using the CC1000 radio stack ported by Victor Shnayder from
Harvard, for TOSSIM. We are using TinyOS 1.15, and have also tried the
latest version of the code from the TinyOS1.x CVS.
According to the instructions at
Well I was using wait-state loosely...it does appear to have
a similar effect. Anyway your interpretation of the two figures
makes sense, but I'm sure we could collect 10 people and get at
least 5 answers...The key for me is that the block diagram shows
no direct path between the Flash mem and
(at the risk of being wrong again)
I'd say yes, it's (almost) that simple.
But make sure you are counting instruction
clock CYCLES not just instructions. And if
there are branches, they take a different
number of cycles for true/false so it's
not quite that easy...
MS
Artur Skrajnowski
Hi all,
I want to use NetSync to provide time synchronization in the Delta app
code for Tmotes at full power. In the NetSyncC file it says, never to
wire to it but instead use make tmote lowpower. So, when I compile
using make tmote lowpower not providing the duty cycle value there
but changing
21 matches
Mail list logo
