dubnet

Members
  • Content count

    536
  • Joined

  • Last visited

  • Days Won

    23

dubnet last won the day on July 31

dubnet had the most liked content!

About dubnet

  • Rank
    Level 3

Profile Information

  • Gender
    Not Telling
  • Location
    USA

Recent Profile Visitors

993 profile views
  1. No problem. Happy to hear you got it resolved.
  2. I think I might see what the problem is. Energia places the some things in the User folder which you have apparently named "Mike KM6KWG" which has a space in it. If you have another user account without spaces that you can use, or create a new user account without spaces, and then install while logged into that user name. You may also want to make that user account an administrator account to eliminate that variable. You can revert it to a standard user account if you want when you have a successful install.
  3. First of all, welcome to the forum. It appears that a space in your file path may be causing the issue. Best to avoid spaces, special characters and long path names with Energia. I typically put Energia in the root of C: and use a short path structure ( e.g. c:\energia ).
  4. If I am not mistaken, the F149 doesn't support Spy-Bi-Wire using RST and TST. It only supports full JTAG which uses TDI, TDO, TCK, TMS, etc. TI's MSP-FET430UIF should support full JTAG ( http://www.ti.com/tool/msp-fet430uif ).
  5. You may want to take a look at page 29 and 30 of the 2553 datasheet which characterizes the DCO. The DCO is not particularly accurate and my guess is that you will need the crystal to get the accuracy you are looking for as well as better consistency from device to device. EDIT: forgot the link to the datasheet http://www.ti.com/lit/ds/symlink/msp430g2553.pdf
  6. My understanding is that Energia will consume more resources than an equivalent program written in C using, for example, CCS. Since Energia abstracts away some of the hardware details in favor of simpler programming, that abstraction consumes extra flash and ram. Trying V12 of Energia as Rei Vilo suggested or moving to CCS would perhaps get the numbers down to what you are expecting/require for your application.
  7. Welcome to the forum!
  8. Welcome to the forum!
  9. By the way, if you are using the XMS version of the MSP432 then you are should have the black board. I believe that the sensitivity issue has been addressed in the final board release (red board). I know that TI has been pretty strongly recommending moving to the red board since the black board used the pre-production XMS silicon.
  10. Your circuit diagram didn't post. Given your symptoms the diagram will be very helpful in trying to understand the problem.
  11. If you read through some of the posts on E2E there may be a solution in terms of replacing the damaged part, but that may not be worth the cost or trouble. The other solution is to replace the board.
  12. This is a known issue typically due to static/handling damage. Please see the E2E site for more info: http://e2e.ti.com/search?q=msp432 gets hot
  13. The multi-tasking examples are for the MCUs that have the resources (processing power, memory, etc) to handle the TI-RTOS overhead. The value line series (like the 2553 you are using) are not capable of running the real time operating system. The MSP432 is a good example of a MCU that can run the multi-tasking environment.
  14. I have at times used the calculator that comes with windows to do quick hex -> binary as well as binary -> hex. From the view menu of the calculator, choose "Programmer". Once you have moved past the blinking LED and dive further into the wonderful world of microcontrollers, you will appreciate having a logic analyzer with 8-16 channels. They are worth their weight in gold when troubleshooting communication problems.
  15. First off, welcome to the forum. A couple of ideas come to mind. The first is that you might want to consider controlling the power to the SD card with a free I/O line and a transistor, only powering it up when you need to write to it. The other idea is to store multiple samples in an array (which should survive going into low power mode and back) and write them to the SD card every hour or more. How many samples to store between writes to the SD card would depend on your confidence that you wouldn't lose power or have a reset condition before having a chance to move them to the card.