TTIG don't work after first connection to Wi-FI

Gateways TTIG - The Things Indoor Gateway
1

Hello.
I connected my phone to new TBMH100, add name and password of my wi-fi connection. Pressed “save&reboot”. Green LED blinking a couple of times, then lights up green, after few seconds blinking green/red and after LED is not lit. I’m waiting 20 minutes-nothing. Power off-power on: 1 green blink-3 red/green very fast blinking-1 green blink-LED off. Nothing works, no WI-Fi. Always after power on: 1 green blink-3 red/green very fast blinking-1 green blink-LED off. “Reset” don’t help.
I connected to TTIG via serial terminal and recived such messages:
1

Please help :slight_smile:

2

Can you see it connected to wifi on local network? Getting it running and stable is job 1 to then getting it to register and pull confi =g info from CUPS server…

3

Not connected to WI-FI. I see it in router settings as “offline”.

4

You might want to review whatever you did to attach a serial lead, you may have disrupted some other connection as

rst cause:4, boot mode:(3,6)

is a watchdog timer reboot due to the software failing to respond which may be due to some hardware not being attached.

Please post anything that can be copied & pasted as text as text, not as a screenshot.

5

I disassembled the device only after it stopped working. Serial connection is ok.
Messages go cyclically(i delete just MAC):
ShowCritical:1

ets Jan 8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8

2nd boot version : 1.6
SPI Speed : 80MHz
SPI Mode : QIO
SPI Flash Size & Map: 32Mbit(1024KB+1024KB)
jump to run user2 @ 101000

