Those are the bootloader logs which are printed at 115200 baud, if you use a terminal at 921600 you should see the app logs.
1 Like
Wow, I missed that! Very interesting.
mmmm something is wrong:
screen /dev/cu.usbserial-020067CD 921600
�����<��&ki*jpҁ�q�aY��
1��������#8��,�����a��U����lߜ �����s�����������������ߺ��������K�#��k�/������E
I found a windiws machine, here are the log from Putty:
▒H??:??:?? 0 booted, wake cau se 0 (boot count 1), reset_reason=reset
??:??:?? 0 Filesystem files:
??:??:?? 0 /prefs/db.proto
??:??:?? 0 /prefs/radio.proto
??:??:?? 0 /prefs/channels.proto
??:??:?? 0 I2C device found at address 0x3c
??:??:?? 0 ssd1306 display found
??:??:?? 0 done
??:??:?? 0 Meshtastic hwvendor=4, swver=1.2.39.06892c4, hwver=1.0
??:??:?? 0 Setting random seed 2798039900
??:??:?? 0 Total heap: 255008
??:??:?? 0 Free heap: 221016
??:??:?? 0 Total PSRAM: 4194252
??:??:?? 0 Free PSRAM: 4194252
??:??:?? 0 NVS: UsedEntries 70, FreeEntries 560, AllEntries 630
??:??:?? 0 Setup Preferences in Flash Storage
??:??:?? 0 Number of Device Reboots: 3
??:??:?? 0 Initial packet id 1163046622, numPacketId 4294967295
??:??:?? 0 Setting default channel and radio preferences!
??:??:?? 0 Expanding short PSK #1
??:??:?? 0 Wanted region 0, using Unset
??:??:?? 0 Loading /prefs/db.proto
??:??:?? 0 Loaded saved preferences version 11
??:??:?? 0 Loading /prefs/radio.proto
??:??:?? 0 Loading /prefs/channels.proto
??:??:?? 0 Number of Device Reboots: 3
??:??:?? 0 Expanding short PSK #1
??:??:?? 0 Wanted region 0, using Unset
??:??:?? 0 region=0, NODENUM=0x336a8e95, dbsize=1
??:??:?? 0 AXP192 not found
??:??:?? 0 Read RTC time as 0 (cur millis 101) quality=0
??:??:?? 0 WANT GPS=1
??:??:?? 0 Setting GPS power=1
??:??:?? 0 Connected to UBLOX GPS successfully
??:??:?? 2 External Notification Plugin Disabled
??:??:?? 2 NOTE! Recording critical error 6 at src/main.cpp:1d5
??:??:?? 2 Turning on screen
??:??:?? 2 Starting meshradio init...
??:??:?? 2 (bw=125, sf=12, cr=4/8) packet symLen=32 ms, payloadSize=16, time 226 9 ms
??:??:?? 2 Set radio: name=LongSlow, config=3, ch=0, power=0
??:??:?? 2 Radio myRegion->freq: 903.080017
??:??:?? 2 Radio myRegion->spacing: 2.160000
??:??:?? 2 Radio myRegion->numChannels: 13
??:??:?? 2 Radio channel_num: 0
??:??:?? 2 Radio frequency: 903.080017
??:??:?? 2 Short packet time: 2269 msec
??:??:?? 2 Set radio: final power level=17
??:??:?? 2 RF95 init result 0
??:??:?? 2 RF95 Radio init succeeded, using RF95 radio
??:??:?? 2 PowerFSM init, USB power=1
[D][esp32-hal-cpu.c:189] setCpuFrequencyMhz(): PLL: 320 / 4 = 80 Mhz, APB: 80000 000 Hz
??:??:?? 2 [Screen] Screen: Started...
??:??:?? 2 [GPS] publishing GPS lock=0
??:??:?? 2 [GPS] No GPS lock
??:??:?? 2 [GPS] got gps notify time=0, lat=0, bat=0
??:??:?? 2 [GPS] DB update position node=0x336a8e95 time=0, latI=0, lonI=0
??:??:?? 2 [GPS] Node status update: 1 online, 1 total
??:??:?? 2 [SerialPlugin] Serial Plugin Disabled
??:??:?? 2 [StoreForwardPlugin] Store & Forward Plugin - Disabled
??:??:?? 2 [RangeTestPlugin] Range Test Plugin - Disabled
Transition powerFSM transition=boot timeout, from=BOOT to=POWER
??:??:?? 5 [Power FSM] Setting bluetooth enable=1
Pre BT: 209372 heap size
??:??:?? 5 [PowerFSM] Starting bluetooth
??:??:?? 5 [Screen] Done with boot screen...
??:??:?? 5 [Screen] Screen: Powered...
??:??:?? 5 [Screen] showing standard frames
??:??:?? 5 [Screen] Showing 0 plugin frames
??:??:?? 5 [Screen] Total frame count: 35
??:??:?? 5 [Screen] Added plugins. numframes: 0
??:??:?? 5 [Screen] Finished building frames. numframes: 3
??:??:?? 5 [Screen] Setting fast framerate
??:??:?? 6 [Screen] BLE task running
??:??:?? 6 [Screen] registered service 0x1800 with handle=1
??:??:?? 6 [Screen] registered service 0x1801 with handle=6
??:??:?? 6 [Screen] registered service 6ba1b218-15a8-461f-9fa8-5dcae273eafd with handle=10
??:??:?? 6 [Screen] registered service cb0b9a0b-a84c-4c0d-bdbb-442e3144ee30 with handle=18
[D][esp32-hal-i2c.c:1345] i2cProcQueue(): Gross Timeout Dead start=0x18e6, end= 0x18e6, =0, max=50 error=1
[E][esp32-hal-i2c.c:318] i2cDumpI2c(): i2c=0x3ffbe2c8
[I][esp32-hal-i2c.c:319] i2cDumpI2c(): dev=0x60013000 date=0x16042000
[I][esp32-hal-i2c.c:321] i2cDumpI2c(): lock=0x3ffbbed8
[I][esp32-hal-i2c.c:323] i2cDumpI2c(): num=0
[I][esp32-hal-i2c.c:324] i2cDumpI2c(): mode=1
[I][esp32-hal-i2c.c:325] i2cDumpI2c(): stage=3
[I][esp32-hal-i2c.c:326] i2cDumpI2c(): error=1
[I][esp32-hal-i2c.c:327] i2cDumpI2c(): event=0x3ffbade4 bits=10
[I][esp32-hal-i2c.c:328] i2cDumpI2c(): intr_handle=0x3ffbab50
[I][esp32-hal-i2c.c:329] i2cDumpI2c(): dq=0x3ffd9534
[I][esp32-hal-i2c.c:330] i2cDumpI2c(): queueCount=1
[I][esp32-hal-i2c.c:331] i2cDumpI2c(): queuePos=0
[I][esp32-hal-i2c.c:332] i2cDumpI2c(): errorByteCnt=2
[I][esp32-hal-i2c.c:333] i2cDumpI2c(): errorQueue=0
[I][esp32-hal-i2c.c:334] i2cDumpI2c(): debugFlags=0x00000000
[I][esp32-hal-i2c.c:311] i2cDumpDqData(): Debug Buffer not Enabled
[I][esp32-hal-i2c.c:354] i2cDumpInts(): Debug Buffer not Enabled
??:??:?? 6 [Screen] BLE advertisting type=0, Private=0, Device Address: 85:c4:4f :33:6a:8e
??:??:?? 6 [Screen] Setting idle framerate
??:??:?? 32 [NodeInfoPlugin] Sending our nodeinfo to mesh (wantReplies=1)
??:??:?? 32 [NodeInfoPlugin] sending owner !336a8e95/Unknown 8e95/?95
??:??:?? 32 [NodeInfoPlugin] Update DB node 0x336a8e95, rx_time=0
??:??:?? 32 [NodeInfoPlugin] handleReceived (id=0x4552aee1 Fr0x95 To0xff, WantAc k0, HopLim3 Ch0x0 Portnum=4 WANTRESP priority=10)
??:??:?? 32 [NodeInfoPlugin] Plugin nodeinfo wantsPacket=1
??:??:?? 32 [NodeInfoPlugin] Received nodeinfo from=0x336a8e95, id=0x4552aee1, p ortnum=4, payloadlen=40
??:??:?? 32 [NodeInfoPlugin] old user !336a8e95/Unknown 8e95/?95
??:??:?? 32 [NodeInfoPlugin] updating changed=0 user !336a8e95/Unknown 8e95/?95
??:??:?? 32 [NodeInfoPlugin] Plugin nodeinfo considered
??:??:?? 32 [NodeInfoPlugin] Plugin routing wantsPacket=1
??:??:?? 32 [NodeInfoPlugin] Received routing from=0x336a8e95, id=0x4552aee1, po rtnum=4, payloadlen=40
??:??:?? 32 [NodeInfoPlugin] Routing sniffing (id=0x4552aee1 Fr0x95 To0xff, Want Ack0, HopLim3 Ch0x0 Portnum=4 WANTRESP priority=10)
??:??:?? 32 [NodeInfoPlugin] FIXME-update-db Sniffing packet
??:??:?? 32 [NodeInfoPlugin] Delivering rx packet (id=0x4552aee1 Fr0x95 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=4 WANTRESP priority=10)
??:??:?? 32 [NodeInfoPlugin] Forwarding to phone (id=0x4552aee1 Fr0x95 To0xff, W antAck0, HopLim3 Ch0x0 Portnum=4 WANTRESP priority=10)
??:??:?? 32 [NodeInfoPlugin] Update DB node 0x336a8e95, rx_time=0
??:??:?? 32 [NodeInfoPlugin] Plugin routing considered
??:??:?? 32 [NodeInfoPlugin] Adding packet record (id=0x4552aee1 Fr0x95 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=4 WANTRESP priority=10)
??:??:?? 32 [NodeInfoPlugin] Expanding short PSK #1
??:??:?? 32 [NodeInfoPlugin] Installing AES128 key!
??:??:?? 32 [NodeInfoPlugin] enqueuing for send (id=0x4552aee1 Fr0x95 To0xff, Wa ntAck0, HopLim3 Ch0xb1 encrypted priority=10)
??:??:?? 32 [NodeInfoPlugin] (bw=125, sf=12, cr=4/8) packet symLen=32 ms, payloa dSize=62, time 4694 ms
??:??:?? 32 [NodeInfoPlugin] txGood=0,rxGood=0,rxBad=0
??:??:?? 32 [NodeInfoPlugin] AirTime - Packet transmitted : 4694ms
??:??:?? 32 [Screen] Screen: Joined: Unknown 8e95
??:??:?? 33 [RadioIf] Starting low level send (id=0x4552aee1 Fr0x95 To0xff, Want Ack0, HopLim3 Ch0xb1 encrypted priority=10)
??:??:?? 37 [RadioIf] Completed sending (id=0x4552aee1 Fr0x95 To0xff, WantAck0, HopLim3 Ch0xb1 encrypted priority=10)
The critical part of the log is:
??:??:?? 0 AXP192 not found
??:??:?? 0 Read RTC time as 0 (cur millis 101) quality=0
??:??:?? 0 WANT GPS=1
??:??:?? 0 Setting GPS power=1
??:??:?? 0 Connected to UBLOX GPS successfully
??:??:?? 2 External Notification Plugin Disabled
??:??:?? 2 NOTE! Recording critical error 6 at src/main.cpp:1d5
The firmware has not been able to communicate with the AXP192 power management chip. Some people have had success fixing this by trying to reflow the solder joints on the AXP192. Sometimes reflashing the firmware helps in case there was an error in the initial writing of it. Sometimes the chip is just broken. Otherwise the tbeam will usually continue to work, you just won’t have proper power management, battery charging, etc.
Edited to add I probably wouldn’t try charging any batteries with it, just in case they explode!
1 Like
thank you,
I have 3 of them, first I made a mistake when I put the screen so I had to heat it too much, It sounds logical that I broke somtthning, it was the AXP192 that was broken… 1 months later the screen stoped working also… but the second one I did very careful and it worked with previous version so I will downgrade the firmware to check. Two solutions: Firmware bug or this board is a piece of shit.
I have my answer: I’ve big doubt about the LILYGO® TTGO Meshtastic T-Beam V1.1 ESP32 868 quality…
And you’re perfectly right!
I had a failure on my t-beam 1.1 with axp192. I had a friend replace the IC for me and now my GPS does not work. I don’t think I’ll be getting any more t-beams.
I have two T-Beam v1.0 AXP192 chip are bad, install the battery will be hot to explode, can only use USB power.
1 Like
Is there a step by step guide on how to properly acess the boot log? I have very little experience with command line interfaces and would like to provide the seller with a log for my TBeams error code 6. I ordered 3 and 2 work fine so Im sure its not a firmware issue.
1 Like
No need to read the logs. If it says critical fault 6 the axp192 is busted.
Current critical error code documentation link