dubnet

Members
  • Content count

    536
  • Joined

  • Last visited

  • Days Won

    23

Everything posted by dubnet

  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.
  16. First of all, welcome to the forum. Sounds like it could be thermal shutdown. Are your LEDs current limited? Does the 23017 chip run hot before the LEDs turn off? Does the total load (all four LEDs) exceed the package dissipation specification?
  17. How is the stream of data not suitable? With regard to your question on software serial you may want to search the forum using software serial as the search term. I did so and it produced 123 results. You should be able to confirm an answer on the availability of software serial on any MSP430 devices other than the 430G series that don't have hardware serial capability on the chip.
  18. I used P4_4 and P4_5 for the PC serial console and P3_3 and P3_4 for my RF link. You could remove the jumpers on 4_4 and 4_5 and use them for another hardware device. However, I believe that you will lose the debugging/programming functionality. Shouldn't be an issue once you have programmed the MCU, repurposed the port and have put it in your project. http://energia.nu/wordpress/wp-content/uploads/2014/01/MSP430F5529.jpeg
  19. Assuming by your mention of arduino that you are using Energia. The '5529 supports two hardware serial ports under Energia. IIRC, software serial is not supported in Energia on the '5529 but only on some of the lower end MSP430G devices. In the past I have successfully used the two serial ports (Serial and Serial1) on the '5529, one for the console and the other for a RF link module with a serial interface.
  20. Welcome to the forum!
  21. Energia has had some sensitivity to not only unusual characters that might be in the path but also very long paths. What has worked in the past to is to move the Energia folder to the root of your drive (or one or two folders away from the root) and to use text based folder names, avoiding special characters.
  22. Welcome to the forum!
  23. It sounds like the RAID you are describing is RAID 0 which is non redundant striping, used to increase performance but has no redundancy/failure tolerance. Although single disk backups have simplicity, the risk you run is that drive can fail anytime (usually when you need it most ). It happened once when I was doing a customer workstation upgrade from XP to Win7. Copied the customer's data to a USB hard drive, did the OS install and then during the restore the disk started to fail. After much sweat and coaxing was able to get the restore finished but it was yet another reminder of the frailty of hard drives. RAID 1, 5 or 6 or even some of the RAID xx variants are, however, excellent backup platforms. For customer near line server backups we used 8, 12 and 16 drive SAS and high speed iSCSI based disk arrays, typically configured as RAID 6 with a hot spare. This allowed up to three drive failures before the array became critical (after the 4th drive failure your data is history). While this might sound like overkill in terms of redundancy, it addressed the problem of drives sourced from the same batch that tended to fail at the same time, or a drive failing during rebuild (happens with a weak drive due to the stress of the rebuild process). This gave us a little headroom to get drives replaced and put the array back to optimum status. With regard to controller failure, although I can't say that it never happens, in 20+ years I've had no controller failures but more drive failures (including enterprise drives) than I could even count.
  24. ...and a third monitor (or laptop/PC) for the logic analyzer watching the comms. I can truly relate as I had two laptops and a PC in play debugging comms not too long ago. It is somewhat interesting that we need a handful of computers to play with very inexpensive MCUs.
  25. @NurseBob For your video work where is the bottleneck? If it's the drive subsystem then perhaps an upgrade to SSD would be helpful. Perhaps not for the whole 21TB but maybe as scratch drives for the rendering process. Prices keep dropping and are now at the point, in my opinion at least, where the price difference between spinning drives and SSD is pretty easily justified by the performance gains. I have them in my laptops and main desktop and love the performance boost. In the past I have recommended adding memory, to a point (and you are north of the point with 24GB), as a way to inexpensively increase performance. Now, its a toss up between memory and SSD and I am leaning more toward the SSD and not solely due to lower prices. Reason is that even with less than optimal memory, the swap to virtual memory on the SSD is so much faster it mitigates the need for more system memory.