MDot appears not to wake up from Deep Sleep.

Home › Forums › mDot/xDot › MDot appears not to wake up from Deep Sleep.

Tagged: , ,

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • May 16, 2017 at 4:22 pm #19121
    Ajay K
    Participant

    I am not sure if this is happening with the latest MDot production libmdot version 2.0.17 or used to happen earlier.

    We have a custom firmware compiled against the libmdot library mentioned earlier. On MDot wake cycle, the application reads sensor data transmits it to conduit if the data has changed, or just sends some kind of heart beat to indicate the mdot is active and then goes into deep sleep mode for a minute and wakes up using RTC WAKE mode. This cycle repeats.

    Although the time interval when it doesn’t come out of sleep seems random, if we keep the mdot running all the time, the mdot suddenly won’t wake up even though the 1 minute sleep cycle has elapsed. Sometimes it 10 hrs into the wake/sleep cycles, sometimes 24 hrs and the longest so far we have seen is 30 hrs into the wake/sleep cycle. Also we have enabled debug full trace, so we know that the mdot went into sleep and the session info was stored successfully in the flash and then it never seems to wake up. So it almost seems like the mdot has entered some idle cpu mode.

    So currently we send data via the USB serial port and all of a sudden the mdot seems active again and goes back into its regular wake/sleep cycles, until it hits the sleep mode scenario described above.

    Any thoughts on why this could be happening over long period of time?

    Thanks,
    Ajay

    May 16, 2017 at 5:30 pm #19122
    Javier Pedrido
    Participant

    Hi,

    If you are using dot->sleep(x, mDot::RTC_ALARM_OR_INTERRUPT), the wake pin has to be low before going to sleep. If it’s high, It won’t return from sleep.

    Wake from RTC alarm and interrupt

    Regards,
    Javier

    May 17, 2017 at 11:57 am #19136
    Ajay K
    Participant

    Hi Javier,

    I am just calling dot->Sleep(nSeconds); I am using the defaults for the rest of the parameters and the default seems like is mdot::RTC_ALARM and so I am not sure if I need to manage the state of the wake pin?

    Why would it run thru’ the entire sleep/wake cycle and stall after a long run of sleep/wake cycle and mostly seems to happening since the latest build 2.0.17

    Thanks,
    Ajay

    May 17, 2017 at 3:20 pm #19146
    Javier Pedrido
    Participant

    Hi,

    The state of the wake pin only matters if you are using mDot::RTC_ALARM_OR_INTERRUPT. By the way, I’m using 2.0.17 and mDot::RTC_ALARM_OR_INTERRUPT in my app and it seems to be working fine.

    Regards,
    Javier

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.