search

edysuardiyana / tinyos-main

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

Rfxlink problem on release 2.1.2 RC1 with telosb #116

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/rfxlink/TestTransmit
3. compile with "make telosb cc2420x" and program two motes

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

Expected: Leds should start toggling (see README).

Instead: Nothing happens. Additionally, if I add a "call Leds.led2On()" in 
Boot.booted, the led does not power on, as if the code never starts.

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

OS: Ubuntu Lucid 10.4
Tinyos: 2.1.2 RC1
Msp430-gcc: 4.5.3

Please provide any additional information below.

I have the same behavior by running TestNetworkLpl (it runs with "make telosb" 
but not with "make telosb cc2420x"), even if I don't know whether the rfxlink 
is supported on this app.

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

GoogleCodeExporter commented 9 years ago 
I plugged the JTAG and compiled RadioCountToLeds app with -O0 . It seems that 
the problem appears in CC2420XDriverLayerP.nc during SoftwareInit.init:
At the end of the function there is a call SpiResource.request() that, when 
granted calls the initRadio function. This function calls on its turn 
resetRadio() which writes on IOCFG0 register of CC2420. 
The writeRegister function fails on "status.value = call 
FastSpiByte.splitRead()" in the sense that it loops forever in 
Msp430SpiNoDMAP.nc in a while(! call Usart.isRxPending()) .
I commented the content of the resetRadio() function in CC2420XDriverLayerP and 
at least the mote boots (but of course the radio does not work).
Am I the only one having this issue? Am I missing something when using the 
cc2420x stack?

Original comment by ucolesa...@gmail.com on 16 Feb 2012 at 4:29

GoogleCodeExporter commented 9 years ago 
I have a custom application based on cc2420x which exhibits the same problem. 
Compiling with -O2 instead of -Os solved the problem for me though.

Original comment by marku...@gmail.com on 27 Feb 2012 at 3:26

GoogleCodeExporter commented 9 years ago 
Thanks a lot! it worked for me too.

Original comment by ucolesa...@gmail.com on 27 Feb 2012 at 3:40

GoogleCodeExporter commented 9 years ago 
fixed in r5914

Original comment by sallai.j...@gmail.com on 27 Feb 2012 at 7:08

GoogleCodeExporter commented 9 years ago

Original comment by marku...@gmail.com on 28 Feb 2012 at 8:34