richonguzman/LoRa_APRS_Tracker

reboot loop

Opened this issue · 10 comments

dg1kwa commented

What happen?

--- Terminal on COM6 | 115200 8-N-1
--- Available filters and text transformations: colorize, debug, default, direct, esp32_exception_decoder, hexlify, log2file, nocontrol, printable, send_on_enter, time
--- More details at https://bit.ly/pio-monitor-filters
--- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (Sv: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:13232
load:0x40080400,len:3028
entry 0x400805e4
[INFO][AXP192] init done!
[INFO][Main] RichonGuzman (CA2RXU) --> LoRa APRS Tracker/Station
[INFO][Main] Version: 2024.06.04
[INFO][LoRa] Initializing SX127X ...
[INFO][LoRa] LoRa init done!
Guru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout on CPU1).

Core 1 register dump:
PC : 0x4008672a PS : 0x00050035 A0 : 0x4023ba9e A1 : 0x3ffbf82c
A2 : 0x00000000 A3 : 0x00000009 A4 : 0x00000016 A5 : 0x3ffbf7bc
A6 : 0x00000000 A7 : 0x3ffbdf04 A8 : 0x00000000 A9 : 0x00000000
A10 : 0x3ffbdf00 A11 : 0x00000000 A12 : 0x00000001 A13 : 0x3ffbdf00
A14 : 0x00000003 A15 : 0x00060023 SAR : 0x00000000 EXCCAUSE: 0x00000006
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000
Core 1 was running in ISR context:
EPC1 : 0x401252eb EPC2 : 0x00000000 EPC3 : 0x00000000 EPC4 : 0x00000000

Backtrace: 0x40086727:0x3ffbf82c |<-CORRUPTED

Core 0 register dump:
PC : 0x4023ba9e PS : 0x00060f35 A0 : 0x80123d74 A1 : 0x3ffbb1d0
A2 : 0x00000000 A3 : 0x40092940 A4 : 0x00060820 A5 : 0x3ffcf4d0
A6 : 0x007bf848 A7 : 0x003fffff A8 : 0x8012384e A9 : 0x3ffbb1a0
A10 : 0x00000000 A11 : 0x80000001 A12 : 0x8009978c A13 : 0x3ffbb0d0
A14 : 0x00000003 A15 : 0x00060023 SAR : 0x0000001a EXCCAUSE: 0x00000006
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

Backtrace: 0x4023ba9b:0x3ffbb1d0 0x40123d71:0x3ffbb1f0 0x400971d4:0x3ffbb210
#0 0x4023ba9b in cpu_ll_waiti at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/hal/esp32/include/hal/cpu_ll.h:183
(inlined by) esp_pm_impl_waiti at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp_pm/pm_impl.c:853
#1 0x40123d71 in esp_vApplicationIdleHook at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp_system/freertos_hooks.c:63
#2 0x400971d4 in prvIdleTask at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/tasks.c:4099

richonguzman commented

Hi

I need lots of info:
Which board?
Which env selected?

Firmware uploaded?
Tracker_conf.json edited?
Filesystem uploaded?

dg1kwa commented
richonguzman commented

sorry the Picture didn't load as needed

but you can know the "real" board to use by reading the text near the SMA antenna.

its V1.1 or V1.0 or V1.2 but all of them need to be selected specifically or they will fail

PS: usually the LoRa fail error in this case is because it wasn't loaded the filesystem too

dg1kwa commented
OK2MOP commented

Double check you are building for ttgo-t-beam-v1 (if you do not have also SX126x chip on board) not the default one, (which is ttgo-t-beam-v1_2), and that the configuration file is correct and you have uploaded it.

I was fighting with boot loops using older version of config file for two days, compiling different versions of firmware (add to that the present issue of aprs.fi with the normal compressed packets - mic-E packets work - when I returned back to old firmware and settings) and in the end I just copied all the settings to new configuration file to make it work.

In my case the probable culprit was the lora section, in configuration file, which was originally an object with values in JSON, but in present version is an array of objects.

richonguzman commented

Double check you are building for ttgo-t-beam-v1 (if you do not have also SX126x chip on board) not the default one, (which is ttgo-t-beam-v1_2), and that the configuration file is correct and you have uploaded it.

I was fighting with boot loops using older version of config file for two days, compiling different versions of firmware (add to that the present issue of aprs.fi with the normal compressed packets - mic-E packets work - when I returned back to old firmware and settings) and in the end I just copied all the settings to new configuration file to make it work.

In my case the probable culprit was the lora section, in configuration file, which was originally an object with values in JSON, but in present version is an array of objects.

the way its saved on the json file does not change the way it works

from the start to use Tracker Firmware there is a three process way to make it work:

1)select the environment for the board you will use
2)upload firmware (the program the tracker runs)
3)upload filetsystem (the json you edited with your calling and preferences)

dg1kwa commented
RadioMan57 commented

Reboot loop also here, due to a home-made syntax error in tracker_config.json.
There was an extra comma in the bme section. VSCode flagged it.
Error corrected, problem gone.
73, Markus HB9BRJ

  • 👍1
richonguzman commented

has @dg1kwa solved his issue?

dg1kwa commented
  • 👍1