Not working on Heltec V3/V4 – is this supported? #5

Open
opened 2026-10-05 06:05:58 +02:00 by adam · 11 comments
Owner

I’m currently trying to get lunarcore running, but so far without success.

I’ve tested it on:
• Heltec WiFi LoRa 32 V3
• Heltec WiFi LoRa 32 V4

Unfortunately, I wasn’t able to get it working on either board.

Is anyone successfully running lunarcore?

If yes, could you please share:
• The exact hardware (board + radio chip)
• Firmware version / branch used
• Any required configuration changes
for repeater or companion

It would be very helpful to know if the project is confirmed working on Heltec V3 or V4, or if specific hardware is required.

Thanks in advance for any clarification.

I’m currently trying to get lunarcore running, but so far without success. I’ve tested it on: • Heltec WiFi LoRa 32 V3 • Heltec WiFi LoRa 32 V4 Unfortunately, I wasn’t able to get it working on either board. Is anyone successfully running lunarcore? If yes, could you please share: • The exact hardware (board + radio chip) • Firmware version / branch used • Any required configuration changes for repeater or companion It would be very helpful to know if the project is confirmed working on Heltec V3 or V4, or if specific hardware is required. Thanks in advance for any clarification. <!-- github-sync-id:3984762679 -->
Author
Owner

i got it to boot once on v3 3.2. I have no idea what i did to get it to run, it just randomly ran once.....i was unable to connect with anything and the screen was weirdly dim. Theres something whacky with the pins i assume.

yes i saw something on the screen once. no ive never seen anything more than that

i got it to boot once on v3 3.2. I have no idea what i did to get it to run, it just randomly ran once.....i was unable to connect with anything and the screen was weirdly dim. Theres something whacky with the pins i assume. yes i saw something on the screen once. no ive never seen anything more than that <!-- github-comment-id:3962602169 -->
Author
Owner

i have two heltec v3's 3.2, should i try or it's a bad deal?

i have two heltec v3's 3.2, should i try or it's a bad deal? <!-- github-comment-id:4088416329 -->
Author
Owner

i have two heltec v3's 3.2, should i try or it's a bad deal?

dont waste time unless you can fix code

> i have two heltec v3's 3.2, should i try or it's a bad deal? dont waste time unless you can fix code <!-- github-comment-id:4104520523 -->
Author
Owner

I somehow got it working but problem is that neither of the apps want to connect to it not even wiht serial ill try meshtastic cli and see what it will do

I somehow got it working but problem is that neither of the apps want to connect to it not even wiht serial ill try meshtastic cli and see what it will do <!-- github-comment-id:4113603852 -->
Author
Owner

@straskyj09-prog any news?

@straskyj09-prog any news? <!-- github-comment-id:4582468773 -->
Author
Owner

@straskyj09-prog any news?

Even if u got this to work, its now so outdated I wouldnt bother

> @straskyj09-prog any news? Even if u got this to work, its now so outdated I wouldnt bother <!-- github-comment-id:4582562686 -->
Author
Owner

if anyone know rust maybe fork and add latest features to it?

if anyone know rust maybe fork and add latest features to it? <!-- github-comment-id:4582570674 -->
Author
Owner

if anyone know rust maybe fork and add latest features to it?

Even if you sprinkle glitter on a turd its still a turd.

Nobody has ever reliably gotten it to even boot.

> if anyone know rust maybe fork and add latest features to it? Even if you sprinkle glitter on a turd its still a turd. Nobody has ever reliably gotten it to even boot. <!-- github-comment-id:4582606007 -->
Author
Owner

except maybe xeros in #9

except maybe xeros in #9 <!-- github-comment-id:4582639631 -->
Author
Owner

@straskyj09-prog any news?

unfortunately no I've been on meshcore since I had two heltecs one for meshcore and one for meshtastic but ppl stopped to use meshtastic almost and one of my heltecs broke cuz I accidentally ripped the antenna connector off

> [@straskyj09-prog](https://github.com/straskyj09-prog) any news? unfortunately no I've been on meshcore since I had two heltecs one for meshcore and one for meshtastic but ppl stopped to use meshtastic almost and one of my heltecs broke cuz I accidentally ripped the antenna connector off <!-- github-comment-id:4590807358 -->
Author
Owner

Can confirm — same issue here on Heltec WiFi LoRa 32 V4.

Flashed lunarcore-esp32s3.bin (v1.1.0) via esptool after a full erase_flash. Boot proceeds normally through heap init, SPI flash detection, and driver init (I2C, timer, pcnt), but the device gets stuck in a reset loop right after main_task: Calling app_main() — no further log output, no display activity (screen stays blank), and the board resets itself repeatedly (rst:0x15 USB_UART_CHIP_RESET).

Relevant log excerpt:

I (509) coexist: coexist rom version e7ae62f
I (515) main_task: Started on CPU0
I (520) main_task: Calling app_main()
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x29 (SPI_FAST_FLASH_BOOT)
...

(repeats indefinitely)

Also noticed a size mismatch warning that might be relevant:

W (454) spi_flash: Detected size(16384k) larger than the size in the binary image header(4096k). Using the size in the binary image header.

My guess is this might be related to the V4's additional FEM chip (GC1109) and its control pins, which V3 doesn't have — if radio/display init assumes V3-specific pin behavior without accounting for the FEM, that could explain a hard crash right after app_main() starts.

Happy to test a debug build or provide more info if useful.

Can confirm — same issue here on Heltec WiFi LoRa 32 V4. Flashed lunarcore-esp32s3.bin (v1.1.0) via esptool after a full erase_flash. Boot proceeds normally through heap init, SPI flash detection, and driver init (I2C, timer, pcnt), but the device gets stuck in a reset loop right after main_task: Calling app_main() — no further log output, no display activity (screen stays blank), and the board resets itself repeatedly (rst:0x15 USB_UART_CHIP_RESET). Relevant log excerpt: I (509) coexist: coexist rom version e7ae62f I (515) main_task: Started on CPU0 I (520) main_task: Calling app_main() ESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0x15 (USB_UART_CHIP_RESET),boot:0x29 (SPI_FAST_FLASH_BOOT) ... (repeats indefinitely) Also noticed a size mismatch warning that might be relevant: W (454) spi_flash: Detected size(16384k) larger than the size in the binary image header(4096k). Using the size in the binary image header. My guess is this might be related to the V4's additional FEM chip (GC1109) and its control pins, which V3 doesn't have — if radio/display init assumes V3-specific pin behavior without accounting for the FEM, that could explain a hard crash right after app_main() starts. Happy to test a debug build or provide more info if useful. <!-- github-comment-id:5358624107 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/lunarcore#5