Closed htdvisser closed 6 years ago
I got the same LORA: UART TIMEOUT
as in @jurrienjurrien's previous comment, but then already on first boot. However, in my case it continues operation, maybe as in my case it already was configured when using my own firmware (then based on the February 14th firmware with additional debugging enabled and using a 921600 baud rate for the logging).
This is using the firmware from #19. (So: no programmer. Instead: powered down, replaced the firmware on the SD card without any modifications, and powered up without clearing the serial flash):
Firmware name: AmazingAckermann, type: 0, version: 1.0.1, commit: 91648b7e, timestamp: 1520959697
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Mar 13 2018 16:49:17
...
LORA: Changing state from 4 to 6
LORA: Starting reconfiguration
LORA: version: 01
LORA: UART TIMEOUT
LORA: Configuration succeeded
LORA: Starting operation
LORA: Changing state from 6 to 8
MON: SYS Stack size: 2869
MON: heap usage: 151KB (233KB), free: 188KB
LORA: Changing state from 8 to 5
LORA: GOING ASYNC
...
It's accepting and forwarding uplinks just fine.
Hi, I am observing a similar behaviour as @jurrienjurrien after applying the #19 firmware. The gateway is apparently able to maintain a stable connection now (for more than an hour) but will stop accepting uplink messages after 10-20 minutes.
Previous state was firmware 1.0 reboot reason 0x13
Installed the new firmware from #19. (So: no programmer. Instead: powered down, replaced the firmware on the SD card without any modifications, and powered up without clearing the serial flash):
Started up, did get several messages LORA: UART Timeout. on the lora module the green led was on. gateway didn't work. removed sd, tried several times after reboot no suc6.
powered down: decided to push the lora module a very little bit further into the connector. powered up and voila, No lora : Uart Timeout messages anymore. After a few minutes the gw was up and running now for 2 hours. and still accepting uplink messages
Just to reaffirm,
After applying the #19 firmware and rebooting the gateway this morning, I have enjoyed at least 10 hours of (still) uninterrupted gateway connection BUT the gateway will stop uplinking messages after a few messages (i.e. 7 minutes or so).
Gateway information
@Reiniervdl
On the working LoRa module the SX1301 chip is running hot (69C), the microchip PIC is 52C. This is normal according to @nestorayuso. On the defective LoRa module the chip temperatures are much lower.
I don't think that by looking at the temperature you can tell if a module is defective or not. My LoRA module was also cold, but that was simply because it stops accepting commands and stop sending pkts and getting into reboots. Now that the firmware fixes are working for me the module is also hotter, the more pkts it's sent in a row without reboots in between the hotter it gets.
I have also a gateway that reboots 2 times a day. I will try the latest test/beta firmware. Tnx
My feedback with regard to the 1.0.2 firmware: it is slightly more prone to reboot than the 1.0.1. firmware (but it will recover eventually), but in my case it too will stop uplinking messages after a while, making the gateway still unusable.
Gateway information
How does the gateway uses date and time, I know it queries ntp servers to keep uptodate, but I cannot find any date or time printed in any of the log messages. Losing connection via wifi and mqtt can be wrong date/time related (renewal of keying) maybe it's an idea to log lines with date/time in them? (according to gateway)
Hmm although I see some logs where date and time is printed... Maybe I''m not uptodate ;-)
@cyberjunky
I see some logs where date and time is printed...
For my logs, I use a Raspberry Pi to capture and enhance the serial output, and send alerts through Telegram or Slack.
Alternatively, like when using PlatformIO: LOG="ttn-gateway-`date +'%Y%m%d-%H%M%S'`.log"; pio serialports monitor --raw -b 115200 | while read l; do echo "[`date +'%F %T'`] $l" | tee -a $LOG; done
Aha, so time is coming from pi instead of gw...
Op 16 mrt. 2018 19:28 schreef "Arjan" notifications@github.com:
@cyberjunky https://github.com/cyberjunky
I see some logs where date and time is printed...
For my logs, I use a Raspberry Pi to capture and enhance the serial output, and send alerts through Telegram or Slack https://github.com/avbentem/raspi-uart-monitor.
Alternatively, like when using PlatformIO https://platformio.org/: LOG="ttn-gateway-
date +'%Y%m%d-%H%M%S'
.log"; pio serialports monitor --raw -b 115200 | while read l; do echo "[date +'%F %T'
] $l" | tee -a $LOG; done— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/TheThingsProducts/gateway/issues/1#issuecomment-373804496, or mute the thread https://github.com/notifications/unsubscribe-auth/AFMd-U_312RgHf8OK7UPZ9QD688X81KOks5tfARCgaJpZM4R0NRp .
I just flashed the latest beta firmware with the SD card (I do not have a programmer). The update went fine, but unfortunately it had no effect at all for the bootloop issue.
Edit: I left it booting for a while, and after approx. 2 hours, it became stable - it has been up and running for an hour now! Progress after all...
Edit2: after 24 hours of stability, the gateway rebooted (as expected) - but subsequently ended up in the eternal reboot loop again...
Gateway information
Version Info |
-- | --
Hardware: | v1
Bootloader: | r1-7167873a (2017-06-02T13:48:18Z)
Firmware: | v1.0.2-475aef56 (2018-03-15T09:43:08Z)
|
Network |
Uptime: | 26
Connected: | true
Interface: | Ethernet
Wifi SSID: | Things-Gateway-001EC03AF660
|
Configuration |
Activation locked: | true
Config correct: | true
Region: | EU_863_870
Gateway Card: | 868Mhz
|
Packet forwarding |
Broker connection: | false
Packets up: | 0
Packets down: | 0
|
Miscellaneous |
External storage: | false
I was hoping v1.0.2. would fix the rebooting on my gateway, but i don't see any improvement
Firmware name: AmazingAckermann, type: 0, version: 1.0.2, commit: 475aef56, timestamp: 1521108973
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Mar 15 2018 10:16:33
The gateway gets an IP-address, in the packet capture on the router i see it fetching the right date/time through NTP it reaches a third blue LED which flickers and then it reboots after one or two of these lines
SNTP: State change from 0 to 0
Wouldn't mind bringing in the gateway to see if updating the bootloader would help, i work in Amsterdam.
Updated my Gateway to 1.0.1 via USB and then FOTA to 1.0.2. Still a reboot loop. Gateway Module is a LG8271 and Socket labeled 1636D4.
Firmware name: AmazingAckermann, type: 0, version: 1.0.2, commit: 475aef56, tim3
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Mar 15 2018 10:16:33
Reboot reason: 0x10
...
CNFG: Load online user config state change to 7
CNFG: Configuring LoRa module
LORA: Changing state from 2 to 4
LORA: Starting reconfiguration
LORA: version: 01
LORA: Configuration failed, retry
LORA: Starting reconfiguration
LORA: version: 01
LORA: Configuration failed, retry
LORA: Starting reconfiguration
MON: SYS Stack size: 2833
MON: heap usage: 151KB (233KB), free: 188KB
LORA: version: 01
LORA: Configuration failed, retry
LORA: RESET MODULE
LORA: ChaSNTP: State change from 0 to 0
SNTP: State change from 0 to 0
Can confirm reboot is still an issue with beta firmware (uploaded via microsd card)
@egarl004 please provide the exact version and commit so that we know what version you're talking about (you can find that in the logs or using ttnctl gateways status <GatewayID>
).
Logs would also be very helpful
@htdvisser A little new at this. Is there a way I can get access to the logs without a serial interface - or do you have a procedure? I've only attempted to load new firmware via sd card. (maybe a future suggestion would be to dump the logs to the sd card so we can easily get them to you?)
The TTN gateway, previously DOA, is alive and running for 12 hrs now, receiving packets successfully. Downloaded firmware 1.0.3 on SD card, and left the unit connected while it was rebooting every 45 seconds (with firmware 1.0.1 installed previously). It either updated firmware from SD or got an on-line update, but it is now stable and working with FW 1.0.3
Hello, is there anyone working on this issue? So far I haven't seen any helpful info from the folks working at TTN. This is quite a bad situation, as some customers are literally left with 300€ bricks.
There were even at least two users (@machiavello & @beamzer) offering to bring their GWs to the TTN offices in Amsterdam for investigation. We would do the same with ours but are unfortunately based in south Germany.
It seems to me, that some lucky users got working GWs. Based on this, I would like to ask:
Thanks a lot in advance! Cheers!
@skaldo Have you read the latest posts and tried firmware update 1.03?
Thanks @ReiniervdL, I've overseen your very last post somehow. Will try it next week as soon as I get access to the GW.
Looking at the commits on the beta branch (1.0.3), the feature/fixes_lora_module_communication
has been merged into it. But as you commented, the GW was still stuck in the reboot loop when you used the FW built from that branch.. :worried:
It would be nice if someone from TTN would let us know in case that there is a release that could possibly fix the reboot loop issue. I would be very happy to help with testing and share the logs here.
I am sorry to report that the 1.0.3 firmware also results in the gateway stopping to forward traffic after 10 minutes or so. The connection with the network will remain stable (no reboots in at least 7 hours), but it will simply not perform its primary purpose: relay LoRa traffic.
I am starting to feel that we are dealing with a range of issues (with multiple causes), the firmware patches are only solving a subset of.
Gateway information
I'm not personally involved with the firmware development, so I may not have the most up-to-date information, but here's what I know:
@mrjdomingus: Correct, there seem to be multiple, unrelated issues. The gateway's way of dealing with any unexpected issues is to reboot, so we really need to see some logs in order to track down the cause.
@egarl004: I'm afraid the only way to get the logs is indeed the serial method. I have suggested the SD card solution several times, but apparently the team didn't see the value in that. I'll ask again.
@skaldo: Thanks for offering your help. The 1.0.3 firmware that is in the beta
branch should fix the reboots that are caused by flaky LoRa Module communication. However, it seems that the gateway also still has some difficulties with MQTT (issue #21) and SNTP (issue #24). If you could get the logs from when your gateway reboots, that would be very helpful to the team. Please look through the list of issues to see where they fit.
It seems there's no download for specifically 1.0.3 for use on an SD card. But today the latest "beta channel" on https://github.com/TheThingsProducts/gateway/tree/master/firmware#installation is indeed 1.0.3.
This seems to install fine for me but I only upgraded a few minutes ago.
Earlier today, I had problems upgrading from 1.0.1 (running on an SD card) to the latest beta. Though obsolete now, it was interesting to see that removing the SD card got me 1.0.2 without seeing anything being dowloaded. So I assume it already downloaded that earlier, but then still used the older firmware from the SD card? I did NOT have "Automatically update gateway" nor "Beta Updates" enabled in TTN Console, so I guess that's why 1.0.2 was waiting, not 1.0.3.
Just in case it helps, this version 1.0.2 gave me the reboot loop again, which I did not have in 1.0.1:
LORA: Starting reconfiguration
MON: SYS Stack size: 2869
MON: heap usage: 154KB (234KB), free: 185KB
LORA: version: 01
LORA: Configuration failed, retry
LORA: RESET MODULE
So:
1.0.1 worked fine for me, though it often logged LORA: UART TIMEOUT
or LORA: UART WRITE ERROR!
, and on one or two occasions stopped forwarding packets. It also still needed me to manually reboot every now and then, to solve a lost network connection; #8.
1.0.2 gives me reboot loops. (LoRa module LG8271
, with on its bottom side: LG8501601782
, LG-X271
, REV: C
. Connector says 1635D4
.)
1.0.3 only tested for a few minutes now. Just like with 1.0.1, this actually logs an error during configuration, but maybe the existing configuration is fine as it still continues:
LORA: Starting reconfiguration
LORA: version: 01
LORA: UART TIMEOUT
LORA: Configuration succeeded
LORA: Starting operation
Yeah 1.0.3 is the same as develop branch, I run it for some days now (with bootloader v2), and it seems to be able to reach an uptime of 86400 sec, which is the hardcoded 24 hours reboot cycle.
Version Info | |
---|---|
Hardware: | v1 |
Bootloader: | r2-c463e87e (2018-02-23T14:42:40Z) |
Firmware: | v1.0.3-2c56ce09 (2018-03-22T12:02:04Z) |
But it has issues forwarding packets as if it doesn't connect to the cloud correctly, it says it has, but see no data.
@cyberjunky: If you are able to see that the gateway is connected on you console, that means that it is sending status packets properly. Do you have a device nearby sending uplinks?
@KrishnaIyer I have a kiss-lora and a ttn-uno device with dust-sensor on my desk sending packets 24/7, I restarted them, the gw is online, but packet count doesn't go up in console gw stats. Last Seen 12 seconds ago Received Messages 71305 Transmitted Messages 62 Uno stopped to upload packets 5 hours ago, rebooting gw and device didn't seem to help. Status 5 hours ago Frames up 6774 Frames down 0 I will hook up my serial cable again to see what gw is reporting, will report back
@KrishnaIyer and it's like visiting the dentist again, hooked up uart cable, saw no packets from devices, only mqtt status packets, rebooted gw again and it started working. See attached log, you can see one LORA UART TIMEOUT thought during init. Both kiss-lora and ttn-uno device report now to cloud, before it looked like as if lora board was not initialized correctly and could not receive packets or devices couldn't register but rest of gw worked somehow. (hence the mqtt status packets and gw up status in console)
If i look back the 24 hour hardcoded reboot early this morning stopped my sensor for being connected to the cloud and report, so it did more harm then good to be honest. Can this be disabled, if someone has unticked Automatically update gateway in console settings?
@cyberjunky :
We are looking at a way to better handle the firmware update process and we should have some solutions soon. Thanks!
@KrishnaIyer I have uplink packets every 30secs with my two sensors placed near the gw, so loss of connection because of stale communication cannot be the reason here. Will leave the logging active for now.
Bummer, version 1.0.3 stopped receiving uplinks (after 7 hours, following a reboot after an MQTT error). A manual reboot fixed it. Though reported above earlier, I'd say it's unrelated to any reboot loop but I could not find any other open issue about it. So I've opened a new issue: #29.
So - it seems that I have resolved my issues by performing the following steps:
Updated microSD card according to the firmware page (using beta 1.03)
Reset the gateway by pressing and holding the reset button under white cover until all lights were illuminated
removed power and inserted microSD card.
plugged in the device and let sit for 3-5 mins
In the TTN Console, I deleted the old gateway name I created (when originally setting up the device with the bad firmware) I think this is key
followed along with the gateway activation per usual.
I have this exact issue yesterday after I pulled the gateway off the window and dropped it on the floor!
This was enough to dislodge the LoRa board at the card connection, and it sat in a reboot loop for 7 hours...
All it needed was to press the board back in so none of the gold connections were visible, and it started working again.
With the latest firmwares, both stable and development releases via SD card, the frequent reboot doesn't occur any more. After a fresh provisioning like egarl004 explained, my gateway now repeats the following log entries once I'm in step 4 of the activation process.
LORA: UART TIMEOUT
LORA: UART TIMEOUT
MON: SYS Stack size: 2845
MON: heap usage: 151KB (233KB), free: 188KB
LORA: UART TIMEOUT
LORA: Close and reopen UART on 115200 baud.
LORA: Changing state from 2 to 1
LORA: Wait init complete, check for communication on 115200 baud.
LORA: Changing state from 1 to 2
LORA: UART TIMEOUT
MON: SYS Stack size: 2845
MON: heap usage: 151KB (233KB), free: 188KB
LORA: UART TIMEOUT
LORA: UART TIMEOUT
LORA: UART TIMEOUT
Manual restart by button of power disconnect has the same effect. Details of the gateway after a reboot by disconnecting power are
Firmware name: AmazingAckermann, type: 0, version: 1.0.3, commit: a9d6c1a7, timestamp: 1523035644
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Apr 6 2018 17:28:25
Reboot reason: 0x03
BOOT: (persisted info) 6F 72 72 65 01 03 BD 7C EF FE F9 BA 77 6B 2C E7
Flashed my "reboot loop" TTN gateway to the beta (1.0.3) version with bootloader r2. Now the reboot loop is solved, but still lots of LORA: UART WRITE ERROR!'s (new bootloader, so Lora board communication should be solved?). Despite of setting in Console: no automatic update and no beta!, “new” firmware was downloaded, version 1.0.2. This version did not connect to my WIFI! Again flashed with 1.0.3 (beta) with bootloader r2, but now in Console settings: NO automatic update and YES Beta. And again, after a series of LORA: UART WRITE ERROR!’s it requests a new firmware download. (now V1.0.3 – because of the Yes beta in Console?). And at the end, despite of LORA communication problems (WRITE ERRORS, Bad CRC’s and Kicking Lora because of time-out) a working TTN Gateway!!!!
**************************
* The Things Network *
* G A T E W A Y *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.3, commit: 2c56ce09, timestamp: 1521721252
Bootloader revision: 2, commit: c463e87e, timestamp: 1519396960
Build time: Mar 22 2018 12:21:52
Reboot reason: 0x01
BOOT: (persisted info) 6F 72 72 65 01 03 AE 97 F1 78 38 80 79 B6 29 75
WIFI: Entering state 0
WIFI: Entering SCAN state 0
MAIN: Initialisation complete
LORA: Changing state from 0 to 0
MAIN: Leaving state 0
MAIN: Entering state 1
FLASH: Magic bytes found: wifi config present
FLASH: Magic bytes found: activation data present
FLASH: Magic bytes found: FOTA data present
FLASH: Loading Firmware Data
CNFG: (Firmware HASH (sha256)) 87 93 F2 0A xx yy zz
FLASH: Loading WiFi Data
CNFG: WiFi SSID: WLAN12
CNFG: WiFi key: ***
CNFG: WiFi conn_type: 1
CNFG: WiFi sec_type: 4
FLASH: Loading Activation Data
CNFG: Gateway ID: cicon
CNFG: Gateway Key: ***
CNFG: Account Server URL: https://account.thethingsnetwork.org
CNFG: Locked: true
CNFG: Locked first time: false
MAIN: Leaving state 1
MAIN: Entering state 2
INET: State change to 0
LORA: Initialisation complete
LORA: Changing state from 0 to 1
WIFI: Entering state 1
ETH: IP Address: 0.0.0.0
WIFI: Entering state 4
WIFI: Entering SCAN state 1
SNTP: State change from 0 to 1
Scan is completed successfully
WIFI: Entering SCAN state 2
WIFI: Entering SCAN state 5
WIFI: Entering SCAN state 0
WIFI: Entering state 2
WIFI: Disabling modules
Head magic match void: trying to free an already freed block, ignore
SNTP: State change from 1 to 1
WIFI: Entering state 3
WIFI: Enabling modules for client
WIFI: Entering state 6
>WIFI: IP Address: 0.0.0.0
LORA: Wait init complete, check for communication on 115200 baud.
LORA: Changing state from 1 to 2
LORA: Communication on 115200 OK, waiting for application.
LORA: Changing state from 2 to 4
CB: INET: Gateway has WiFi
INET: State change to 2
INET: Connected to a network, waiting for DHCP lease, checking validity with ping
SNTP: State change from 1 to 2
MON: SYS Stack size: 3959
MON: heap usage: 147KB (156KB), free: 192KB
WIFI: IP Address: 192.168.0.55
INET: State change to 3
INET: Ping probe
INET: Error sending probe on Eth
INET: Ping response from MRF24WN, set as default
INET: State change to 4
SNTP: State change from 2 to 3
SNTP: State change from 3 to 4
SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
INET: State change to 5
MAIN: Leaving state 2
MAIN: Entering state 3
CNFG: Load online user config state change to 4
HTTP: Close active socket 0
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1417 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
CONF: Parsing response token: HTTP/1.1 200 OK
CONF: ROUTER URL: mqtts://bridge.eu.thethings.network:8883
CNFG: Load online user config state change to 6
MON: SYS Stack size: 2870
MON: heap usage: 151KB (233KB), free: 188KB
FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/EU_863_870
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1232 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
CNFG: Load online user config state change to 7
CNFG: Configuring LoRa module
LORA: Changing state from 4 to 6
LORA: Starting reconfiguration
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: version: 00
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: Configuration failed, retry
LORA: Starting reconfiguration
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: version: 00
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: Configuration failed, retry
LORA: Starting reconfiguration
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: version: 00
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: Configuration failed, retry
LORA: RESET MODULE
LORA: Changing state from 6 to 0
LORA: Initialisation complete
LORA: Changing state from 0 to 1
MON: SYS Stack size: 2870
MON: heap usage: 151KB (233KB), free: 188KB
LORA: Wait init complete, check for communication on 115200 baud.
LORA: Changing state from 1 to 2
LORA: Communication on 115200 OK, waiting for application.
LORA: Changing state from 2 to 4
LORA: Changing state from 4 to 6
LORA: Starting reconfiguration
LORA: version: 01
LORA: UART TIMEOUT
LORA: Configuration succeeded
LORA: Starting operation
LORA: Changing state from 6 to 8
LORA: Changing state from 8 to 5
LORA: GOING ASYNC
LORA: Changing state from 5 to 11
CNFG: Load online user config state change to 9
MAIN: Leaving state 3
MAIN: Entering state 4
FLASH: Loading FOTA Data
FIRM: Requesting key ...
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
MON: SYS Stack size: 2837
MON: heap usage: 246KB (252KB), free: 93KB
HTTP: Got 515 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
FIRM: Starting download
FIRM: available bytes: 79
FIRM: (Downloaded FOTA key) 14 3E 99 52 xx yy zz
FIRM: (Stored FOTA key) 87 93 F2 0A xx yy zz
FLASH: Erasing FOTA Data and Image
MON: SYS Stack size: 2837
MON: heap usage: 168KB (252KB), free: 171KB
LORA: Packet dropped! Bad CRC
MON: SYS Stack size: 2837
MON: heap usage: 168KB (252KB), free: 171KB
MON: SYS Stack size: 2837
MON: heap usage: 168KB (252KB), free: 171KB
MON: SYS Stack size: 2837
MON: heap usage: 168KB (252KB), free: 171KB
MON: SYS Stack size: 2837
MON: heap usage: 168KB (252KB), free: 171KB
FLASH: Storing FOTA Checksum
FIRM: Finishing writing to storage
FIRM: New firmware found, start downloading!
FIRM: (OLD key) 87 93 F2 0A xx yy zz
FIRM: (NEW key) 14 3E 99 52 xx yy zz
FIRM: Requesting firmware ...
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
FIRM: Starting download
FIRM: available bytes: 583
FLASH: Storing FOTA Image
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
LORA: Accepted packet
LORA: Accepted packet
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
LORA: Kick LoRa module with ACK after not acked it for 60s
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
LORA: Accepted packet
LORA: Accepted packet
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
LORA: Packet dropped! Bad CRC
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
MON: SYS Stack size: 2837
MON: heap usage: 246KB (253KB), free: 93KB
HTTP: Connection Closed
FIRM: Finishing writing to storage
FLASH: Finalizing FOTA
MAIN: NEW FIRMWA
*** Application reboot
SNTP: State change from 0 to 0
SNTP: State change from 0 to 0
**************************
* The Things Network *
* G A T E W A Y *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.3, commit: 2c56ce09, timestamp: 1521721252
Bootloader revision: 2, commit: c463e87e, timestamp: 1519396960
Build time: Mar 22 2018 12:21:52
Reboot reason: 0x40
BOOT: (persisted info) 6F 72 72 65 01 03 AE 97 F1 78 38 80 79 B6 29 75
WIFI: Entering state 0
WIFI: Entering SCAN state 0
MAIN: Initialisation complete
LORA: Changing state from 0 to 0
MAIN: Leaving state 0
MAIN: Entering state 1
FLASH: Magic bytes found: wifi config present
FLASH: Magic bytes found: activation data present
FLASH: Magic bytes found: FOTA data present
FLASH: Loading Firmware Data
CNFG: (Firmware HASH (sha256)) 14 3E 99 52 xx yy zz
FLASH: Loading WiFi Data
CNFG: WiFi SSID: WLAN12
CNFG: WiFi key: ***
CNFG: WiFi conn_type: 1
CNFG: WiFi sec_type: 4
FLASH: Loading Activation Data
CNFG: Gateway ID: cicon
CNFG: Gateway Key: ***
CNFG: Account Server URL: https://account.thethingsnetwork.org
CNFG: Locked: true
CNFG: Locked first time: false
MAIN: Leaving state 1
MAIN: Entering state 2
INET: State change to 0
LORA: Initialisation complete
LORA: Changing state from 0 to 1
WIFI: Entering state 1
ETH: IP Address: 0.0.0.0
WIFI: Entering state 4
WIFI: Entering SCAN state 1
SNTP: State change from 0 to 1
Scan is completed successfully
WIFI: Entering SCAN state 2
WIFI: Entering SCAN state 5
WIFI: Entering SCAN state 0
WIFI: Entering state 2
WIFI: Disabling modules
Head magic match void: trying to free an already freed block, ignore
SNTP: State change from 1 to 1
WIFI: Entering state 3
WIFI: Enabling modules for client
WIFI: Entering state 6
>WIFI: IP Address: 0.0.0.0
CB: INET: Gateway has WiFi
INET: State change to 2
INET: Connected to a network, waiting for DHCP lease, checking validity with ping
SNTP: State change from 1 to 2
LORA: Wait init complete, check for communication on 115200 baud.
LORA: Changing state from 1 to 2
LORA: Communication on 115200 OK, waiting for application.
LORA: Changing state from 2 to 4
CB: MON: SYS Stack size: 3959
MON: heap usage: 147KB (156KB), free: 192KB
INET: State change to 3
INET: Ping probe
INET: Error sending probe on Eth
SNTP: State change from 2 to 6
INET: Ping Timeout
INET: Ping probe
INET: Error sending probe on Eth
WIFI: IP Address: 192.168.0.55
INET: Ping Timeout
INET: Ping probe
INET: Error sending probe on Eth
INET: Ping response from MRF24WN, set as default
INET: State change to 4
SNTP: State change from 6 to 1
INET: Initiated NTP request.
SNTP: State change from 1 to 2
MON: SYS Stack size: 3959
MON: heap usage: 147KB (156KB), free: 192KB
SNTP: State change from 2 to 3
SNTP: State change from 3 to 4
SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
INET: State change to 5
MAIN: Leaving state 2
MAIN: Entering state 3
CNFG: Load online user config state change to 4
HTTP: Close active socket 0
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1417 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
CONF: Parsing response token: HTTP/1.1 200 OK
CONF: ROUTER URL: mqtts://bridge.eu.thethings.network:8883
CNFG: Load online user config state change to 6
FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/EU_863_870
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1232 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
CNFG: Load online user config state change to 7
CNFG: Configuring LoRa module
LORA: Changing state from 4 to 6
LORA: Starting reconfiguration
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: version: 00
LORA: UART WRITE ERROR!
MON: SYS Stack size: 2870
MON: heap usage: 152KB (234KB), free: 187KB
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: Configuration failed, retry
LORA: Starting reconfiguration
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: version: 00
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: Configuration failed, retry
LORA: Starting reconfiguration
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: version: 00
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: UART WRITE ERROR!
LORA: Configuration failed, retry
LORA: RESET MODULE
LORA: Changing state from 6 to 0
LORA: Initialisation complete
LORA: Changing state from 0 to 1
LORA: Wait init complete, check for communication on 115200 baud.
LORA: Changing state from 1 to 2
LORA: Communication on 115200 OK, waiting for application.
LORA: Changing state from 2 to 4
LORA: Changing state from 4 to 6
LORA: Starting reconfiguration
LORA: version: 01
LORA: UART TIMEOUT
LORA: Configuration succeeded
LORA: Starting operation
LORA: Changing state from 6 to 8
MON: SYS Stack size: 2870
MON: heap usage: 152KB (234KB), free: 187KB
LORA: Changing state from 8 to 5
LORA: GOING ASYNC
LORA: Changing state from 5 to 11
CNFG: Load online user config state change to 9
MAIN: Leaving state 3
MAIN: Entering state 4
FLASH: Loading FOTA Data
FIRM: Requesting key ...
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 515 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
FIRM: Starting download
FIRM: available bytes: 79
FIRM: (Downloaded FOTA key) 14 3E 99 52 xx yy zz
FIRM: (Stored FOTA key) 14 3E 99 52 xx yy zz
FIRM: Firmware is already downloaded
MAIN: No new firmware available
MAIN: Leaving state 4
MAIN: Entering state 5
MQTT: GOT IP: 52.169.76.203
Connecting to: 52.169.76.203
MQTT: Connection Opened: Starting TLS Negotiation
MQTT: Wait for SSL Connect
MQTT: TLS ready: Connect MQTT
RQMQTT: Connected
*************************
MAIN: Gateway bridging
*************************
MQTT: Sending status packet
MQTT: Report reboot error: 0103
MQTT: Report config error: 0600000080
MQTT: Sending status succeeded: 0
MON: SYS Stack size: 2831
MON: heap usage: 262KB (263KB), free: 76KB
MON: SYS Stack size: 2831
MON: heap usage: 262KB (263KB), free: 76KB
MON: SYS Stack size: 2831
MON: heap usage: 262KB (263KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 1
MON: SYS Stack size: 2831
MON: heap usage: 262KB (263KB), free: 77KB
MON: SYS Stack size: 2831
MON: heap usage: 262KB (263KB), free: 77KB
MON: SYS Stack size: 2831
MON: heap usage: 262KB (263KB), free: 77KB
LORA: Accepted packet
MQTT: Sending UPLINK OK
LORA: Accepted packet
MQTT: Sending UPLINK OK
MQTT: Sending status packet
MQTT: Sending status succeeded: 2
MON: SYS Stack size: 2831
MON: heap usage: 262KB (263KB), free: 77KB
MON: SYS Stack size: 2831
MON: heap usage: 262KB (263KB), free: 77KB
LORA: Packet dropped! Bad CRC
MON: SYS Stack size: 2831
MON: heap usage: 262KB (266KB), free: 77KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 3
MON: SYS Stack size: 2831
MON: heap usage: 262KB (266KB), free: 77KB
MON: SYS Stack size: 2831
MON: heap usage: 262KB (266KB), free: 77KB
MON: SYS Stack size: 2831
MON: heap usage: 262KB (266KB), free: 77KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 4
MON: SYS Stack size: 2831
MON: heap usage: 262KB (266KB), free: 77KB
LORA: Packet dropped! Bad CRC
LORA: Accepted packet
MQTT: Sending UPLINK OK
LORA: Accepted packet
MQTT: Sending UPLINK OK
MON: SYS Stack size: 2831
MON: heap usage: 262KB (266KB), free: 77KB
MON: SYS Stack size: 2831
MON: heap usage: 262KB (266KB), free: 77KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 5
This afternoon I've downloaded the latest develop firmware and the gateway was working fine for about 20 minutes.
Firmware name: AmazingAckermann, type: 0, version: 1.0.3, commit: 2d743f4f, timestamp: 1523350945
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Apr 10 2018 09:03:31
Reboot reason: 0x03
BOOT: (persisted info) 6F 72 72 65 01 03 BD 5C EF FE F9 BA 67 6A 2C F7
After about 20 minutes the gateway restarted because of a MQTT error according to the log. Meanwhile a new firmware was installed although I unchecked the boxes Automatically update gateway and Beta Updates in the gateway settings of TTN console.
MQTT: Sending status packet
MQTT: Sending status succeeded: 41
MON: SYS Stack size: 2847
MON: heap usage: 261KB (262KB), free: 77KB
MON: SYS Stack size: 2847
MON: heap usage: 261KB (262KB), free: 77KB
LORA: Kick LoRa module with ACK after not acked it for 60s
MON: SYS Stack size: 2847
MON: heap usage: 261KB (262KB), free: 77KB
MQTT: Sending status packet
MQTT: Sending status failed
MAIN: MQTT error
MAIN: Leaving state 5
SNTP: State change from 0 to 0
SNTP: State change from 0 to 0
**************************
* The Things Network *
* G A T E W A Y *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.3, commit: fd0901ae, timestamp: 1523880794
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Apr 16 2018 12:14:13
Reboot reason: 0x10
BOOT: (persisted info) 6F 72 72 65 01 10 BD 5C EF FE F9 BA 67 6A 2C F7
Unfortunately after this restart the gateway doesn't connect any more according to the logs. Soft via the button and hard restart via power disconnect gives the same result.
LORA: UART TIMEOUT
LORA: UART TIMEOUT
LORA: Close and reopen UART on 115200 baud.
LORA: Changing state from 2 to 1
MON: SYS Stack size: 2859
MON: heap usage: 151KB (233KB), free: 188KB
LORA: Wait init complete, check for communication on 115200 baud.
LORA: Changing state from 1 to 2
LORA: UART TIMEOUT
MON: SYS Stack size: 2859
MON: heap usage: 151KB (233KB), free: 188KB
LORA: UART TIMEOUT
LORA: UART TIMEOUT
Meanwhile a new firmware was installed although I unchecked the boxes Automatically update gateway and Beta Updates in the gateway settings of TTN console.
That's interesting. Your logs show that it installed version: 1.0.3, commit: fd0901ae
, but that version isn't on any of our update channels at the moment. We retracted 1.0.3 because of those LORA: UART
errors.
Hi, I am happy to inform that after having updated my faulty gateway to below bootloader and firmware versions with a PICkit3 all my gateway isseus appear te be resolved:
Version Info | |
---|---|
Hardware: | v1 |
Bootloader: | r2-c463e87e (2018-02-23T14:42:40Z) |
Firmware: | v1.0.3-485eaceb (2018-04-21T15:57:49Z) |
Mine has been up for 24 hours, never got more than 30 minutes before this latest update. Maybe its fixed, fingers crossed
**************************
* The Things Network *
* G A T E W A Y *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.3, commit: 2c56ce09, timestamp: 1521721252
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Mar 22 2018 12:21:52
Reboot reason: 0x03
BOOT: (persisted info) 6F 72 72 65 01 03 57 B3 ED 9B 84 CE 7A 7E CE 8D
This is my version, now running steadily for 36 hours
Spoke too soon. As long as I do not cycle power, touch my gateway physically or look at it funny it runs. Do anything else and it goes into reboot loop. Complains that LoRa UART is not communicating. I do the full pink button initialise gateway, follow all steps and voila, it works again until next time I touch it, cycle power or yes, look at it funny.
While 1.0.3 (commit: 2c56ce09, timestamp: 1521721252, Build time: Mar 22 2018 12:21:52) was not getting me the reboot loop, today's 1.0.4 is. Connected through ethernet. Reverted back to 1.0.3 now (which is giving me #8).
After trying to get my gateway up and running using the latest beta 1.0.4 release this morning I've compiled the current develop branch.
Initially the gateway connected for about a minute but after got stuck in a reboot loop repeating in approx. every 30 seconds.
One minor issue with the console. When I deselect the option automatic update during activation, the option Automatically update gateway is still selected in the gateway settings.
My gateway has been running stable since the 1.03 update, more than a month, but suddenly stopped this morning (May 10). Power cycling did not help, and I updated the SD card to the stable release candidate. Also did a new setup. It's rebooting since. Log below:
Firmware name: AmazingAckermann, type: 0, version: 1.0.4, commit: a7beae91, timestamp: 1525259181 Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298 Build time: May 2 2018 11:07:39 Reboot reason: 0x10 BOOT: (persisted info) 6F 72 72 65 01 03 71 50 87 D9 A1 06 25 0E 11 42
WIFI: Entering state 0 WIFI: Entering SCAN state 0
MAIN: Initialisation complete LORA: Changing state from 0 to 0
MAIN: Leaving state 0 MAIN: Entering state 1 FLASH: Magic bytes found: wifi config present FLASH: Magic bytes found: activation data present FLASH: Magic bytes not found: no stored FOTA data present FLASH: Loading Firmware Data CNFG: (Firmware HASH (sha256)) FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FLASH: Loading WiFi Data CNFG: WiFi SSID: xxxxxxxxx CNFG: WiFi key: CNFG: WiFi conn_type: 1 CNFG: WiFi sec_type: 4 FLASH: Loading Activation Data CNFG: Gateway ID: wilson-creek-winery CNFG: Gateway Key: CNFG: Account Server URL: https://account.thethingsnetwork.org CNFG: Locked: true CNFG: Locked first time: false
MAIN: Leaving state 1 MAIN: Entering state 2 INET: State change to 0 LORA: Initialisation complete LORA: Changing state from 0 to 1 WIFI: Entering state 1 ETH: IP Address: 0.0.0.0 WIFI: Entering state 4 WIFI: Entering SCAN state 1 Scan is completed successfully WIFI: Entering SCAN state 2 WIFI: Entering SCAN state 5 WIFI: Entering SCAN state 0 WIFI: Entering state 2 WIFI: Disabling modules Head magic match void: trying to free an already freed block, ignore WIFI: Entering state 3 SNTP: State change from 0 to 1 WIFI: Enabling modules for client WIFI: Entering state 6
WIFI: IP Address: 0.0.0.0 CB: INET: Gateway has WiFi INET: State change to 2 INET: Connected to a network, waiting for DHCP lease, checking validity with ping SNTP: State change from 1 to 2 WIFI: IP Address: 192.168.0.xxx LORA: Wait init complete, waiting for application. LORA: Changing state from 1 to 2 INET: State change to 3 INET: Ping probe INET: Error sending probe on Eth INET: Ping response from MRF24WN, set as default INET: State change to 4 SNTP: State change from 2 to 3 MON: SYS Stack size: 3959 MON: TCPIP Stack size: 3828 MON: APP Stack size: 7951 MON: LoRa Stack size: 3883 MON: heap usage: 163KB (172KB), free: 176KB SNTP: State change from 3 to 4 SNTP: State change from 4 to 5 SNTP: State change from 5 to 6 SNTP: State change from 6 to 7 INET: State change to 5
MAIN: Leaving state 2 MAIN: Entering state 3
CNFG: Load online user config state change to 4 HTTP: Close active socket 0 HTTP: Starting connection HTTPS: Connection Opened: Starting TLS Negotiation HTTP: Wait for TLS Connect HTTP: TLS Connection Opened: Starting Clear Text Communication HTTP: Got 1535 bytes HTTP: Connection Closed HTTP: Close active socket 1 CONF: Parsing response token: HTTP/1.1 200 OK CONF: ROUTER URL: mqtts://bridge.us-west.thethings.network:8883
CNFG: Load online user config state change to 6 FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/US_902_928 HTTP: Starting connection HTTPS: Connection Opened: Starting TLS Negotiation HTTP: Wait for TLS Connect MON: SYS Stack size: 2833 MON: TCPIP Stack size: 3828 MON: APP Stack size: 3294 MON: LoRa Stack size: 3883 MON: heap usage: 244KB (249KB), free: 95KB HTTP: TLS Connection Opened: Starting Clear Text Communication HTTP: Got 1179 bytes HTTP: Connection Closed HTTP: Close active socket 1
CNFG: Load online user config state change to 7
CNFG: Configuring LoRa module LORA: Changing state from 2 to 4 LORA: Starting reconfiguration LORA: version: 02 LORA: Configuration failed, retry LORA: Starting reconfiguration LORA: version: 02 LORA: Configuration failed, retry LORA: Starting reconfiguration MON: SYS Stack size: 2833 MON: TCPIP Stack size: 3828 MON: APP Stack size: 3294 MON: LoRa Stack size: 3855 MON: heap usage: 167KB (249KB), free: 172KB LORA: version: 02 LORA: Configuration failed, retry LORA: RESET MODULE LORA: ChaSNTP: State change from 0 to 0 SNTP: State change from 0 to 0
@ReiniervdL and @eddyvdh can you please edit your earlier comments to put the long log into something like the following?
<details>
<summary>Reboot loop in 1.0.3</summary>
```text
your
log
here
```
</details>
...which will get you:
Thanks! (I will delete this comment later.)
Same thing here : lot of reboots (~10min period) with GW connected over WIFI.
>WIFI: IP Address: 0.0.0.0
CB: INET: Gateway has WiFi
INET: State change to 2
INET: Connected to a network, waiting for DHCP lease, checking validity with ping
LORA: Wait init complete, waiting for application.
LORA: Changing state from 1 to 2
SNTP: State change from 1 to 2
WIFI: IP Address: 192.168.43.36
MON: SYS Stack size: 3959
MON: heap usage: 147KB (156KB), free: 193KB
INET: State change to 3
INET: Ping probe
INET: Error sending probe on Eth
INET: Ping response from MRF24WN, set as default
INET: State change to 4
SNTP: State change from 2 to 3
SNTP: State change from 3 to 4
SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
INET: State change to 5
MAIN: Leaving state 2
MAIN: Entering state 3
CNFG: Load online user config state change to 4
HTTP: Close active socket 0
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
SNTP: State change from 0 to 0
SNTP: State change from 0 to 0
**************************
* The Things Network *
* G A T E W A Y *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.2, commit: 475aef56, timestamp: 1521106500
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Mar 15 2018 09:35:17
Reboot reason: 0x10
BOOT: (persisted info) 6F 72 72 65 01 10 25 0B 9D F4 25 0B 9D 8D 7F AC
Hi there, got my brand new gateway yesterday and right from the beginning I was stuck in a boot loop. Tried all firmware versions and always the same: got 2 LEDs on, 3rd one blinking slowly, then the 3rd LED goes off and the gateway reboots...and everything starts from the beginning.
I have read the markdown guide, but don't see how you have been adding your log files as some form of link. How do you do this?
From what I can see in the source code, that's a
RESET_REASON_WDT_TIMEOUT
(0x10
).Based on what I see on the forum this happens a lot.