Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by rockets4kids

  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. 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.

  3. 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.

  4. Personally, I would ask the following questions:


    1.  Is there a fully open source, cross-platform toolchain available?


    2.  Does the part have community support and acceptance?


    3.  Is the part well stocked by distributers?


    4.  Does the manufacturer have a history of long-term product support?

  5. 8051 (and derivatives) will not die as long as a) there are applications for it 2) it is cheap iii) there are legacy applications where there is no reason to replace it/recode -..) manufacturers keep upgrading the peripherals to meet new needs


    I'm not sure it has to do with any of that.  You don't see the 8051 as a stand-alone part any more, you see it embedded into other chips.  In that realm, the 8051 has become the de-facto architecture and it will likely stay that way for some time to come.  I do suspect that at some point that ARM will supplant the 8051, and the only real question is when that will happen.

  6. It seems these parts have been in the pipeline for quite some time now:


    $ whois msp432.com


       Domain Name: MSP432.COM
       Registrar: GKG.NET, INC.
       Sponsoring Registrar IANA ID: 93
       Whois Server: whois.gkg.net
       Referral URL: http://www.gkg.net
       Name Server: NS.TI.COM
       Name Server: NS2.TI.COM
       Name Server: NS3.TI.COM
       Name Server: NS4.TI.COM
       Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
       Updated Date: 04-dec-2013
       Creation Date: 13-jan-2011                          <<<<<<<<---------------------------------------------
       Expiration Date: 13-jan-2019
  • Create New...