Core 1 Panic .. Board keeps resetting

resolved

#1

Just got OMG set up on my ESP32 and I see that it is resetting every 30 seconds or so:

WiFi ok with manual config credentials
OpenMQTTGateway mac: 
CC:50:E3:80:A9:14
OpenMQTTGateway ip: 
192.168.0.19
1883
Connecting to MQTT by IP adress
192.168.0.25
IR_EMITTER_PIN 
14
IR_RECEIVER_PIN 
27
ZgatewayIR setup done 
RF_EMITTER_PIN 
12
RF_RECEIVER_PIN 
13
ZgatewayRF setup done 
ZgatewayBT multicore ESP32 setup done 
BT Task running on core 0
MQTT_MAX_PACKET_SIZE
1024
Setup OpenMQTTGateway end
MQTT connection...
Connected to broker
Subscription OK to the subjects
Guru Meditation Error: Core  1 panic'ed (Cache disabled but cached memory region accessed)
Core 1 register dump:
PC      : 0x400dcce8  PS      : 0x00060034  A0      : 0x40081864  A1      : 0x3ffc0bf0  
A2      : 0x00000001  A3      : 0x00000002  A4      : 0x000000ff  A5      : 0x400905d0  
A6      : 0x00000000  A7      : 0x1300045c  A8      : 0x80081388  A9      : 0x3ff5f024  
A10     : 0x3ffc1170  A11     : 0x20000000  A12     : 0x00000400  A13     : 0x00000000  
A14     : 0x3ffc8584  A15     : 0xffffffff  SAR     : 0x00000016  EXCCAUSE: 0x00000007  
EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  
Core 1 was running in ISR context:
EPC1    : 0x40082407  EPC2    : 0x00000000  EPC3    : 0x00000000  EPC4    : 0x400dcce8

Backtrace: 0x400dcce8:0x3ffc0bf0 0x40081861:0x3ffc0c10 0x40082404:0x00000000

Rebooting...
ets Jun  8 2016 00:22:57

rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:956
load:0x40078000,len:0
load:0x40078000,len:13256
entry 0x40078a90
Connecting to 

Any idea why this might be? Also, does it relay all BT devices it detects? I’m not seeing any BT broadcasts. I haven’t connecting RF yet so I don’t see that either but I do see the initial version and LWT messages on my MQTT.


#2

Now I’m seeing this:

WiFi ok with manual config credentials
OpenMQTTGateway mac: 
CC:50:E3:80:A9:14
OpenMQTTGateway ip: 
192.168.0.19
1883
Connecting to MQTT by IP adress
192.168.0.25
Guru Meditation Error: Core  1 panic'ed (InstrFetchProhibited)
. Exception was unhandled.
Core 1 register dump:
PC      : 0xffffffff  PS      : 0x00060230  A0      : 0x800dd00e  A1      : 0x3ffda040  
A2      : 0x3ffda084  A3      : 0x3f401a29  A4      : 0x00000000  A5      : 0x0000ff00  
A6      : 0x00ff0000  A7      : 0xff000000  A8      : 0x800dcfea  A9      : 0x3ffda020  
A10     : 0x3ffdffa8  A11     : 0x3f401a29  A12     : 0x3ffc144c  A13     : 0x00000001  
A14     : 0x00060c20  A15     : 0x3ffe3a84  SAR     : 0x0000001a  EXCCAUSE: 0x00000014  
EXCVADDR: 0xfffffffc  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0xffffffff  

Backtrace: 0x7fffffff:0x3ffda040 0x400dd00b:0x3ffda060 0x400d4911:0x3ffda080 0x400d4b7a:0x3ffda0b0 0x401be8da:0x3ffda100

Rebooting...

#3

The board I have claims to be an NodeMCU32-S … I tried compiling with that board type and I get this:

Sketch uses 1630978 bytes (124%) of program storage space. Maximum is 1310720 bytes.
Global variables use 75184 bytes (25%) of dynamic memory, leaving 219728 bytes for local variables. Maximum is 294912 bytes.
Sketch too big; see http://www.arduino.cc/en/Guide/Troubleshooting#size for tips on reducing it.
Error compiling for board NodeMCU-32S

