Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


NurseBob last won the day on January 6

NurseBob had the most liked content!


About NurseBob

  • Rank
    Level 2
  • Birthday 09/09/1950

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    St. Helena, CA

Recent Profile Visitors

3,198 profile views
  1. Google is your friend... I did this lookup (msp430f5529 "write to flash" memory energia)and in under 5 minutes found this reference, which might serve as a starting point for you... FWIW, TI's example code for CCS/IAR can also serve as an educational reference. HTH
  2. > This is why I said it is odd, but I have never tried it myself with devices that are so closely related. I don't know if it actually was programmed with the wrong device specified, but I can see no reason there would be damage IF it was programmed this way < Agreed. Like you, I've never tried with such closely related devices.
  3. This is "expected behavior." When the watchdog is enabled, it needs to be serviced regularly on a schedule that's far shorter than serial communication. The intent of the watchdog is to restart the device in the event of an unexpected endless loop, or other conditions that result in the mcu hanging. This reference on Wikipedia will explain it better. FWIW - it is not at all unusual for makers (or others) to disable the watchdo. Bob
  4. Interesting. My experience with both IAR and CCS is that they refuse to load images to a device when it's different than what the project specifies and they both clearly report it as an error.
  5. " Multiple libraries were found for..." You've got a configuration error message. Time to read the docs on porting from other libraries. How-To: Porting Libraries Posting a Library for Energia Some Misconceptions about Libraries The above may provide guidance. I am not able to help much beyond this suggestion as I'm deeply involved in other non-coding projects at this time.
  6. Have you attempted #1 ? If so, what error messages, if any. If you've not even tried, time to edit code and see what happens. Re: #2 - time to read the docs... The calls to SoftwareSerial are well documented. As to the speed limit, yes. Google is your friend regarding both questions; there are dozens, if not hundreds of answered questions and coding examples on the topics of porting and serial communications.
  7. With C/C++ compilers you want to address/fix errors in the order they are presented - that is, read and understand that first error. Generally, compilers will cascade a long series of errors that all are triggered by that first error. FWIW, a missing semi-colon can trigger a similar long list of errors. So, looking at your first error message: " C:\Users\Harizazmi\Desktop\energia-1.8.7E21\hardware\energia\msp430\libraries\SoftwareSerial\SoftwareSerial.cpp:81:2: error: #error This version of SoftwareSerial supports only 16MHz processors" It's telling you that you have not selected the 16MHz version of the launchpad. If I remember correctly the F5529 board has two entries, one for 16MHz and the second for 24MHz. The SoftwareSerial library is not compatible with the 24MHz version. Further, hardware serial is the preferred library with the F5529. So, changing the board in Energia and calling the other library in your code should be your first steps.
  8. There's far too little information in your question to be able to answer. A screenshot or text file of the Actual errors will help point to the first problem. Debugging compile and link errors requires a structured approach, usually starting with a google search of the reported error statement. 1) Have you updated (ported) the Gamebuino-Meta.h for Energia compatibility? 2) Have you converted the bitmaps to a "C" representation - TI offers both sample code (CCS) and tools for that display with a '5529. Take a look at the MSPWare library for CCS sample code and comments, which may help.
  9. I can't specifically answer for Entergia, but from what I can see, it looks like you'll need to use CCS and perhaps the driver library.
  10. You've described the problem, but supplied no information to allow remote diagnosis. Without a schematic and related code, there's really no way to help, aside from the most general suggestions regarding jumpers, pins and I2C pullup resistors, all of which you've likely read (and hopefully applied). Finally, you mention migrating an existing project; did you have that working, and if so, under what version of Energia? Re: UART - there may be no hardware UART on your chip. "If your Launchpad is version 1.4 or earlier, the chips that it shipped with have no hardware UART and thus, no hardware configuration is necessary, but you must use the SoftwareSerial library included in Energia to communicate over the serial port." You indicate you have an MSP430G2452, according to SLAU318G, there is only USI availble on that chip, the UART is on the G2553's USCI impementation.
  11. @Anshikajain Sorry, I've been offline for a couple of days. Not really sure what your question was, but FWIW, I rarely use Energia. That said, when I2C fails in Energia, it's almost always a configuration problem. My suggestion with the video was focused on how they configured the '430 jumpers. The G25 devices were significantly different from the later versions, and many have tripped over jumpers incorrectly configured. In your photo it appears you have the jumper P1.6 placed for the LED, and that was the very first comment in the video - the device will not work in I2C mode if that jumper is placed (at least on the older boards). Looking at the docs, pins P2.1 and P2.2 are designated as SCL and SDA (sw), which I presume means software, not hardware I2C? It's difficult to see in your photo, but it looks like you're using P1.6 and P1.7. So, the video's comments, and this from Energia docs: " When using I2C When using the Hardware I2C (Wire library) with SCL on P1.6 and SDA on P1.7 on the MSP-EXP430G2 you should remove the P1.6 jumper (GREEN LED) so that the LED doesn’t interfere with the I2C SCL signal... " Energia reference I don't know if I'm able to help much further. Please check your jumpers!
  12. Take a look at this youtube, it may help...
  13. > I am currently studying for a computer engineering degree Cool > My first project (besides a blinking led) is to play a classical piece on an electric buzzer! A couple of thoughts: 1) Buzzers are not speakers; typically they have a very limited repertoire, like a single frequency... 2) Depending on the device you are using, you may find significant memory limitations. So, as always, RTFM the specs before you buy... Have fun
  14. Glad to be of assistance! :)
  15. To enable a hardware reset of the device. If the RST/NMI pin is low, the device is held in a perpetual reset. It needs to be high for the chip to run. Having made a similar omission years back I found out the need. Take a look at any of the LP schematics, or better yet, the specs. In SLAS590M.pdf (for a msp430F5529) you'll find a description on pg. 18. RST/NMI/SBWTDIO - Nonmaskable interrupt input, Spy-Bi-Wire data input/output when Spy-Bi-Wire operation activated
  • Create New...