Oops!
Please ignore my last reply.
After looking at one the forum posts of David Gay, I went back to the most
recent mspgcc and did what he advised. Namely:
---------------------------------------
By default, TinyOS (ncc) assumes you're using a gcc compiled for
cygwin, and which therefore accepts cygwin paths like
/usr/lib/ncc/tdspecs. You're clearly using one compiled for win32,
which doesn't understand cygwin paths. You should be able to tell ncc
to use a gcc compiled for win32 by passing the -mingw-gcc flag to ncc
- this definitely used to work, though I'm not 100% sure if it still
works...
The easiest way to do this would be to add
PFLAGS += -mingw-gcc
to your Makelocal file in tinyos-2.x/support/make
David Gay
---------------------------------------
So now I'm getting this error:
---------------------------------------
fab...@fabien-pc /opt/tinyos-2.x/apps/Null
$ make z1
C:\cygwin\opt\tinyos-2.x\support\make\Makerules:32: warning, MAKERULES
contains
backslashes.
The environment variable MAKERULES contains backslashes \'s. This can
cause shell scripts including ones in this make system to fail in
strange ways. I've changed those to forward slashes for you for this
build. However, you are strongly encouraged to respecify MAKERULES as
either a standard unix-style path or as a mixed-style path where the
backslashes are replaced with forward slashes /'s.
mkdir -p build/z1
compiling NullAppC to a z1 binary
ncc -o build/z1/main.exe -Os -mingw-gcc -mdisable-hwmul -Wall -Wshadow
-Wnesc-
all -target=z1 -fnesc-cfile=build/z1/app.c -board= -fnesc-separator=__
-DDEFINED
_TOS_AM_GROUP=0x22 NullAppC.nc -lm
<commandline>: C file tos not found
<commandline>: component TinySchedulerC not found
<commandline>: Scheduler `TinySchedulerC' has no scheduling interface named
`Tas
kBasic'
In component `NullAppC':
NullAppC.nc:44: component MainC not found
In file included from NullAppC.nc:44:
In component `NullC':
NullC.nc:43: interface Boot not found
NullC.nc:47: `booted' is not in interface `Boot'
In component `NullAppC':
NullAppC.nc:46: cannot find `Boot'
make: *** [exe0] Error 1
---------------------------------------
Any suggestions there?
Thanks,
Fabien.
On Thu, Feb 4, 2010 at 7:59 PM, Fabien CHRAIM <[email protected]>wrote:
> Thank you for the reply Jordi.
>
> I have followed the instructions on the wiki. The only difference is that I
> installed an older mspgcc because the most recent one was giving me an
> error:
> "msp430-gcc.exe: /usr/lib/ncc/tdspecs: No such file or directory"
>
>
> But with the old mspgcc, I am getting a "bigger" error when I "make z1":
> ---------------------------------------------
> In file included from
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430Tim
> erC.nc:68,
> from
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430Clo
> ckC.nc:33,
> from
> C:\cygwin\opt\tinyos-2.x\tos/platforms/z1/PlatformC.nc:9,
> from C:\cygwin\opt\tinyos-2.x\tos/system/MainC.nc:50,
> from NullAppC.nc:44:
> In component `Msp430TimerCapComP':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc: In
> funct
> ion `Control.isInterruptPending':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc:81:
> `CCIF
> G' undeclared (first use in this function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc: In
> funct
> ion `Control.clearPendingInterrupt':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc:86:
> `CCIF
> G' undeclared (first use in this function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc: In
> funct
> ion `Capture.setSynchronous':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc:114:
> `SCS
> ' undeclared (first use in this function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc: In
> funct
> ion `Control.enableEvents':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc:121:
> `CCI
> E' undeclared (first use in this function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc: In
> funct
> ion `Control.disableEvents':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc:126:
> `CCI
> E' undeclared (first use in this function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc: In
> funct
> ion `Control.areEventsEnabled':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc:131:
> `CCI
> E' undeclared (first use in this function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc: In
> funct
> ion `Capture.isOverflowPending':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc:161:
> `COV
> ' undeclared (first use in this function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc: In
> funct
> ion `Capture.clearOverflow':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerCapComP.nc:166:
> `COV
> ' undeclared (first use in this function)
> In component `Msp430TimerC':
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc: At top
> level:
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:69:
> `TACCTL1_'
> undeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:69:
> `TACCR1_' u
> ndeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:70:
> `TACCTL2_'
> undeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:70:
> `TACCR2_' u
> ndeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:71:
> `TBCCTL0_'
> undeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:71:
> `TBCCR0_' u
> ndeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:72:
> `TBCCTL1_'
> undeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:72:
> `TBCCR1_' u
> ndeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:73:
> `TBCCTL2_'
> undeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:73:
> `TBCCR2_' u
> ndeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:74:
> `TBCCTL3_'
> undeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:74:
> `TBCCR3_' u
> ndeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:75:
> `TBCCTL4_'
> undeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:75:
> `TBCCR4_' u
> ndeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:76:
> `TBCCTL5_'
> undeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:76:
> `TBCCR5_' u
> ndeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:77:
> `TBCCTL6_'
> undeclared here (not in a function)
> C:\cygwin\opt\tinyos-2.x\tos/chips/msp430X/timer/Msp430TimerC.nc:77:
> `TBCCR6_' u
> ndeclared here (not in a function)
> make: *** [exe0] Error 1
>
>
> ----------------------------------------------------------
> (this was only the end of the error message)
>
>
> Any suggestions?
> Thank you
>
>
>
> On Thu, Feb 4, 2010 at 3:16 PM, Jordi Soucheiron <
> [email protected]> wrote:
>
>> We've been able to use msp430f2617 with tinyos 2.1.0
>> You'll find some documentation here: http://zolertia.sourceforge.net
>> Good luck
>>
>> 2010/2/4 Fabien CHRAIM <[email protected]>:
>> > Hello,
>> > Has anyone been able to successfully add support for family 2 MSP430
>> > processors? I've been trying to use the build-mspgcc script found here:
>> > http://www.tinyos.net/tinyos-1.x/tools/src/mspgcc/
>> > I've modified some things (like the mirror sites and the line that says
>> "cp
>> > -a "$BUILD_BASE"/mspgcc-cvs/gcc/gcc-3.3/* . || exit 1"), but I'm still
>> > getting errors. Last error in the terminal was:
>> >
>> -------------------------------------------------------------------------
>> > checking for clock_t... yes
>> > checking if mkdir takes one argument... no
>> > Configuration msp430-unknown-none not supported
>> > Configure in /home/fabien/build/gcc-3.2.3-obj/gcc failed, exiting.
>> >
>> -------------------------------------------------------------------------
>> > and looking at the config.log file, it ends at:
>> >
>> > configure:4863: checking for clock_t
>> > configure:4879: gcc -c -g -O2 -I/home/fabien/build/gcc-3.2.3/gcc
>> > -I/home/fabien/build/gcc-3.2.3/gcc/../include conftest.c 1>&5
>> > configure:4904: checking if mkdir takes one argument
>> > configure:4926: gcc -c -g -O2 conftest.c 1>&5
>> >
>> -------------------------------------------------------------------------
>> >
>> > I'm getting really frustrated with this so any help will be more than
>> > welcome. I wouldn't mind starting from scratch.
>> > Thank you,
>> > Fabien.
>> >
>> > _______________________________________________
>> > Tinyos-help mailing list
>> > [email protected]
>> >
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>> >
>>
>>
>>
>> --
>> Jordi Soucheiron
>> Software Engineer
>>
>> DEXMA
>> Parc Tecnològic la Salle
>> Sant Joan de la Salle, 42
>> 08022 Barcelona
>> t/f: [+34] 93 181 01 95
>> www.dexmatech.com
>> [email protected]
>>
>
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
