Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


rockets4kids last won the day on May 30 2015

rockets4kids had the most liked content!

About rockets4kids

  • Rank
    Level 3

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I you want someone to build a project for you, then you should start by stating that clearly in the title. However, I highly doubt that unless you have a fair bit of money to offer you are not likely to find anyone interested. If you want to start learning on your own, I suggest you start by learning how to blink an LED.
  2. Are you looking to learn how to build this yourself, or are you looking for someone to build it for you?
  3. All of the G2 parts with a UART have a bootloader in ROM. http://www.ti.com/lit/ug/slau319j/slau319j.pdf
  4. I believe mspgcc supports the interrupt format used by msp430-gcc, so that shouldn't be a problem. Historically mspgcc used only the gcc-style interrupt declaration format and only added the IAR/CL430 format late in its development run. It is because msp430-gcc tries to say closer to pure gcc that it only supports the gcc format.
  5. Amateur high altitude balloon projects have actually become quite casual in the past year or two.
  6. I have seen plenty of people using Arduinos and Raspberry Pis as flight computers for these applications, so clearly power consumption isn't *that* great of a concern. ;-) I agree that an MSP430 part would likely have lower power consumption than a Hercules part, but I would be willing to bet that a Hercules part -- when used/coded properly -- would consume *considerably* less power than what most people are actually using. I mention this application because I have seen a fair number of discussions on flight computer failures. Now personally, I suspect the primary cause to be related to vibration on spring-loaded connectors. I've seen some pretty janky wiring jobs. But cosmic radiation levels are much greater at high altitudes so this is a real possibility. (BTW, janky *is* a real word now. http://time.com/3724601/oxford-dictionary-janky-egot-ridesharing/) I am aware that FRAM has some level of immunity to the effects of cosmic rays, but as I understand it the SRAM and the core logic could certainly be effected. As such, the effects of a cosmic-ray induced bit flip could easily go unnoticed causing a series of cascading failures before the watchdog is triggered. But then you still are left with all the mess between the cosmic ray event and the watchdog trigger. (There is also no guarantee that a failure will result in triggering of the watchdog.) As best as I can tell, the lock-step operation of the Hercules parts would provide much quicker notification of an event, and thus much quicker restart with less chance of data loss or corruption. This is certainly no substitute for a fully rad-hard system, but it seems as if it gets you a long way in that direction for a fraction of the price. In any case, it seems as if this could be a prime hobbyist application for the part. I am *very* curious to know if anyone who knows more about the architecture of the Hercules can actually provide some more detail here.
  7. Perhaps a better way to discuss this would be, "For what hobbyist applications would the Hercules part be well suited?" The first thing that comes to my mind would be high-altitude balloon projects or cubesats that would be subject to cosmic rays. Does anyone know if the Hercules architecture will really provide a benefit here?
  8. Before migrating to TIs gcc compiler you will really want to investigate its actual condition and level of support. For instance, can you even find any proper documentation on the new compiler? The older toolchain, though obsolete, is more reliable and much better suited for most projects.
  9. The simple solution is to always place the constant on the left hand side. This will always force an error if you use = instead of ==
  10. Have you gotten "hello world" to compile under the new toolchain? If not, that is where you want to start. Most of your size issues are likely coming from newlib, not the compiler directly. That said, I still have reservations about the new compiler so unless you need support for large memory or C++11 I suggest you stick with 4.6.3.
  11. What core is the current msp432 part using?
  12. My understanding is that most of the issues were fixed in the LM4 parts, and most if not all of the LM4 parts still exist and were simply renamed as TM4.
  13. Just stumbled across this and though some people might be interested: http://rohitg.in/2015/05/17/FM430/ These FM receiver modules go for about $1 on eBay.
  14. The word from someone inside of TI is that the name was changed from Stellaris to Tiva because Asians had too much trouble pronouncing "Stellaris." I still don't know is this is serious or a joke.
  15. Correction: Your idea is worthless until you patent it. Then you can let someone else do the work and profit anyway.
  • Create New...