Transmittimg message causes remote node to reboot

Hey Folks,

ISSUE:
When I transmit to the mesh using the python CLI the remote node restarts.

Info:
Both nodes are running firmware_version: “2.0.10.e09b12c-d” uploaded from web flasher.

They were added to node with QR code using the android app.
On the remote node I see this in the log when running meshtastic --reply --debug

DEBUG file:mesh_interface.py _handleFromRadio line:534 in mesh_interface.py _handleFromRadio() fromRadioBytes: b'@\x01'
DEBUG file:mesh_interface.py _handleFromRadio line:536 Received from radio: rebooted: true

After this I do see some info from the node but the message is not presented in app or, device on the CLI. Then the node promptly reboots.

The remote node can send and receive to the local node without rebooting.

There were some bug fixes related to spontaneous reboots since 2.0.10, so updating the firmware might already fix it.

Otherwise, can you post what you see on the remote node when running meshtastic –noproto when you transmit from the local node? The rebooted: true message is coming from the radio to inform the CLI it rebooted, it is not the cause of the reboot.

Since the remote node can send and it can be received correctly on the local node, are there any differences in hardware or settings between the two?


`WARNING file:mesh_interface.py _sendToRadio line:511 Not sending packet because protocol use is disabled by noProto
Connected to radio
WARNING file:mesh_interface.py _sendPacket line:389 Not sending packet because protocol use is disabled by noProto
Guru Meditation Error: Core  1 panic'ed (StoreProhibited). Exception was unhandled.

Core  1 register dump:
PC      : 0x400f6c75  PS      : 0x00060630  A0      : 0x800f6d28  A1      : 0x3ffd8620
A2      : 0x3ffdcbc0  A3      : 0x3ffeab84  A4      : 0x00000000  A5      : 0x3ffd90a4
A6      : 0x3ffd8660  A7      : 0x00000008  A8      : 0x800f6c72  A9      : 0x3ffd8600
A10     : 0x001b11b8  A11     : 0x3ffeab96  A12     : 0x000000a0  A13     : 0x3f404147
A14     : 0x00ff0000  A15     : 0xff000000  SAR     : 0x0000000a  EXCCAUSE: 0x0000001d
EXCVADDR: 0x00000000  LBEG    : 0x400869f5  LEND    : 0x400869fd  LCOUNT  : 0x00000027


Backtrace: 0x400f6c72:0x3ffd8620 0x400f6d25:0x3ffd8640 0x400f6d95:0x3ffd8690 0x400e3b8a:0x3ffd86b0 0x400e85a9:0x3ffd86f0 0x400e8665:0x3ffd8710 0x400e8681:0x3ffd8730 0x400e7e0d:0x3ffd8760 0x400d8de6:0x3ffd8780 0x400ff1d1:0x3ffd87a0 0x400e1aa0:0x3ffd87d0 0x401360bd:0x3ffd87f0




ELF file SHA256: deleted

E (5818) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_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:2
load:0x3fff0030,len:1184
load:0x40078000,len:13132
load:0x40080400,len:3036
entry 0x400805e4
E (807) esp_core_dump_flash: No core dump pF???????found!
E (807) esp_core_dump_flash: No core dump partition found!
[    12][D][esp32-hal-cpu.c:244] setCpuFrequencyMhz(): PLL: 480 / 2 = 240 Mhz, APB: 80000000 Hz
[   463][I][esp32-hal-psram.c:96] psramInit(): PSRAM enabled
WARNING file:mesh_interface.py _sendToRadio line:511 Not sending packet because protocol use is disabled by noProto
??:??:??```

The error disappeared after I upgraded the destination node to 12.1.3. Hope this helps someone else. Thanks for all help. @GUVWAF