Guru meditation error
I am getting this Guru Meditation Error with FIPY communicating over Lora with other LoPy unit and Pushing data to AWS.
Both Lopy and FiPy are running 1.17.0.b1.
Other thing I noticed was after crash FiPy resets itself and can not make connected to WiFi, while keeps receiving LoRa messages from LoRa unit and sends back ACK but can not see this activity in console.
Please provide solution.
seb last edited by
Are you running an upto date version of pymakr? The ability to copy from the terminal was added quite a while ago
How to get complete log from Atom editor. It does not allow me to copy console log.
seb last edited by
Could you share complete the core dump that shows when the guru meditation happens?
We tested the gateway code that makes the AWS connection with the latest pycom firmware 1.17.3.b1 however we are still getting the core panic and guru meditation error.
We made code changes to connect to AWS IoT host only when where is data is the receive buffer as shown below:
# Connect with AWS IoT Hub.
time.sleep(0.25) # Time to stabilize connection.
# Check if there are messages to be sent in buffer.
# pop one message from buffer and publish on MQTT.
# give it 1 second between messages.
# Disconnect from AWS IoT Hub to free up websocket memory.
pass # Nothing to do.
# Sleep for about a minute, before checking for new messages in buffer.
With this change we found the code more stable however it does re-start and cause the guru medication error once in 5 mins. We also played around the connectdisconnetTimeout and noticed better behaviour when the timeout was reduced from 10 second to 5 second. The timeout affects the mqtt.disconnect() more than the mqtt.connect()
livius last edited by
what about new firmware
We noticed that even when we are not sending any lora packets the core panics and restarts periodically.
So just doing mqtt connect and mqtt disconnect repeatedly with 1 min sleep time it causes the guru meditation error.
Attached is the screenshot of the error message.