ESP32: Ebyte E22 900M30S Board support

[tomuk5]

Based off the reference Meshtastic design:
https://github.com/NanoVHF/Meshtastic-DIY/blob/main/Schematics/E-Byte_E22/Mesh_Ebyte_E22-XXXM30S.pdf

• future pull req's to include further documentation additions to build this design and radio power output chart.

[jacobeva]

Very cool. Does it boot and run with your changes?

[tomuk5]

Boots and runs :) - i know i got the hardware part right as i flashed meshtastic to it and used it to prove i can send/receive and have the pins correct.

Only issue is the same one affecting ESP32 boards with the TX power mismatch preventing them from being used with Reticulum at the moment.

[jacobeva]

Excellent. Thank you for the hard work.

[tokio69]

Hello @tomuk5 , I have build this with the exact same pinout, esp32 , tranceiver,... But on the screen I get "Radio Not Found error"
In the scematic on the NanoVHF github I see that it has some flaws like where the RXEN (14) and TXEN (13) has to go, in the firmware it is not connected but on the scematic it is. Also GPIO26 and 33 seems to have contradictions in the scematic. I am sure it is just something small but I am already weeks trying to get a E22-900M30S working with a ESP32. Hope you can point me in the right direction on where to look further.

        18, // pin_ss
          5, // pin_sclk
          27, // pin_mosi
          19, // pin_miso
          32, // pin_busy
          33, // pin_dio
          23, // pin_reset
          **-1, // pin_txen**
          14, // pin_rxen
          -1  // pin_tcxo_enable

[tomuk5]

Hi @tokio69
There is a deviation from the schematic in that Pin 7 (TXEN) is not connected to GPIO13 at all, its instead connected/jumpered to Pin 8 (DIO2) on the E22 itself so that it can be used as a SoftRF switch.
Pin 13 (DIO1) on the E22 connects to GPIO33 and GPIO26 is not connected.