Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Thanks Hogemark! I've just hit this same problem with my project and after replacing the standard libraries with your code my I2C ports are working correctly :-)
  2. Hi D, Welcome to the party! I've been trying to get I2C to work on the MSP430 devices for some time now with very limited success. The best I've come to getting I2C to actually work in a real device situation in the Examples/TMP006 project in Energia. This connects a Texas Instr. temperature measurement IC to the MSP and allows two way communications. The examples from TI are pretty much worthless for me since they assume 1. That your MSP will only transmit or receive, but never do both in the same program, and 2. That I2C communications is all that your MCU will ever be doing since their examples force your MCU to go into a brain dead low power mode and only wake up when an I2C operation happens. The Energia examples are way better than anything TI offers. Now if Energia would only offer a USB library so I could use the MSP430F5529 to transmit data. Will
  3. I've ported the USB_API library from the Code Compiler studio into the Energia libraries, and created a wrapper based on the Energia Serial example code. The USB port shows up in the Windows device manager it is in the HID section where it should be, but it doesn't have a serial number or a serial string. The VID is the TI one along with a PID of 0x301 which should be OK. Everything compiles without errors but something isn't getting baked in the mix. Energia uses GCC, I think. Well at least I had to add #ifdefs to several of the modules to pull in GCC type definitions. I used the USB descripter program to create the descriptor files, and they look identical to the one in the TI CCStudio example directory. The TI example works and the USB shows up correctly in the windows device manger. Can anyone point me at an answer, or at least a few clues?
  4. OK, Responding to my own question :-) The MSP430-USB com port does eventually start working, it takes about 40 seconds to start. Why this is so is still a mystery. This is pretty unacceptable behavior for a system to have. Anyone have any ideas? Will
  5. I'm in the middle of a project using the f5529 launchpad and Energia. I'm trying to use both the USB and the I2C port at the same time. I can initialize the USB and see it enumerate in the windows device manager and I can read/write to it and it works properly. But as soon as I try to enable the I2C port using the USCI_B1 the USB dies and can no longer be read or written to. The example codes in Energia work for both the USB examples and for the TMP006 example, so the harware is OK. But trying to get them both to play at the same time is a nogo. What am I missing? #include <USBSerial.h> #include "tmp006.h" #define USE_USCI_B1 USBSerial mySerial(1); // USB tmp006 tmp006; void setup() { // open the USBSerial port mySerial.begin(); mySerial.println("setup!"); // Setup the temperature sensors //The following line is killing the USB port tmp006.begin(FOUR_SAMPLES); // Takes 4 averaged samples for measurement } void loop() { mySerial.println("loop!"); }
  6. Just wanted to say Hi. Great little micro, and great projects!
  • Create New...