This is the board I bought:
https://www.amazon.com/gp/product/B0718T232Z/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

Is it incompatible? It does flash as the dev board as instructed but panics like crazy. I am no longer seeing any messages being sent via MQTT.


#4

Did you put minimal spiffs in your upload parameters (as stated in the wiki)?


#5

Yes… I certainly did…The NodeMCU32-S does not allow for the minimal spiffs option though.


#6

WARNING: library WiFi claims to run on (esp32) architecture(s) and may be incompatible with your current board which runs on (arduino-esp32) architecture(s).
WARNING: library ArduinoOTA claims to run on (esp32) architecture(s) and may be incompatible with your current board which runs on (arduino-esp32) architecture(s).
WARNING: library Update claims to run on (esp32) architecture(s) and may be incompatible with your current board which runs on (arduino-esp32) architecture(s).
WARNING: library ESP32_BLE_Arduino claims to run on (esp32) architecture(s) and may be incompatible with your current board which runs on (arduino-esp32) architecture(s).
WARNING: library rc-switch claims to run on (avr, esp8266, esp32) architecture(s) and may be incompatible with your current board which runs on (arduino-esp32) architecture(s).
WARNING: library ESPmDNS claims to run on (esp32) architecture(s) and may be incompatible with your current board which runs on (arduino-esp32) architecture(s).
Sketch uses 1636286 bytes (83%) of program storage space. Maximum is 1966080 bytes.
Global variables use 75248 bytes (25%) of dynamic memory, leaving 219664 bytes for local variables. Maximum is 294912 bytes.
esptool.py v2.3.1
Connecting........_____....._____.....__
Chip is ESP32D0WDQ6 (revision (unknown 0xa))
Features: WiFi, BT, Dual Core, VRef calibration in efuse
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 8192 bytes to 47...

Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 655.4 kbit/s)...
Hash of data verified.
Compressed 14320 bytes to 9346...

Writing at 0x00001000... (100 %)
Wrote 14320 bytes (9346 compressed) at 0x00001000 in 0.9 seconds (effective 123.4 kbit/s)...
Hash of data verified.
Compressed 1637440 bytes to 913975...

