Reboot Loop when enabling TX functionality #296
Comments
|
looks like something is taking to long and the wathdog is restarting the esp. can you post your exact configuration? please remove your personal data (callsign, wifi settings, aprs-is passcode) |
|
Here we are... { |
|
for me the LoRa-TX is working like a charm!
…--
Disclaimer: May be opened and read by the NSA, CIA, GCHQ, KGB, BND, and
whoever else it may NOT concern.
Am Sa., 20. Mai 2023 um 08:19 Uhr schrieb Mane76 ***@***.***>:
Here we are...
when I change the "tx_enable" in section "lora" to "false" everything is
working fine.
The frequency 433.781 is the correction of the offset of "my" module to
the "real" RX/TX frequency.
As I see in the preview the formatting gets lost.
{
"callsign": "xxx",
"network": {
"DHCP": true,
"static": {
"ip": "192.168.0.100",
"subnet": "255.255.255.0",
"gateway": "192.168.0.1",
"dns1": "192.168.0.1",
"dns2": "192.168.0.2"
},
"hostname": {
"overwrite": false,
"name": "xxx"
}
},
"wifi": {
"active": true,
"AP": [
{
"SSID": "xxx",
"password": "xxx"
}
]
},
"beacon": {
"message": "LoRa iGate v23.17.1m",
"position": {
"latitude": xxx,
"longitude": xxx
},
"use_gps": false,
"timeout": 15
},
"aprs_is": {
"active": true,
"passcode": "xxx",
"server": "germany.aprs2.net",
"port": 14580,
"filter": "r/xxx/xxx/50 -t/tpo"
},
"digi": {
"active": false,
"beacon": false
},
"lora": {
"frequency_rx": 433781000,
"gain_rx": 0,
"frequency_tx": 433781000,
"power": 20,
"spreading_factor": 12,
"signal_bandwidth": 125000,
"coding_rate4": 5,
"tx_enable": true
},
"display": {
"always_on": false,
"timeout": 10,
"overwrite_pin": 0,
"turn180": true
},
"ftp": {
"active": false,
"user": [
{
"name": "ftp",
"password": "ftp"
}
]
},
"mqtt": {
"active": false,
"server": "",
"port": 1883,
"name": "",
"password": "",
"topic": "LoraAPRS/Data",
"will_active": false,
"will_topic": "LoraAPRS/State",
"will_message": "offline",
"birth_message": "online"
},
"syslog": {
"active": true,
"server": "xxx",
"port": 514
},
"ntp_server": "pool.ntp.org"
}
—
Reply to this email directly, view it on GitHub
<#296 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ6LUOCZTPTRA6PVWALXXTXHBO6HANCNFSM6AAAAAAYGFLU7Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
I have similar issue maybe with same board? Backtrace only when TX enabled, in RX mode, ok: `[INFO][WiFiEvent] WiFi IPv4: 192.168.88.31 assert failed: heap_caps_free heap_caps.c:360 (heap != NULL && "free() target pointer is outside heap areas") Backtrace: 0x40083d95:0x3ffb1f90 0x4008e151:0x3ffb1fb0 0x40093ead:0x3ffb1fd0 0x40084282:0x3ffb2100 0x40093edd:0x3ffb2120 0x40166655:0x3ffb2140 0x400d7cf9:0x3ffb2160 0x400d8463:0x3ffb2180 0x40182062:0x3ffb2230 0x400d3302:0x3ffb2250 0x400f255d:0x3ffb2290 ELF file SHA256: a003e5a76581958a Rebooting... rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) |
|
I have the same issue with a LoRa32 board. |
|
issue was reproduced, fix is in: #303 |
|
reboot loop is solved BUT when "tx_enable": true no RX of tracker is possible when "tx_enable": true everything which passes the filter set in section aprs-is is TXd '73, Mane |
|
@Mane76 I just tried to reproduce your issue, but couldn't. can you please retry again (delete flash first, than upload config and than firmware upload with monitoring)? |
|
@peterus, no, same frequencies for RX and TX. See serial output attached, 1st boot shows some corrupntess, then it reboots and starts up, independent if tx_enable" is true or false. Reconnecting to /dev/ttyACM0 ... Connected! abort() was called at PC 0x400fb184 on core 0 Backtrace: 0x40083c1d:0x3ffbeccc |<-CORRUPTED ELF file SHA256: d42c675df63b5cd3 Rebooting... rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) |
|
@Mane76 can you post your config again that i can try to reproduce your issue. the first boot looks very strange to me. in the second boot i can not see that something should be sent. |
|
{ |
|
I am very sorry, but I can't reproduce your issue here on my system. this is my config: please use this steps for further debugging:
in the log, you will get the first boot (board finding) and than the second boot (normal operation), please post both bootups here. |
|
By checking your config I found that you have in digi section the lines "active" and "beacon" set to true. Debug I can provide tomorrow. |
|
@Mane76 good found! have not seen this difference! Will need to check this, but i think most probably this is the issue 👍 will check tomorrow 👍 |
|
I see the same here. The reboot problem is fixed but the RX doesnt work if TX is enabled. Digi section "active" and "beacon" are set to false. |
|
i refactored the RadioLib Task, added the newest version of RadioLib and now it is working as expected (on my side at least). please try the latest master again and give feedback! thanks! changes: #305 |
|
Still the same on my side: If TX is enabled, RX seems to be disabled. |
|
@ohanssen did you follow this steps: #296 (comment) |
|
I too had the "Reboot Loop when enabling TX functionality" problem. |
|
@beppelpo can you check if RX is still possible when TX is active? thanks! |
unfortunately same behaviour. When tx_enable: true NO RX is possible, wenn set to false RX is possible. I also checked the serial output in debug environment, no difference if tx_enable is set to true or false. |
Unfortunately there is no LoRa station in the area, I was hoping to spread this technique among local OMs. But I have another identical board with the TinyGS console. Then I try to install this iGate and see if the two devices listen to each other. I'll keep you posted on developments. Good evening. |
|
Phu... slowly I am giving up on this topic as on my side everything is working correctly and I have no idea anymore. So...
|
|
Well, I've installed an identical copy of iGate on another identical LILYGO card. I only changed id on the second one (i3lpo-9) . Both receive and transmit (tx true), in the video made on -9 then you see the msg received from -10. Only question that "Type: error.data ".... Uploading video5771553211001343426.mp4… |
|
@beppelpo: can you post the logs from the serial monitor too? to make sure? can you activate the beacon mode ( |
|
Just tested, same behaviour. See pic from device attached. |
|
send_on_hf: true in both tabs, I'll see if I can send the log, I'm not very practical! |
|
@Mane76 I think your issue is now at this point something different than the original issue described here. can you comment all lines which are responsible for the watchdog? I think your esp needs more time to connect to your wifi and than the watchdog is kicking in. |
|
commented watchdog lines, unfortunately no effect on RX problem |
|
I don't know if this img is enough, I can't activate the output to file. I'm sorry but I'm really a sucker with VSCode. Beppe i3lpo |
|
sucker = duffer |
Describe the bug
When enabling TX functionality of iGate the code compiles, but the esp32 is in an reboot loop. By changing the line lora_tx_enable to false everything works fine as before
To Reproduce
Steps to reproduce the behavior:
Expected behavior
start as usual
Screenshots
Rebooting...
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, 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:13192
load:0x40080400,len:3028
entry 0x400805e4
[INFO][Main] LoRa APRS iGate by OE5BPA (Peter Buchegger)
[INFO][Main] Version: 23.06.0
[INFO][Main] Board TTGO_LORA32_V2 loaded.
[INFO][Main] Will start watchdog now...
[INFO][TaskManager] will setup all tasks...
[DEBUG][TaskManager] call setup for WifiTask
[INFO][WiFiEvent] WiFi Started
[DEBUG][WifiTask] Looking for AP: xxxx
[DEBUG][TaskManager] call setup for DisplayTask
[DEBUG][TaskManager] call setup for RadiolibTask
[DEBUG][TaskManager] call setup for RouterTask
[DEBUG][TaskManager] call setup for BeaconTask
[DEBUG][TaskManager] call setup for OTATask
[DEBUG][TaskManager] call setup for NTPTask
[DEBUG][TaskManager] call setup for AprsIsTask
[INFO][Main] setup done...
E (22408) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (22408) task_wdt: - loopTask (CPU 1)
E (22408) task_wdt: Tasks currently running:
E (22408) task_wdt: CPU 0: IDLE
E (22408) task_wdt: CPU 1: IDLE
E (22408) task_wdt: Aborting.
abort() was called at PC 0x400fb130 on core 0
Backtrace: 0x40083c1d:0x3ffbeccc |<-CORRUPTED
ELF file SHA256: d0eeed056324df7f
Rebooting...
Desktop (please complete the following information):
Board name:
TTGO LORA32
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: