SX1280- LILYGO T3S3 at 2.4Ghz

[samuk]

Is this hardware likely to work with this firmware https://wiki.lilygo.cc/get_started/en/LoRa_GPS/T3S3/T3S3.html#Modules

Chip: ESP32-S3FH4R2
PSRAM: 2MB (Quad-SPI)
FLASH: 4MB (Quad-SPI)
SX1280

I see this https://github.com/jrl290/RTNode-HeltecV4/blob/main/sx128x.cpp so I'm thinking it may work?

Edit: This also seems hopeful https://github.com/jrl290/RTNode-HeltecV4/blob/main/platformio.ini#L150

[samuk]

This was reported working on Matrix

[samuk]

It seems like this works with this env

[env:lilygo-t3-s3-sx1280-pa-boundary] platform = espressif32 board = lilygo-t3-s3 custom_variant = t3s3_sx1280_pa_boundary board_build.filesystem = littlefs board_build.partitions = no_ota.csv monitor_speed = 921600 build_flags = ${env.build_flags} -DBOARD_MODEL=BOARD_T3S3 -DMODEM=SX1280 -DBOUNDARY_MODE -DRNS_USE_TLSF=1 -DRNS_USE_ALLOCATOR=1 ; --- Boundary mode defaults (override via config portal at runtime) --- ; TCP server mode (0=server, 1=client) -DBOUNDARY_TCP_MODE=0 ; TCP listen/connect port -DBOUNDARY_TCP_PORT=4242 lib_deps = ${env.lib_deps} XPowersLib@^0.2.1 monitor_filters = esp32_exception_decoder

Would you be interested in a pull request adding support for this board?

[GrayHatGuy]

@samuk
I have identified code changes that will permit the addition of both the Xiao esp32S3_wioSX1262 and the lilygo T3S3 sx1280(mentioned) above for boundary mode operation.

@jrl290 How do you want to proceed shall I push the commits to you?

[jrl290]

I think it might be best to fork this to your own repo. I can't test it myself since I don't have the hardware. We can both put up links to ours and any other ports that are made. Also, if I make any updates here, you'll be able to vet them before merging with your repo instead of possibly breaking the support

[GrayHatGuy]

Sonuds like a plan I was able to put a fork up this afternoon. Basically I have the 4 devices (v3 v4 XiaoESP32S3 and T3S3) working in boundary mode only I still have some work to do to enable the other modes. A few people are lined up for testing some are awaint delivery of devices so I'll field it from there
https://github.com/GrayHatGuy/RTNode-HeltecV4

[jrl290]

I suggest changing the "HeltecV4" part for ease of distinction

But I would be hesitant to expand the modes. While the firmware started out in Boundary mode, it became clear that more custom routing was required. It only passes through the addresses on its "LAN" side and anything that the "LAN" side devices reference themselves. Everything else gets blocked.

It doesn't change the functionality really. It just doesn't take responsibility for routing aside from when its relevant to the devices on its "LAN" side

Mind you, there's a pretty good amount of extra memory on the 2 MB chips. So you might be able to find a use for it. Just be aware, the routing in this firmware is not standard