Warning: Failed to find SX1262 radio

Support
1

Hi all,

I’m new to this project, but excited about it. I bought two of the following radios:
https://www.aliexpress.com/item/1005001446909901.html?spm=a2g0s.9042311.0.0.1cc14c4dnSnozU

I purchased the 915MHz flavor since I’m in the US. I purchased two OLED modules, but apparently bought the wrong ones since the pinout doesn’t match the pin ordering … no big deal, I’ve got other ones ordered, I mention that because I don’t have an LED display active and am doing all debug over serial.

I’ve been able to connect via bluetooth, I’ve seen the GPS’s lock on my location, I’ve shared a channels with both the radios, but the two radios never discover each other. In the bootup process, I get the warning “Warning: Failed to find SX1262 radio”. I’m assuming the Lora radio is never initialized. I’ll paste in my bootup log. Any ideas on what might be wrong. Both units I purchased are doing the same thing.

FYI, I’ve flashed both the firmware-tbeam-US-1.1.5.bin and firmware-tbeam-US-1.0.0.bin on the boards and both sets of firmware are doing the same thing.

Thanks in advance for helping me with this. I really want to use this project.

Eric

booted, wake cause 0 (boot count 1), reset_reason=reset
I2C device found at address 0x34
axp192 PMU found
done
Meshtastic swver=1.1.5, hwver=1.0-US
Setting random seed 3024016252
Total heap: 251752
Free heap: 224124
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
Read power stat 1
Battery 4177mV 100%
Read RTC time as 0 (cur millis 77) quality=0
WANT GPS=1
Setting GPS power=1
Connected to UBLOX GPS successfully
Setting default preferences!
Installing AES128 key!
Initial packet id 1156077522, numPacketId 4294967295
Loading saved preferences
Loaded saved preferences version 11
Installing AES128 key!
legacy_region=1.0-US, region=1, NODENUM=0xb22421d8, dbsize=1
Wanted region 1, using US
Starting meshradio init...
Set radio: name=Default, config=3, ch=6, power=0
Radio myRegion->freq: 903.080017
Radio myRegion->spacing: 2.160000
Radio myRegion->numChannels: 13
Radio channel_num: 6
Radio frequency: 916.040039
Set radio: final power level=17
RF95 init result -2
Warning: Failed to find RF95 radio
Starting meshradio init...
Set radio: name=Default, config=3, ch=6, power=0
Radio myRegion->freq: 903.080017
Radio myRegion->spacing: 2.160000
Radio myRegion->numChannels: 13
Radio channel_num: 6
Radio frequency: 916.040039
Set radio: final power level=22
SX1262 init result -2
Warning: Failed to find SX1262 radio
NOTE! Recording critical error 3, address=0
PowerFSM init, USB power=1
[D][esp32-hal-cpu.c:189] setCpuFrequencyMhz(): PLL: 320 / 4 = 80 Mhz, APB: 80000000 Hz
Read power stat 1
publishing GPS lock=0
No GPS lock
Sending position to mesh
Update DB node 0xb22421d8, rx_time=0
Node status update: 1 online, 1 total
Stripping time 0 from position send
Adding packet record (id=0x44e857d5 Fr0xd8 To0xff, WantAck0, HopLim3 Payload:Position)
Dropping packet - no interfaces - fr=0xb22421d8,to=0xffffffff,id=1156077525
sending owner !ac67b22421d8/Unknown 21d8/?D8
Update DB node 0xb22421d8, rx_time=0
old user !ac67b22421d8/Unknown 21d8/?D8
updating changed=0 user !ac67b22421d8/Unknown 21d8/?D8
Adding packet record (id=0x44e857d6 Fr0xd8 To0xff, WantAck0, HopLim3 Payload:User)
Dropping packet - no interfaces - fr=0xb22421d8,to=0xffffffff,id=1156077526
publishing GPS lock=0
No GPS lock
Update DB node 0xb22421d8, rx_time=0
Node status update: 1 online, 1 total
Setting RTC 1606225285 secs
Read RTC time as 1606225285 (cur millis 6279) quality=2
publishing GPS lock=0
Update DB node 0xb22421d8, rx_time=1606225285
Node status update: 1 online, 1 total
Transition powerFSM transition=boot timeout, from=BOOT to=POWER
Setting bluetooth enable=1
Pre BT: 213436 heap size
Starting bluetooth
BLE task running
registered service 0x1800 with handle=1
registered service 0x1801 with handle=6
registered service 6ba1b218-15a8-461f-9fa8-5dcae273eafd with handle=10
registered service cb0b9a0b-a84c-4c0d-bdbb-442e3144ee30 with handle=18
BLE advertisting type=0, Private=0, Device Address: b5:ac:67:b2:24:21
1 Like
2

Hi @ericjmonson,

maybe you have a display type where you can change two resistors to swap gnd and power pin. See here.

But this is for sure not your highest priority :wink:

What exact version label do you have on your boards? It is very strange that both suffer the same issue.

3

Why you don’t swap the two pin of the screen with a pice of cable?

4

Your t-beam’s could be the older SX1276 version. Verify the printing on shield says sx1262. If it is the original 915Mhz version you should still get it working with the firmware you selected (just slightly less sensitivity)

5

This is the SX1276. So this must be a SPI problem. The return code ‘-2’ is returned by the SPI class.

This is why I asked for the exact board labeling.

6

IMG-2783
IMG-27834032×3024 2.18 MB

The link I provided is the exact model I purchased. Claims to be a SX1262. Here’s a picture of my unit.

1 Like
7

I have the exact same boards, but use them with 865MHz. I startet with fw 0.9.7 i think. Maybe give it a try. At the moment they run on 1.1.8.

I would check if there are bad solder connections and that nothing is shorted (the default GPS Antenna placement is suboptimal in my opinion).

1 Like
8

Ok … so I must have gotten myself confused last night when looking through the logs. It appears that only one of the units is reporting the error message, and the other appears to be working. I must have a faulty unit. I’ll apply for a refund on AliExpress and wait the 2 months for a replacement to come in.

2 Likes
9

yes alas - I’m glad everyone was able to help with answers. But something does seem busted on that unit. The firmware first tries to find an old RF95/SX1276 based radio then tries to find a SX1262. Your 1262 was found but it failed during init. so yeah bummer - but the seller will have to send a replacement/refund.

1 Like
10

i have 2 of this board and on my units i have to add soldering on sx1262 pin because of SPI error sometime, it solved all SPI error

3 Likes
11

So one of my units has a weak GPS signal compared to the other. I thought it’s the antenna, because of a not properly soldered “antenna rf shield case”. But exchanging the antenna leads to the same result, also after properly placing/fixing the “rf shield”.

So thanks for your input @pheex, i will try resoldering the GPS piggyback board. Would be nice if this is the problem :+1:

1 Like
12

Ok, I resoldered the UBLOX unit, but unfortunately it did not improve the GPS signal reception. Too bad…