This is the 2nd TTN Gateway we have to play with and this one won’t register on the TTN network. I have tried reset the device and re registering it several times, but it doesn’t want to play ball. It gets as far as LORA: starting reconfiguration, SNTP state change from 0 to 0 and reboots (see debug below).
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 1292 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: 2843
MON: heap usage: 152KB (234KB), free: 187KB
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 2 to 4
LORA: Starting reconfiguration
MON: SYS Stack size: 2843
MON: heap usage: 152KB (234KB), free: 187KB
SNTP: State change from 0 to 0
SNTP: State change from 0 to 0
[Device Appears to reboot]
I did see the following during the last attempt “CNFG: Gateway activation locked”. I am not sure if that is good or bad.
Have tried the beta firmware. On the debug, it shows version 1.0.4 (build May 2 2018). Still reboots at:-
CNFG: Configuring LoRa module
LORA: Changing state from 2 to 4
LORA: Starting reconfiguration
SNTP: State change from 0 to 0
SNTP: State change from 0 to 0
@mikcatta - you are a legend - this is exactly when was wrong with mine too. I have been dicking around with this thing for almost a year now playing with firmware and all sorts trying to work out what was wrong… it was bloody hardware. Agree with @m_p_m they need to make this much clearer!