Actually I have just noticed that the successful debug message is only intermittently received. Sometimes it does fall back to NMEA. When using the T-Beam reset button it is almost 50/50 as to whether it uses UBX or not. Also, I got this log on one of the resets…
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=unset, hwver=unset
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 1 (cur millis 1529) valid=0
Connected to UBLOX GPS successfully
assertion “ok” failed: file “src\gps\UBloxGPS.cpp”, line 53, function: virtual bool UBloxGPS::setup()
abort() was called at PC 0x401086cf on core 1
Backtrace: 0x400950e4:0x3ffd9780 0x40095315:0x3ffd97a0 0x401086cf:0x3ffd97c0 0x400d5e21:0x3ffd97f0 0x400d69c2:0x3ffd9820 0x400ec597:0x3ffd9850 0x400913f9:0x3ffd9870
Rebooting…