This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430 devices sw LP-mode dependency...

Hi

Some troubles occured when checking MSP launchpad examples how the sw activates devices... mostly the main

execution is ended in low-power mode function... and usually interrupts used in the device will release

the execution when it happens and LP modes are ended.

Now I have been thinking is this intentional and the only way use for example the timers in MSP ?

If there is some tips for another approach would appreciate links.

Regards Kari B

  • kba said:
    Now I have been thinking is this intentional and the only way use for example the timers in MSP ?

    Interrupts are present in most timer applications. That's the beauty of interrupt use here - CPU does not have to check timer all the time, it can do other tasks or just sleep saving power - while timer runs. Timer calls ISR to signal that time is up or signal captured.

    Using timer in poll mode is of course possible, but it's more or less special case. Why you ask for non-IRQ timer samples? What's your application?

  • Ilmars said:

    Now I have been thinking is this intentional and the only way use for example the timers in MSP ?

    Interrupts are present in most timer applications. That's the beauty of interrupt use here - CPU does not have to check timer all the time, it can do other tasks or just sleep saving power - while timer runs. Timer calls ISR to signal that time is up or signal captured.

    Using timer in poll mode is of course possible, but it's more or less special case. Why you ask for non-IRQ timer samples? What's your application?

    [/quote]

    Yes, I do agree... my point is on examples given using some devices. They give impression they can't used otherwise than stopping the processor in lp-mode waiting the device to awoke them alive. Meanwhile all activity is down and nothing else can happen.

    Most MSP sw examples try to explain how the internal devices can be initialized and the basic use, but it's general difficulty in documentation how extensive that should be.

  • kba said:
    Yes, I do agree... my point is on examples given using some devices. They give impression they can't used otherwise than stopping the processor in lp-mode waiting the device to awoke them alive. Meanwhile all activity is down and nothing else can happen.

    Thing is that msp430 examples are not about programming classes teaching multitasking but msp430 hardware. To learn interrupt concept and how to do something while waiting for interrupt, perhaps you shall look for other sources of information than msp430 examples. Like read some book or just attend embedded programming class :)

  • kba said:
    my point is on examples given using some devices. They give impression they can't used otherwise than stopping the processor in lp-mode waiting the device to awoke them alive. Meanwhile all activity is down and nothing else can happen.

    Yes, the examples are showing how to use a specific module in a simple way. They are not meant for demonstrating how two modules can be used together.
    The examples are a starting point at best. You can study them and figure out how they work and why - in the limits of this example.

    Demonstrating how to play a certain chord on a guitar tells you how to use your fingers to produce this specific chord, along with the idea that you can play chords at all on a guitar. But it doesn't tell you how to do all the possible chords and of course won't turn you into a top-class guitar hero.
    But at least you have one known working position to start from.

**Attention** This is a public forum