ooh - I just reread this thread (sorry - so many threads). I didn’t realize you weren’t running meshtastic! I think dafeman was correct - you’ll need to turn on GPS power via the axp192.
Actually, i did just flash the meshtastic firmware, firmware-tbeam0.7-US-0.9.1.bin!
This the output on the serial monitor @ 115200 bps:
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, 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:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:8896
load:0x40080400,len:5828
entry 0x400806ac
[D][esp32-hal-psram.c:47] psramInit(): PSRAM enabled
v⸮c⸮⸮⸮_#⸮⸮ ⸮⸮g⸮⸮⸮⸮⸮j⸮⸮/⸮#E⸮XH⸮0⸮a%Iw⸮⸮;⸮⸮⸮⸮⸮{⸮#0⸮⸮⸮⸮{⸮…
it looks like it’s booting then switching to a different port speed?? Also, still no power to GPS or AXP that i can see.
You need to use the firmware-tbeam-US-0.9.1 .bin not the tbeam0.7. The earlier version does not have an AXP192 PMU.
Yep you are correct, it runs the debug serial at 921600. PuTTY is a good option for viewing the output if your current serial terminal doesn’t support 921600.
1 Like
Okay so that’s one thing corrected. Flashed the proper file (and many thanks for that!), here’s my output:
Hbooted, wake cause 0 (boot count 1), reset_reason=reset
No I2C devices found
Meshtastic swver=0.9.1, hwver=1.0-US
Setting random seed 1462714770
Total heap: 265576
Free heap: 238388
Total PSRAM: 4194252
Free PSRAM: 4194252
NVS: UsedEntries 68, FreeEntries 562, AllEntries 630
AXP192 not found
Read RTC time as 0 (cur millis 50) valid=0
ERROR: No UBLOX GPS found
Hoping that NEMA might work
RadioConfig reset!
Installing AES128 key!
Initial packet id 1847518185, numPacketId 4294967295
Loading saved preferences
Warn: devicestate is old, discarding
RadioConfig reset!
Installing AES128 key!
Installing AES128 key!
NODENUM=0xabf84e88, dbsize=1
Starting meshradio init…
Set radio: name=Default, config=3, ch=6, power=23
RF95 init result 0
[D][esp32-hal-cpu.c:189] setCpuFrequencyMhz(): PLL: 320 / 4 = 80 Mhz, APB: 80000000 Hz
sending owner !2462abf84e88/Unknown 4e88/?88
Update DB node 0xabf84e88, rx_time=0
old user !2462abf84e88/Unknown 4e88/?88
updating changed=0 user !2462abf84e88/Unknown 4e88/?88
Adding packet record (id=0x6e1ee3ed Fr0x88 To0xff, WantAck0, HopLim3 Payload:User)
enqueuing for send (id=0x6e1ee3ed Fr0x88 To0xff, WantAck0, HopLim3 encrypted)
txGood=0,rxGood=0,rxBad=0
Battery -3mV 0%
Starting low level send (id=0x6e1ee3ed Fr0x88 To0xff, WantAck0, HopLim3 encrypted)
Transition powerFSM transition=boot timeout, from=BOOT to=ON
Setting bluetooth enable=1
Pre BT: 226208 heap size
Starting bluetooth
BLE task running
registered service 0x1800 with handle=1
registering characteristic 0x2a00 with def_handle=2 val_handle=3
registering characteristic 0x2a01 with def_handle=4 val_handle=5
registered service 0x1801 with handle=6
registering characteristic 0x2a05 with def_handle=7 val_handle=8
registered service 6ba1b218-15a8-461f-9fa8-5dcae273eafd with handle=10
registering characteristic f75c76d2-129e-4dad-a1dd-7866124401e7 with def_handle=11 val_handle=12
registering characteristic 8ba2bcc2-ee02-4a55-a531-c525c5e454d5 with def_handle=13 val_handle=14
registering characteristic ed9da18c-a800-4f66-a670-aa7547e34453 with def_handle=15 val_handle=16
FromNum handle 16
registered service cb0b9a0b-a84c-4c0d-bdbb-442e3144ee30 with handle=18
registering characteristic e74dd9c0-a301-4a6f-95a1-f0e1dbea8e1e with def_handle=19 val_handle=20
registering characteristic e272ebac-d463-4b98-bc84-5cc1a39ee517 with def_handle=21 val_handle=22
registering characteristic 4826129c-c22a-43a3-b066-ce8f0d5bacc6 with def_handle=23 val_handle=24
registering characteristic 5e134862-7411-4424-ac4a-210937432c77 with def_handle=25 val_handle=26
update result handle 26
Addr type 0, Private=0, Device Address: f9:24:62:ab:f8:4e
Completed sending (id=0x6e1ee3ed Fr0x88 To0xff, WantAck0, HopLim3 encrypted)
So i’m not seeing any good news here…
1 Like
Hmm, not good news it would seem. Failing to find the AXP192 with both Meshtastic and the Arduino sketch likely means a dud AXP192 or poor PCB assembly.
1 Like
My other unit accepted the firmware and looks like everything is A-OK:
Hbooted, wake cause 0 (boot count 1), reset_reason=reset
I2C device found at address 0x34
axp192 PMU found
I2C device found at address 0x3c
ssd1306 display found
done
Meshtastic swver=0.9.1, hwver=1.0-US
Setting random seed 904547957
Total heap: 265576
Free heap: 238388
Total PSRAM: 4194252
Free PSRAM: 4194252
NVS: UsedEntries 68, FreeEntries 562, AllEntries 630
chip id detect 0x3
Detect CHIP :AXP192
OUTPUT Register 0x5f
AXP192 Begin PASS
DCDC1: ENABLE
DCDC2: ENABLE
LDO2: ENABLE
LDO3: ENABLE
DCDC3: ENABLE
Exten: ENABLE
/--------------------------
DCDC1: ENABLE
DCDC2: ENABLE
LDO2: ENABLE
LDO3: ENABLE
DCDC3: ENABLE
Exten: ENABLE
SRC REG:0xcf
Charging enable is enable
Charging target-voltage : 0x2
end when the charge current is lower than 10% of the set value
Charge current : 1000.00 mA
enable [0x40]val:0xdc
enable [0x41]val:0xff
enable [0x42]val:0x3b
Turning on screen
Read RTC time as 0 (cur millis 131) valid=0
Connected to UBLOX GPS successfully
RadioConfig reset!
Installing AES128 key!
Initial packet id 335380177, numPacketId 4294967295
Loading saved preferences
Warn: devicestate is old, discarding
RadioConfig reset!
Installing AES128 key!
Installing AES128 key!
NODENUM=0xabf83ec4, dbsize=1
Starting meshradio init…
Set radio: name=Default, config=3, ch=6, power=23
RF95 init result 0
[D][esp32-hal-cpu.c:189] setCpuFrequencyMhz(): PLL: 320 / 4 = 80 Mhz, APB: 80000000 Hz
sending owner !2462abf83ec4/Unknown 3ec4/?C4
Update DB node 0xabf83ec4, rx_time=0
old user !2462abf83ec4/Unknown 3ec4/?C4
updating changed=0 user !2462abf83ec4/Unknown 3ec4/?C4
Adding packet record (id=0x13fd7ed5 Fr0xc4 To0xff, WantAck0, HopLim3 Payload:User)
enqueuing for send (id=0x13fd7ed5 Fr0xc4 To0xff, WantAck0, HopLim3 encrypted)
txGood=0,rxGood=0,rxBad=0
Screen: Started…
Battery 4140mV 100%
GPS fix type 0
Ignoring invalid GPS month=0, year=47333, unixtime=-1
New GPS pos lat=0.000000, lon=0.000000, alt=0, pdop=0.000000, heading=0.000000, sats=60
showing standard frames
Starting low level send (id=0x13fd7ed5 Fr0xc4 To0xff, WantAck0, HopLim3 encrypted)
Transition powerFSM transition=boot timeout, from=BOOT to=ON
Setting bluetooth enable=1
Pre BT: 223184 heap size
Starting bluetooth
BLE task running
registered service 0x1800 with handle=1
registering characteristic 0x2a00 with def_handle=2 val_handle=3
registering characteristic 0x2a01 with def_handle=4 val_handle=5
registered service 0x1801 with handle=6
registering characteristic 0x2a05 with def_handle=7 val_handle=8
registered service 6ba1b218-15a8-461f-9fa8-5dcae273eafd with handle=10
registering characteristic f75c76d2-129e-4dad-a1dd-7866124401e7 with def_handle=11 val_handle=12
registering characteristic 8ba2bcc2-ee02-4a55-a531-c525c5e454d5 with def_handle=13 val_handle=14
registering characteristic ed9da18c-a800-4f66-a670-aa7547e34453 with def_handle=15 val_handle=16
FromNum handle 16
registered service cb0b9a0b-a84c-4c0d-bdbb-442e3144ee30 with handle=18
registering characteristic e74dd9c0-a301-4a6f-95a1-f0e1dbea8e1e with def_handle=19 val_handle=20
registering characteristic e272ebac-d463-4b98-bc84-5cc1a39ee517 with def_handle=21 val_handle=22
registering characteristic 4826129c-c22a-43a3-b066-ce8f0d5bacc6 with def_handle=23 val_handle=24
registering characteristic 5e134862-7411-4424-ac4a-210937432c77 with def_handle=25 val_handle=26
update result handle 26
Addr type 0, Private=0, Device Address: f9:24:62:ab:f8:3e
Completed sending (id=0x13fd7ed5 Fr0xc4 To0xff, WantAck0, HopLim3 encrypted)
1 Like
On the dud unit have you got anything attached to the I2C pins (eg LCD) that could be holding the pins 21 and 22 low/high? It would pay to remove anything from those pins first and try again.
1 Like
i have nothing connected to the I2C pins at all. It’s the twin of the other board but i guess i’m out $50 
oh poo.
Good board:
GPS fix type 3
Update DB node 0xabf83ec4, rx_time=1596488772
Node status update: 1 online, 1 total
New GPS pos lat=XX.276014, lon=-XX.755113, alt=83, pdop=2.600000, heading=0.000000, sats=6
Battery 4132mV 100%
As an endnote, i really do thank you all for the help with this. DOA board it seems.
Well something in the AXP192 is still alive because it is powering the ESP32 so not all hope is lost. But without getting deep into bus monitoring and PCB fault finding you may be out of luck. If you have a multi meter you could check the basics that pins 21 and 22 are pulled high (3.3V) with power on. Although you had an I2C LCD working didn’t you?
Well, i’ll flog this horse and break out my multimeter… will reply shortly
1 Like
The TBeam datasheet may be helpful. https://github.com/meshtastic/Meshtastic-device/blob/post1/docs/hardware/T_BeamV1.0.pdf
Okay, 5V = 4.97v but 3.3v = 1.80v… i wonder if the AXP has been put into sleep mode? I thought i read somewhere that there’s a bug regarding deep sleep mode.
Are header pins 21 and 22 at 3.3V? I have read about an issue where they were powering the screen off with the AXP192 and then the screen was holding the I2C pins to ransom so you couldn’t turn it on again! Not related here though sorry.
No voltage on both pins.
Odd. But you have 1.8V between the 3V3 and GND pins next to pins 22 and 21?
Also - if it helps I’ve bought a bunch of TTGO boards and received a couple of duds. Each time I had a dud they happily sent a replacement (but yeah - another long wait)
@dafeman:
Yes, i had an OLED soldered on before and it worked fine. Since last reply, running Meshtastic 0.9.1, these are the voltages:
GND to pin 21 (SDA) = 3.27v
GND to pin 22 (SCL) = 3.27v
@geeksville:
TBH, i’d rather be molested by a koala than wait 6+ months for a replacement. Unless we can figure out how to access the AXP chip and turn it on, i’ll just swallow the loss and get another one. 
1 Like
can confirm. i did this a few days ago, board is fried after placing battery in backwards, warm axp192 chip.
nothing works tho. no response from board in putty at all. esp flasher times out when attempting to
re-flash.
1 Like
Just found this: https://www.thethingsnetwork.org/forum/t/ttgo-t-beam-v1-0-oled-deep-sleep-needs-proper-power-design/30800/46 and it sounds like what i am encountering.
But you said
You also had the OLED working with SoftRF didn’t you? If you do have an OLED attached I would remove it and have another go at it.