You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RH_ASK together with WiFi in some cases leads to Guru Meditation Error (Cache disabled but cached memory region accessed)
Solution: add ESP32 handling #define INTERRUPT_ATTR IRAM_ATTR for RH_PLATFORM == RH_PLATFORM_ESP32
by changing in RH_ASK.cpp file
FROM:
#if (RH_PLATFORM == RH_PLATFORM_ESP8266)
// interrupt handler and related code must be in RAM on ESP8266,// according to issue #46.
#defineINTERRUPT_ATTR ICACHE_RAM_ATTR
#else
#defineINTERRUPT_ATTR
#endif
TO:
#if (RH_PLATFORM == RH_PLATFORM_ESP8266)
// interrupt handler and related code must be in RAM on ESP8266,// according to issue #46.
#defineINTERRUPT_ATTR ICACHE_RAM_ATTR
#elif (RH_PLATFORM == RH_PLATFORM_ESP32)
#defineINTERRUPT_ATTR IRAM_ATTR
#else
#defineINTERRUPT_ATTR
#endif
If this is a correct way to solve it, please include in your next version.
(For me it solved it, I can observer a stable run for some longer time)
By the way I do expect same problem (and solution) for the module CC110, which I want o use in the next (hardware) release in my project.
The DRAM_ATTR part was what really helped me. The IRAM part was already inside the lib, but I still got the Cache panics regularily and I only looked inside the code part.
RH_ASK together with WiFi in some cases leads to Guru Meditation Error (Cache disabled but cached memory region accessed)
Solution: add ESP32 handling
#define INTERRUPT_ATTR IRAM_ATTR
for RH_PLATFORM == RH_PLATFORM_ESP32by changing in RH_ASK.cpp file
FROM:
TO:
If this is a correct way to solve it, please include in your next version.
(For me it solved it, I can observer a stable run for some longer time)
By the way I do expect same problem (and solution) for the module CC110, which I want o use in the next (hardware) release in my project.
A more detailed description is here: espressif/arduino-esp32#3634
Best
Peter
The text was updated successfully, but these errors were encountered: