On Thu, Jul 12, 2012 at 11:31 AM, steve ayer <[email protected]> wrote:

> all,
>
> i just printed out my original post and stepped through it with a fairly
> crufty version of the shimmer distro vmware image.  i found the problem at
> the end after finishing: the msp430-46 all installation doesn't upgrade
> nesc (or, not visibly anyway); you need nesc >= 1.3.3 to work with the new
> toolchain.
>

Hi,

I'm Eric for everyone else on this list (Steve already knows who I am) and
I maintain the tinyprod repository.   Yes all volunteer so some times it
takes a while for things to change.

I don't think the problem that Franz originally saw had anything to do with
nesc being down rev.   Although it is a good idea to bring nesc up to
currency.   If you build 1.3.4 that is good.   1.3.3 from deb
http://tinyprod.net/repos/debian squeeze main (nesc) is fine for the time
being.

The TinyProd repository is getting a face lift and nesc 1.3.4 will be out
there soon.

1.3.4 fixes some bugs but more importantly fixes problems with the nesc to
msp430-gcc 4.7 interface.   It is fully backward compatable with all
previous msp430-gcc installations.

But I don't think nesc being down rev had anything to do with Franz's
problem.


Now back to Franz's original problem:


   WARNING: Minimum recommended msp430-gcc version for this TinyOS release
> is 4.6.3!!!
> ncc -o build/shimmer2r/main.exe  -Os -fnesc-separator=__ -Wall -Wshadow
> -Wnesc-all -target=shimmer2r -fnesc-cfile=build/shimmer2r/**app.c -board=
> -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\"
> -DIDENT_USERNAME=\"tiny2\" -DIDENT_HOSTNAME=\"**ShimmerLive\"
> -DIDENT_USERHASH=0xe8d0c5b7L -DIDENT_TIMESTAMP=0x4ffec110L
> -DIDENT_UIDHASH=0x25356caaL  BlinkAppC.nc -lm
> In file included from /home/tiny2/tinyos-main/tos/**
> platforms/shimmer/chips/**msp430/msp430hardware.h:46,
>                  from /home/tiny2/tinyos-main/tos/**
> platforms/shimmer2r/hardware.**h:39,
>                  from /home/tiny2/tinyos-main/tos/**
> system/SchedulerBasicP.nc:52:
> /opt/msp430/msp430/include/io.**h:93:2: warning: #warning "Unknown arch!
> Please check"
> In file included from /home/tiny2/tinyos-main/tos/**
> system/TinySchedulerC.nc:52:
> In component `McuSleepC':
> /home/tiny2/tinyos-main/tos/**chips/msp430/McuSleepC.nc: In function
> `getPowerState':
> /home/tiny2/tinyos-main/tos/**chips/msp430/McuSleepC.nc:77: `TACCTL0'
> undeclared (first use in this function)
> /home/tiny2/tinyos-main/tos/**chips/msp430/McuSleepC.nc:77: (Each
> undeclared identifier is reported only once
> /home/tiny2/tinyos-main/tos/**chips/msp430/McuSleepC.nc:77: for each
> function it appears in.)
>
>
>

The line bitching about TACCTL0 is a clue.   TACCTL0 is a control register
in the cpu and being bitched about indicates that the underlying toolchain
is out of date.   This indicates version skew in the toolchain and in
particular the compiler version.


Anytime something weird like the above happens, the first things anyone
should do is the following:

ncc --version
msp430-gcc --version

The output should look like something like....

(this is assuming that one is using the SVN T2 development trunk or the
upcoming T2.1.2 release)

zot (19): ncc --version
ncc: 1.2.4
nescc: 1.3.4x

(the cruft in yellow below, you can ignore, we didn't tell ncc what
platform we are using so invoked the native compiler, you can ignore that
output)
gcc: gcc (Ubuntu/Linaro 4.6.1-9ubuntu3) 4.6.1
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

zot (20): msp430-gcc --version
msp430-gcc (GCC) 4.6.3 20120301 (mspgcc LTS 20120406 unpatched)
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
_______________________________________________
Shimmer-users mailing list
[email protected]
https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users

Reply via email to