Hi Franz,

Yeah, I get the same warnings. I also get the exact same image size (for
the Bluetooth test app), which more or less indicates (baring a major
coincidence) that our development environments are the same.

My full output is below (including proof of connection and nesc and
msp430-gcc versions).

Mike


mgh@desktop:/opt/tinyos-2.x-contrib/shimmer/swtest/Bluetooth$ make
> shimmer2r install bsl,/dev/ttyUSB0
> mkdir -p build/shimmer2r
>     compiling TestBluetoothAppC to a shimmer2r binary
> 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=\"TestBluetoothAp\"
> -DIDENT_USERNAME=\"mgh\" -DIDENT_HOSTNAME=\"desktop\"
> -DIDENT_USERHASH=0x649a0bd4L -DIDENT_TIMESTAMP=0x5003f805L
> -DIDENT_UIDHASH=0xa74471b5L  TestBluetoothAppC.nc -lm
> TestBluetoothC.nc:73: warning: `activityTimer.startPeriodic' called
> asynchronously from `Bluetooth.connectionMade'
> TestBluetoothC.nc:78: warning: `activityTimer.stop' called asynchronously
> from `Bluetooth.connectionClosed'
> /opt/msp430-46/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/include/msp430f1611.h:275:
> warning: non-atomic accesses to shared variable `P1IE':
> /opt/tinyos-main/tos/chips/msp430/pins/HplMsp430InterruptP.nc:92:
> warning:   non-atomic r/w
> /opt/msp430-46/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/include/msp430f1611.h:271:
> warning: non-atomic accesses to shared variable `P1IFG':
> /opt/tinyos-main/tos/chips/msp430/pins/HplMsp430InterruptP.nc:108:
> warning:   non-atomic r/w
> /opt/msp430-46/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/include/msp430f1611.h:286:
> warning: non-atomic accesses to shared variable `P2IFG':
> /opt/tinyos-main/tos/chips/msp430/pins/HplMsp430InterruptP.nc:212:
> warning:   non-atomic r/w
> /opt/msp430-46/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/include/msp430f1611.h:290:
> warning: non-atomic accesses to shared variable `P2IE':
> /opt/tinyos-main/tos/chips/msp430/pins/HplMsp430InterruptP.nc:196:
> warning:   non-atomic r/w
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:74:
> warning: non-atomic accesses to shared variable `btConnected':
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:308:
> warning:   non-atomic read
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:318:
> warning:   non-atomic read
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:547:
> warning:   non-atomic write
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:74:
> warning: non-atomic accesses to shared variable `runningMasterCommands':
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:312:
> warning:   non-atomic write
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:321:
> warning:   non-atomic write
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:332:
> warning:   non-atomic write
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:547:
> warning:   non-atomic write
> TestBluetoothC.nc: In function ‘TestBluetoothC__sendStuff__runTask’:
> TestBluetoothC.nc:63:3: warning: pointer targets in passing argument 1 of
> ‘TestBluetoothC__Bluetooth__write’ differ in signedness [-Wpointer-sign]
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/Bluetooth.nc:51:23:
> note: expected ‘const uint8_t *’ but argument is of type ‘char *’
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:
> In function ‘RovingNetworksP__UARTData__rxDone’:
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:598:11:
> warning: pointer targets in passing argument 3 of ‘msg_cmp_buf’ differ in
> signedness [-Wpointer-sign]
> /opt/tinyos-main/tos/platforms/shimmer/shimmerMessage.h:194:22: note:
> expected ‘const uint8_t *’ but argument is of type ‘char *’
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:
> In function ‘RovingNetworksP__writeCommand’:
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:180:3:
> warning: pointer targets in passing argument 1 of
> ‘RovingNetworksP__Bluetooth__write’ differ in signedness [-Wpointer-sign]
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:97:16:
> note: expected ‘const uint8_t *’ but argument is of type ‘char *’
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:
> In function ‘RovingNetworksP__writeCommandNoRsp’:
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:191:3:
> warning: pointer targets in passing argument 1 of
> ‘RovingNetworksP__Bluetooth__write’ differ in signedness [-Wpointer-sign]
> /opt/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:97:16:
> note: expected ‘const uint8_t *’ but argument is of type ‘char *’
>     compiled TestBluetoothAppC to build/shimmer2r/main.exe
>             7752 bytes in ROM
>              578 bytes in RAM
> msp430-objcopy --output-target=ihex build/shimmer2r/main.exe
> build/shimmer2r/main.ihex
>     writing TOS image
> cp build/shimmer2r/main.ihex build/shimmer2r/main.ihex.out
>     installing shimmer2r binary using bsl
> tos-bsl --invert-test --invert-reset -c /dev/ttyUSB0 -r -e -I -p
> build/shimmer2r/main.ihex.out
> MSP430 Bootstrap Loader Version: 1.39-telos-8
> Mass Erase...
> Transmit default password ...
> Invoking BSL...
> Transmit default password ...
> Current bootstrap loader version: 1.61 (Device ID: f16c)
> Program ...
> 8066 bytes programmed.
> Reset device ...
> rm -f build/shimmer2r/main.exe.out build/shimmer2r/main.ihex.out


