Hello meshtastic users/devs, I have been reviewing the progress of this great project and I think it’s fantastic all that the community has achieved, well, my question is this module “ttgo lora32 v1.3” is compatible with the project?
It is a cheap module, allows a battery and is portable
I checked the spreadsheet and I think it doesn’t match with any already supported board.
Here is the pinout of the board
Would it be possible to support that board? Thank you very much <3
(alas no promises because I personally haven’t used this board but…) I just took a look at the schematic you linked. I think our existing “ttgo-lora32-v1” load should “just work” for that new 1.3 version. That said, it looks like they have added an extra button (which is a really useful feature which was missing from the old board). If you buy one of these boards and want us to add support for the extra button it would be easy (we’d add a new ttgo-lora32-v1.3 build). Just open a bug (preferably linking to this thread) and we can make the extra button do something.
Hi geeksville i dont remember the email from the another acount… but
I checked the datasheet and apparently one button is connected to reset and the other is connected to s_vp (gpio36).
I also think the gpio35 is connected to the battery to know its voltage, I think.
Sure! I will buy a couple but it will take some time to receive it
Thanks for the screen shots. I just checked our configuration file. The button and the battery doesn’t line up with any of the existing boards. It’ll be easy to add support for this.
Could I ask you to open a feature request for this?
I’ll find time to make a custom firmware for you to try out.
Let me know when you have your boards. I’ll send you a private build to test out before I include it into the package for the released firmware bundles.
… it’s my first time adding a target board to this project and I’m just lightly nervous because I don’t have one of those to try out myself. Will need your feedback to confirm it works.
I do see that series of boards have a bug on our firmware for battery monitoring, so no guarantees that’ll work.
Hi Arne, yes, @mc-hamster added provisional support for your board based on this thread. But I think you are the first person to actually have have one in their hands. So there could be problems.
Could you connect to the board with a serial terminal at at 921600 baud, then press the reset button? If you could post the first 100ish lines it prints we could probably see why the screen didn’t work.
I received LORA32 v1.3 and LORA 32 v2.1 devices today.
For the v2 board the firmware installation went well, I can connect to the app, seems all good
For the v1 board I am having difficulties installing the latest firmware (firmware-tlora-v1-1.2.11.bin). I run
python -m esptool --baud 921600 write_flash 0x10000 firmware-tlora-v1-1.2.11.bin
esptool.py v3.0
Found 3 serial ports
Serial port /dev/cu.usbserial-0001
Connecting.....
Detecting chip type... ESP32
Chip is ESP32-D0WDQ6-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 26MHz
MAC: c4:4f:33:7f:6f:89
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Compressed 1573152 bytes to 927003...
Wrote 1573152 bytes (927003 compressed) at 0x00010000 in 19.5 seconds (effective 644.8 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
but the display won’t turn on after restarting. The red LED is flashing and it seems not to show as a bluetooth device. Also:
meshtastic --info
…
Timed out waiting for connection completion
There was some other firmware on it before and when I turned it on for the first time there was some output on the display. So I am sure the hardware/display is okay.
It seems that I picket the wrong firmware for this board, or I ordered the wrong board that might not even be supported. How can I find out?
Hi, I use firmware-tlora-v1-1.2.11.bin and it seems to me there is only one firmware file for all frequencies now and frequency needs to be configured instead of selected by the firmware file (since 1.2?) - I would configure 433MHz as soon as I could connect to the device.