[Tinyos-help] CC2420 transmission power
Hi guys, I was curious, I have done some experiments with RSSI and varying transmission power under the micaz. In the datasheet, I think it said that the respected powers were: 0x03, 0x07, 0x11, 0x15, 0x19, 0x23 and 0x27 However, I've had some strange results (some numbers not transmitting as far as lower powers, specifically). Does anyone know for sure or have any experience with the explicit transmission power levels on the CC2420? Thanks -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: CC2420 transmission power
Additionally, can anyone verify whether these numbers should be passed in as hex or base ten? On 2/14/06, Sam Pierson [EMAIL PROTECTED] wrote: Hi guys, I was curious, I have done some experiments with RSSI and varying transmission power under the micaz. In the datasheet, I think it said that the respected powers were: 0x03, 0x07, 0x11, 0x15, 0x19, 0x23 and 0x27 However, I've had some strange results (some numbers not transmitting as far as lower powers, specifically). Does anyone know for sure or have any experience with the explicit transmission power levels on the CC2420? Thanks -- Sam Pierson -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Tinysec version for micaz
Does anyone know of a package that provides link-layer encryption for the micaz motes? I think tinysec would be perfect, unfortunately, I read that it's only supported on mica2 motes and all I can work with right now are the micaz'. -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Pong application
Tony, I think this problem arises from the two different definitions of TOS_Msg (which I think you're using here). For example: in /opt/tinyos-1.x/tos: find . | grep AM.h ./platform/micaz/AM.h ./platform/telcos/AM.h ./types/AM.h if you grep each of these files for lqi, you'll only find it in the first, while the last default declaration of TOS_Msg doesn't contain it. I think this is because the CC2420 (which the micaz uses, I can't speak for telcos) uses an 8 bit RSSI and an 8 bit LQI on return of packets. I think you can make pong for the telco, right? I don't think it was intended for simulation, you might as well just run it on the motes [I think make pc includes the default AM.h file, not the ones containing lqi, therefore you wouldn't be able to get the LQI anyway (maybe)] -Sam Pierson Message: 5 Date: Thu, 26 Jan 2006 17:13:00 +0700 From: Chalermphol Thammapalerd [EMAIL PROTECTED] Subject: Re: [Tinyos-help] Pong application To: L Tony [EMAIL PROTECTED] Cc: tinyos-help@millennium.berkeley.edu Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=gb2312 Hi Tony, Install the Pong application into 2 motes, with different id. Start the SerialForwarder, then compile and use the java tool in the same directory, the usage is java PingPong. However, I've never tried your latter question. Hope someone can help you out. Good Luck, Chalermphol On 1/25/06, L Tony [EMAIL PROTECTED] wrote: Hi, I have some questions about Pong application on tmote sky. First, how to read RSSI and LQI value from base tmote? Second, I want to do some simulation on this application, but when I do make pc, there is an error in PongM.nc that in ReceiveMsg.receive, structure has no number named 'lqi'. Is there any error in the source code? If anyone who used this application, pls give me some more information. Thanks in advance. Best regards, Tony _ Ãâ·ÑÏÂÔØ MSN Explorer: http://explorer.msn.com/lccn ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Micaz UART message length problem
Message: 5 Date: Tue, 10 Jan 2006 08:14:14 -0800 From: David Gay [EMAIL PROTECTED] Subject: Re: [Tinyos-help] Micaz UART message length problem To: TINYOS HELP tinyos-help@millennium.berkeley.edu Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 You would hope, but owing to what I think is a rather broken decision, Crossbow decided to make micaz packets look like mica2 ones (it does some rewriting of packets in the serial layer to achieve this). Strangely, this isn't reflected all the way through, so when you specify micaz in your MOTECOM environment variable or in serial forwarder, it expects regular CC2420 packets. There's three basic fixes: - specify mica2 as the mote platform - remove the FramerM.nc file from platform/micaz (this removes the packet rewriting) - remove the #define MICA2MSGTYPE from the start of FramerM.nc (same effect as removing FramerM.nc, but maybe easier to switch around) David Gay David, Do you know how this affects the way the signal strength is reported through something like TOSBase on the micaz? Since the CC2420 reports an 8 bit number for RSSI and in the mica2 TOS_Msg, it is 16 bits, I've done a bit of fiddling with things. Before the packet is rewritten and forwarded over the serial port, I modified TOSBase such that it takes the micaz reported signal strength and overwrites 8bits of the data portion of the packet and is therefore not changed even if the packet is rewritten. I have not been successful in getting the old format, even following your above fix of commenting out the define line in FramerM.nc. It's strange to me, because the reported signal strength of the micaz is nowhere to be found in the rewritten packet (except the data portion as per above). Where do you suppose they're getting the bits that are being displayed as RSSI in the converted packet? I cannot determine, even after going though FramerM.nc. Anyone else have any ideas? On a last note, I'm 99% sure that my RSSI bits are correct. They stay the same while the distance between sending and receiving mote does not change, and when I move the motes closer, the values get closer to 0xFF and while I move them apart, they fall down to around 0xD2 before failing to receive packets at all. -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Yet Another Signal Strength Question [over micaz]
I should rephrase my question, after thinking about it more. While the micaz packets are being forwarded over the serial port, they're being rewritten into the old mica2 format. The mica2 TOS_Msg-strength member is declared as uint16_t while the same micaz member is declared as an eight bit value and the signal reading don't make much sense at this point. Does anyone know a way to accurately determine the signal strength of incoming RF packets to a micaz mote, while fixing the problem above? Thanks, On 1/18/06, Sam Pierson [EMAIL PROTECTED] wrote: Last question on the subject: I'm using micaz motes and in tos/platform/micaz/AM.h, TOS_Msg-strength is listed as type uint8_t and in tos/types/AM.h, TOS_Msg-strength is listed as type uint16_t. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Yet Another Signal Strength Question [over micaz]
I tried an interesting thing today, suggested to me by one of my professors: Copy the TOS_Msg-strength to the data section before TOSBase actually sends it over the UART. I did this: pBuf-data[2]=pBuf-strength; pBuf-data[1]=0x99; And then from there, examine the raw packet. The values that are copied into the data section are nothing like the 16 bits being called strength under the old AM.h. Though, the values that I copy into the data section change as I move the motes away from each other. When I leave the motes at a constant distance apart, the values stay very close together (vary by 1). I checked the CC2420 Manual and it says that it reports the RSSI in a range of 0-255, called LQI, link quality indicator. Any guesses to whether the 8 bits being copied into the data section are really the signal strength? Funny thing is, it really only goes from about 0xFF down to about 0xD2. I would *assume* that any signals lower than this cannot actually be picked up and are therefore dropped anyway. -Sam Pierson On 1/19/06, Michael Schippling [EMAIL PROTECTED] wrote: again I could be wrong about thisbut my one excursion into reading radio strength on the host side indicated that it is not actually being sent from TOSBase. I'd like to be proved wrong on that though. As long as you are within the TOS system itself, then everyone is using the same TOSMsg struct and you are not faced with field conversions. You might want to look through the CC2420 code in platform/micaz and see where the ADC is being pinged for the RSSI value, and what part of the 10bits is being truncated into the 8bit field. MS -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Yet Another Signal Strength Question [over micaz]
Hi everyone, I dug through the mailing list archives looking for some info on the received signal strength of incoming packets. I have one mote that transmits messages of type IntMsg over the radio. The other mote has TOSBase installed on it and is on the programming board, which is then connected to the serial port. When I use the java tool ListenRaw, I get things like the following: 7E 42 FF FF 04 7D 5D 04 22 00 01 00 EA 1E 7E 42 FF FF 04 7D 5D 04 23 00 01 00 5E 68 7E 42 FF FF 04 7D 5D 04 24 00 01 00 73 39 So from what I've gathered from micaz/AM.h: uint8_t length =-| uint8_t fcfhi =| Not sure about these top four. uint8_t fcflo = 7E | uint8_t dsn = 24 _| uint16_t destpan = FF FF uint16_t addr = 04 7D uint8_t type = 5D uint8_t group = 04 int8_t data = 22 uint8_t strength = 00-- ?? I know the 22, 23, 24 is the data portion, so ListenRaw or the serial port must be cutting something off from the beginning. It appears as though the strength is registered as 0 though. Does anyone know of a better approach? -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Micaz UART message length problem
Out of curiousity, this is related to a problem I had today... are these rewritten packets changed as far as received signal strength goes? As I said in a previous email, the micaz AM.h file declares TOS_Msg-strength as uint8_t and regular AM.h is uint16_t. Now my micaz messages being forwarded over the serial port are almost certainly in mica2 format, I'm not sure what to trust as far as strength goes. Date: Wed, 11 Jan 2006 01:37:39 -0800 From: Jeongyeup Paek [EMAIL PROTECTED] Subject: Re: [Tinyos-help] Micaz UART message length problem To: Michael Schippling [EMAIL PROTECTED] Cc: TINYOS HELP tinyos-help@millennium.berkeley.edu Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed David's suggestions (or more like solutions) should work. This has been an issue since the first release of MicaZ, and identical issue is appied to telos-series also. Here is a note that I had a year ago: == TOS_Msg Packet format in CC2420 (MicaZ and TelosB) A. currently there are two TOSMessage formats/structures: -MICA2 family (Mica, Mica2, Mica2dot), (tos/type/AM.h) -CC2420 family (MicaZ / Telos), (tos/platform/micaz/AM.h, tos/platform/msp430/AM.h) B. Legacy/MICA2 Users This is what we are doing! -Use host side tools (SerialForwarder, Surge gui etc) specifying MICA2 mode (eg. SerialForwarder [EMAIL PROTECTED]:mica2 ) -make micaz using maintree tos/platform/micaz. In this configuration All UART traffic to/from host is in MICA2 family TOSMsg format. Host applications process messages using MICA2 format. The platform/micaz FramerM.nc adapts UART traffic between the message types . Host application works directly across all platforms (mixed MICA2, MICAZ) C. TELOS/MICAZ Only Users -Must rebuild host side tools and use java tools specifying micaz mode -make micaz using maintree tos/platform/micaz AFTER removing the local FramerM.nc module. The tos/system FramerM.nc module handles MICAZ TOSMsg structure UART traffic. In this configuration All UART traffic to/from host is in MICAZ family TOSMsg format. Host applications process messages using MICAZ/telos format. Host application works in single platform (MICAz) network. * There are two 'FramerM' files in the tinyos tree. 1. tinyos-1.x/tos/system/FramerM.nc o This is the 'normal' file 2. tinyos-1.x/tos/platform/micaz/FramerM.nc o This file changes the Micaz/telos TOS_Msg header to Mica2 header ONLY WHEN sending over the UART. * If you want to use the latter to work, copy the latter to tinyos-1.x/tos/lib/CC2420/ * If you want to go back to the native formats, the just remove the file (which will use the former) ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] SendMsg not connected
Hey guys,
I'm trying to fix this program I'm writing, I think it is just a minor
problem. In the program, I send a message each time a timer
firers. I introduce the SendMsg interface like this:
uses {
interface SendMsg as SendIntMsg;
...
}
and then I send my message like this:
event result_t Timer.fired() {
message = (IntMsg *)buf.data;
message- val = 5;
message-src = 0x1456;
call SendIntMsg.send(TOS_BCAST_ADDR, sizeof(IntMsg), buf);
return SUCCESS;
}
When I compile for micaz by typing make micaz, it tells me:
RangerM.nc: In function 'Timer.fired':
RangerM.nc:66: SendIntMsg.send not connected
make: *** [exe0] Error 1
The thing I can't understand is how my other application can
successfully compile, since I do it almost exactly the same
way. I've tried variations of including some different components
that provide the SendMsg interface, but no luck.
Thanks,
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] SendMsg not connected
configuration Ranger {
}
implementation {
components Main, RangerM, SingleTimer, LedsC, GenericComm as Comm;
Main.StdControl - SingleTimer.StdControl;
Main.StdControl - RangerM.StdControl;
RangerM.Timer - SingleTimer.Timer;
RangerM.Leds - LedsC;
}
I have GenericComm in there because I read it was a component that
provides the SendMsg interface, but again I'm having trouble with it.
Thanks
On 1/16/06, Dave Tucker [EMAIL PROTECTED] wrote:
(Offline) Can you send the file that links RangerM as well ?
Dave
On Mon, Jan 16, 2006 at 03:33:55PM -0600, Sam Pierson wrote:
Hey guys,
I'm trying to fix this program I'm writing, I think it is just a minor
problem. In the program, I send a message each time a timer
firers. I introduce the SendMsg interface like this:
uses {
interface SendMsg as SendIntMsg;
...
}
and then I send my message like this:
event result_t Timer.fired() {
message = (IntMsg *)buf.data;
message- val = 5;
message-src = 0x1456;
call SendIntMsg.send(TOS_BCAST_ADDR, sizeof(IntMsg), buf);
return SUCCESS;
}
When I compile for micaz by typing make micaz, it tells me:
RangerM.nc: In function 'Timer.fired':
RangerM.nc:66: SendIntMsg.send not connected
make: *** [exe0] Error 1
The thing I can't understand is how my other application can
successfully compile, since I do it almost exactly the same
way. I've tried variations of including some different components
that provide the SendMsg interface, but no luck.
Thanks,
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
Sam Pierson
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] CC2420Radio sendFailed, sendDone
I was curious about a strange warning I received when
I compiled a program involving the micaz radio stack:
C:/tinyos/snip/tos/lib/CC2420Radio/CC2420RadioM.nc:115: warning:
`Send.sendDone' called asynchronously from 'sendFailed'
The relevent snippet is:
void sendFailed() {
atomic stateRadio = IDLE_STATE;
txbufptr-length = txbufptr-length - MSG_HEADER_SIZE - MSG_FOOTER_SIZE;
signal Send.sendDone(txbufptr, FAIL);
}
I'm in tinyos 1.1.10 right now.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: Tinyos-help Digest, Vol 33, Issue 18
In the latter case, where I don't want parallel directory trees, I simply download the directories you mentioned and then add them to the beginning of my path? Then after this, I just need to wire TimeSyncC.StdControl to Main.StdControl and it will be set? Thanks a ton, Date: Tue, 10 Jan 2006 17:24:51 -0600 From: Janos Sallai [EMAIL PROTECTED] Subject: RE: [Tinyos-help] FTSP application To: tinyos-help@Millennium.Berkeley.EDU Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Sam, There is a readme file in contrib/vu that explains how to set up the build environment we use at VU. Basically, we have another tinyos directory structure that precedes the official tinyos directory structure in the search path and thus redefines some of the components in the official release. If you go for this option, all you need to do is to wire TimeSyncC.StdControl to Main.StdControl and you are all set. Alternatively, if you are bound to a build environment or simply you do not want two parallel directory structures, you can put together your search path manually. This is what you will need from contrib/vu: tos/lib/TimeSync tos/platform/avrmote tos/platform/mica2 tos/lib/CC2420 (for micaz) Make sure that the components in these directories precede the corresponding ones from the official tinyos release in your search path. Janos -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sam Pierson Sent: Tuesday, January 10, 2006 4:51 PM To: tinyos-help@Millennium.Berkeley.EDU Subject: [Tinyos-help] FTSP application I know there is a testing application that verifies the accuracy of the FTSP algorithm for mica2/micaz networks. Is there a codebase which I can simply insert into my existing application so that it would synchronize itself upon startup? Or is it not that easy? Thanks, ___ 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] FTSP application
I know there is a testing application that verifies the accuracy of the FTSP algorithm for mica2/micaz networks. Is there a codebase which I can simply insert into my existing application so that it would synchronize itself upon startup? Or is it not that easy? Thanks, ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: Tinyos-help Digest, Vol 33, Issue 10
I tried all of the following suggestions, and the same problem arises. I installed tinyos 1.1.11 because I had the install shield version and it seems to be much cleaner than installing 1.1.0 and then upgrading via RPM to 1.1.10. I could only find the January cvs release of 1.1.10. The programming board does not respond to /dev/ttyS0 and hangs again when I try to manually use uisp as below. I know that my programming board is on COM1. Is there any other step I can take? Thanks, Date: Fri, 6 Jan 2006 13:52:18 -0800 From: Mike Smith [EMAIL PROTECTED] Subject: [Tinyos-help] trouble uploading to mica z To: tinyos-help@Millennium.Berkeley.EDU Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Sam, Crossbow currently supports TinyOS 1.1.10 for the use of our software applications. There are several bugs in the more recent versions and although we continue to test some of the newest versions we think it is important to have a stable version to work from. In response to your questions, please consider the following possibilities: 1) Make sure that your SW2 switch is in the OFF position on the MIB510 at all times and make sure that the green LED is lit. 2) In version 1.1.11 and higher you will need to type make micaz install mib510,/dev/ttyS0 for COM1, ttyS1 for COM2 the first time you attempt to install to the mote. If you don't do this, you can hang the COM port which prevents further communication. Simply reboot the computer and try the command line above if you have a frozen COM port 3) Your output should look like this: uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128 The -dprog indicates you are using the MIB510 and the -dserial output indicates your COM port. If the -dprog output states dapa, this means you are trying to access the parallel port which will result in a series of flash errors. Sincerely, Michael Smith Application Engineer/Tech Support Crossbow Technology, Inc. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: Trouble uploading to micaz
I apologize for not editing subject on the previous email! On 1/9/06, Sam Pierson [EMAIL PROTECTED] wrote: I tried all of the following suggestions, and the same problem arises. I installed tinyos 1.1.11 because I had the install shield version and it seems to be much cleaner than installing 1.1.0 and then upgrading via RPM to 1.1.10. I could only find the January cvs release of 1.1.10. The programming board does not respond to /dev/ttyS0 and hangs again when I try to manually use uisp as below. I know that my programming board is on COM1. Is there any other step I can take? Thanks, Date: Fri, 6 Jan 2006 13:52:18 -0800 From: Mike Smith [EMAIL PROTECTED] Subject: [Tinyos-help] trouble uploading to mica z To: tinyos-help@Millennium.Berkeley.EDU Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Sam, Crossbow currently supports TinyOS 1.1.10 for the use of our software applications. There are several bugs in the more recent versions and although we continue to test some of the newest versions we think it is important to have a stable version to work from. In response to your questions, please consider the following possibilities: 1) Make sure that your SW2 switch is in the OFF position on the MIB510 at all times and make sure that the green LED is lit. 2) In version 1.1.11 and higher you will need to type make micaz install mib510,/dev/ttyS0 for COM1, ttyS1 for COM2 the first time you attempt to install to the mote. If you don't do this, you can hang the COM port which prevents further communication. Simply reboot the computer and try the command line above if you have a frozen COM port 3) Your output should look like this: uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128 The -dprog indicates you are using the MIB510 and the -dserial output indicates your COM port. If the -dprog output states dapa, this means you are trying to access the parallel port which will result in a series of flash errors. Sincerely, Michael Smith Application Engineer/Tech Support Crossbow Technology, Inc. -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] trouble uploading to mica z
I reinstalled everything from scratch today, installed first 1.1.0 and then
upgraded to 1.1.11 and it failed. I then upgraded to 1.1.15cvs snapshot
from December, but it still fails. I notice now that I cannot interrupt the
transfer where it's stuck and it isn't doing the receive infinite loop anymore,
it is just sitting blank after two transmits, as in the email below.
On 1/5/06, Sam Pierson [EMAIL PROTECTED] wrote:
Specifically,
$ uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128
--wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out -v=4
Transmit: { . [aa] U [55] U [55] . [aa] . [17] Q [51] 1 [31] . [13] . [01] }
Transmit: { . [aa] U [55] U [55] . [aa] . [17] Q [51] 1 [31] . [13] . [01] }
Receive: { }
Receive: { }
Receive: { }
Receive: { }
Receive: { }
...
On 1/5/06, Sam Pierson [EMAIL PROTECTED] wrote:
It appears as though mine is stuck in the same Receive loop.
On 1/5/06, Hannes Geissbuehler [EMAIL PROTECTED] wrote:
I have exaclty the same problem..
till last week it worked and now it dies during trying to uplad the file.
Could It be that a new Windows Bugfix somehow prevents some commands to
the com port ?
running the uisp in debug mode shows that it ends in an endless loop
of
Receive: { } commands..
any Ideas ?
Hannes
I've been sort of stuck on this after trying a lot of different things.
I have an MIB510 board and a few micaz motes. I connect the
board to this laptop through the serial port. I've successfully
uploaded binaries to mica2's in the past.
Now I've tried on tinyos 1.1.10, 1.1.11, and the latest 1.1.15 cvs
snapshot. The problem still occurs:
If I try to upload the Blink app, for example, I do this:
make micaz install mib510,com1
It compiles the binary and then executes this command to upload:
uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128
--wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out
But it just sits here during this command and nothing happens.
Any ideas would be appreciated.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
Sam Pierson
--
Sam Pierson
--
Sam Pierson
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] trouble uploading to mica z
I've been sort of stuck on this after trying a lot of different things. I have an MIB510 board and a few micaz motes. I connect the board to this laptop through the serial port. I've successfully uploaded binaries to mica2's in the past. Now I've tried on tinyos 1.1.10, 1.1.11, and the latest 1.1.15 cvs snapshot. The problem still occurs: If I try to upload the Blink app, for example, I do this: make micaz install mib510,com1 It compiles the binary and then executes this command to upload: uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128 --wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out But it just sits here during this command and nothing happens. Any ideas would be appreciated. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] trouble uploading to mica z
I tried this earlier, using the line like you said and then I tried the line, but using micaz instead. Both resulted in the scrolling Flash error at address... errors. The difference is the uisp command syntax, with this way: uisp -dprog=dapa --wr_fuse_h=0xd8 -dpart=ATmega128 --wr_fuse_e=ff --upload if=build/micaz/main.srec.out I would assume my original port specification is correct, since here it says -dprog=dapa, as opposed to mib510, which is what I'm using. On 1/5/06, Sankar Gorthi [EMAIL PROTECTED] wrote: I had the same problem with the Mica2's programming them with a serial programmer (I had worked with the parallel programmer before with mica's). The MIB510=COM1 command is apparently case-sensitive. Please try that. Could work. MIB510=COM1 make mica2 install(/reinstall) Sankar. On Thu, 05 Jan 2006 14:22:20 -0600, Sam Pierson [EMAIL PROTECTED] wrote: I've been sort of stuck on this after trying a lot of different things. I have an MIB510 board and a few micaz motes. I connect the board to this laptop through the serial port. I've successfully uploaded binaries to mica2's in the past. Now I've tried on tinyos 1.1.10, 1.1.11, and the latest 1.1.15 cvs snapshot. The problem still occurs: If I try to upload the Blink app, for example, I do this: make micaz install mib510,com1 It compiles the binary and then executes this command to upload: uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128 --wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out But it just sits here during this command and nothing happens. Any ideas would be appreciated. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] trouble uploading to mica z
I did, and it said: Programmer is not responding. make: *** [program] Error 2 On 1/5/06, David Moss [EMAIL PROTECTED] wrote: Have you tried make micaz install mib510,/dev/ttyS0 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sam Pierson Sent: Thursday, January 05, 2006 1:22 PM To: tinyos-help@Millennium.Berkeley.EDU Subject: [Tinyos-help] trouble uploading to mica z I've been sort of stuck on this after trying a lot of different things. I have an MIB510 board and a few micaz motes. I connect the board to this laptop through the serial port. I've successfully uploaded binaries to mica2's in the past. Now I've tried on tinyos 1.1.10, 1.1.11, and the latest 1.1.15 cvs snapshot. The problem still occurs: If I try to upload the Blink app, for example, I do this: make micaz install mib510,com1 It compiles the binary and then executes this command to upload: uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128 --wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out But it just sits here during this command and nothing happens. Any ideas would be appreciated. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] trouble uploading to mica z
It appears as though mine is stuck in the same Receive loop.
On 1/5/06, Hannes Geissbuehler [EMAIL PROTECTED] wrote:
I have exaclty the same problem..
till last week it worked and now it dies during trying to uplad the file.
Could It be that a new Windows Bugfix somehow prevents some commands to
the com port ?
running the uisp in debug mode shows that it ends in an endless loop
of
Receive: { } commands..
any Ideas ?
Hannes
I've been sort of stuck on this after trying a lot of different things.
I have an MIB510 board and a few micaz motes. I connect the
board to this laptop through the serial port. I've successfully
uploaded binaries to mica2's in the past.
Now I've tried on tinyos 1.1.10, 1.1.11, and the latest 1.1.15 cvs
snapshot. The problem still occurs:
If I try to upload the Blink app, for example, I do this:
make micaz install mib510,com1
It compiles the binary and then executes this command to upload:
uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128
--wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out
But it just sits here during this command and nothing happens.
Any ideas would be appreciated.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
Sam Pierson
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] trouble uploading to mica z
Specifically,
$ uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128
--wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out -v=4
Transmit: { . [aa] U [55] U [55] . [aa] . [17] Q [51] 1 [31] . [13] . [01] }
Transmit: { . [aa] U [55] U [55] . [aa] . [17] Q [51] 1 [31] . [13] . [01] }
Receive: { }
Receive: { }
Receive: { }
Receive: { }
Receive: { }
...
On 1/5/06, Sam Pierson [EMAIL PROTECTED] wrote:
It appears as though mine is stuck in the same Receive loop.
On 1/5/06, Hannes Geissbuehler [EMAIL PROTECTED] wrote:
I have exaclty the same problem..
till last week it worked and now it dies during trying to uplad the file.
Could It be that a new Windows Bugfix somehow prevents some commands to
the com port ?
running the uisp in debug mode shows that it ends in an endless loop
of
Receive: { } commands..
any Ideas ?
Hannes
I've been sort of stuck on this after trying a lot of different things.
I have an MIB510 board and a few micaz motes. I connect the
board to this laptop through the serial port. I've successfully
uploaded binaries to mica2's in the past.
Now I've tried on tinyos 1.1.10, 1.1.11, and the latest 1.1.15 cvs
snapshot. The problem still occurs:
If I try to upload the Blink app, for example, I do this:
make micaz install mib510,com1
It compiles the binary and then executes this command to upload:
uisp -dprog=mib510 -dserial=com1 --wr_fuse_h=0xd8 -dpart=ATmega128
--wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out
But it just sits here during this command and nothing happens.
Any ideas would be appreciated.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
Sam Pierson
--
Sam Pierson
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] java signal strength?
I know you can retrieve the signal strength of an incoming packet in tinyos, but if you have a mote on a mica2 forwarding packets to a java program through TOSBase, is it possible to use the java program on the computer to analyze the signal strength of said packet? Thanks, ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Playing with CC1000Control.SetRFPower
Hi all, I'm beginning to explore transmission power control with the mica2. I read some other posts from awhile back which describe the way to control the signal strength: 1) wire to CC1000Control and 2) call SetRFPower. I added a couple lines to IntToRfmM.nc to see if I could make a difference but I only end up with compiler errors and I don't understand what I'm doing wrong. I add uses CC1000Control under the uses part of IntToRfmM.nc and I add the line call CC1000Control.SetRFPower(0x02); in the function IntOutput.output. When I attempt to compile CntToRfm (which uses IntToRfm), it reports a compiler-time error, saying CC1000Control.SetRFPower not connected. I can only assume that I have not wired something correctly, but I don't know what. Can someone point out my error? -- Sam Pierson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
