search

VijayaLakshmiMaurya / tinyos-main

Automatically exported from code.google.com/p/tinyos-main
0 stars 0 forks source link

Deluge problem on tinyos-2.1.2-rc1 with telosb #115

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Checkout release-2.1.2-rc1 from tags folder 
2. go in apps/tests/deluge/Blink
3. run ./burn bsl,/dev/ttyUSB0 serial@/dev/ttyUSB0:115200 telosb

What is the expected output? What do you see instead?

Expected: After the first step of the script, there should be a leds fading 
(tosboot) then the red led should start blinking, after the second step the 
node should get reprogrammed and the blue led should start blinking.

Instead: the code gets compiled with no errors and the mote is programmed, but 
after the first step there is no leds fading and the blink app seems not to 
start. If I press ENTER anyway to proceed with the second step, the script 
gives me the following error: "ERROR: Timeout. Is the node a Deluge T2 base 
station?"

What version of the product are you using? On what operating system?

OS: ubuntu lucid 10.4 64bit

TinyOS distribution: 2.1.2 RC1

Msp430-gcc: 4.5.3

Please provide any additional information below.

By replacing msp430-gcc 4.5.3 with the old one (3.2.3), the first step passes 
(leds fading and red led blinking), but the second step fails (the Reverse 
Blink seems not to be copied correctly on the mote and the  red led keeps 
blinking).

Using official 2.1.1 with msp430-gcc 3.2.3 and checking out the tools folder 
from trunk everything works fine.

Original issue reported on code.google.com by ucolesa...@gmail.com on 9 Feb 2012 at 11:35

GoogleCodeExporter commented 9 years ago 
Since Vlado is responsible for Telos testing I've assigned it to him.

Original comment by philip.l...@gmail.com on 8 Mar 2012 at 10:47

GoogleCodeExporter commented 9 years ago 
I did not have time to look closer into the deluge errors when I was testing, 
but I suspect that at least some of the problems are related to tosboot 
incompatibilities with the new toolchain. I don't have a lot of spare cycles at 
the moment, so it would be great if someone steps forward and takes over the 
issue.

Original comment by vlado.handziski on 8 Mar 2012 at 11:00

GoogleCodeExporter commented 9 years ago 
Issue resolved with revision 5957

Original comment by vlado.handziski on 15 Jun 2012 at 4:18

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Watchdog state fix and delay loop fix in revision 5955 and revision 5956

Original comment by vlado.handziski on 15 Jun 2012 at 4:24