rashedtalukder
commented
3 years ago Hi @David-Mesa, I'll be investigating the issue today. I haven't seen this regression in my prior tests, but your detailed explanation and the log is very helpful.
Closed David-Mesa closed 3 years ago
rashedtalukder
commented
3 years ago Hi @David-Mesa, I'll be investigating the issue today. I haven't seen this regression in my prior tests, but your detailed explanation and the log is very helpful.
rashedtalukder
commented
3 years ago Issue should be fixed. Please run the commands to get and merge the changes into your local repository:
git fetch
git pullSorry for the challenge you experienced, but your time to report this was very appreciated. I'll leave the issue open for 24 hours to give you time to try it and let me know if it resolved all of your issues.
David-Mesa
commented
3 years ago I'm getting this error:
PS C:\Core2-for-AWS-IoT-EduKit\Smart-Thermostat> git pull
error: Your local changes to the following files would be overwritten by merge:
Smart-Thermostat/main/main.c
Please commit your changes or stash them before you merge.
Aborting
Updating b281edf..3586294Is the main.c file already updated in the code repository? I could replace that file directly if it is the only thing missing. Right?
David-Mesa
commented
3 years ago Also, do I have to erase the device memory and compile it again? Or can I just compile on topof it once I have the updated code?
rashedtalukder
commented
3 years ago I'm getting this error:
PS C:\Core2-for-AWS-IoT-EduKit\Smart-Thermostat> git pull error: Your local changes to the following files would be overwritten by merge: Smart-Thermostat/main/main.c Please commit your changes or stash them before you merge. Aborting Updating b281edf..3586294Is the main.c file already updated in the code repository? I could replace that file directly if it is the only thing missing. Right?
Yes, you can replace the contents of the file directly. You can also stash your changes if you want by doing a git stash and then git pull. You can get back to your changes later with git pop.
rashedtalukder
commented
3 years ago Also, do I have to erase the device memory and compile it again? Or can I just compile on topof it once I have the updated code?
You don't need to erase the memory and go through the full build process again. What will happen is that the linker will see the change to the few files and compile a new application binary with an appended list of files. Most of the things you see and time that's taken is from all the drivers (e.g. flash, wi-fi, UART, etc) being linked and compiled. Since those haven't changed, it won't take as long to compile.
We recommend erasing the memory mainly to save yourself from having unwanted cloud service fees with the device continually running and to avoid strange/hard to diagnose behavior from having data from a different application still existing in the memory map.
David-Mesa
commented
3 years ago Thank you for your swift response, Rashed. It is all working as expected with no rebooting. Lights are working as well with the temperature changes.
Hello,
I went through this exercise multiple times and a couple of unexpected errors kept occurring.
In step c) Data Sync, there is a bug during the validation step. Once a shadow message is published, the M5Core 2 device starts rebooting the program and attempting reconnection (connection with AWS is stable before publishing the message).
If the validation is skipped without publishing, the device and monitoring keep working correctly. Then, a similar error occurs building the cloud application, once AWS IoT starts publishing messages to the device. The device keeps rebooting after sending only one set of data, so the intervals become around 15 seconds (this is what it takes the device to reset and reconnect).
Also, the device lights are not being triggered when the states are changed to COOLING or HEATING (they remain off).
I hope this information is useful.
Cheers, David