-
Notifications
You must be signed in to change notification settings - Fork 214
Description
I would love to say exactly what the fix for this is, but I can only make some guesses.
My product is the "PA" version of the LilyGO T3S3 2.4 GHz LoRa board ( https://lilygo.cc/products/t3s3-v1-0?variant=42586879656117 )
After installing the latest tinyGS code via VSCode, a check of the serial monitor shows the device in a continuous boot loop.
After loading via the Web Flasher, the 'My TinyGS' wi-fi AP is available and you can log into the web interface to configure the device.
With valid MQTT & other settings entered, the device shows up in the list of tinyGS STATIONS and can be reached via the local LAN wi-fi. My test device has the name 'K4KDR_2g4_2'.
What does not work is the initialization of the LoRa radio ( -2 error ).
After MUCH research to confirm the pin values for this specific device - but with NO luck entering a Board Template that results in a successful radio start, I believe that the issue MIGHT be that there is a difference between the parameter string for an 'sx1280' -vs- this 'sx1280PA'.
Besides some different pin #'s for the latter, there are two additional parameters ( 'RADIO_RX_PIN' & 'RADIO_TX_PIN' ) as shown in one of the LilyGO examples at: https://github.com/Xinyuan-LilyGO/LilyGo-LoRa-Series/blob/master/examples/RadioLibExamples/Receive_Interrupt/utilities.h
The entire list of pin assignments for the sx1280PA are listed at: https://github.com/Xinyuan-LilyGO/LilyGo-LoRa-Series/blob/master/docs/en/t3_s3_sx1280pa/t3_s3_sx1280pa.md#-pins-map
... IF the solution to this is the addition of a new 'sx1280PA' radio definition, would you consider putting that on your to-do list? Or, if there is an easier work-around that I can accomplish on my own, I'll be glad to do so.
Thanks very much for considering this issue.
-Scott, K4KDR