I fix it! 
Well, rather than fix it I erased everything and tried with a fresh copy of 
Ubuntu 11 and it worked. 


The only thing I had to patch was adding: 



CFLAGS += -I/usr/msp430/include 
CFLAGS += -I/usr/lib/gcc/msp430/4.5.3/include 


in the msp.rules file, but I had to do that also for Ubuntu 10, because for 
some strange reason the new ubuntu don't include that two lines. Maybe it can 
be included in some version of TinyOS. 


Thank you very much!! 


Regards, 
Alfonso Martínez 
----- Mensaje original ----- 
De: "Eric Decker" <[email protected]> 
Para: "Philip Levis" <[email protected]> 
CC: "Alfonso Martinez" <[email protected]>, 
[email protected] 
Enviados: Martes, 23 de Agosto 2011 21:04:32 
Asunto: Re: [Tinyos-help] MSPGCC and telosb problem 



Something is very screwy in his development environment. 


There is somekind of skew between parts that were updated and other parts that 
aren't. 


I'm guessing he got the new msp430-gcc but didn't get the msp430mcu or possibly 
the msp430libc parts. 


__BCSCTL1 is defined by the cpu header which isn't getting included properly. 




Bottom line, his development tools are not set up properly. 


eric 



On Tue, Aug 23, 2011 at 10:33 AM, Philip Levis < [email protected] > wrote: 






On Aug 23, 2011, at 6:59 AM, Alfonso Martinez wrote: 

> Hi! 
> 
> I have been working for some time with TinyOS 2.1.1 with telosb motes without 
> any problem, but recently I have updated the MSP430 GCC using Synaptic in 
> Ubuntu 10.10 and when now I try to compile for example Blink it gives me a 
> lot of errors: 
> 
> /tmp/ccr4C49d.o: In function `__nesc_atomic_end': 
> app.c:(.text+0x88): undefined reference to `__eint' 
> /tmp/ccr4C49d.o: In function `__nesc_disable_interrupt': 
> app.c:(.text+0x8e): undefined reference to `__dint' 
> app.c:(.text+0x92): undefined reference to `__nop' 
> /tmp/ccr4C49d.o: In function `__nesc_atomic_start': 
> app.c:(.text+0x9a): undefined reference to `__read_status_register' 
> /tmp/ccr4C49d.o: In function `main': 
> app.c:(.text+0x5ce): undefined reference to `__BCSCTL1' 
> app.c:(.text+0x5d2): undefined reference to `__BCSCTL2' 
> app.c:(.text+0x5d8): undefined reference to `__TBCCTL0' 
> app.c:(.text+0x5f4): undefined reference to `__BCSCTL1' 
> app.c:(.text+0x5fe): undefined reference to `__BCSCTL1' 
> app.c:(.text+0x602): undefined reference to `__DCOCTL' 
> app.c:(.text+0x60e): undefined reference to `__TBR' 
> app.c:(.text+0x614): undefined reference to `__TBCCR0' 
> app.c:(.text+0x618): undefined reference to `__TBCCTL0' 
> app.c:(.text+0x61c): undefined reference to `__TBCCTL0' 
> app.c:(.text+0x624): undefined reference to `__TAR' 
> app.c:(.text+0x65c): undefined reference to `__BCSCTL1' 
> app.c:(.text+0x666): undefined reference to `__BCSCTL1' 
> app.c:(.text+0x66a): undefined reference to `__DCOCTL' 
> app.c:(.text+0x66e): undefined reference to `__BCSCTL1' 
> app.c:(.text+0x67a): undefined reference to `__BCSCTL1' 
> app.c:(.text+0x67e): undefined reference to `__BCSCTL2' 
> app.c:(.text+0x686): undefined reference to `__TAR' 
> app.c:(.text+0x690): undefined reference to `__TBR' 
> app.c:(.text+0x6ba): undefined reference to `__P1SEL' 
> app.c:(.text+0x6be): undefined reference to `__P2SEL' 
> app.c:(.text+0x6c2): undefined reference to `__P3SEL' 
> app.c:(.text+0x6c6): undefined reference to `__P4SEL' 
> app.c:(.text+0x6ca): undefined reference to `__P5SEL' 
> app.c:(.text+0x6ce): undefined reference to `__P6SEL' 
> app.c:(.text+0x6d2): undefined reference to `__P1OUT' 
> app.c:(.text+0x6d8): undefined reference to `__P1DIR' 
> app.c:(.text+0x6de): undefined reference to `__P2OUT' 
> app.c:(.text+0x6e4): undefined reference to `__P2DIR' 
> app.c:(.text+0x6e8): undefined reference to `__P3OUT' 
> app.c:(.text+0x6ee): undefined reference to `__P3DIR' 
> app.c:(.text+0x6f4): undefined reference to `__P4OUT' 
> app.c:(.text+0x6fa): undefined reference to `__P4DIR' 
> app.c:(.text+0x6fe): undefined reference to `__P5OUT' 
> app.c:(.text+0x702): undefined reference to `__P5DIR' 
> app.c:(.text+0x706): undefined reference to `__P6OUT' 
> app.c:(.text+0x70a): undefined reference to `__P6DIR' 
> app.c:(.text+0x70e): undefined reference to `__P1IE' 
> app.c:(.text+0x712): undefined reference to `__P2IE' 
> app.c:(.text+0x716): undefined reference to `__TAR' 
> app.c:(.text+0x71e): undefined reference to `__TAR' 
> app.c:(.text+0x748): undefined reference to `__nop' 
> app.c:(.text+0x74c): undefined reference to `__nop' 
> app.c:(.text+0x852): undefined reference to `__eint' 
> app.c:(.text+0x882): undefined reference to `__TACCTL0' 
> app.c:(.text+0x88c): undefined reference to `__TACCTL1' 
> app.c:(.text+0x898): undefined reference to `__TACCTL2' 
> app.c:(.text+0x8a4): undefined reference to `__TACTL' 
> app.c:(.text+0x8b4): undefined reference to `__ME1' 
> app.c:(.text+0x8ba): undefined reference to `__U0TCTL' 
> app.c:(.text+0x8c4): undefined reference to `__ME2' 
> app.c:(.text+0x8ce): undefined reference to `__U1TCTL' 
> collect2: ld devolvió el estado de salida 1 
> make: *** [exe0] Error 1 
> 
> 
> It looks like a problem with the register library, but I don't know how to 
> fix it. 
> I tried to download the last version of TinyOS doing svn checkout 
> http://tinyos-main.googlecode.com/svn/trunk/ tinyos-2.x but it continues the 
> same. 
> 
> Any ideas of how to fix it? 
> 
> Thanks in advance! 


Alfonso, 

1) Which version of msp430-gcc and msp430-binutils are you using? Are they the 
updated TinyOS packages or something from another repository? 
2) Can you give an example application that causes this error? E.g., tell me 
how to repeat it fully? 

Phil 



_______________________________________________ 
Tinyos-help mailing list 
[email protected] 
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help 




-- 
Eric B. Decker 
Senior (over 50 :-) Researcher 


_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to