Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README to list LilyGo TTGO v1 as a supported board. #5

Closed
saket424 opened this issue Feb 28, 2020 · 14 comments
Closed

Update README to list LilyGo TTGO v1 as a supported board. #5

saket424 opened this issue Feb 28, 2020 · 14 comments
Assignees
@saket424
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@saket424
Copy link

How hard would it be to add support for the https://github.com/LilyGO/TTGO-LORA-V1 in addition to Heltec board that you already support?

$36 for a pair of them and they have a nice 3d-printed case
https://www.aliexpress.com/item/32842155838.html
@geeksville
Copy link
Member

This would be super easy to add - because all of the TTGO devices are quite similar in most ways (I've used a bunch of them on previous projects). If you wanna get a couple of these devices and add the support I'm happy to provide further pointers/help. It should be mostly just a change to configuration.h

@geeksville
Copy link
Member

(temporarily marking you as a person who might be doing this ;-) )

@geeksville geeksville added enhancement New feature or request good first issue Good for newcomers labels Feb 28, 2020
@saket424
Copy link
Author

I bricked a TTGO v1 board by trying to flash the heltec image. I am unable to erase_flash anymore. Pretty stupid of me to have tried that.

I guess if you tell me exactly what changes I need to make to configuration.h for the TTGO v1 board, I am willing to attempt and sacrifice one more for this noble cause.

Thanks

@saket424
Copy link
Author

Hope this helps you in making a new configuration.h

https://github.com/espressif/arduino-esp32/blob/master/variants/ttgo-lora32-v1/pins_arduino.h

@geeksville
Copy link
Member

by coincidence it sounds like @claesg might be using this same board with success. I've asked him to chime in.

Btw: I think it is quite possible your board is not bricked. From looking at the docs you linked to, I didn't see anything fatally incompatible wrt the Heltec device. I suspect that if it is seriously messed up in the appload, the only thing you need to do to unbrick it is to hold GPIO 0 to ground while powering on the board (to keep it in the bootloader), then something like "esptool.py chip_id" should be able to see your board again.

I've accidentially flashed the heltec load on my ttgo beams many times without a problem.

@geeksville
Copy link
Member

though this did show a problem ;-) : https://github.com/geeksville/Meshtastic-esp32/issues/10

@claesg
Copy link
Contributor

claesg commented Feb 29, 2020

I have flashed the prebuilt 0.0.5 zipfiles to this board:
https://www.banggood.com/LILYGO-TTGO-LORA32-868Mhz-SX1276-ESP32-Oled-Display-bluetooth-WIFI-Lora-Development-Module-Board-p-1248652.html?cur_warehouse=UK
I think it is a V1 TTGO board.

@saket424
Copy link
Author

saket424 commented Mar 1, 2020

@geeksville
Your hunch was right, what i thought a bricked esp32 came back to life today on its own

@claesg
No such luck for me. When I tried flashing the pre-compiled 0.0.5 US, it just rolls in this

