Guru Meditation Error
-
I am also seeing Guru Meditation Errors with latest firmware v1.20.1.r2 and vanilla releases.
Here's just a few:Guru Meditation Error: Core 1 panic'ed (Unhandled debug exception)
Guru Meditation Error: Core 0 panic'ed (IllegalInstruction). Exception was unhandled.
Guru Meditation Error: Core 0 panic'ed (IllegalInstruction). Exception was unhandled.The code makes heavy use of the UARTs and runs flawlessly on desktop.
-
Dear @sita,
decoding the core dump shows (without guarantee):
==================== CURRENT THREAD STACK ===================== #0 0x4009192e in vTaskExitCritical (mux=0x844a) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:4274 #1 0x401124f0 in lora_join (n_args=1073518712, pos_args=0x3ffc990c <lora_partial_rx_packet+12>, kw_args=0x401124f0 <lora_join+16>) at mods/modlora.c:1843 ======================== THREADS INFO ========================= Id Target Id Frame 16 process 15 0x4000bff0 in ?? () 15 process 14 xQueueCreateCountingSemaphoreStatic (uxMaxCount=1073426000, uxInitialCount=1073431200, pxStaticQueue=0x3ffb2e9c) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:659 14 process 13 xQueueCreateCountingSemaphoreStatic (uxMaxCount=1073495820, uxInitialCount=0, pxStaticQueue=0x3ffc3f58 <vflash_mem+1900>) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:659 13 process 12 xQueueCreateCountingSemaphoreStatic (uxMaxCount=1073444348, uxInitialCount=0, pxStaticQueue=0x3ffb7648) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:659 12 process 11 0x4000bff0 in ?? () 11 process 10 xQueueCreateCountingSemaphoreStatic (uxMaxCount=1073458244, uxInitialCount=1073580336, pxStaticQueue=0x3ffbac90) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:659 10 process 9 xQueueCreateCountingSemaphoreStatic (uxMaxCount=1073445832, uxInitialCount=0, pxStaticQueue=0x3ffb7c14) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:659 9 process 8 xQueueCreateCountingSemaphoreStatic (uxMaxCount=1073589088, uxInitialCount=1073603328, pxStaticQueue=0x3ffdabac) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:659 8 process 7 0x4000bff0 in ?? () 7 process 6 0x40092b55 in xTaskNotify (xTaskToNotify=0x0, ulValue=<optimized out>, eAction=<optimized out>) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:4872 6 process 5 0x4009192e in vTaskExitCritical (mux=0x8484) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:4274 5 process 4 xQueueCreateCountingSemaphoreStatic (uxMaxCount=1073468564, uxInitialCount=1073458080, pxStaticQueue=0x3ffbd4e0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:659 4 process 3 0x40206db2 in API_vhci_host_check_send_available () 3 process 2 xQueueCreateCountingSemaphoreStatic (uxMaxCount=1073470132, uxInitialCount=0, pxStaticQueue=0x3ffbdb00) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:659 2 process 1 0x4009192e in vTaskExitCritical (mux=0x844a) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:4274 * 1 <main task> 0x4009192e in vTaskExitCritical (mux=0x844a) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:4274So, it seems to happen while performing
lora_joinwithinmods/modlora.c.// check for the correct lora radio mode if (lora_obj.stack_mode != E_LORA_STACK_MODE_LORAWAN) { nlr_raise(mp_obj_new_exception_msg(&mp_type_OSError, mpexception_os_request_not_possible)); }I assume this is some synchronization issue wrt. the code is already doing other things.
Maybe waiting for successfully joining the LoRaWAN network helps like outlined within [1] before doing other operations.Forget about my last words. I believe this is wrong as I've probably used the wrong
application.elffile for decoding the core dump -- see next post(s).I just recognized you are using pure LoRa instead of LoRaWAN....
@sita said in Guru Meditation Error:
lora = LoRa(mode=LoRa.LORA, region=LoRa.EU868, frequency=433000000, power_mode=LoRa.ALWAYS_ON, tx_power=10, bandwidth=LoRa.BW_125KHZ, sf=8, preamble=8, coding_rate=LoRa.CODING_4_8)... so who should be actually invoking
lora_joinanyway ;].With kind regards,
Andreas.P.S.: To be safe that the core dump decoding gives us the correct results: Are you using
lopy4-vanilla-dragonfly-onewireorlopy4-vanilla-dragonfly-onewire-i2s? -
What baffles me is that [1] shows:
// check for the correct lora radio mode if (lora_obj.stack_mode != E_LORA_STACK_MODE_LORAWAN) { nlr_raise(mp_obj_new_exception_msg(&mp_type_OSError, mpexception_os_request_not_possible)); }Drawing a conclusion from that, might it be that
lora_joinis not advisable when doing raw LoRa as outlined within your code@sita said in Guru Meditation Error:
lora = LoRa(mode=LoRa.LORA, region=LoRa.EU868, frequency=433000000, power_mode=LoRa.ALWAYS_ON, tx_power=10, bandwidth=LoRa.BW_125KHZ, sf=8, preamble=8, coding_rate=LoRa.CODING_4_8)But who is actually invoking
lora_joinanyway?With kind regards,
Andreas.[1] https://github.com/pycom/pycom-micropython-sigfox/blob/Dev/esp32/mods/modlora.c#L1841-L1844
-
@andreas said in Guru Meditation Error:
P.S.: To be safe that the core dump decoding gives us the correct results: Are you using lopy4-vanilla-dragonfly-onewire or lopy4-vanilla-dragonfly-onewire-i2s?
I have to admit I didn't keep track of the
application.elffiles coming out of my builds which are required to properly decode the core dumps. May I humbly ask you to try again using LoPy4-1.20.1.r3-0.8.0-vanilla-squirrel.tar.gz? -
@andreas said in Guru Meditation Error:
P.S.: To be safe that the core dump decoding gives us the correct results: Are you using lopy4-vanilla-dragonfly-onewire or lopy4-vanilla-dragonfly-onewire-i2s?
I've tried to reproduce a corresponding
application.elffile for the LoPy4-0.7.0-vanilla-dragonfly-modonewire-i2s firmware which shows the core dump is happening here:==================== CURRENT THREAD STACK ===================== #0 0x4009192e in vTaskExitCritical (mux=0x844a) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:4274 #1 0x401124f0 in lora_bandwidth (n_args=<optimized out>, args=0x3ffc990c <lora_partial_rx_packet+12>) at mods/modlora.c:2117See also [1]. I believe this is also due to a erroneous core dump decoding, so nevermind.
I have now kept the
application.elffile for the new build LoPy4-1.20.1.r3-0.8.0-vanilla-squirrel.tar.gz. If you are able to catch another core dump when running this firmware, we would probably get correct results. Sorry for the extra mile.[1] https://github.com/pycom/pycom-micropython-sigfox/blob/Dev/esp32/mods/modlora.c#L2116-L2118
-
Another attempt by trying to reproduce a corresponding
application.elffile for the LoPy4-0.7.0-vanilla-dragonfly firmware without support for 1-Wire and I2S.==================== CURRENT THREAD STACK ===================== #0 0x4009192e in prvAddNewTaskToReadyList (pxNewTCB=0x844a, xCoreID=1073476968, pxTaskCode=<optimized out>) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:1175 #1 0x401124f0 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) ======================== THREADS INFO ========================= Id Target Id Frame 16 process 15 0x4000bff0 in ?? () 15 process 14 xQueueGenericSend (xQueue=0x3ffb2e50, pvItemToQueue=<optimized out>, xTicksToWait=4294967295, xCopyPosition=0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:780 14 process 13 xQueueGenericSend (xQueue=0x3ffc3f0c <vflash_mem+1840>, pvItemToQueue=<optimized out>, xTicksToWait=4294967295, xCopyPosition=0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:780 13 process 12 xQueueGenericSend (xQueue=0x3ffb75fc, pvItemToQueue=<optimized out>, xTicksToWait=4294967295, xCopyPosition=0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:780 12 process 11 0x4000bff0 in ?? () 11 process 10 xQueueGenericSend (xQueue=0x3ffbac44, pvItemToQueue=<optimized out>, xTicksToWait=4294967295, xCopyPosition=0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:780 10 process 9 xQueueGenericSend (xQueue=0x3ffb7bc8, pvItemToQueue=<optimized out>, xTicksToWait=4294967295, xCopyPosition=0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:780 9 process 8 xQueueGenericSend (xQueue=0x3ffdab60, pvItemToQueue=<optimized out>, xTicksToWait=4294967295, xCopyPosition=0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:780 8 process 7 0x4000bff0 in ?? () 7 process 6 0x40092b55 in vTaskNotifyGiveFromISR (xTaskToNotify=0x0, pxHigherPriorityTaskWoken=0x0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:5044 6 process 5 0x4009192e in prvAddNewTaskToReadyList (pxNewTCB=0x8484, xCoreID=1073476968, pxTaskCode=<optimized out>) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:1175 5 process 4 xQueueGenericSend (xQueue=0x3ffbd494, pvItemToQueue=<optimized out>, xTicksToWait=100, xCopyPosition=0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:780 4 process 3 0x40206db2 in littleFsErrorToErrno (littleFsError=393251) at littlefs/vfs_littlefs.c:175 3 process 2 xQueueGenericSend (xQueue=0x3ffbdab4, pvItemToQueue=<optimized out>, xTicksToWait=4294967295, xCopyPosition=0) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/queue.c:780 2 process 1 0x4009192e in prvAddNewTaskToReadyList (pxNewTCB=0x844a, xCoreID=1073476968, pxTaskCode=<optimized out>) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:1175 * 1 <main task> 0x4009192e in prvAddNewTaskToReadyList (pxNewTCB=0x844a, xCoreID=1073476968, pxTaskCode=<optimized out>) at /Users/iwahdan/esp/pycom-esp-idf/components/freertos/tasks.c:1175Looking at
littleFsErrorToErrno (littleFsError=393251) at littlefs/vfs_littlefs.c:175here.
-
@sita said in Guru Meditation Error:
while True: # f = open('/sd/A_3001SF8.txt', 'a+') f.write(message) f.write(' ') f.write('\n') f.close()Could you stop opening and closing the file within such a tight loop? You might want to
time.sleep_ms()for at least some milliseconds between iterations. To be safe, try to use longer intervals first and get shorter if things might become more stable.When being at it, you might also want to think about optimizing things using a single
writecall likef.write(message + ' \n'). -
Hello @andreas,
Thanks for the information. I kept time.sleep_ms(10) in the loop and will change f.write as you said.I will do the the experiment again and let you know if i got same again.
Thanks once again.Have a nice day
-
Hello @andreas ,
I have changed the firmware to LoPy4-1.20.1.r3-0.8.0-vanilla-squirrel.tar.gz. I will do the experiment again and let you know if i got same issue again.
Thanks once again & have a nice day
-
Hello @andreas ,
I have now flashed the latest firmware (LoPy4-1.20.1.r3-0.8.0-vanilla-squirrel.tar.gz). I got a new problem.When i try to upload my project, it gets struck while uploading the additional library files required. I attached the screenshot below.
As far i understood, it is trying to compress the library files before uploading and it gets struck with that. I haven't observed this phenomenon with earlier firmware versions. Please have a look
Thanks & Best regards,
Have a nice weekend -
Hello all,
I got an issue regarding uploading the project and connecting the port after updating new firmware LoPy4-1.20.1.r3-0.8.0-vanilla-squirrel.tar.gz, the respective problem screenshots shown in the below.
My doubt is, Is it related to new firmware update or any change in ATOM editor settings ??
Could anyone please suggest me how to resolve this problem ?
Uploading project (main folder)... Safe booting device... (see settings for more info) Safe boot failed, uploading anyway. Upload failed: timeout. Please reboot your device manually.Connecting to COM12... Connection error: Error: timeoutThanks in advance & Have a nice day
-
Dear @sita,
sorry to hear that this didn't work out well. While I have to admit I haven't tested the firmware on a LoPy4 device, I just compiled it like any other Dragonfly builds I have done before.
I haven't seen the error you are observing anytime before.
So, to be better safe than sorry, downgrading to any other former release from [1] might help. If it doesn't you might want to downgrade to a regular release from Pycom using the regular firmware installer.
Sorry for the hassle!
With kind regards,
Andreas.[1] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/
-
Hello @andreas ,
I have tested my devices all the versions in the [1] but in every version i observed the Guru meditation error. Is there any permanent solution for this problem ? It would be very helpful if i know exact reason behind issue ,if you know the reason could you please let me know..
Thanks in advance & have a nice day
[1] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/
-
Dear @sita,
just a short question: Have you been able to run your MicroPython program successfully with
LoPy4-1.20.1.r3-0.8.0-vanilla-squirreluntil the Guru Meditation error happened again? I am asking because it looked like you had other problems with this the other day.With kind regards,
Andreas. -
Hello @andreas,
The other problems are still there, for temporarily i am running [1] in cmd so that error not coming.
[1]pycom-fwtool-cli.exe --verbose --port COM12 erase_all
-
Thanks. So, to make sure we are on the same page...
- Invoking
erase_allonce before uploading a new firmware image is considered good practice. Thanks for letting me know. - After that, you are able to invoke your MicroPython program using the
LoPy4-1.20.1.r3-0.8.0-vanilla-squirrelfirmware? - However, Guru Meditation errors still occur?
Now, are you able to submit another core dump when running this firmware build? I have saved a local copy of
lopy4-0.8.0-vanilla-squirrel.elfon my workstation in order to decode core dumps produced by this build. - Invoking
-
@andreas Now i got an issue with the atom editor :( :(
i have updated the ATOM editor evening and now i it is not showing REPL console. I will check with this and send you the core dump (LoPy4-1.20.1.r3-0.8.0-vanilla-squirrel). -
@sita can you try again with 1.20.2.rc3
@pigamonte same advice to you, but in case it doesn't solve it for you, I suggest to open your own thread. Otherwise we end up mixing different issues. Just because it shows a Guru Meditation Error, doesn't necessarily mean the issues are related.
-
Hello @peterp,
I have tried with new firmware version (1.20.2.rc3) but same error is coming again. I will open new thread to avoid mixing of different issues.
Thanks & Have a nice day
-
Dear @sita,
@sita said in Guru Meditation Error:
I have tried with new firmware version (1.20.2.rc3) but same error is coming again.
Either with the original Pycom's 1.20.2.rc3 and/or with the corresponding/updated LoPy4-1.20.2.rc3-0.8.0-vanilla-squirrel.tar.gz, I will be happy to receive respective core dumps. I have now kept the definitive
.elffiles around for decoding the core dumps appropriately.Thanks and with kind regards,
Andreas.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login