folks,
i'm buried right now, but can someone please file a bug report with the
googlecode tinyos repository?
http://code.google.com/p/tinyos-main/issues/list
-steve
On 08/31/2011 03:43 AM, mike healy wrote:
Hi Nick,
I have confirmed that this is a problem (i.e. I'm seeing the same
behaviour when I update tos-bsl).
It looks like an update to tos-bsl.in <http://tos-bsl.in> in the
tinyos-main tree on the 14th of August (2011) is causing your problem
(http://code.google.com/p/tinyos-main/source/browse/trunk/tools/platforms/msp430/pybsl/tos-bsl.in).
I'll look into what exactly is causing the problem later today or
tomorrow, but in the interim it is very easy for you to revert to the
old (working) version.
tos-bsl is a python script, so to revert back to the old you you just
need to replace the tos-bsl file.
To locate this (on a linux system) just type:
which
On Tue, Aug 30, 2011 at 9:10 PM, Nicholas Hosein <[email protected]
<mailto:[email protected]>> wrote:
So up until recently i have been able to install code to the shimmer
fine using the manual instructions. As of a week or two ago though
that same procedure isnt working. Just typing make shimmer2r works.
I also checked the base and shimmer module on an older setup that is
working and the application loads fine. This is the error:
nova@trinidad:~/Code/tinyos-main/apps/Blink$ make shimmer2r install
bsl,/dev/ttyUSB0
mkdir -p build/shimmer2r
compiling BlinkAppC to a shimmer2r binary
ncc -o build/shimmer2r/main.exe -Os -O -mdisable-hwmul
-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=\"nova\" -DIDENT_HOSTNAME=\"trinidad\"
-DIDENT_USERHASH=0x3edaca8bL -DIDENT_TIMESTAMP=0x4e5d423fL
-DIDENT_UIDHASH=0xfdb26278L BlinkAppC.nc -lm
compiled BlinkAppC to build/shimmer2r/main.exe
3020 bytes in ROM
54 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-goodfet-8
Mass Erase...
MSP430 Bootstrap Loader Version: 1.39-goodfet-8
Mass Erase...
Traceback (most recent call last):
File "/usr/local/bin/tos-bsl", line 1918, in <module>
main(0);
File "/usr/local/bin/tos-bsl", line 1833, in main
for f in toinit: f()
File "/usr/local/bin/tos-bsl", line 1098, in actionMassErase
0xa506) #Required setting for mass erase!
File "/usr/local/bin/tos-bsl", line 758, in bslTxRx
rxFrame = self.comTxRx(cmd, dataOut, len(dataOut)) #Send frame
File "/usr/local/bin/tos-bsl", line 440, in comTxRx
rxHeader, rxNum = self.comRxHeader() #receive header
File "/usr/local/bin/tos-bsl", line 346, in comRxHeader
if not hdr: raise BSLException("Timeout")
__main__.BSLException: Timeout
make: *** [program] Error 1
The only change i can see from the old setups i have and the 3 new
ones where i get the above error is the new systems use
the 1.39-goodfet-8 bootstrap loader where as the older setups use
the telos. I cant seem to figure out how to switch back to telos as
im not sure what caused it to use the goodfet bootloader.
Much thanks,
Nick
_______________________________________________
Shimmer-users mailing list
[email protected] <mailto:[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
_______________________________________________
Shimmer-users mailing list
[email protected]
https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users