rst:0x10 (RTCWDT_RTC_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:251564
ets Jun 8 2016 00:22:57

@claesg
Copy link
Contributor

claesg commented Mar 1, 2020

@saket424
This is what it look like when I flash the Heltec build of 0.0.5 from the zip-file

check for boards:

$ esptool.py chip_id
esptool.py v2.6
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting........___
Detecting chip type... ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
MAC: 3c:71:bf:f0:86:ac
Uploading stub...
Running stub...
Stub running...
Warning: ESP32 has no Chip ID. Reading MAC instead.
MAC: 3c:71:bf:f0:86:ac
Hard resetting via RTS pin...

flash:

$ esptool.py write_flash 0x10000 release/latest/firmware-HELTEC-EU-0.0.5.bin
esptool.py v2.6
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
MAC: 3c:71:bf:f0:86:ac
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 1202416 bytes to 662970...
Wrote 1202416 bytes (662970 compressed) at 0x00010000 in 58.7 seconds (effective 163.7 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

@geeksville
Copy link
Member

hmm - I just looked at the pinouts and memory info at https://github.com/LilyGO/TTGO-LORA-V1

And I can't really help too much by debugging (I don't have that board type) remotely but it sure looks almost identical to the heltec board. I'm happy to help if you have questions but I suspect some local debugging will be involved.

@saket424
Copy link
Author

saket424 commented Mar 4, 2020

@geeksville ,
For the moment I have ordered a HELTEC v2 board from https://www.amazon.com/NEXTION-Display-Transceiver-Bluetooth-Development/dp/B07916Q3T6/ref=cm_cr_arp_d_product_top?ie=UTF8 and some TTBEAMs . After I am successful with them, I will try to figure out what makes the TTGO-V1 board different

Thanks

@saket424 saket424 closed this as completed Mar 4, 2020
@saket424
Copy link
Author

saket424 commented Mar 5, 2020

@geeksville and @claesg
Silly me. It was pilot error on my part. The LilyGO TTGO board works fine with the HELTEC firmware
I was flashing to 0x1000 instead of 0x10000 . That would do it

python3 -m esptool --chip esp32 --port /dev/ttyUSB1 --baud 115200 write_flash -z 0x10000 release/latest/firmware-HELTEC-US-0.1.0.bin

You can advertise that TTGO Lora v1 works fine on this meshtastic project

The only difference I could tell in the PINOUT connections is on the TTGOv1 board LED is at pin 2 and on the Heltec v2 board the LED pin is at pin 25. But I doubt that is worth a whole new configuration.h

@geeksville geeksville changed the title support for LilyGo TTGO v1 board ? Update README to list LilyGo TTGO v1 as a supported board. Mar 6, 2020
@geeksville geeksville reopened this Mar 6, 2020
@geeksville
Copy link
Member

ooh cool - thats good to know. yah, I could also see how flashing to 0x1000 could hurt bootability because there is some important system stuff esp32 stores down there.

I'm reopening this issue as "we should cleanup README.md to list supported devices in a table and add this new device." If you wanna submit a PR that's great but no pressure - we'll get to it someday.

@geeksville
Copy link
Member

README fixed by @claesg. Thanks!

geeksville pushed a commit that referenced this issue Sep 2, 2020
@Dafeman
Merge pull request #5 from meshtastic/master
7ca752c 
Merge latest
mc-hamster added a commit that referenced this issue Sep 19, 2020
@mc-hamster
Merge pull request #5 from meshtastic/dev-wifi
b1643e6 
Dev wifi
@mc-hamster mc-hamster mentioned this issue Jan 5, 2021
Closed
@newtocrypto newtocrypto mentioned this issue Dec 26, 2021
Closed
@GUVWAF GUVWAF mentioned this issue Apr 20, 2023
Merged
@mverch67 mverch67 mentioned this issue Aug 12, 2023
Merged
thebentern added a commit that referenced this issue Nov 5, 2023
@RicInNewMexico @thebentern
INA3221 / Power Telemetry Payload Variant Implementation (#2916)
f570204 
* INA3221 / Power Telemetry Variant Implementation
	modified:   platformio.ini
	modified:   src/configuration.h
	modified:   src/detect/ScanI2C.h
	modified:   src/detect/ScanI2CTwoWire.cpp
	modified:   src/main.cpp
	modified:   src/modules/Modules.cpp
	new file:   src/modules/Telemetry/PowerTelemetry.cpp
	new file:   src/modules/Telemetry/PowerTelemetry.h
	new file:   src/modules/Telemetry/Sensor/INA3221Sensor.cpp
	new file:   src/modules/Telemetry/Sensor/INA3221Sensor.h
	modified:   src/mqtt/MQTT.cpp

* ifdef for portduino / linux native
	modified:   src/modules/Telemetry/PowerTelemetry.cpp

* try #2
	modified:   src/modules/Modules.cpp
	modified:   src/modules/Telemetry/PowerTelemetry.cpp
	deleted:    variants/xiao_ble/1.0.0/libraries/SPI/SPI.cpp

* try #3
	modified:   src/modules/Modules.cpp

* try #4
	modified:   src/modules/Telemetry/PowerTelemetry.cpp

* try #5?
	modified:   src/modules/Telemetry/PowerTelemetry.cpp

* try #6
	modified:   src/modules/Telemetry/PowerTelemetry.cpp

---------

Co-authored-by: Ben Meadors <[email protected]>
@mverch67 mverch67 mentioned this issue Mar 11, 2024
Merged
@thebentern thebentern mentioned this issue Oct 10, 2024
Closed
@zhuzhe1983 zhuzhe1983 mentioned this issue Nov 5, 2024
Closed
rickmark pushed a commit to rickmark/meshtastic-firmware that referenced this issue Dec 26, 2024
@mc-hamster
Merge pull request meshtastic#5 from crossan007/add-data-rates-to-doc
8729bad 
fix Bw125Cr48Sf4096 comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@saket424 saket424

Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@geeksville @saket424 @claesg