Jump to content


  • Content Count

  • Joined

  • Last visited

  1. I think I finally figured it out. It appears that others have seen this behavior as well, and that it indicates a non working MSP432: https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/449768#pi316701=2 Because of the whole revision A/B happening right now, I won't have new boards to test from the fab for a few weeks. But I am looking forward to. Thanks to everybody for their help
  2. I measured it at 140 (not a typo). I am not at the lab today, but when I get back to the office I will pull a reading from the development board as well to cross check a native CCS app versus an Energia sketch and compare that way. Good idea! Thanks!
  3. I am confident in my board because I can flash a LPM3 binary (written in CCS) from CCS and see less than 2mA. That leads me to believe the problem is in an underlying Energia library.
  4. Unfortunately, sleep isn't supported by the MSP432 yet (it won't compile). The Energia documentation I have found has indicated that delay is similar to LPM3 sleep. The documentation I am referring to is here: http://energia.nu/energia-mt-for-msp432/ And this is the relevant section: "For example, if you use a delay(500) at the end of your loop instead of ticking for 500 milliseconds, TI-RTOS will set an interrupt and go into deep sleep until the 500 milliseconds is up."
  5. Just to expand on this a little more. If I import an Energia project into CCS, it will still consume between 140 and 160 mA. If I write native c in CCS, I am looking at sub 2mA (which I would expect to see). It appears to be something in the underlying Energia libraries which is overriding the lower sleep level. I am open to ideas if anybody has any. My next thought will be to start stripping out individual libraries and seeing if that has any effect.
  6. For the record, I just tested a basic program in CCS, and the draw was 2mA. Here is the app I ran: #include "msp.h" void main(void){ WDTCTL = WDTPW | WDTHOLD; // Stop watchdog timer while(1) { for(i=10000; i>0; i--); // Delay } } I wrote this test in Energia, with a power draw of 140mA. void setup(){ delay(10); } void loop(){ delay(1000); } I am trying to understand the significant difference in power draw between the two applications. For the Energia sketch, I loaded it to a custom board using UniFlash (flashing the ELF). For the CCS, I load
  7. Whoops, I just noticed that I mistyped - it should have read that the board drops to 90 mA in delay. Also, the board itself is a board I developed, so it just has the bare necessities for the MSP432 to run. It is not the development board. Thanks!
  8. That is what I thought as well, but it only drops to 90 mv in delay (versus 100 when running). Sleep isn't supported, but the documentation says that delay will work in the place of sleep - I am just not seeing it with a real-world test. The LPM3 for MSP432 claims it can get to 850nA in LPM3, but I am far from seeing that with just a delay in the loop and nothing else. My tests show it being off by an order of magnitude. I am open for testing. My next steps will be to use code composer to put it into LPM3, and measuring that directly, but I am hoping for more information first. Tha
  9. I was wondering if anybody has been able to get LPM modes working with Energia EMT and the MSP432. I have tried a few things, but have been unsuccessful in lowering the current draw of the MSP432. Any insights would be appreciated. Thanks!
  10. Of course, right after I posted this I found that you need SWDIOTMS (pin 94) and SWCLKTCK (pin 95) to program the msp432. Hope this can help somebody else too!
  11. Does anybody know how I can do the same thing with the msp432?
  • Create New...