Kinetis Microcontrollers中的主题 Re: DEEP SLEEP

DEEP SLEEP

haroldvogel — Wed, 04 May 2016 19:30:14 GMT

Here is the code that I am using to put my MK36L256VLL4 chip into Deep Sleep but the system is drawing 175m volts. Hope some one can tell me where I am going wrong:

Original Attachment has been moved to: deepSleep.c.zip

Re: DEEP SLEEP

jeremyzhou — Thu, 05 May 2016 01:31:32 GMT

Hi Harold,

I was wondering if you can tell me what the exactly power consumption after the K36 enter the LLS mode.

I'm looking forward to your reply.
Have a great day,
Ping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: DEEP SLEEP

haroldvogel — Thu, 05 May 2016 10:49:01 GMT

Hello Ping,

Sorry I thought I had entered that in my request. The power consumption is 175m volts if you wish to know the amps I will have to get with the EE to find out.

I hope that this helps.

John V.

Re: DEEP SLEEP

haroldvogel — Thu, 05 May 2016 16:31:59 GMT

Found out that the 175 millivolts is 450 micro amps. Hope this helps.

Re: DEEP SLEEP

jeremyzhou — Fri, 06 May 2016 01:30:58 GMT

Hi Hardold,

We usually check out the power consumption level to find out the MCU enter what the kind of the low power mode, none with the voltage supply level.

About your case, the power consumption seems too large for the LLS mode and I've attached the Fig 1 which come form the datasheet.

Have a great day,
Ping

Re: DEEP SLEEP

haroldvogel — Fri, 06 May 2016 11:06:52 GMT

Hello Ping,

Thanks for confirming that the unit is using more power than it should. Do you have any idea why the MCU is using so much power? The attached file, with the first posted message, shows what is done to put the unit into Deep Sleep, is there something that is missing?

Sincerely,

H. John Vogel

Re: DEEP SLEEP

jeremyzhou — Mon, 09 May 2016 01:31:54 GMT

Hi John,
Please try the codes below, I think it can make the MCU enter the LLS mode successful.

void enter_lls(void)
{
  volatile unsigned int dummyread;
  /* Write to PMPROT to allow LLS power modes this write-once 
     bit allows the MCU to enter the LLS low power mode*/
  SMC_PMPROT = SMC_PMPROT_ALLS_MASK;   
  /* Set the STOPM field to 0b011 for LLS mode  */
  SMC_PMCTRL &= ~SMC_PMCTRL_STOPM_MASK; 
  SMC_PMCTRL |=  SMC_PMCTRL_STOPM(0x3); 
  /*wait for write to complete to SMC before stopping core */  
  dummyread = SMC_PMCTRL;
  dummyread++;
  /* Now execute the stop instruction to go into LLS */
  #ifdef CMSIS
  /* Set the SLEEPDEEP bit to enable deep sleep mode (STOP) */
  SCB_SCR |= SCB_SCR_SLEEPDEEP_MASK;
  __wfi();
#else
  stop();
#endif
}

Have a great day,
Ping

Re: DEEP SLEEP

haroldvogel — Mon, 09 May 2016 11:52:50 GMT

Hello Ping,

Thanks I will try the code out and see how it goes. I was wondering what the ‘stop()’ function does?

Sincerely,

John Vogel

Re: DEEP SLEEP

haroldvogel — Mon, 09 May 2016 13:59:27 GMT

Hello Ping,

Well was able to test the code with the re-marks that you made but still the same result.

The only thing that I can think of is a pin is either tri-stated or is configured incorrectly, not sure how to check this. The reason I say this is that if an older version of the code is loaded on the system then the unit goes into Deep Sleep mode (the Deep Sleep mode is the same as the code that I posted on this request) the only change is that the old chip was 125 instead of the 256 chip and the lines that have been configured for use now.

Re: DEEP SLEEP

haroldvogel — Mon, 09 May 2016 14:19:29 GMT

Hello Ping,

What is the difference between MUX_MASK, MUX_GPIO, MUX_ALT2, and MUX_ALT3 and how do I know which to use when I am turning OFF/ON a line in the code example:

