• Announcements

    • bluehash

      Forum Upgrade   03/11/2017

      Hello Everyone, Thanks for being patient while the forums were being fixed and upgraded. Please see details and report issues in this thread. Thanks!

Search the Community

Showing results for tags 'Sleep'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • Announcements
    • Suggestions
    • New users say Hi!
  • Spotlight!
    • Sponsor Spotlight
    • Sponsor Giveaways
  • Energia
    • Energia - MSP
    • Energia - TivaC/CC3XXX
    • Energia - C2000
    • Energia Libraries
  • MSP Technical Forums
    • General
    • Compilers and IDEs
    • Development Kits
    • Programmers and Debuggers
    • Code vault
    • Projects
    • Booster Packs
    • Energia
  • Tiva-C, Hercules, CCXXXX ARM Technical Forums
    • General
    • SensorTag
    • Tiva-C, Hercules, CC3XXX Launchpad Booster Packs
    • Code Vault
    • Projects
    • Compilers and IDEs
    • Development Kits and Custom Boards
  • Beagle ARM Cortex A8 Technical Forums
    • General
    • Code Snippets and Scripts
    • Cases, Capes and Plugin Boards
    • Projects
  • General Electronics Forum
    • General Electronics
    • Other Microcontrollers
  • Connect
    • Embedded Systems/Test Equipment Deals
    • Buy, Trade and Sell
    • The 43oh Store
    • Community Projects
    • Fireside Chat
  • C2000 Technical Forums
    • General
    • Development Kits
    • Code Vault
    • Projects
    • BoosterPacks

Calendars

  • Community Calendar

Found 5 results

  1. First, I'd like to say thanks for the implementation of EasyLink for the cc1310/cc1350 in Energia 18. Last year the community was invaluable in helping me develop some MSP430FR5949/BME280 dataloggers for my dissertation research. I'm working on a new version based off the cc1310, because well, transmitting my data wirelessly sure beats having to recover the dataloggers. I have a couple questions that I have been unable to answer - 1. The EMT documentation suggests that if you use delay, during compiling this is converted to a low power mode. Is this only for the MSP430/432 variants? The main reason I ask is because sleep(), sleepSeconds(), etc... do not appear to be available for the cc1310/cc1350. Low power modes would be essential for this project. 2. As general advice, any opinions if I would be better off using Sensor Controller Studio, TI-RTOS, CCS for the development of this project and then simplify and port functionality back to Energia? As always, thanks for the help and insight.
  2. Hi All, I'm new to the forum, and fairly new to developing for TI chips, that being said I've played about in TI-RTOS for the SensorTag. I am trying to build a low power sub-GHz network, and as such I've got hold of some CC1310 LaunchPads, and I'd love to use Energia for my project. Can someone please explain how to put this board into any or each of the different low power modes it has? I've tried using the Sleep() command, but the compiler tells me it's not defined, and when I measure the power of the LaunchPad board during a Delay() command I'm seeing several mA. If I can get this down to tens of uA I'd be very happy. All and any help is greatly appreciated. Regards, -Steve
  3. Is there a way to wake the CC3200 via WiFi? I read this post but can someone let me know if this is operational in the latest version of Energia?
  4. I am taking an intro to electronics course. In lab we are implementing "power blocking" to reduce the total amount of power used by our sensor front end. Bellow is the sketch we are using. I do not understand how it works. The way another student described the code to me is: assume the entire loops runs in 1 + 19 ms. power would be on for a total of 1/20 ms == 5% of the time my confusion is with the call delayMicroseconds(1000) in the loop. (I did not find the documentation helpful) thanks in advance Andy //*************************************************************************************** // EE40LX // Sketch 3.2 // // Description; Power-block a 3.3V rail at P1.1 and subsequently read inputs from // Wheatstone bridges, connected to P1.2 and P1.7 // // Tom Zajdel // University of California, Berkeley // July 27, 2015 // // Version 1.2 July 27, 2015 - Added curly brackets to conditional statements // // Version 1.1 January 26, 2015 - Fixed a timing bug by using delayMicroseconds() // and also corrected errors in pin assignment // //*************************************************************************************** int PBRAIL = P1_1; // set PBRAIL as P1.1 alias int LPHOTO = P1_2; // set LPHOTO as P1.2 alias int RPHOTO = P1_7; // set RPHOTO as P1.7 alias int REDLED = P1_0; // set REDLED as P1_0 alias int GRNLED = P1_6; // set GRNLED as P1_6 alias void setup() { // set power block pin and led pins as outputs pinMode(PBRAIL, OUTPUT); pinMode(REDLED, OUTPUT); pinMode(GRNLED, OUTPUT); // set photocell input pins pinMode(LPHOTO, INPUT); pinMode(RPHOTO, INPUT); } void loop() { digitalWrite(PBRAIL, HIGH); // supply 3.3V to the power rail delayMicroseconds(1000); // delay briefly to allow comparator outputs to settle if (digitalRead(LPHOTO) == HIGH) // if LPHOTO is on, turn REDLED on { digitalWrite(REDLED, HIGH); // otherwise, turn REDLED off } else { digitalWrite(REDLED, LOW); } if (digitalRead(RPHOTO) == HIGH) // if RPHOTO is on, turn GRNLED on { digitalWrite(GRNLED, HIGH); // otherwise, turn GRNLED off } else { digitalWrite(GRNLED, LOW); } digitalWrite(PBRAIL, LOW); // turn the power rail off again sleep(19); // wait 19 ms (can do other tasks in this time, // but we are simply demonstrating that you can cut power // to the circuits for 95% of the time and not notice! }
  5. Hello all, I am struggling to set up a timer to implement a "wait" function. Basically, I have a piece of code that lights up a few LED's, then I want to wait a couple seconds and turn them off. The way I have it implemented at the moment: Timer configuration (in main function) // DCO configuration DCOCTL = CALDCO_1MHZ; //Set DCO to 1 MHz BCSCTL1 = CALBC1_1MHZ; // Calibrate internal clock for 1 MHz // Timer_A configuration TACTL = TASSEL_2 + TACLR + ID_3 + MC_0; CCTL0 |= CCIE; TACCR0 = 125; // 1 ms period ISR routine #pragma vector = PORT1_VECTOR __interrupt void button( void ) { (...) // Does stuff, lights LED's (...) // Wait a little - start timer, then TACTL |= MC_1; // Clears interrupt flag P1IFG &= ~BIT3; } Timer A interrupt #pragma vector = TIMERA0_VECTOR __interrupt void Timer_A0 (void) { i++; turn_leds_off(); if (i >= TIMEWAIT) { i = 0; // Turns leds off turn_leds_off(); // Stops timer TACTL |= MC_0; } else return; } The counter "i" is incremented until it reaches the value of constant TIMEWAIT I set at the beggining of the code. In theory my timer has a period of 1 ms, so if TIMEWAIT is set to 3000, it will go inside the IF statement after 3 seconds, turn the LED's off and stop the timer by setting MC_0. It doesn't work though. What am I doing wrong?