PhracturedBlue
PhracturedBlue
FYI, I found that the issue was that my cert was generated using SHA512. I used the openssl defaults and everything worked fine. Feel free to close the issue, but...
I guess this is a bug in the 2.4 staging core? I'm not sure how to provide a test-case though, since the connection goes through many layers. Thanks for confirming...
yes, that would work great
I don't think there are any defines (or at least I too could not find them). However I think the point is that nvic_set_priority uses different semantics than the CM3...
The STM32F0 IPR registers are only word accessible (I assume this is true of all M0 cortex), unlike some other cortex processors. thus the current nvic_set_priority doesn't work at all...
It is very unlikely there was a hardware reboot, but I can't rule it out. This software runs on hundreds of machines in an enterprise environment and the issue was...
i don't think you can sleep with a mesh node. If you shut off the wireless, then you can't act as a relay, and you will miss all messages not...
your crash report isn't helpful, since there is no backtrace to debug. I am only guessing, but to make deepsleep work we probably need to take down any mqtt/socket connections...
I'm not really keen to rename credentials.h.example. There are 2 reasons: 1) It makes it more difficult for me to maintain the code, as I need to keep the template...
I'd be happy to take a patch but I didn't find an Async library for GSM. If one existed, we could probably work something out, but without it, the code...