PORTE_PCR5 &= ~(uint32_t)(PORT_PCR_MUX(MUX_MASK);

PORTE_PCR24 &= ~(uint32_t)(PORT_PCR_MUX)(MUX_MASK);

PORTE_PCR5 != (unit32_t)(PORT_PCR_MUX(MUX_GPIO);

PORTE_PCR24 |= (unit32_t)PORT_PCR_MUX(MUX_MASK);

as you see the PCR5 turns off with MUX_MASK but on with MUX_GPIO and PORTE_PCR24 use MUX_MASK for both, was wondering why and how do I know which to use, not sure if this could be causing the problem.

John V.

Re: DEEP SLEEP

haroldvogel — Mon, 09 May 2016 18:25:55 GMT

Hello Ping,

Do pins not being used have pull up resisters on them?

If they don't are they in a tri-state or are they off?

John V.

Re: DEEP SLEEP

jeremyzhou — Tue, 10 May 2016 05:45:53 GMT

Hi John,

You can disable the clock of the PORT prior to enter the low power mode, it will guarantee the enter low power operation execute well.

I'd highly recommend you to refer to the FRDM-KL25's sample code package which contains the low power demo, and I think it can help you out.

FRDM-KL25's sample code package: 面向Kinetis KL的Freedom开发平台|恩智浦

Hope it helps.
Have a great day,
Ping

Re: DEEP SLEEP

haroldvogel — Tue, 10 May 2016 11:17:00 GMT

Hello Ping,

I don't see a low power demo. I don't see in the code where it is calling wfi in the code.

John V.

Re: DEEP SLEEP

haroldvogel — Tue, 10 May 2016 11:28:15 GMT

Also none of the code that I down loaded and have looked at explain anything to me about the use of PORT_PCR_MUX(MUX_MASK); and/or PORT_PCR_MUX(MUX_GPIO);

I am also not sure if that is why the unit is still running at 440 micro amps when it is in Deep Sleep mode. The EE has looked over the pins and does not see any pins that I have missed. The EE was wondering if there are any internal pull up resisters on ports which are not connected?

John

Re: DEEP SLEEP

haroldvogel — Tue, 10 May 2016 13:58:45 GMT

Hello Ping,

Some more information. I am not sure how to send such information to you but I have add a number of pins using Processor Expert to the system. When I load code that does not have these pins in processor expert nor the generated code the system goes to about 4 micro amps.

Now, I am new to Freescale and also Processor Expert so something might have gone wrong in the creation of the generated code. I then added the pins that I used to the PowerManagement module (function). I will gladly send you what code that you might like to look at to help me figure out what is wrong with the Deep Sleep.

John V.

Re: DEEP SLEEP

haroldvogel — Tue, 10 May 2016 14:31:54 GMT

I have attached all the new code that has been generated from the new pins that have been added to the system.

I did not add this but I have added the TSS code which uses USART0 in the other version of the code it uses USART1.

John

Re: DEEP SLEEP

jeremyzhou — Wed, 11 May 2016 02:48:26 GMT

Hi John,

Downloading the sample code package flow:

Click the 面向Kinetis KL的Freedom开发平台|恩智浦
Download the sample code package

3. After install the sample code package, you can find the PEx_low_power_demo which integrates with the PE.

Hope it helps.

Have a great day,

Ping

Re: DEEP SLEEP

haroldvogel — Wed, 11 May 2016 12:04:35 GMT

Hello,

The selection that you give me is in Chinese (I believe), I cannot read the page. Please send me the link in English.

Did you have a chance to look over the other items that I have posted and sent to you?

Re: DEEP SLEEP

jeremyzhou — Thu, 12 May 2016 02:18:45 GMT

Hi John,

I've already had a look through the other items, and you thought the kind of GPIO configuration may corrupt the MCU enter the low power mode.

However from my experience, to enter the low power mode hasn't be associated with the GPIO configuration, so I think you'd better to refer the demo code.

Click the link

FRDM-KL25Z|Freedom Development Platform|Kinetis MCU|NXP

Hope it helps.

Have a great day,

Ping

Re: DEEP SLEEP

haroldvogel — Thu, 12 May 2016 10:56:34 GMT

Hello Ping,

I understand what you are saying but the fact that I took existing code and the sleep mode was okay. After adding a few new pins to be used the sleep current goes up to 440 micro amps. So the indication is that the configuration of the new pins is what caused the problem. As I have said, I am new to using Processor Expert and configuring items using the generated code.

John V.