Writing at 0x00010000... (1 %)
Writing at 0x00014000... (3 %)
Writing at 0x00018000... (5 %)
Writing at 0x0001c000... (7 %)
Writing at 0x00020000... (8 %)
Writing at 0x00024000... (10 %)
Writing at 0x00028000... (12 %)
Writing at 0x0002c000... (14 %)
Writing at 0x00030000... (16 %)
Writing at 0x00034000... (17 %)
Writing at 0x00038000... (19 %)
Writing at 0x0003c000... (21 %)
Writing at 0x00040000... (23 %)
Writing at 0x00044000... (25 %)
Writing at 0x00048000... (26 %)
Writing at 0x0004c000... (28 %)
Writing at 0x00050000... (30 %)
Writing at 0x00054000... (32 %)
Writing at 0x00058000... (33 %)
Writing at 0x0005c000... (35 %)
Writing at 0x00060000... (37 %)
Writing at 0x00064000... (39 %)
Writing at 0x00068000... (41 %)
Writing at 0x0006c000... (42 %)
Writing at 0x00070000... (44 %)
Writing at 0x00074000... (46 %)
Writing at 0x00078000... (48 %)
Writing at 0x0007c000... (50 %)
Writing at 0x00080000... (51 %)
Writing at 0x00084000... (53 %)
Writing at 0x00088000... (55 %)
Writing at 0x0008c000... (57 %)
Writing at 0x00090000... (58 %)
Writing at 0x00094000... (60 %)
Writing at 0x00098000... (62 %)
Writing at 0x0009c000... (64 %)
Writing at 0x000a0000... (66 %)
Writing at 0x000a4000... (67 %)
Writing at 0x000a8000... (69 %)
Writing at 0x000ac000... (71 %)
Writing at 0x000b0000... (73 %)
Writing at 0x000b4000... (75 %)
Writing at 0x000b8000... (76 %)
Writing at 0x000bc000... (78 %)
Writing at 0x000c0000... (80 %)
Writing at 0x000c4000... (82 %)
Writing at 0x000c8000... (83 %)
Writing at 0x000cc000... (85 %)
Writing at 0x000d0000... (87 %)
Writing at 0x000d4000... (89 %)
Writing at 0x000d8000... (91 %)
Writing at 0x000dc000... (92 %)
Writing at 0x000e0000... (94 %)
Writing at 0x000e4000... (96 %)
Writing at 0x000e8000... (98 %)
Writing at 0x000ec000... (100 %)
Wrote 1637440 bytes (913975 compressed) at 0x00010000 in 86.0 seconds (effective 152.3 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 144...

Writing at 0x00008000... (100 %)
Wrote 3072 bytes (144 compressed) at 0x00008000 in 0.1 seconds (effective 234.1 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
Invalid library found in C:\Users\User\Documents\Arduino-esp32\hardware\espressif\arduino-esp32\libraries\AzureIoT: no headers files (.h) found in C:\Users\User\Documents\Arduino-esp32\hardware\espressif\arduino-esp32\libraries\AzureIoT
Invalid library found in C:\Users\User\Documents\Arduino-esp32\hardware\espressif\arduino-esp32\libraries\BLE: no headers files (.h) found in C:\Users\User\Documents\Arduino-esp32\hardware\espressif\arduino-esp32\libraries\BLE
Invalid library found in C:\Users\User\Documents\Arduino-esp32\hardware\espressif\arduino-esp32\libraries\AzureIoT: no headers files (.h) found in C:\Users\User\Documents\Arduino-esp32\hardware\espressif\arduino-esp32\libraries\AzureIoT
Invalid library found in C:\Users\User\Documents\Arduino-esp32\hardware\espressif\arduino-esp32\libraries\BLE: no headers files (.h) found in C:\Users\User\Documents\Arduino-esp32\hardware\espressif\arduino-esp32\libraries\BLE

Also, how do you totally clear the settings in the chip? I tried using the WIFI manager but when it came back up after flashing it was connecting to my SSID like it was prior to flashing.


#7

Choose esp32 dev module instead, you should have more options.


#8

Correct. That is what I’m choosing… See the screenshot above (very first bit before the log information).


#9

Ok, you should not have memory space issue with these settings.
Regarding wifimanager it is not currently supported with esp32. You have to set your credentials into user_config.h.


#10

I just noticed that in the code where it checks to see if it’s an ESP32 and used supplied credentials. This part doesn’t matter much to me.

Any thing you can think of to check to see why it panics?


#11

Try first with only zgatewayBT uncommented if you are interested by ble.


#12

Sure. I have tried this and have the same problem with panics. I have tried other example sketches and they work fine… no panics.


#13

You tried with only zgatewayBT only, esp32 dev module and minimal spiff, and you still get panic ?


#14

I just did an erase using ESP32 download tool and running just BT and it seems to be stable and broadcasting BT information. This is great. I need to get RF working and things will be good. I’m not sure if something got corrupted and the erase has helped fix it?


#15

It’s something to do with RF. I turned RF back on with BT and it’s back to panics.


#16

You are using v0.8 isn t it ?


#17

That’s correct. My RF receiver is not connected to the chip yet. Will that pose a problem?

Also, how do I correlate the BT value provided by OMG to the device? Is it supposed to match the BT MAC address?


#18

It could pose a problem, i never tried without the module.
The last part of the subject is the ble mac adress of the device indeed.


#19

Ok… I’m trying again with it hooked up. To make matters worse, the chip I have doesn’t have the pins labeled on the silk screen so I’m not certain where the GPIO pin is that I need to use…


#20

Can you tell me where RF_RECEIVER_PIN 13 // D13 on DOIT ESP32 is on this board?

Is it GPIO13 which is at 15?

I checked my receiver module and I’m getting 3.3v so power and ground are correct. Not sure about the rf receiver pin though.