You dont need to define the InterruptIn pin.

It seems that the version requirements are pretty specific. Previous versions of the library required mbed-rtos r110 otherwise join wouldnt work.

Multitech need to get their act together to produce a stable library.

Andrew

Andrew,

I apologize for the inferior experience you’ve had. We have had to recommend specific versions of the mbed and mbed-rtos libraries due to bugs or serious changes in the mbed libraries. Those kinds of issues are more obvious because we can only release binary builds of the mDot library. We are working hard to improve the mDot library and keep it compatible with the latest mbed versions.

Cheers,

Mike

Javier,

I just had another thought. It might be worthwhile to make sure there’s nothing wrong with the RTC on that mDot. Can you test on another mDot? Here’s the main for a simple app that will make sure the RTC is functioning properly.

#include "mbed.h"

int main() {
    printf("initializing RTC\r\n");
    // 1/3/2016 00:00:00 GMT - 1451779200
    set_time(1451779200);

    while (true) {
        printf("time %d\r\n", time(NULL));
        wait(1);
    }

    return 0;
}

Cheers,

Mike

Javier,

PA_0 needs to be 0 not 1. That is the problem.

Leon

Javier,

It’s an errata on the processor with a simple work around. The errata for the processor states…
“The various wakeup sources are logically OR-ed in front of the rising-edge detector which generates the wakeup flag (WUF). The WUF needs to be cleared prior to Standby mode entry, otherwise the MCU wakes up immediately.
If one of the configured wakeup sources is kept high during the clearing of the WUF (by setting the CWUF bit), it may mask further wakeup events on the input of the edge detector. As a consequence, the MCU might not be able to wake up from Standby mode.”

So if the processor is configured to wake from, both RTC and the wake pin, then deepsleep/standby is initiated while the wake pin is already high, wake functionality will not work correctly.

To avoid this, make sure the wake pin is low when you enter deepsleep/standby. Wake it by raising the wake pin… or the RTC timer.

FYI: On the MDK, the wake pin is the RTS signal coming from the XR21V1410 chip. If you attach to the serial port and are manipulating RTS, you will see that RTS is logically inverted by the XR21V1410 chip.

Leon

Javier,

Q: So, if I run the program without using the MDK and nothing attached to PA_0 will it wake from RTC?
A: As long as the wake pin is low(pulled down) when deepsleep/standby is entered.

Q: Is it possible to wake from deep sleep when attached to the MDK?
A: Yes, but you need to attach to the virtual serial port with RTS active so RTS is driven low from the XR21V1410 chip.

I like your code above where you read and output the state of the wake pin. I recommend you use that to make sure the wake pin is low before going into deep sleep… at least until you pass this hurdle.

Leon

When you plug the MDK with mdot into a computer, it should enumerate two ports. I’m assuming you are already using one of the two for communication to the mdot. The one that connects to the XR21V1410 is the one you need to control RTS on. If you are using Windows, you should see it in the device manager.

Fantastic, thanks for choosing MultiTech!

Hi Andrew,
Please provide an app that we can run to duplicate this issue and let us know what version of mbed, mbed-rtos and libmDot you are using to build it. Also, are you building off line or on line?
Leon