It definitely sounds like your development environment is the problem so. I don't know why you would have a problem building for shimmer2r if shimmer2 works. You just need to make sure that you are working off a relatively recent copy of the tinyos-main tree from googlecode svn ( http://code.google.com/p/tinyos-main/). Although any copy from the last two years should allow this app to work. The relevant environment variables shouldn't need to be changed.
You might also need to upgrade the version of msp430-gcc that you are using. Version 4.6.3 is recommended. Currently I'm using the tinyprod repository to manage my msp430-gcc install, but there are other ways of doing so depending on your preferences (http://tinyprod.net/repos/debian/) Mike On Wed, Nov 28, 2012 at 10:47 AM, Dang Thi Hai Ha <[email protected]>wrote: > Hi, > > On Wed, Nov 28, 2012 at 11:36 AM, mike healy <[email protected]> wrote: > >> Hi, >> >> From your last mail I get the impression that you used the "Shimmer >> Windows Bootstrap Loader" Windows based application to load the BoilerPlate >> image on your shimmer. Have you tried building and installing BoilerPlate >> from source to see if that works (to test your build environment). >> > > Exactly, I used that famous "Shimmer Windows Bootstrap Loader" to load the > BoillerPlate image. > > >> >> From the rest of your explanation the shimmer does seem to be bound to >> /dev/rfcomm0 correctly, and you are using minicom correctly. If you want >> you can try to connect to the shimmer running BoilerPlate with minicom. >> Once connected, from the minicom window type <Ctrl+f> (i.e. hold down the >> Ctrl key while pressing f). Each time this command is sent the red LED on >> the shimmer should toggle. Similarly <Ctrl+g> will start data streaming >> (this will be unintelligible as the data is binary, not ascii, but it will >> confirm operation). Pressing the spacebar will stop streaming. >> > > Okay, I'll try that now. > > >> When building the Bluetooth application are you typing: >> >>> make shimmer >> >> or >> >>> make shimmer2r >> >> > I did none of those. Mine is: > > make shimmer2 > > That is because I did not successfully install tinyos for shimmer2r, and > it happened that I still can program shimmer motes to do almost everything > using the usb connection. It's only this time when I try with Bluetooth > that it blocks me. > > >> It should be the latter, assuming you are using shimmer2r devices (or >> "make shimmer2" if using shimmer2 devices). If necessary I can send you a >> compiled image, once you confirm which shimmer version you are using, to >> test. >> > > As I said, I have a shimmer2r device, but use a shimmer2 compilation (?!) > > Ha. > > >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