r#▒▒▒c
▒▒#$c▒▒c|▒dēdc▒▒g▒▒
▒▒▒
d▒
▒
d
dl▒▒▒▒$▒n▒▒▒▒▒c ll▒{▒c▒▒▒▒c d▒b▒lsd▒▒▒▒o▒;▒▒g|▒ lld$▒
ets Jan 8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8

2nd boot version : 1.6
SPI Speed : 80MHz
SPI Mode : QIO
SPI Flash Size & Map: 32Mbit(1024KB+1024KB)
jump to run user2 @ 101000

?{▒▒c▒▒▒c▒▒cdc▒▒#|r▒l▒▒lb▒▒o▒▒’▒▒▒▒l▒▒lld▒Č▒d▒'▒▒▒▒cll▒{▒c ▒▒▒c l▒#▒$sd▒▒▒n▒{▒▒o|▒l$ld▒mode : sta(MAC)
add if0
ShowCritical:1

ets Jan 8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8

2nd boot version : 1.6
SPI Speed : 80MHz
SPI Mode : QIO
SPI Flash Size & Map: 32Mbit(1024KB+1024KB)
jump to run user2 @ 101000

s▒c▒▒▒b▒▒bl#▒▒▒c|;▒$▒▒lc▒▒’▒og▒
▒▒▒$▒▒
$
ll▒
▒▒▒▒l ▒g▒▒▒▒b$
d▒s▒
▒▒bl
▒c▒d;l▒▒▒g▒s▒▒n|▒$
dll`▒ShowCritical:1

ets Jan 8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8

2nd boot version : 1.6
SPI Speed : 80MHz
SPI Mode : QIO
SPI Flash Size & Map: 32Mbit(1024KB+1024KB)
jump to run user2 @ 101000

~;▒c▒▒▒c
▒▒cdc▒▒#<▒l▒▒lc▒▒o▒▒’▒▒▒▒l▒
▒l
l$▒▒▒▒d`▒o▒ğ▒#
d
d▒r▒
▒▒▒#$
▒c▒l{l▒▒▒g▒▒s▒▒’|▒
d
l$l ▒
ets Jan 8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8

2nd boot version : 1.6
SPI Speed : 80MHz
SPI Mode : QIO
SPI Flash Size & Map: 32Mbit(1024KB+1024KB)
jump to run user2 @ 101000

{▒▒c▒▒▒b▒▒clb▒▒c|;▒$▒▒l#▒▒n▒og▒▒▒▒$▒▒$
ld▒
▒▒▒▒l▒'▒▒▒▒cll▒{▒c ▒▒▒c l▒#▒$sd▒▒▒n▒{▒▒o|▒llld▒mode : sta(MAC)
add if0
ShowCritical:2

ets Jan 8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8

2nd boot version : 1.6
SPI Speed : 80MHz
SPI Mode : QIO
SPI Flash Size & Map: 32Mbit(1024KB+1024KB)
jump to run user2 @ 101000

s▒c▒▒▒#Čbl#▒▒▒c|{▒d▒▒$c▒▒’▒ng▒
▒▒▒d▒▒
d
$l▒
▒▒▒▒l ▒g▒▒▒▒bl
d▒s▒
▒▒▒cl▒c▒d;l▒▒▒’▒{▒▒n<▒$
dld`▒ShowCritical:1

6

I made screenshot before rebooting when I set wi-fi parameters:
FW Build: 2018-12-06 09:30:37
FW Version: 2.0.0
Core Version: 2.0.0(minihub/debug)
Perhaps, after connecting to wi-fi, it tried to update and something went wrong?

7

I assume you have tried a full reset, then gone back to config page and tried to enter WiFi details again & rebooted?

8

“Reset” don’t help.

9

I didn’t say disassembling it was bad. I said:

so I was suggesting that you go and check all the connections are in place.

But now you have revealed after you’ve started the post that you disassembled the device “after it stopped working” perhaps you could be polite enough to tell us what stopped working along with any other history of the device so we don’t end up asking you endless pointless questions.

10

Thanks everyone for trying to help :slight_smile:
I described everything in the first post. How could.The condition with the LED flashing and turning off, I consider “the device is not working.” Because this blinking is not in the manual. And there is no way to reset it or somehow connect in standard ways. Briefly: I started to configure according to the instructions, rebooted. Received incomprehensible blinking of the LED and the inability to reset / connect. Dissasembled and connected to the serial port. The data obtained indicate the obviousness of the error. I think that it is of a programmatic nature, because before rebooting with the entered wi-fi parameters, everything worked according to the instructions.

11

There is only 2 connections on the board: from the 220V to 5V converter to the main board and antenna connection. Everything is fine with this. Also, the board is visually intact, and behaves the same as before disassembly. Just like after a reboot with WI-FI parameters: the LED flashes and turns off.

12

I think this was/is an interpretation thing - generally the rate & type of flashing of an LED wouldn’t lead me to assume there was a physical problem that required disassembly of the device. I thought you were saying you’d repaired it and now it wasn’t working.

I suspect the reason the LED goes off which isn’t documented as a mode is because it’s crashed - which is what’s going on with the debug output.

The hard reset should return the settings to no WiFi which should then allow the firmware to work. If not I think it’s a return to vendor situation.

13

Which power source are you using? Did you make sure the power source is capable of supplying 1A at 5V? Try out a few different power sources if possible.
If that doesn’t help try holding the reset button while powering up the device. This should bring the device back to factory condition.
Please configure the baud rate to 115200 when reading the serial port in order to see what’s going on past the bootloader.

14

Reset does not work. After that, nothing has changed. Many, many times I tried this.

15

I used:
-TTIG integrated power supply.
-USB port from my PC.
-USB port(2 A) from my outlet.
-USB adapter(3 A) from my phone.
-3 different USB cables.

When I hold down “reset” button and power on:
“1 red blink-3 red/green very fast blinkings-1 red blink” cyclically(as long as I hold “reset” button).
When I release “reset” button:
1 red blink-3 red/green very fast blinking-1 green blink-LED off.
It doesn`t help.
I configured the baud rate to 115200 as in manual.
Log from PUTTy higher showed. I used ch341a based programmer for connection.

Maybe it’s possible for manual flashing firmware?

16

I check now first message in log(I delete MAC,EUI etc):

rld▒▒|▒l▒|
▒$▒c|▒▒▒▒;▒clc▒▒g’▒lng▒▒▒
bx▒l;l{lx▒o▒
▒
d
#g▒|▒▒
#▒▒no▒$▒▒l ▒
dgs▒▒▒o ▒▒lp▒’▒
s▒ܜ▒▒
co▒<쎇▒b▒▒og▒
l▒ dgs▒ۓo
▒$p▒’▒
s▒ܜ▒▒▒$
co▒<▒▒▒
b▒▒og▒
$▒o dgs▒ۓo
▒$;▒▒g ▒l {$▒▒n▒▒▒gn▒▒▒▒▒{g▒ d▒c▒d▒$▒ۃ ▒ $d{l ▒lllo▒▒ ▒ d▒dld▒$▒▒n▒o▒▒▒▒l$▒c▒ldpc▒cp▒▒ ▒csbp▒▒ ▒c #d$▒▒' ▒g▒▒▒ol▒| c ll $sd?{▒▒c▒▒▒b▒▒clb▒▒c|;▒$▒▒l#▒▒n▒og▒▒▒▒$▒▒$
ld▒
▒▒▒▒l▒n▒▒▒▒c ll▒{▒c▒▒▒▒c d▒b▒$sd▒▒▒▒o▒;▒▒g|▒lld$▒mode : sta(DELETED YURII)
add if0
1970-01-01 00:00:02.133 [SYS:INFO] FSCK found section marker A0
1970-01-01 00:00:02.139 [SYS:INFO] FSCK section A: 22 records, 5956 bytes used, 1018044 bytes free
1970-01-01 00:00:02.627 [SYS:INFO] FSCK section A followed by erased flash - all clear.
1970-01-01 00:00:02.635 [SYS:INFO] Checking file: [ cups-boot.uri ] OK
1970-01-01 00:00:02.638 [SYS:INFO] Checking file: [ cups-boot.key ] OK
1970-01-01 00:00:02.642 [SYS:INFO] Checking file: [ cups-boot.trust ] OK
1970-01-01 00:00:02.645 [SYS:INFO] Checking file: [ sig-0.key ] OK
1970-01-01 00:00:02.651 [SYS:INFO] Checking file: [ station.conf ] OK
1970-01-01 00:00:02.674 [SYS:INFO] Checking file: [ web/index.html ] OK
1970-01-01 00:00:02.682 [any:INFO] HW pipe bound with fd=0
1970-01-01 00:00:02.683 [any:INFO] AIO registered for HW pipe &aio=0x3ffeea98

1970-01-01 00:00:00.007 [SYS:DEBU] ======= VER ======
1970-01-01 00:00:00.008 [SYS:DEBU] Station Version 2.0.4(minihub/debug)
1970-01-01 00:00:00.011 [SYS:DEBU] Version Commit f63908e
1970-01-01 00:00:00.014 [SYS:DEBU] Station Build 2020-05-07 16:03:53
1970-01-01 00:00:00.020 [SYS:DEBU] Firmware Version 2.0.4
1970-01-01 00:00:00.025 [SYS:DEBU] FW Flavor ID semtech0
1970-01-01 00:00:00.031 [SYS:DEBU] Model minihub
1970-01-01 00:00:00.036 [SYS:DEBU] ======= SYS ======
1970-01-01 00:00:00.045 [SYS:DEBU] CPU Freq 80 / 80000000 / 80000000
1970-01-01 00:00:00.048 [SYS:DEBU] Random Number 122389149
1970-01-01 00:00:00.053 [SYS:DEBU] Reset cause 0
1970-01-01 00:00:00.058 [SYS:DEBU] Booting USER_BIN 2
1970-01-01 00:00:00.063 [SYS:DEBU] FW start addr 0x00101000
1970-01-01 00:00:00.069 [SYS:DEBU] ESP SDK version 2.0-dev(9ec59b5)
1970-01-01 00:00:00.075 [SYS:DEBU] mbedTLS version 2.6.1
1970-01-01 00:00:00.080 [SYS:DEBU] Free Heap Startup 58280 bytes
1970-01-01 00:00:00.086 [SYS:DEBU] ======= MFG ======
1970-01-01 00:00:00.092 [SYS:DEBU] SN DELETED YURII
1970-01-01 00:00:00.097 [SYS:DEBU] MTIME 2020-04-22 06:39:38
1970-01-01 00:00:00.106 [SYS:DEBU] PERSO_HASH DELETED YURII
1970-01-01 00:00:00.109 [SYS:DEBU] AP_PW DELETED YURII
1970-01-01 00:00:00.114 [SYS:DEBU] AP MAC DELETED YURII
1970-01-01 00:00:00.121 [SYS:DEBU] EUI DELETED YURII
1970-01-01 00:00:00.127 [SYS:DEBU] STA MAC DELETED YURII
1970-01-01 00:00:00.134 [SYS:DEBU] ======= CRD ======
1970-01-01 00:00:00.141 [SYS:DEBU] [cups] auth=3 → https://rjs.sm.tc:9191
1970-01-01 00:00:00.145 [SYS:DEBU] type=0 → /s2/cups.trust
1970-01-01 00:00:00.150 [SYS:DEBU] type=2 → /s2/cups.key
1970-01-01 00:00:00.156 [SYS:DEBU] [cups-bak] - not available
1970-01-01 00:00:00.168 [SYS:DEBU] [cups-boot] auth=3 → https://rjs.sm.tc:9191
1970-01-01 00:00:00.170 [SYS:DEBU] type=0 → /s2/cups-boot.trust
1970-01-01 00:00:00.174 [SYS:DEBU] type=2 → /s2/cups-boot.key
1970-01-01 00:00:00.181 [SYS:DEBU] [tc] - not available
1970-01-01 00:00:00.186 [SYS:DEBU] [tc-bak] - not available
1970-01-01 00:00:00.191 [SYS:DEBU] [tc-boot] - not available
1970-01-01 00:00:00.196 [SYS:DEBU] ======= MEM ======
data : 0x3ffe8000 ~ 0x3ffe8d40, len: 3392
rodata: 0x3ffe8d40 ~ 0x3ffe8fd0, len: 656
bss : 0x3ffe8fd0 ~ 0x3fff00a0, len: 28880
heap : 0x3fff00a0 ~ 0x40000000, len: 65376
1970-01-01 00:00:00.216 [SYS:DEBU] ==================
1970-01-01 00:00:00.233 [SYS:DEBU] Start WiFi Scan
ShowCritical:2

ets Jan 8 2013,rst cause:1, boot mode:(3,7)

I see new firmware version. Before reboot when I set WI-FI settings, TTIG haved 2.0.0 firmware version. Now it is 2.0.4.
Probably the problem appeared after the automatic update.

18

The TTIG team thinks this is a specific hardware failure. Where did you purchase this? I’ll try to get in touch with the your seller and get a replacement.

19

Hello,
I just purchased a TBHM100 gateway. It is well connected to my wifi, because I manage to ping it via my PC. But it has been flashing green/red since 2 hours. It does not stay solid green. His EUI : 58A0CBFFFE804277.
Version : 2.0.4
I’am in Europe.
Thanks you for your help !

21

Bit of a obvious question, but have you registered this on the console and if so, what settings did you use?

1 Like
22

Capture d’écran 2022-05-19 à 19.16.08

Yes gateway is registered.