Javier Pedrido
Forum Replies Created
-
AuthorPosts
-
Javier PedridoParticipant
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,
JavierJavier PedridoParticipantHi,
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.
Regards,
JavierJavier PedridoParticipantThanks for the information, Jason.
Best regards,
JavierJavier PedridoParticipantSorry to bump this, but, is it possible to change the coding rate when using P2P?
Regards, JavierJavier PedridoParticipantIf I try to do a soft reset I get:
[INFO] Backing up current firmware
[ERROR] backup_firmware: open failed
[ERROR] update_firmware: Failed to back up current firmware- This reply was modified 7 years, 1 month ago by Javier Pedrido.
Javier PedridoParticipantMike,
Sorry, what’s RFU? Yes I could fork the MBED repository and create a pull request with this change. Is there any chance that this modification gets applied to the main repository?
Thanks,
JavierJavier PedridoParticipantThanks, Leon, I also got it working connected to computer 🙂
Javier PedridoParticipantThanks, Leo, I disconnected the MDK from the computer and connected it to a battery and It worked. I will try it connected to the computer with RTS active later (I don’t know how to do it 🙂 ).
Thanks again,
JavierJavier PedridoParticipantSo, if I run the program without using the MDK and nothing attached to PA_0 will it wake from RTC? Is it possible to wake from deep sleep when attached to the MKD? I tried this and it didn’t wake up.
mDot* dot = mDot::getInstance();
dot->setLogLevel(mts::MTSLog::INFO_LEVEL);
logInfo(“version: %s”, dot->getId().c_str());DigitalOut wake(PA_0);
logInfo(“Hola %d”, wake.read());
wake.write(0);
logInfo(“Hola %d”, wake.read());dot->sleep(10, mDot::RTC_ALARM_OR_INTERRUPT);
Javier
Javier PedridoParticipantLeon, so it’s hardware problem? Javier
Javier PedridoParticipantHi, if I run the following program without anything connected and starting with a powered off mdot:
`DigitalIn wake(PA_0);
DigitalIn other(PA_7);
mDot* dot = mDot::getInstance();
dot->setLogLevel(mts::MTSLog::INFO_LEVEL);
logInfo(“version: %s”, dot->getId().c_str());while (true) {
logInfo(“Hola %d %d”, wake.read(), other.read());
osDelay(2000);
}`I get:
[INFO] mDot Ready
[INFO] version: 2.0.6-2-ge3d307b
[INFO] Hola 1 0
[INFO] Hola 1 0
[INFO] Hola 1 0
[INFO] Hola 1 0Is it ok that PA_0 is allways 1?
Javier
Javier PedridoParticipantLeon, but I dont have anything connected to mdots when I do the tests and they were powered off before the tests.
Javier
Javier PedridoParticipantMike,
I have two mDots, I’ve installed your program, unplugged them, plugged them again and both failed to wake up from RTC, they just printed one time:
[INFO] mDot Ready [INFO] version: 2.0.6-1-g3959fe1 [INFO] entering deepsleep (standby) mode 00000037
The result of the other test was:
time 1451779202 time 1451779203 time 1451779204 time 1451779205 time 1451779206 time 1451779207 time 1451779208 time 1451779209 time 1451779210 time 1451779211 time 1451779212 time 1451779213 time 1451779214 time 1451779215 time 1451779216 time 1451779217 time 1451779218 time 1451779219 time 1451779220 time 1451779221 time 1451779222 time 1451779223 time 1451779224 time 1451779225 time 1451779226 time 1451779227 time 1451779228
I’m openning a support case.
Javier
Javier PedridoParticipantMike, I will try that and I will let you know. Thanks for the help, Javier.
Javier PedridoParticipantMike, did you manage to manage to reproduce this issue? Regards, Javier.
Javier PedridoParticipantFYI, If I use mDot::RTC_ALARM or mDot::INTERRUPT it works OK. The problem is just with mDot::RTC_ALARM_OR_INTERRUPT.
Javier PedridoParticipantMike, I’m using a MDK.
Javier PedridoParticipantIs there some documentation on what versions should be used with mdot 2.0.3?
JavierJavier PedridoParticipantWell, that combination broke p2p data transmission, I guess having wake on interrupt and rtc is not an option right now.
Javier PedridoParticipantFYI, reverting to mbed 116 and keeping rtos 117, mdot 2.0.3, fixed this problem.
Javier PedridoParticipantThanks Andrew, but even if I remove that line still doesn’t wake up with RTC alarms.
-
AuthorPosts