Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by RobLewis

  1. Has anyone worked with TI's CC2540 RF Dongle? I'm trying to use their Bluetooth LE packet sniffer program but it appears to have problems with Windows 10. The quick-start says that when you connect the dongle to the PC's USB port, the "Windows New Hardware Wizard" will appear. But it doesn't. And the sniffer software doesn't see the dongle. No doubt a driver problem but I don't know how to fix it.
  2. Very cool, thanks @@chicken! Do you have any idea whether this may restore the routine's ability to work at a 16MHz clock rate in the F5529? (I found that in later versions of Energia even the patched code would only work at 25 MHz).
  3. Everything I know about this issue is contained in my previous posts, particularly those from last May 3. I don't know whether @@chicken might have any additional insights, or whether Energia has been patched to fix the apparent timing problem.
  4. Reflecting on this a bit more, I wonder if one of the later Energia updates somehow broke the I2C driver when the F5529 (and possibly other boards) is run at 16 MHz. And of course that 8-bit patch needs to be mainlined, eh?
  5. Success, sort of: By going back to the old BMP085 breakout board AND using the patch for the 8-bit read AND changing the F5529 board clock setting from 16 MHz to 25 MHz, I'm now getting apparently good data from the part: Setup has initialized Serial Setup has initialized Wire Attempting to read BMP085 CHIP ID with patched m_read8... AC1=7509 AC2=-1137 AC3=-14499 AC4=34075 AC5=24637 AC6=26359 B1=5498 B2=60 MB=-32768 MC=-11075 MD=2432 Setup has initialized Serial, Wire, and Psensor Reading temperature.. UT=33838 Reading pressure.. UP=42343 Calculating temperature in 0.1 Celcius.. X1=
  6. It worked great for over a year with the BMP085 breakout board, and I haven't changed the hardware configuration except to try it with the new BMP180 breakout board (which lacks the EOC signal), because I thought the BMP085 had failed. Tomorrow I'll go back to the BMP085 and see what's reported by the driver in debug mode. (The humidity sensor which is connected to the same LaunchPad continues to work fine.)
  7. Tried changing this line: #define BMP085_CHIP_ID 85 to 180, and there was no change. Went back to 85, and commented out the return you suggested; still no joy. Here's what it's outputting now (note I still have your suggested patch in that discards the second byte for a 1-byte read): Setup has initialized Serial Setup has initialized Wire Attempting to read BMP085 CHIP ID with patched m_read8... BMP085 device not found AC1=8151 AC2=0 AC3=0 AC4=0 AC5=0 AC6=0 B1=0 B2=0 MB=0 MC=0 MD=0 Setup has initialized Serial, Wire, and Psensor Reading temperature.. UT=0 Reading pressure.. UP=0 C
  8. Well, something different anyway. Now when I power cycle the board, the serial monitor shows this (which includes a few diagnostic print statements I added, and has the debug-enabled version of the driver): Setup has initialized Serial Setup has initialized Wire Attempting to read BMP085 CHIP ID with patched m_read8... BMP085 device not found Setup has initialized Serial, Wire, and Psensor Reading temperature.. UT=0 Reading pressure.. UP=0 Calculating temperature in 0.1 Celcius.. X1=0 X2=-1 B5=-1 T=0 Calculating pressure in Pascal.. B6=-4001 X1=0 X2=0 X3=0 B3=0 X1=0 X2=0 X3=0 B4=0 B7=0 p
  9. Darn, that sounded like the answer, but sadly I don't see any change. It still hangs trying to read the CHIP ID.
  10. Still no luck getting my F5529 to read the BMP180. With or without DEBUG_BMP085 enabled, the program hangs in the begin() method. I added a print statement to the driver just before it tries to read the BMP085 CHIP ID. I see this printout but that's the last output I get, so apparently it is hanging trying to read the ID. I don't get the "BMP085 device not found" message. I wonder if there could be some problem in the Wire module. This is in Energia 15. Frustrating that this all worked fine for a long time.
  11. I replaced the BMP085 sensor with a new BMP180, which is claimed to be 100% compatible, though it seems to lack the EOC output that signals the end of a conversion. Adjusted the code to use wait loops instead of the EOC signal, but the new sensor seems to be doing exactly what the old one did. In the serial monitor, what I'm seeing is the value "2" being sent as the pressure reading. And I don't seem to be getting any temperature reading at all. The separate humidity sensor attached to the same MSP430F5529 continues to work fine. This smells to me like some kind of serial I/O bit timin
  12. I confess I'm not deep into the issues involved in this, but is there a prospect of eventually being able to use both I2C interfaces at the same time? And just to confirm, if I don't call setModule then I'll get the "legacy" pin assignments of P3.0 and P3.1?
  13. The setModule issue may be a red herring. I re-flashed the old LaunchPad code that was working fine, and am still getting the error, so the current suspect is a failed BMP085 sensor. (The other attached sensor, a DHT22 humidity sensor, continues to work fine.) Anybody experienced reliability issues with this part? Mine has been mounted indoors out of the weather the whole time, and a failure after less than 2 years is hopefully a fluke. It appears Bosch has updated the sensor to a new (and improved?) part, the BMP180, which according to AdaFruit is pin- and software-compatible. So I gu
  14. Thanks for the tip, but the newer library isn't working any better than the older one. It might help if I could find some documentation anywhere of the Wire.setmodule() method (especially as regards the MSP430F5529), but I can't.
  15. OK, I'm getting confuseder and confuseder. I had the BMP085 working with an older Windows version of Energia and your library. I've updated to Energia 15 for Ubuntu and presumably have the latest version of BMP085_t.h (dated April 2013). Now my program (on the MSP430F5529) apparently no longer sees the sensor! IIRC I had to patch the earlier library to work with the F5529, but that shouldn't be necessary with this later one, right? I'm using the same "legacy" pin connections as before: SDA to P3.0 and SCL to P3.1. I did notice this in your comments at the top of your driver: MSP4
  16. I want to update the code for my MSP430F5529 but want an easy way to re-flash the old code if I mess something up. Does Energia (or some other utility) provide a way to download and save the ROM contents, and restore them from an image file?
  17. I think I'm looking at the latest version, and line 82 of the .cpp file says: #if defined(__MSP430G2452__) || defined(__MSP430G2553__) || defined(__MSP430G2231__) // LaunchPad specific Can I just add the MSP430F5529 to this list?
  18. Waiting breathlessly for your report :-) I'd like to read a few sensors, not just a single one.
  19. Got it to work (somehow). Updated UniFlash to the new version, still no luck. Went to the Windows XP Device Manager, and saw an entry for COM7 under serial ports (listing an FTDI driver). Fired up UniFlash and entered 7 as the port (why does it initialize to port 30?). Everything worked fine and I was able to install the CC3200 Service Pack. I'll swear I had earlier tried every port number from 1 to 20 with no luck, but perhaps the new UniFlash made the difference.
  20. Been running Java 8 under Yosemite for a while now and would like to be able to use Energia with it.
  21. Energia's installation instructions for Mac specify a USB FTDI driver that apparently hasn't been updated since OS 10.7. Has anyone verified that it works on Mavericks and/or Yosemite? I believe that Yosemite in particular now requires "kext signing" of drivers, which has apparently caused a lot of problems for third-party software.
  22. This "patch" you mention is an archive containing two different .exe files. Looking up the Microsoft KB articles it seems that KB918365 is the relevant patch. But when I try to apply it, it says that my Win XP version is newer than the patch, so there is no need to apply it. I just installed Code Composer Studio, and it can't connect to the board, either.
  23. A bit of additional info: I put UniFlash into debug mode and here's the sequence of log messages when I try to do something simple like read the version number from the LaunchPad: Begin GetVersion operation Executing operation: Connect waiting and clearing UART Rx buffer setting break signal --- please restart the device --- (I hit the Reset button) wait for ack UART timeout --- COM Port timeout on ACK read ---reading ACK signal failed--- disconnecting from device . . . --- Connection failed trying to reconnect... (1 attempt) waiting and clearing UART Rx buffer And so
  24. Just got my CC3200 LaunchPad and am trying to install the Service Pack ( as described here: http://energia.nu/cc3200guide/#upgrade Apparently I can connect to the board (from UniFlash on Windows XP) on COM3, but the Service Pack installation gets to "Executing operation: Connect", then "setting break signal", and
  25. Yes, I saw that page and read it carefully. Have I missed the part where it says what to do after downloading the software? Where to put it? How to launch it? Do I have to change permissions? etc.? I'm a spoiled Mac user accustomed to things that just work. But I really would like to get this going on my Ubuntu box.
  • Create New...