>

> mgh@desktop:/opt/tinyos-2.x-contrib/shimmer/swtest/Bluetooth$ rfcomm
> rfcomm0: 00:06:66:43:B7:71 channel 1 closed
>

>
mgh@desktop:/opt/tinyos-2.x-contrib/shimmer/swtest/Bluetooth$ miniterm
> /dev/rfcomm0
> --- Miniterm on /dev/rfcomm0: 9600,8,N,1 ---
> --- Quit: Ctrl+]  |  Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
> hello, bluetooth is awake!hello, bluetooth is awake!hello, bluetooth is
> awake!hello, bluetooth is awake!
> --- exit ---
>

>
mgh@desktop:/opt/tinyos-2.x-contrib/shimmer/swtest/Bluetooth$ msp430-gcc -v
> Using built-in specs.
> Reading specs from
> /opt/msp430-46/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/lib/msp430mcu.spec
> COLLECT_GCC=msp430-gcc
>
> COLLECT_LTO_WRAPPER=/opt/msp430-46/bin/../libexec/gcc/msp430/4.6.3/lto-wrapper
> Target: msp430
> Configured with: ../configure
> --prefix=/bleed2/ayer/tinyos-toolchain/tinyos-2.x/tools/platforms/msp430/toolchain-46/debian/opt/msp430-46
> --target=msp430 --enable-languages=c
> Thread model: single
> gcc version 4.6.3 20120301 (mspgcc LTS 20120406 unpatched) (GCC)


>
mgh@desktop:/opt/tinyos-2.x-contrib/shimmer/swtest/Bluetooth$ ncc -v
> /usr/bin/nescc -fnesc-include=tos -topdir=/opt/tinyos-main
> -fnesc-scheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask
> -DPLATFORM_NULL -v -fnesc-target=pc -fnesc-no-debug -gcc=gcc
> -I/opt/tinyos-main/tos/platforms/null -I/opt/tinyos-main/tos/lib/timer
> -I/opt/tinyos-main/tos/lib/serial -I/opt/tinyos-main/tos/interfaces
> -I/opt/tinyos-main/tos/types -I/opt/tinyos-main/tos/system
> nescc: 1.3.4
> NCDIR="/usr/lib/ncc"
> NESCC_ARGS="-fnesc-include=nesc_nx -fnesc-include=tos
> -fnesc-scheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask
> -fnesc-target=pc -fnesc-no-debug"
> NESCC_GCC="gcc"
> gcc -specs=/usr/lib/ncc/tdspecs -I/usr/lib/ncc -D PLATFORM_NULL -v -I
> /opt/tinyos-main/tos/platforms/null -I /opt/tinyos-main/tos/lib/timer -I
> /opt/tinyos-main/tos/lib/serial -I /opt/tinyos-main/tos/interfaces -I
> /opt/tinyos-main/tos/types -I /opt/tinyos-main/tos/system -DNESC=134
> Using built-in specs.
> Reading specs from /usr/lib/ncc/tdspecs
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
> 4.4.3-4ubuntu5.1' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
> --enable-multiarch --enable-linker-build-id --with-system-zlib
> --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
> --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4
> --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin
> --enable-objc-gc --disable-werror --with-arch-32=i486 --with-tune=generic
> --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
> --target=x86_64-linux-gnu
> Thread model: posix
> gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1)
>


