I am trying to update the latest firmware V3.1.4.1, and I get the following error when I receive a beacon packet:
[13:16:23]Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
[13:16:23]
[13:16:23]Core 1 register dump:
[13:16:23]PC : 0x400e86eb PS : 0x00060430 A0 : 0x800e8721 A1 : 0x3ffce4a0
[13:16:23]A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000001 A5 : 0x3ffdd812
[13:16:23]A6 : 0x00000029 A7 : 0x00000000 A8 : 0x00000080 A9 : 0x00000000
[13:16:23]A10 : 0xffffff80 A11 : 0xdf77eee9 A12 : 0xdf77eee9 A13 : 0x3ffc506c
[13:16:23]A14 : 0x00000015 A15 : 0x3ffdd7ec SAR : 0x0000001d EXCCAUSE: 0x0000001c
[13:16:23]EXCVADDR: 0x00000020 LBEG : 0x40091ea1 LEND : 0x40091ec3 LCOUNT : 0xffffffff
[13:16:23]
[13:16:23]
[13:16:23]Backtrace: 0x400e86e8:0x3ffce4a0 0x400e871e:0x3ffce4c0 0x400dd601:0x3ffce540 0x400dce4e:0x3ffce560 0x400d32ee:0x3ffce5f0 0x400fcd81:0x3ffce650
[13:16:23]
[13:16:23]
[13:16:23]
[13:16:23]
[13:16:23]ELF file SHA256: 3a68daa483688803
[13:16:23]
[13:16:23]Rebooting...
[13:16:23]ets Jun 8 2016 00:22:57
[13:16:23]
[13:16:23]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[13:16:23]configsip: 188777542, SPIWP:0xee
[13:16:23]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[13:16:23]mode:DIO, clock div:2
[13:16:23]load:0x3fff0030,len:1184
[13:16:23]load:0x40078000,len:13232
[13:16:23]load:0x40080400,len:3028
[13:16:23]entry 0x400805e4
[13:16:26]
[13:16:26]Starting Station: DECODER Version: 2025-11-08
[13:16:26](DigiEcoMode: OFF)
[13:16:33]
[13:16:33]Not connected to WiFi! Starting Auto AP
[13:16:34]
[13:16:34]Not connected to WiFi! Starting Auto AP
[13:16:36]TNC server started successfully
[13:16:36]mDNS Host: igate-DECODER.local
I've tried the upgrade, and the fresh install. This also happens for v3.1.2, v3.1.3, and 3.1.4. If I install 3.0.1 it receives packets with no issues. However when I connect via Network KISS TNC from PinPoint APRS, It only decodes the Callsign and not the Callsign & SSID. So instead of WA0DE-10, I get WA0DE.
Thank you very much!
Michael Smith
KF0PAY - ARES of Douglas & Elbert County
I have a LilyGo T3_V1.6.1 20210104.
I am trying to update the latest firmware V3.1.4.1, and I get the following error when I receive a beacon packet:
[13:16:23]Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
[13:16:23]
[13:16:23]Core 1 register dump:
[13:16:23]PC : 0x400e86eb PS : 0x00060430 A0 : 0x800e8721 A1 : 0x3ffce4a0
[13:16:23]A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000001 A5 : 0x3ffdd812
[13:16:23]A6 : 0x00000029 A7 : 0x00000000 A8 : 0x00000080 A9 : 0x00000000
[13:16:23]A10 : 0xffffff80 A11 : 0xdf77eee9 A12 : 0xdf77eee9 A13 : 0x3ffc506c
[13:16:23]A14 : 0x00000015 A15 : 0x3ffdd7ec SAR : 0x0000001d EXCCAUSE: 0x0000001c
[13:16:23]EXCVADDR: 0x00000020 LBEG : 0x40091ea1 LEND : 0x40091ec3 LCOUNT : 0xffffffff
[13:16:23]
[13:16:23]
[13:16:23]Backtrace: 0x400e86e8:0x3ffce4a0 0x400e871e:0x3ffce4c0 0x400dd601:0x3ffce540 0x400dce4e:0x3ffce560 0x400d32ee:0x3ffce5f0 0x400fcd81:0x3ffce650
[13:16:23]
[13:16:23]
[13:16:23]
[13:16:23]
[13:16:23]ELF file SHA256: 3a68daa483688803
[13:16:23]
[13:16:23]Rebooting...
[13:16:23]ets Jun 8 2016 00:22:57
[13:16:23]
[13:16:23]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[13:16:23]configsip: 188777542, SPIWP:0xee
[13:16:23]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[13:16:23]mode:DIO, clock div:2
[13:16:23]load:0x3fff0030,len:1184
[13:16:23]load:0x40078000,len:13232
[13:16:23]load:0x40080400,len:3028
[13:16:23]entry 0x400805e4
[13:16:26]
[13:16:26]Starting Station: DECODER Version: 2025-11-08
[13:16:26](DigiEcoMode: OFF)
[13:16:33]
[13:16:33]Not connected to WiFi! Starting Auto AP
[13:16:34]
[13:16:34]Not connected to WiFi! Starting Auto AP
[13:16:36]TNC server started successfully
[13:16:36]mDNS Host: igate-DECODER.local
I've tried the upgrade, and the fresh install. This also happens for v3.1.2, v3.1.3, and 3.1.4. If I install 3.0.1 it receives packets with no issues. However when I connect via Network KISS TNC from PinPoint APRS, It only decodes the Callsign and not the Callsign & SSID. So instead of WA0DE-10, I get WA0DE.
Thank you very much!
Michael Smith
KF0PAY - ARES of Douglas & Elbert County
<!-- github-sync-id:3631097252 -->
you should have a valid callsign (Tactical Callsigns are not validated at this moment and should be implemented in the future)
this could be blocking all the decoding and connection to the TNC
please test it with a valid callsign and see if this solves all
Hi,
it seems you are experiencing two errors mixed.
1) you should have a valid callsign (Tactical Callsigns are not validated at this moment and should be implemented in the future)
2) this could be blocking all the decoding and connection to the TNC
please test it with a valid callsign and see if this solves all
<!-- github-comment-id:3541379141 -->
I have a similar problem.
With version 3.0, the ‘panic’ error disappears.
Tomorrow I will post the output at the time of the error, to see if that gives us more clues.
In my case, I have configured my call sign, but I am still getting the error.
Best regards.
Hi,
I have a similar problem.
With version 3.0, the ‘panic’ error disappears.
Tomorrow I will post the output at the time of the error, to see if that gives us more clues.
In my case, I have configured my call sign, but I am still getting the error.
Best regards.
<!-- github-comment-id:3554843723 -->
I've tested with a valid callsign and still have the same issue. If I connect to a WAP, then it doesn't reboot when it receives a packet. And it still doesn't send anything to PinPoint APRS when connected as a Serial TNC.
I've tested with a valid callsign and still have the same issue. If I connect to a WAP, then it doesn't reboot when it receives a packet. And it still doesn't send anything to PinPoint APRS when connected as a Serial TNC.
<!-- github-comment-id:3555164922 -->
you should have a valid callsign (Tactical Callsigns are not validated at this moment and should be implemented in the future)
this could be blocking all the decoding and connection to the TNC
please test it with a valid callsign and see if this solves all
I'm confused - what is invalid about his callsign? From his own comment
So instead of WA0DE-10, I get WA0DE
I see WA0DE and WA0DE-10, both valid calls, neither appear tactical.
Can you explain more?
Cheers and 73 - Jon N7UV
> 1. you should have a valid callsign (Tactical Callsigns are not validated at this moment and should be implemented in the future)
> 2. this could be blocking all the decoding and connection to the TNC
>
> please test it with a valid callsign and see if this solves all
I'm confused - what is invalid about his callsign? From his own comment
> So instead of WA0DE-10, I get WA0DE
I see WA0DE and WA0DE-10, both valid calls, neither appear tactical.
Can you explain more?
Cheers and 73 - Jon N7UV
<!-- github-comment-id:3632914265 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I have a LilyGo T3_V1.6.1 20210104.
I am trying to update the latest firmware V3.1.4.1, and I get the following error when I receive a beacon packet:
[13:16:23]Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
[13:16:23]
[13:16:23]Core 1 register dump:
[13:16:23]PC : 0x400e86eb PS : 0x00060430 A0 : 0x800e8721 A1 : 0x3ffce4a0
[13:16:23]A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000001 A5 : 0x3ffdd812
[13:16:23]A6 : 0x00000029 A7 : 0x00000000 A8 : 0x00000080 A9 : 0x00000000
[13:16:23]A10 : 0xffffff80 A11 : 0xdf77eee9 A12 : 0xdf77eee9 A13 : 0x3ffc506c
[13:16:23]A14 : 0x00000015 A15 : 0x3ffdd7ec SAR : 0x0000001d EXCCAUSE: 0x0000001c
[13:16:23]EXCVADDR: 0x00000020 LBEG : 0x40091ea1 LEND : 0x40091ec3 LCOUNT : 0xffffffff
[13:16:23]
[13:16:23]
[13:16:23]Backtrace: 0x400e86e8:0x3ffce4a0 0x400e871e:0x3ffce4c0 0x400dd601:0x3ffce540 0x400dce4e:0x3ffce560 0x400d32ee:0x3ffce5f0 0x400fcd81:0x3ffce650
[13:16:23]
[13:16:23]
[13:16:23]
[13:16:23]
[13:16:23]ELF file SHA256: 3a68daa483688803
[13:16:23]
[13:16:23]Rebooting...
[13:16:23]ets Jun 8 2016 00:22:57
[13:16:23]
[13:16:23]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[13:16:23]configsip: 188777542, SPIWP:0xee
[13:16:23]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[13:16:23]mode:DIO, clock div:2
[13:16:23]load:0x3fff0030,len:1184
[13:16:23]load:0x40078000,len:13232
[13:16:23]load:0x40080400,len:3028
[13:16:23]entry 0x400805e4
[13:16:26]
[13:16:26]Starting Station: DECODER Version: 2025-11-08
[13:16:26](DigiEcoMode: OFF)
[13:16:33]
[13:16:33]Not connected to WiFi! Starting Auto AP
[13:16:34]
[13:16:34]Not connected to WiFi! Starting Auto AP
[13:16:36]TNC server started successfully
[13:16:36]mDNS Host: igate-DECODER.local
I've tried the upgrade, and the fresh install. This also happens for v3.1.2, v3.1.3, and 3.1.4. If I install 3.0.1 it receives packets with no issues. However when I connect via Network KISS TNC from PinPoint APRS, It only decodes the Callsign and not the Callsign & SSID. So instead of WA0DE-10, I get WA0DE.
Thank you very much!
Michael Smith
KF0PAY - ARES of Douglas & Elbert County
Hi,
it seems you are experiencing two errors mixed.
please test it with a valid callsign and see if this solves all
Hi,
I have a similar problem.
With version 3.0, the ‘panic’ error disappears.
Tomorrow I will post the output at the time of the error, to see if that gives us more clues.
In my case, I have configured my call sign, but I am still getting the error.
Best regards.
I've tested with a valid callsign and still have the same issue. If I connect to a WAP, then it doesn't reboot when it receives a packet. And it still doesn't send anything to PinPoint APRS when connected as a Serial TNC.
I'm confused - what is invalid about his callsign? From his own comment
I see WA0DE and WA0DE-10, both valid calls, neither appear tactical.
Can you explain more?
Cheers and 73 - Jon N7UV