Jump to content


  • Content Count

  • Joined

  • Last visited

About TheTaillessWonder

  • Rank
    Noob Class
  1. Thanks for all the information -- it is really helpful. Just one final thing to close this out: We built our own BoosterPack board which contains several I2C sensors, and according to the BoosterPack pinout standard http://www.ti.com/ww/en/launchpad/byob.html, the I2C bus should be connected to pins 9 and 10. So we connected our I2C bus to these pins, according to the spec. Now we are trying to test the BoosterPack, only to find out that we cannot use it with the MSP430 F5529 using Energia because the F5529 Wire library defaults to the wrong I2C bus (at least according to the BoosterPack s
  2. So close, yet so far away! When I type Wire.setModule(1) into the IDE, the "setModule" part turns orange, like it is a known function. Yet when I try to build, I get an error saying "class TwoWire has no member named 'setModule'. Sure enough, the include path is hardware\msp430\cores\msp430, and when I examine Wire.h at that location, I can verify that the class TwoWire does not implement setModule. Yet I see that setModule is implemented for some other platforms, like the Stellaris. Any ideas? Is this is mistake or oversight, or is there some reason that the MSP430 does not implement setM
  3. Hi, I have an MSP430 F5529 LaunchPad, R1.6. I am trying to use the Wire library to access I2C BoosterPacks. The problem is that the Wire library is accessing the I2C0 interface on pins 14 and 15, while the BoosterPack is connected to I2C1, on pins 9 and 10. How do I select which I2C interface the Wire library uses? I tried using Wire0 and Wire1, but these result in a compiler error -- Wire is the only object defined. Aren't pins 9 and 10 preferred for the I2C interface according to the suggested pinout? If so, then shouldn't the Wire library default to using this interface?
  • Create New...