On Mon, Jul 16, 2012 at 12:07 PM, Franz Gravenhorst <
[email protected]> wrote:

>  Hi Mike,
>
> thank you.
> Did you get the same warning messages when compiling these apps?
>
> I have tested it with two different shimmer devices, it is the same with
> both.
> And when I use the compiled hex-file which is shipped with the device then
> BoilerPlate is working correctly.
>
> So, I think there is something wrong with my dev environment.
> It would be great, if somebody would have some suggestions?
>
> Thanks,
> Franz
>
>
>
> On 16.07.2012 10:40, mike healy wrote:
>
> Hi Franz,
>
> I've just tested both the Bluetooth test app (in shimmer/swtest/Bluetooth)
> and BoilerPlate when compiled with msp430-gcc version 4.6.3 and nesc
> version 1.3.4 and both work correctly for me. I can connect and stream data
> from both without any problem.
>
> Are you sure the problem isn't with the bluetooth stack on the PC side or
> with the particular shimmer you are using?
>
> Mike
>
>
>
> On Fri, Jul 13, 2012 at 7:22 PM, Franz Gravenhorst <
> [email protected]> wrote:
>
>> Hi,
>>
>> sorry, to bother you again...I have now somehow successfully performed
>> the toolchain upgrade:
>> The Blink app is now working, but somehow none of the bluetooth apps is
>> working any more.
>> I tried both the BoilerPlate and the TestBluetoothApp. Both are compiling
>> without fatal errors (only warnings and notes), but the flashed shimmer is
>> not connectable over bluetooth.
>>
>> So, even the Bluetooth Hello-World app is not running any more.
>> Here is the compiler's output:
>>
>> tiny2@ShimmerLive:~/tinyos-2.x-contrib/shimmer/swtest/Bluetooth$ make
>> shimmer2r install bsl,/dev/ttyUSB0
>> mkdir -p build/shimmer2r
>>     compiling TestBluetoothAppC to a shimmer2r binary
>> 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=\"TestBluetoothAp\"
>> -DIDENT_USERNAME=\"tiny2\" -DIDENT_HOSTNAME=\"ShimmerLive\"
>> -DIDENT_USERHASH=0xe8d0c5b7L -DIDENT_TIMESTAMP=0x50006601L
>> -DIDENT_UIDHASH=0xac67268eL  TestBluetoothAppC.nc -lm
>> TestBluetoothC.nc:73: warning: `activityTimer.startPeriodic' called
>> asynchronously from `Bluetooth.connectionMade'
>> TestBluetoothC.nc:78: warning: `activityTimer.stop' called asynchronously
>> from `Bluetooth.connectionClosed'
>> /opt/msp430-46/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/include/msp430f1611.h:275:
>> warning: non-atomic accesses to shared variable `P1IE':
>> /home/tiny2/tinyos-main/tos/chips/msp430/pins/HplMsp430InterruptP.nc:92:
>> warning:   non-atomic r/w
>> /opt/msp430-46/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/include/msp430f1611.h:271:
>> warning: non-atomic accesses to shared variable `P1IFG':
>> /home/tiny2/tinyos-main/tos/chips/msp430/pins/HplMsp430InterruptP.nc:108:
>> warning:   non-atomic r/w
>> /opt/msp430-46/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/include/msp430f1611.h:286:
>> warning: non-atomic accesses to shared variable `P2IFG':
>> /home/tiny2/tinyos-main/tos/chips/msp430/pins/HplMsp430InterruptP.nc:212:
>> warning:   non-atomic r/w
>> /opt/msp430-46/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/include/msp430f1611.h:290:
>> warning: non-atomic accesses to shared variable `P2IE':
>> /home/tiny2/tinyos-main/tos/chips/msp430/pins/HplMsp430InterruptP.nc:196:
>> warning:   non-atomic r/w
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:74:
>> warning: non-atomic accesses to shared variable `btConnected':
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:308:
>> warning:   non-atomic read
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:318:
>> warning:   non-atomic read
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:547:
>> warning:   non-atomic write
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:74:
>> warning: non-atomic accesses to shared variable `runningMasterCommands':
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:312:
>> warning:   non-atomic write
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:321:
>> warning:   non-atomic write
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:332:
>> warning:   non-atomic write
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:547:
>> warning:   non-atomic write
>> TestBluetoothC.nc: In function ‘TestBluetoothC__sendStuff__runTask’:
>> TestBluetoothC.nc:63:3: warning: pointer targets in passing argument 1 of
>> ‘TestBluetoothC__Bluetooth__write’ differ in signedness [-Wpointer-sign]
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/Bluetooth.nc:51:23:
>> note: expected ‘const uint8_t *’ but argument is of type ‘char *’
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:
>> In function ‘RovingNetworksP__UARTData__rxDone’:
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:598:11:
>> warning: pointer targets in passing argument 3 of ‘msg_cmp_buf’ differ in
>> signedness [-Wpointer-sign]
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/shimmerMessage.h:194:22:
>> note: expected ‘const uint8_t *’ but argument is of type ‘char *’
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:
>> In function ‘RovingNetworksP__writeCommand’:
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:180:3:
>> warning: pointer targets in passing argument 1 of
>> ‘RovingNetworksP__Bluetooth__write’ differ in signedness [-Wpointer-sign]
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:97:16:
>> note: expected ‘const uint8_t *’ but argument is of type ‘char *’
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:
>> In function ‘RovingNetworksP__writeCommandNoRsp’:
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:191:3:
>> warning: pointer targets in passing argument 1 of
>> ‘RovingNetworksP__Bluetooth__write’ differ in signedness [-Wpointer-sign]
>> /home/tiny2/tinyos-main/tos/platforms/shimmer/chips/bluetooth/RovingNetworksP.nc:97:16:
>> note: expected ‘const uint8_t *’ but argument is of type ‘char *’
>>     compiled TestBluetoothAppC to build/shimmer2r/main.exe
>>             7752 bytes in ROM
>>              578 bytes in RAM
>> msp430-objcopy --output-target=ihex build/shimmer2r/main.exe
>> build/shimmer2r/main.ihex
>>     writing TOS image
>> cp build/shimmer2r/main.ihex build/shimmer2r/main.ihex.out
>>     installing shimmer2r binary using bsl
>> tos-bsl --invert-test --invert-reset -c /dev/ttyUSB0 -r -e -I -p
>> build/shimmer2r/main.ihex.out
>> MSP430 Bootstrap Loader Version: 1.39-telos-8
>> Mass Erase...
>> Transmit default password ...
>> Invoking BSL...
>> Transmit default password ...
>> Current bootstrap loader version: 1.61 (Device ID: f16c)
>> Program ...
>> 8066 bytes programmed.
>> Reset device ...
>> rm -f build/shimmer2r/main.exe.out build/shimmer2r/main.ihex.out
>> tiny2@ShimmerLive:~/tinyos-2.x-contrib/shimmer/swtest/Bluetooth$
>>
>>
>> Any ideas how to fix this?
>> Would be great!
>>
>> Thanks,
>> Franz
>> _______________________________________________
>> Shimmer-users mailing list
>> [email protected]
>> https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users
>>
>
>
>
>
_______________________________________________
Shimmer-users mailing list
[email protected]
https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users

Reply via email to