meshtastic
Add board and variant definitions for EBYTE_ESP32-S3
Accidentally closed https://github.com/meshtastic/firmware/pull/2841 when renaming the branch and can't reopen. This variant is intended to eventually have support for all 38.5x24mm EBYTE SPI LoRa modules, such as:
- E22-400M30S
- E22-400M33S
- E22-900M30S
- E220-400M30S
- E220-900M30S
- E32-400M30S
- E32-900M30S
Ensure that any other module has an identical pinout before its use!
🤖 Pull request artifacts
| file | commit |
|---|---|
pr2882-firmware-2.2.14.627b285.zip |
e64894c3a8aecbb55df216c44f2a0ed0fd1fe355 |
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
E32-400M30S and E32-900M30S use the SX1276, will work on firmware for this radio chip, can be tested on a user's radio module which uses it
Should wait for an answer to https://github.com/meshtastic/firmware/pull/2930#issuecomment-1796892532 too
For now I will wait untill someone is able to test other EBYTE modules to verify that 22 dBm output from the radio ID is safe, doesn't damage the radio, and is what results in and was inteded to be used to get the maximum power. For non-E22 models they would need to be tested separately, and they have a different internal LoRa IC power output capability.
It is guaranteed that boards with the E22-900M33S will be damaged by outputting 22 dBm out of the radio IC. Ideally the SX126x should have an integrated EEPROM which limits the output power settings to a certain maximum, although this is complicated by the fact that multiple parameters affects its output power.
However, I trust that people who replace the module with their own are able to do their proper research, so will now implement support for the 400M series too (of which there is also a 33S model).