Jump to content


  • Content Count

  • Joined

  • Last visited

  1. update: I (finally) found rtc_[ab].h and noticed that the RTC provides a 32 bit counter mode. My favorite solution would be to run the RTC continually in 32 bit mode and use a compare function to wake it from LPM3.5. I see that a calendar match will wake the processor, but is there a way to: run the RTC at 32678 Hz rather than at 1 Hz? (I think yes) set the comparison register directly as a 32 bit value rather than as year/month/day/hour/minute/second?
  2. (Context: I'm an experienced embedded systems engineer, just dipping my toe into MSP430-land. My target system is an MSP-EXP430FR5994 LaunchPad dev board.) General goal: How do I wake the processor N ticks in the future, where one tick is 1/32768 second and N can be as large as 2^15? My first thought was to use the RTC, but that appears to have a resolution of 1 second. My second thought was to use a timer module (e.g. TA1) and use its compare interrupt to wake the processor from LPM4. So my questions: Is there a better / alternative way to wake the processor N ti
  3. I just received my MSP430 FR5994 LaunchPad kit and fired up my first project using CodeComposer v I'm underwhelemed and wondering if I'm going down the wrong path. Specifically, the compiler feels ancient. For example, for (int i=0; i<100; i++) { do_something_with(i); } won't compile, complaining that i is undefined. All modern compilers I know of support this. So with this construct: int i; for (i=0; i<100; i++) { do_something_with(i); } the compiler gives a "helpful" remark that "Detected loop counting up. Recommend loops count down as detecting
  • Create New...