Re: [Tinyos-help] uisp and mica2 programming problems
Some more news on this problem. It is still occurring, but I can now get around it consistently. I also discovered that it will program the board with no problems if I change the high fuse to 0xD9 (uisp makes is 0xD8). In my last email I said that I was setting this fuse to 0x19, but it seems 0xD9 also works. The only difference this has from the uisp 0xD8 is that the BOOTRST vector is disabled. Does anyone have any idea what's going on here? I also discovered that writing 0xD8 to the high fuse will allow me to read the fuses reliably (it seems), but when I program it (with Blink for example) the program does nothing. So here is how I program my boards: -Write 0xD9 (or 0x19) to the high fuse several times: uisp -dprog=mib510 -dserial=/dev/ttyS0 -dpart=ATmega128 --write_fuse_h=0xD9 -Check the fuses: uisp -dprog=mib510 -dserial=/dev/ttyS0 -dpart=ATmega128 --rd_fuses -If the fuse has changed then continue -Upload the program: make mica2 reinstall mib510,/dev/ttyS0 Does anyone have any ideas why it might be doing this or how I can fix it? Or even a few things I can do with the MIB510 to try and troubleshoot it? I have tried reinstalling cygwin and the tinyos environment, but this did not fix it. I am using TinyOS1.1.15 Thanks again, Simon Simon Willis wrote: I am having problems programming with uisp. I am using Blink for testing. I have a MIB510 and a board that we designed that is based on the mica2. Once I have programmed the ATMEGA128 I cannot reprogram it. It goes through all the correct actions, but the program doesn't seem to change (tested by changing the blinking LED) With a bit of playing around I discovered that I can get it to program after I change the fuse high byte to 0x98 (from 0xd8 set by uisp). This turns on the 'enable JTAG' option (even though I don't have the JTAG plugged in) then it works. Another problem is that when I issue a 'rd-fuses' command it will quite often return all 0s (or give some other error message), also the wr_fuses_h command usually takes about 5 attempts until it does actually change the fuses (checked using rd_fuses). Once it has changed the fuse to 0x98 then rd_fuses will work reliably and I can upload my program. I have also tried other combinations for fuses (like 0x19) and it seems that whenever the 'enable JTAG' option is on it will work. Does anyone have any idea why this might be or what might be wrong here? I have been able to replicate this problem on 2 boards now (I have only built 2 so far). Perhaps I should try changing the makefile so that uisp always enables JTAG, but this seems like a bit of a workaround problem, since normal mica2s seem to work OK. Anothter note: It also seems that I can't program a fresh ATMEGA with uisp until I have plugged in a JTAG and changed the fuses to 0xfd (e) 0x19 (h) 0xfe (l). Is this normal? I was thinking that perhaps this is done by Crossbow before the motes leave the factory. Thanks for your help. Simon ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Guide: TinyOS-2.x environment on MacOS X
Hi, after struggling with it for a couple of days I finally managed to setup a working cross-development environment for TinyOS-2.x avr platform on MacOS X (PPC). I wrote down the steps required to get it finally running. Because it could be useful for others as well I put it online: http://www.inf.ethz.ch/~muellren/tinyosonmac.html But be warned, it is really tedious work. regards, René ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Visualizing topology+nodes'information
Hi all, i'd like to visualize on my pc my network and if possible to show the contents of the packets, in particular one internal parameter (the number of decoded packets, field already inside the packet format). But each node doesn't know about neighbors or the net in general, so routing protocol are not used, they only broadcast the information. I was thinking to use TOS_BASE application to receive packets from the net, send them to my pc and if possible to visualize the number of decoded packets stored in these packets. But how can i visualize these informations on my pc (topology+number of decoded pcks)? Should i use oscilloscope tool or similar?and how? Thanks very much, Daniele ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Question about lost of packets with MultiHop.
Philip Levis wrote: On Jul 25, 2006, at 3:33 AM, Krisakorn Rerkrai wrote: Does this mean these two packets are both acknowledged but the second one in the FIFO is flushed out? Yes. Could I be so lucky, that this "feature" is documented somewhere(besides this thread)? ;o) /Peter ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Cannot run: make micaz sim
Chong Zan Kai wrote: Hi, hi, Can someone tell me why I cannot run "make micaz sim" in ubuntu? Thanks. ... /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:30:20: error: Python.h: No such file or directory ... you need python ? Aurélien ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] Problems with GenericComm and PWM
Hi! Thanks a lot for your fantastic help! PWM works now on a node, which is remote controlled by radio. I just used TOSH_ASSIGN_PIN(MOTOR1DIR, C, 1); TOSH_ASSIGN_PIN(MOTOR1PWM, B, 5); TOSH_MAKE_MOTOR1PWM_OUTPUT(); TOSH_MAKE_MOTOR1DIR_OUTPUT(); TOSH_CLR_MOTOR1PWM_PIN(); TOSH_CLR_MOTOR1DIR_PIN(); instead of outp(0x20, DDRB); and there were no conflicts with radio anymore. BiBe > -Original Message- > From: Michael Schippling [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 26, 2006 6:19 AM > To: BiBe > Cc: tinyos-help@Millennium.Berkeley.EDU > Subject: Re: [Tinyos-help] Problems with GenericComm and PWM > > Oh, now you're going to make me work AND explain what I did...oy... > > First I stole my PWM stuff from Sarah B's cotsbots board code that > uses different pins and a somewhat different idea, vis motor direction. > I then left the direction pin defs in but never used them, so at least > three layers of confusion can ensue...my code is for the mica cards > themselves. > > Second here's a quote from a previous post that might help explain the > macros: > > >> Ian Welch wrote: > >> I was wondering where I could find the TOSH function commands. I'm > going through the CC1000 modules in hopes to write my own drivers. Was > wondering what command like " TOSH_MAKE_CC_CHP_OUT_INPUT() " and " > TOSH_SET_CC_PCLK_PIN() " do. I have an idea on what these functions do > but would I like to know the details. I'm guessing there is a file > locate somewhere that gives all these function. Where I might I find this file. > >> > >> Thanks, > >>Ian > >> > > They are generated by a macro mechanism that run two or three levels > > deep, so there is basically no hope of finding the actual definition > > without searching on each _*_ sub-string. > > Good luck with that... > > > > In any case there is one more missing component you haven't stumbled > > over yet (this is not the real definition, I just pulled it out of a > > hat as an example): > > > > // assign the name "CC_CHP_OUT" to port C, pin 0 > > TOSH_ASSIGN_PIN( CC_CHP_OUT, C, 0 );// PC0 > > > > Then your initial puzzles: > > // set CC_CHP_OUT pin to Input mode (can also use _OUTPUT) > > TOSH_MAKE_CC_CHP_OUT_INPUT() > > // (after using TOSH_MAKE_CC_PCLK_OUTPUT) set pin to high > > TOSH_SET_CC_PCLK_PIN() > > // or, e.g., clear to low > > TOSH_CLR_CC_PCLK_PIN() > > > > The TOSers did a pretty good job of keeping the pin names the same > > as those on the schematic, which are of course slightly different > > from those in the ATMEGA manual. But once you get over the hump it's > > not too hard to intuit. > > > > MS > > > > > > So basically, from the above you should be able to intuit the TOS > mechanism for assigning pins, names, and levels. So you need to make > the PortB pins that can do PWM into outputs by diddling the right BITS > on DDRB, which is done with the TOSH_MAKE_*_OUTPUT() macro, and do all > the other PWM setup. This is done in the init() method of my > HPLMotorIIM.nc file, but only so as to do the exact thing I wanted, so > your pulse rates may change. > > Was that enough gobbledegook to get you going? > MS > > > > > BiBe wrote: > > Hi! > > Thanks a lot for your answer! > > > > With the DDRB register, I set the output pins for PWM. In your code, > this is > > done by: > > > > TOSH_MAKE_MOTOR1PWM_OUTPUT(); > > TOSH_MAKE_MOTOR1DIR_OUTPUT(); > > > > TOSH_CLR_MOTOR1PWM_PIN(); > > TOSH_CLR_MOTOR1DIR_PIN(); > > > > Where are those functions defined and how can I use them to get PWM > > to > Port > > OC1A and OC1B? Can I even use these functions without having the > > cotsbots-board? > > > > Furthermore I found that in a header file: > > > > /** after cotsbots motor/hardware.h for PWM output: **/ // it > > appears that the PWM and DIR appellations are reversed // and also > > that the pins assigned to PWM (sic) are not available // due to > > their being used by the radio: > > // PB1 -- SPI_SCK > > // PB2 -- SPI_MOSI > > // so gotta try somethong else > > > > TOSH_ASSIGN_PIN(MOTOR1DIR, C, 0); // PC0 > > TOSH_ASSIGN_PIN(MOTOR1PWM, B, 6); // PB6 > > > > TOSH_ASSIGN_PIN(MOTOR2DIR, C, 1); // PC1 > > TOSH_ASSIGN_PIN(MOTOR2PWM, B, 5); // PB5 > > > > So there seems to be problems to use radio and PWM together, because > > of corporate use of PB registers. > > > > Can I use TOSH_ASSIGN_PIN() without cotsbots-board in nesC? I tried > > to compile and there were no errors. But will it work expectedly or > > do I > have > > to use any more header files like hardware.h? > > > > Thanks a lot, > > BiBe > > > > > > > >> -Original Message- > >> From: [EMAIL PROTECTED] > >> [mailto:tinyos-help- [EMAIL PROTECTED] On Behalf Of > >> Michael Schippling > >> Sent: Tuesday, July 25, 2006 6:14 AM > >> To: Birger Becker > >> Cc: tinyos-help@Millennium.Berkeley.EDU > >> Subject: Re: [Tinyos-help] Problems with GenericComm and PWM > >> > >> sbi() and cbi() should work fi
[Tinyos-help] equivalent to outp()
Hi! I'd like to update tinyOS from 1.1.0 to 1.1.11. In the programs I used in the older version, there is the function outp() used in some lines, which is no longer available in 1.1.11. So I tried to modify but it doesn't work. Are these methods equivalent? // method 1 (tinyOS 1.1.0) outp(0x4e, ICR1H); outp(0x20, ICR1L); // method 2 (tinyOS 1.1.11) cbi(ICR1H, 0); sbi(ICR1H, 1); cbi(ICR1H, 2); sbi(ICR1H, 3); sbi(ICR1H, 4); cbi(ICR1H, 5); cbi(ICR1H, 6); cbi(ICR1H, 7); cbi(ICR1L, 0); sbi(ICR1L, 1); cbi(ICR1L, 2); cbi(ICR1L, 3); cbi(ICR1L, 4); sbi(ICR1L, 5); cbi(ICR1L, 6); sbi(ICR1L, 7); Are cbi() and sbi() available in tinyOS 1.1.11 or how can those register values be set manually? An assignment like "ICR1H = 0x4e; ICR1L = 0x20;" is not compilable in my environment, because I do not want to include "hardware.h". Thanks, BiBe ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] More documentation about Drip
Hi, I'm interesting in routing protocols, and I have found Drip to disseminate new message in the net.I have read a lot of article about Trickle algorithm(and I have understand it) and the (insufficient!) documentation about Drip.I don't understand what Drip works, can you simply explain me this?I would to send messages in the net and modify them if there are not for me(I have create a field address in TestDripMessage header).When I call Drip.rebroadcast?In Receive.receive or in Drip.rebroadcastRequest??Any help will be appreciatedLORENZO ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Matchbox
Hi David Gay, I'd know which version of TinyOs you have used and what type of sensor. I'm using TinyOS 1.1.7 and mica2 motes. Is it possible that I'm not able to store information using matchbox because I'm using this version of TinyOS? There are some particular flag to set? My aid is to use matchbox with TinyDB but before to do this I have thought to test matchbox. I programmed the mote attached to serial com with Remote application and I used tools like CopyIn and CopyOut to test if matchbox works. Then I run this command: java net.tinyos.matchbox.tools.CopyIn Test.txt Build a Packet source for unknown We're connected to avrmote Hello Ctrl+C java net.tinyos.matchbox.tools.Dir Prova.txt Build a Packet source for unknown We're connected to avrmote Test.txt java net.tinyos.matchbox.tools.CopyOut Test.txt Build a Packet source for unknown We're connected to avrmote Hello If I reset the mote I got this: Build a Packet source for unknown We're connected to avrmote (It doesn't report the file that i have written) If I run again CopyIn and Dir (with success), when I run CopyOut i got this: Build a Packet source for unknown We're connected to avrmote error : file open Could you help me? Thanks for all. Roberto. - Original Message - From: "David Gay" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 25, 2006 9:06 PM Subject: Re: Matchbox On 7/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi David, I'm using Matchbox. It is supposed to write on flash. I have tryed matchbox applications (like CopyIn e CopyOut) but when I reset the mote the file that I have written doesn't exist more. It seems that matchbox writes only on ram. I'm using mica2 mote and the Remote application. Have you any ideas about this problem? No. Last time I tried it, it worked. There's no "temporary ram storage" which could explain your behaviour. I'd suggest emailing the tinyos-help mailing list. David Gay ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Power consumption of SurgeTelos
Hi, all, I am currently estimating the power consumption of tmote sky to support SurgeTelos. I found a strange thing: When I program the SurgeTelos for 5 sec sampling period, it consume arround 28mA. But when I program for 3 minutes sampling period, it still consume 28mA. It seems the radio is always on either TX or RV mode. How can I make the program to be really low power consumption? Any help is appreciated. Best Zhengsu ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] testing MultiHopRSSI
Hi! I'm trying to test the MultiHopRSSI on Tmote Sky, I have had to add some files as RouteStatics as well as modifying multihop.h and multihop.nc because I want it to be tested with Delta (so I have to do it compatible). But I'm finding it rather difficult (changing too much things) and I'm wondering if there is any other way to test it... Thanks! Jesus Serna. Valencia ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Changing Delta Message size
Hello all,
we have added two more fields in the Delta Message,
typedef struct DeltaMsg {
uint32_t seqno;
uint16_t Humidity;// New field added by us
uint16_t Temper;
uint16_t Voltage; // New field added by us
uint16_t parent;
uint8_t neighborsize;
uint8_t retransmissions;
uint16_t neighbors[MHOP_PARENT_SIZE];
uint16_t quality[MHOP_PARENT_SIZE];
} DeltaMsg;
However we face "ArrayIndexOutOfBounds Exception for get_neighborsize"
at run time. We think this should be a problem with the payload length.
so we decided to change its value. As can be seen in the Makefile for
data application:
CFLAGS += -DTOSH_DATA_LENGTH=28+3*2+2
First Question: Can someone explain why the offset 3*2+2 is present
there? It seems that this value is bigger than what is needed by
original Delta application and the Multihop message. If we're not
mistaken a data length of 28 will suffice for it (??).
Second Question:
How should we change the payload length in the Makefile for the above
delta message and why?
thanks
Yannis
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Power consumption of SurgeTelos
SurgeTelos doesn't turn off the radio. Use Delta with the lowpower option instead. On 7/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi, all, I am currently estimating the power consumption of tmote sky to support SurgeTelos. I found a strange thing: When I program the SurgeTelos for 5 sec sampling period, it consume arround 28mA. But when I program for 3 minutes sampling period, it still consume 28mA. It seems the radio is always on either TX or RV mode. How can I make the program to be really low power consumption? Any help is appreciated. Best Zhengsu ___ 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] Cannot run: make micaz sim
On Jul 25, 2006, at 6:39 PM, Chong Zan Kai wrote: Hi, Can someone tell me why I cannot run "make micaz sim" in ubuntu? Thanks. You need to change the Python version in the sim.extra file. I think Ubuntu generally comes with 2.4, and by default TOSSIM assumes 2.3. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] DripSend
Hi, in the Drip folder I have found the DripSend module, but there are absolutally no documentation.Please can you explain me how use this modules?LORENZO ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Tinyos tutorial's lesson 7
hi,
i'm trying to do the lesson 7 exercise of tinyos tutorial. but i'm dealing with error during compilation. here is what i have done.(i'm using tinyos v1.1.10)
first step: in SimpleCmd.nc i add "SimpleCmdM.Sounder ->Sounder;"
second step: in SimpleCmdM.nc i add in "uses", "interface StdControl as Sounder;" and in "command result_t StdControl.init()" i add "call Sounder.init();"
third step: also in SimpleCmdM.nc i add this code for command:
{
bool sound=TRUE;
case TOG_SOUNDER:
if (sound) call Sounder.start();
else call Sounder.stop();
sound=!sound;
break;
}
fourth step: in SimpleCmdMsg.h i add commandes types like TOG_SOUNDER=5
after all this i regenerate java class and recompile BcastInject.java
When i made compilation (make mica2) i got this error message:
$ make mica2
compiling Bcast to a mica2 binary
ncc -o build/mica2/main.exe -Os -board=micasb -target=mica2 -DCC1K_DEF_FREQ=9164
0 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -finline-limit=10 -f
nesc-cfile=build/mica2/app.c Bcast.nc -lm
SimpleCmdM.nc:152: parse error before `{'
SimpleCmdM.nc:157: warning: type defaults to `int' in declaration of `sound'
SimpleCmdM.nc:157: initializer element is not constant
SimpleCmdM.nc:157: (near initialization for `sound')
SimpleCmdM.nc:157: warning: data definition has no type or storage class
SimpleCmdM.nc:158: parse error before `break'
: `ReceiveCmdMsg.receive' not implemented
: `ProcessCmd.execute' not implemented
SimpleCmd.nc:56: cannot find `Sounder'
make: *** [build/mica2/main.exe] Error 1
analysing the message error, i think that error source is in the command line i wrotte at the third step.
could anybody give me a help? thx
Play Q6 for your chance to WIN great prizes.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Regarding MAC layer implementation in TinyOS
Hello, I have a question regarding the CSMA link layer implementation in TinyOS. Is there a way to set the number of retransmissions that the MAC layer attempts to reach the destination? I am actually testing a simple program to send unicast messages to a common destination from 4 different nodes placed in close proximity to one another. For shorter distances all four of them succesfully transmit the messages but for longer distances from the destination just one or two of them is succesful in reaching the destination. I understand that the CSMA MAC layer supports random back-off mechanism so that there is fair distribution of access to the wireless channel. Could someone please answer my question?-- regards,Ravi ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] parallel JTAG with telos b
Hi,I have a short question regarding to the JTAG. I'm using telos b. It's quite slow to download the code with the parallel JTAG. Is it possible to download the code with "make telosb debug" and then "make telosb reinstall" and use the parallel JTAG to debug the program? Or I have to download the code with "load main.exe" in gdb command prompt?regards,Natalie ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TinyDB Events
I'm trying to use the events under tinyDB but I've got some problems.
1 - If I write the following query, as in the TinyDB reference,
On evtTest:
SELECT nodeid,light
SAMPLE PERIOD 1024
the GUI always tell "errorMsg = Syntax error at on".
What is the problem?
2 - I modified the TinyDBApp in nesC as following, including the code of
/tinyos-1.x/tos/lib/TinyDB/TinyDBEvent.nc:
includes CompileDefines;
configuration TinyDBApp {
provides interface EventUse;
provides interface StdControl;
}
implementation {
components Main, TupleRouter, Event, TinyDBEventM;
Main.StdControl -> TupleRouter;
EventUse = Event.EventUse;
Event.StdControl = StdControl;
TinyDBEventM.StdControl = StdControl;
TinyDBEventM.EventRegister -> Event;
}
Does it is correct?
3 -I spent time to undurstand the way to use the
tinyos-1.x/tos/lib/TinyDB/TinyDBEvent.nc in the TinyDBApp.nc without copy
the code directly inside, but using the nesC syntax. Unfortunately I can't
undestand exactly how I shuold do.
What is the correct way to do?
In general what is the right way to use components which are already made?
Roberto Pietrangeli
-
EDALab - Networked Embedded Systems
C.S. Dept - University of Verona - IT
-
email: [EMAIL PROTECTED]
tel. : +39 045 802 70 62
fax : +39 045 802 70 68
web: www.edalab.net
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] RE: Question on flash
Hi Andrea, First, it sounds like you want a storage solution like LogStorage. Unfortunately, this isn't available in TinyOS 1.x, so if you're using BlockStorage you'll have to do it manually somehow. The best solution would be to do this in RAM if possible, since it sounds like your storage is temporary anyway. In BlockStorage, you can erase the volume you're mounted to without having to format. So, if you write data to the flash and want it erased, just call BlockWrite.erase(). From what I recall, you're using tmote's, right? In that case, when you call BlockWrite.erase(), the sector(s) you're mounted to get wiped clean. The bad part is it takes ~1 second to erase a single sector, and a lot of energy. And, if you're erasing all the time, you'll reach the lifetime of the flash faster so it won't last as long. If you really wanted to implement it on flash instead of RAM, maybe what you could do is mount() and erase() the flash when you turn on the mote, then write your data until the current volume is filled by keeping the write address and other address bookmarks in RAM (keep in mind the last page of each sector is reserved in BlockStorage for the STM25P tmote flash) Then, once you reach the end of the volume, call BlockWrite.erase and start over from the beginning. Overall, this sounds like a pretty difficult thing to do in flash without LogStorage available, but it can be done if you have a lot of time and patience! -David -Original Message- From: lamiaimeil [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 25, 2006 4:04 AM To: David Moss Subject: Question on flash Hi David, do you remember me? I have a question for you. I want to use eeprom like a circular array (if possible).. I have format flash with FormatStorage.allocate command but I had known that I can't rewrite the same portion on memory without reformat it.. I must write on eeprom some data get periodically from ADC and send them to base station. Everytime data arrive on base station I want erase them from eeprom so I can reuse it. How can I do? Any ideas for a nice use of eeprom? Thanks a lot! Andrea. Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Modifying Oscilloscope
Well, as I said, look at my code to see how I did a similar thing.
But I think you are on the right track, you need:
OscilloscopeM.SensorControl -> ADCC;
instead of:
OscilloscopeM.ADCControl -> ADCC.ADC[11];
Because SensorControl is the name used in the O'scope code.
And then I don't know what ADC number 11 is since
there are only 8 of them on the ATMEGA. I guess the MDA300
adds a few more ADCs, but I've never used it and don't know
how it works. You might find clues in:
contrib\xbow\tos\sensorboards\mda300\Sample*.nc
Or you can just dispense with the MDA thing altogether and use one
of the ADCs (1-6, where 0 is the radio RSSI and 7 is connected to a
battery monitor) on the main mica controller. Or even just use the ADC
normally assigned to the DemoSensor code and not make any changes to
O'scope. If you have no sensorboard attached, all of those ADCs are
available.
sorry I can't be of much more help than that
MS
Steve the Taiwanese wrote:
I tried swaping wherever sensor was with ADCC in the
Oscilloscope config file as seen below:
configuration Oscilloscope { }
implementation
{
components Main, OscilloscopeM
, TimerC
, LedsC
, DemoSensorC as Sensor
, ADCC
, GenericComm as Comm;
Main.StdControl -> OscilloscopeM;
Main.StdControl -> TimerC;
OscilloscopeM.Timer ->
TimerC.Timer[unique("Timer")];
OscilloscopeM.Leds -> LedsC;
OscilloscopeM.ADCControl -> ADCC.ADC[11];
OscilloscopeM.ADC -> ADCC.ADC[11];
OscilloscopeM.CommControl -> Comm;
OscilloscopeM.ResetCounterMsg ->
Comm.ReceiveMsg[AM_OSCOPERESETMSG];
OscilloscopeM.DataMsg -> Comm.SendMsg[AM_OSCOPEMSG];
}
but it gets a compile error when I try to use the
ADC11 and even if I take out the ".ADC[11]" it still
gives me errors. I looked at your code and am still a
little fuzzy as to how it works. I just need it to
read a value from the mote using the MDA300.
Thanks in advance,
Steve
--- Michael Schippling <[EMAIL PROTECTED]> wrote:
You should be able to swap out the Sensor stuff in
the
config file and use ADCC instead. See how it's done
in:
tos\sensorboards\micasb\PhotoTemp.nc
If you follow the O'scope silly-Sensor modules all
the way
down you get to the real ADCC...
Or look in my code bolus at:
http://www.etantdonnes.com/Motes/robocode.tar.gz
MS
Steve the Taiwanese wrote:
Hi, I am trying to make a wireless EKG. I want to
try
to use Oscilloscope to graph the data from the ADC
11,
or ADC0. How can I change it from the photo sensor
to
the ADC?
Thanks,
Stephen Anderson
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tinyos tutorial's lesson 7
I'd have to see more of the file with the line numbers to have a
stronger opinion, but there are a couple problems with the snippet
you sent...
First the brackets are not correct around the case stmt.
Second defining "bool sound" locally as you seem to be
trying to do makes it a pointless state variable since
it gets initialized to TRUE on every pass and then gets
forgotten again due to C scoping rules.
To fix the bracketing, this may be what you were thinking:
case TOG_SOUNDER:
{
bool sound=TRUE;
if (sound) call Sounder.start();
else call Sounder.stop();
sound=!sound;
}
break;
however you probably want to but the
bool sound=TRUE;
somewhere outside all the function decls so it is a global.
Hope this is a good start...
MS
jurin dan wrote:
hi,
i'm trying to do the lesson 7 exercise of tinyos tutorial. but i'm
dealing with error during compilation. here is what i have done.(i'm
using tinyos v1.1.10)
*first step:* in SimpleCmd.nc i add "SimpleCmdM.Sounder ->Sounder;"
*second* *step:* in SimpleCmdM.nc i add in "uses", "interface
StdControl as Sounder;" and in "command result_t StdControl.init()" i
add "call Sounder.init();"
*third step:* also in SimpleCmdM.nc i add this code for command:
{
bool sound=TRUE;
case TOG_SOUNDER:
if (sound) call Sounder.start();
else call Sounder.stop();
sound=!sound;
break;
}
*fourth step:* in SimpleCmdMsg.h i add commandes types like
TOG_SOUNDER=5
after all this i *regenerate java class *and *recompile
BcastInject.java *
When i made compilation (make mica2) i got this *error message*:
$ make mica2
compiling Bcast to a mica2 binary
ncc -o build/mica2/main.exe -Os -board=micasb -target=mica2
-DCC1K_DEF_FREQ=9164
0 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all
-finline-limit=10 -f
nesc-cfile=build/mica2/app.c Bcast.nc -lm
SimpleCmdM.nc:152: parse error before `{'
SimpleCmdM.nc:157: warning: type defaults to `int' in declaration of
`sound'
SimpleCmdM.nc:157: initializer element is not constant
SimpleCmdM.nc:157: (near initialization for `sound')
SimpleCmdM.nc:157: warning: data definition has no type or storage class
SimpleCmdM.nc:158: parse error before `break'
: `ReceiveCmdMsg.receive' not implemented
: `ProcessCmd.execute' not implemented
SimpleCmd.nc:56: cannot find `Sounder'
make: *** [build/mica2/main.exe] Error 1
analysing the message error, i think that error source is in the
command line i wrotte at the *third step*.
could anybody give me a help? thx
Play Q6 for your chance to WIN
great prizes.
___
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] Regarding MAC layer implementation in TinyOS
I don't think the MAC layer does any retries at all. At least in the mica code, retries are a user level thing involving some kind of ACK from the receiver. The backoff should keep backing-off until it finds an open window, but that isn't dependent on the distance between motes. I have some ACK and various reliability issue info here: http://www.etantdonnes.com/Motes/report_mica2/ MS Ravilochan G S wrote: Hello, I have a question regarding the CSMA link layer implementation in TinyOS. Is there a way to set the number of retransmissions that the MAC layer attempts to reach the destination? I am actually testing a simple program to send unicast messages to a common destination from 4 different nodes placed in close proximity to one another. For shorter distances all four of them succesfully transmit the messages but for longer distances from the destination just one or two of them is succesful in reaching the destination. I understand that the CSMA MAC layer supports random back-off mechanism so that there is fair distribution of access to the wireless channel. Could someone please answer my question? -- regards, Ravi ___ 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] Reading speed when accessing external flash
Hi everybody,I'm writing a program that makes a lot of reading in the external flash.All the accesses are at different addresses, and each time I read only 1 byte.I'm using Tmote sky sensors and BlockStorage abstraction. Now, the problem is that each access to the flash costs me nearly 1ms, so the whole operation takes a veeery long time to finish.I've tried looking into low level modules (HALSTM25PM and HPLSTM25PM) and I saw that probably the slowdown is due to the fact that each time I access the flash, the modules: -gain access to the bus-turn on the flash-make the access-turn off the flash-release the bus.My question is:is there any way that I can speed up this process? For example by keeping the bus occupied and the flash turned on for a longer time in order to make all my accesses? Energy consumption is not a concern in this issue, and my module doesn't make use of the radio either. So, I thought that this could be done.Does anyone have an idea about this?Thank you ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Packet Loss Models in Sensor Network
Dear All, Are you aware of any study that provides model for packet losses as a function of distance in wireless sensor networks. I need this information to simulate realistic loss scenarios in my simulator. Alternatively, I can use some data traces for the losses, any pointer to the available traces would be highly appreciated. Thanks,Tarun ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Matchbox
Sorry, I don't use versions of TinyOS, but the CVS repository... I'd suggest running the Matchbox regression test in apps/TestMatchbox/Remote (it's a shell script called regress, run it with a serial forwarder setup to talk to a mote with the application in the Remote directory installed). If this works, then the problem is how you're using Matchbox. Look at the examples in TestMatchbox for guidance. David Gay ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] [tinyos2.0] event timer.fired() getting lost on telosb using BlinkToRadio apps.
I've committed fixes to VirtualizeTimerC and VirtualizeAlarmC to
tinyos-2_0_devel-BRANCH.
Both components would fail if an alarm/timer was overdue. An overdue
Timer in VirtualizeTimerC would only affect that particular virtual
timer. An overdue Alarm in VirtualizeAlarmC would affect all
virtualized alarms in that component. I have tested my updates to
both components and believe the issues are resolved.
Here's my commit log:
* Fixed a bug in VirtualizeTimerC that caused "late timers" to catastrophically
fail and not fire again for a very long time. This required a small fix.
* Fixed a related bug in VirtualizeAlarmC that caused "late alarms" to
catastrophically impact the behavior of other virtual alarms. The complete bug
was fairly subtle and required a minor overhaul of the component.
Cory
On 7/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
I've executed BlinkToRadio application with two telosb motes for about 3
hours after adding one line of code in VirtualizeTimerC.nc.
These two motes are still operating correctly without event timer.fired()
getting lost.
It seems that the bug's been fixed.
Thank you.
Inyong Park
> Whoah, it looks like I have a blatantly ugly bug in VirtualizeTimerC
> in lib/timer/ where the remaining time is not correctly calculated for
> an overdue periodic timer.
>
> Note, the radio does not play a significant role. If you take
> Jonathan's sample application, take out all the radio stuff, and
> busywait for 1ms in the fast timer, the problem still occurs. I'm
> surprised that other platforms report to not have this problem,
> because they should.
>
> As a quick hack to see if it solves the problem on your side of
> things, try adding this one line of code at around line 100 in
> VirtualizeTimerC.nc:
>
> else
> {
> // The remaining time is non-positive (the timer had fired).
> // So add dt to convert it to remaining for the next event.
> timer->t0 += timer->dt;
> remaining += timer->dt;
> if (remaining & 0x8000L) remaining = 0; // <-- ADD THIS
> LINE
> }
>
> If a couple of you can test that, then I'll try to mix up a cleaner
> solution and review the rest of the VirtualizeTimerC code.
>
> Thanks,
> Cory
>
> On 7/24/06, Cory Sharp <[EMAIL PROTECTED]> wrote:
>> Boomerang has no significant changes from the 2.x timer stack. We are
>> actively looking into this issue, now. - Cory
>>
>> On 7/23/06, Philip Levis <[EMAIL PROTECTED]> wrote:
>> > On Jul 23, 2006, at 11:37 AM, Jonathan Hui wrote:
>> >
>> > > After a little testing, it looks like the radio stack is still
>> alive.
>> > > I modified BlinkToRadio to maintain two timers (1ms and 1s period),
>> > > both of which attemps to send a message on each fire event. After a
>> > > few moments, the 1ms timer will fail to fire, but the 1s timer will
>> > > continue firing and sending messages. Even more interesting is that
>> > > the 1ms timer starts firing at the same period as the 1s timer.
>> > >
>> > > It's probably the case that the radio stack is somehow affecting the
>> > > operation of the msp430 timer stack and causing it to fail in
>> > > repeatedly firing the 1ms timer. Haven't dug too much into the timer
>> > > code to understand why this is.
>> > >
>> > > I've attached the modified app I used to test.
>> > >
>> > > Cory, do you have an ideas?
>> >
>> > Yeah, I should have given more background. I think it's definitely
>> > the case that it's the MSP430 timer stack, which runs into some
>> > issues when timers are at too fast a rate (e.g., 1ms). E.g., in the
>> > 2.0 tutorials, there's a part where you try using very long tasks of
>> > different length to show the run-to-completion semantics. On atm128
>> > platforms, a task that's too long causes you to lose timer events but
>> > things continue as expected; on msp430 ones, the timer stack can act
>> > erratically.
>> >
>> > Joe, Cory, does Boomerang 2.0.2 use the 2.x timer stack unchanged, or
>> > have you incorporated fixes?
>> >
>> > Phil
>> >
>>
> ___
> 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] problem adding fields to QueryMessage in TinyDB
Hi, I am trying to add a uint8_t field to QueryMessage structure in TinyDB.h. Nothing gets outputted on TinyDB GUI. Checking logs, I find the following error: Error : 9 at line 1057 Can anyone tell me what other changes do I have to make to make this run? And what does this error denote? kind regards rajesh ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Parse error
Hello everybody: I am trying to use the component GenericComm to send packets to UART. However, everytime I add such component I get the following error: c:/tinyos/cygwin/tinyos-1.x/tos/types/AM.h:51: parse error before '0x' The code is the following: implementation{ #define AM_TYPE 50 components Main, SMACTestM, SMAC, LedsC, UART, GenericComm as Comm; Main.StdControl -> SMACTestM; SMACTestM.MACControl -> SMAC; SMACTestM.MACComm -> SMAC; SMACTestM.LinkState -> SMAC; SMACTestM.MACTest -> SMAC; SMACTestM.Leds -> LedsC; SMACTestM.PP_signal ->
SMAC; SMACTestM.UARTControl -> UART; SMACTestM.UARTComm -> UART; // To use an external time stamp in S-MAC, provide the following wiring // SMAC.TimeStamp -> YourComponent.TimeStamp;} Could someone help me please? Thank you! Miguel A. Erazo
Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail Beta.___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Use SerialForwarder or MoteIF?
> Don't know about forward portability, but the basic question boils down to: > Do you want your Java code to connect directly to the serial port (meaning > always run on the local host that has the programmer attached), or do you > want to always have to start SerialForwarder on the local host and be able > to connect your program from anywhere on the net (modulo firewalls etal). > > If your code is always local, use MoteIF or BuildSource. Otherwise you > need SF to be your local intermediary. My personal belief system defines > SF as an unnecessary and confusing annoyance, but YMMV. > The other advantage of SF (probably the main one in my mind) is that you can have multiplex your serial port using it. I use one app (like Listen) to log incoming packets and another app to display the useful data from the packets. This does not work so well if you connect to the serial port directly. Also, from the initial question, Im not sure why you are required to change your java code? All you need is to set the MOTECOM environment variable as described in the SerialComm documentation. http://www.tinyos.net/tinyos-1.x/doc/serialcomm/index.html KAR. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] excute patch
hi, i would like to excute MatlabControl-R13-R14.patch in cygwin. but i don't know the command syntax. could anybody give me a help? thx _ Play Q6 for your chance to WIN great prizes. http://q6trivia.imagine-live.com/enca/landing ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] uisp and mica2 programming problems
I have now fixed the problem properly and I thought I would post it on this mailing list for future reference. The simple fix was to change the low fuse to 0xFF. It was previously set at 0xFD which is what is stated in the fuse information on the xbow site. However, I noticed in a different Mica2 document that a screen shot of rd_fuses showed is was 0xFF. The difference here relates to the clock setting. According to page 37 of the ATMEGA128 datasheet OxFF is used for a XTAL with low rising power (start-up time from power save is 16K CK and additional delay from reset of 65ms). OxFD is used for a ceramic resonator with fast rising power (start-up time from power save is 1K CK and additional delay from reset is 4.1ms). This problem probably won't ever bother anyone with a purchased Mica2, but may catch out those people like me who are making a node from scratch. Cheers, Simon Simon Willis wrote: Some more news on this problem. It is still occurring, but I can now get around it consistently. I also discovered that it will program the board with no problems if I change the high fuse to 0xD9 (uisp makes is 0xD8). In my last email I said that I was setting this fuse to 0x19, but it seems 0xD9 also works. The only difference this has from the uisp 0xD8 is that the BOOTRST vector is disabled. Does anyone have any idea what's going on here? I also discovered that writing 0xD8 to the high fuse will allow me to read the fuses reliably (it seems), but when I program it (with Blink for example) the program does nothing. So here is how I program my boards: -Write 0xD9 (or 0x19) to the high fuse several times: uisp -dprog=mib510 -dserial=/dev/ttyS0 -dpart=ATmega128 --write_fuse_h=0xD9 -Check the fuses: uisp -dprog=mib510 -dserial=/dev/ttyS0 -dpart=ATmega128 --rd_fuses -If the fuse has changed then continue -Upload the program: make mica2 reinstall mib510,/dev/ttyS0 Does anyone have any ideas why it might be doing this or how I can fix it? Or even a few things I can do with the MIB510 to try and troubleshoot it? I have tried reinstalling cygwin and the tinyos environment, but this did not fix it. I am using TinyOS1.1.15 Thanks again, Simon Simon Willis wrote: I am having problems programming with uisp. I am using Blink for testing. I have a MIB510 and a board that we designed that is based on the mica2. Once I have programmed the ATMEGA128 I cannot reprogram it. It goes through all the correct actions, but the program doesn't seem to change (tested by changing the blinking LED) With a bit of playing around I discovered that I can get it to program after I change the fuse high byte to 0x98 (from 0xd8 set by uisp). This turns on the 'enable JTAG' option (even though I don't have the JTAG plugged in) then it works. Another problem is that when I issue a 'rd-fuses' command it will quite often return all 0s (or give some other error message), also the wr_fuses_h command usually takes about 5 attempts until it does actually change the fuses (checked using rd_fuses). Once it has changed the fuse to 0x98 then rd_fuses will work reliably and I can upload my program. I have also tried other combinations for fuses (like 0x19) and it seems that whenever the 'enable JTAG' option is on it will work. Does anyone have any idea why this might be or what might be wrong here? I have been able to replicate this problem on 2 boards now (I have only built 2 so far). Perhaps I should try changing the makefile so that uisp always enables JTAG, but this seems like a bit of a workaround problem, since normal mica2s seem to work OK. Anothter note: It also seems that I can't program a fresh ATMEGA with uisp until I have plugged in a JTAG and changed the fuses to 0xfd (e) 0x19 (h) 0xfe (l). Is this normal? I was thinking that perhaps this is done by Crossbow before the motes leave the factory. Thanks for your help. Simon ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Help!Vanderbilt Acoustic localisation
Hi! I want to have a try of Vanderbilt Acoustic Localisation Component,but I don't know how to to download the FULL minitasks/02/vu CVS directory from SourceForge. Should I download files one by one? Thanks in advance! Stanley Lee ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
