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

Reply via email to