I followed the instructions exactly as shown in the youtube video, however I cannot successfully enter the firmware and the display remains off. I have tried both versions available on the meshforge website. It flashes and verifies the firmware, then exits. I don't see any error messages nor do I see any serial output.
yeah, I have the same issue and compiling it manually doesn't work either (see issue # 4) hopefully someone can advise.
yeah, I have the same issue and compiling it manually doesn't work either (see issue # 4) hopefully someone can advise.
<!-- github-comment-id:3797431442 -->
how is the node behaving post reboot - it sure looks like it flashed fine. i don't think using esptool is going to show the node id - note i never watched the video.
as an aside, take a look at this article on including code blocks in markdown - results in much cleaner representation of things like command output.
how is the node behaving post reboot - it sure looks like it flashed fine. i don't think using `esptool` is going to show the node id - note i never watched the video.
as an aside, take a look at [this article](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks) on including code blocks in markdown - results in much cleaner representation of things like command output.
<!-- github-comment-id:3820854138 -->
I followed the instructions exactly as shown in the youtube video, however I cannot successfully enter the firmware and the display remains off.
> I followed the instructions exactly as shown in the youtube video, however I cannot successfully enter the firmware and the display remains off.
<!-- github-comment-id:3832243797 -->
I have succeded by manually compiling the source and flashing it. I think there is something wrong with the version downloaded from meshforge. if you follow the local build script (bash) it should work. but make sure you either have python 3.14 or create a virtual environment with it. I ran into a few snags but they are detailed in issue #4
I have succeded by manually compiling the source and flashing it. I think there is something wrong with the version downloaded from meshforge. if you follow the `local build script (bash)` it should work. but make sure you either have python 3.14 or create a virtual environment with it. I ran into a few snags but they are detailed in issue #4
<!-- github-comment-id:3832679268 -->
After flashing did you connect to the Heltec's console and look at what it was outputing? I have a v3 and v4 I have been trying to flash from the comipled meshforge firmware and they will both sit there in a boot loop. This took me a bit to diagnose as the discord told me that the screens aren't expected to work on the v3 now???
After flashing did you connect to the Heltec's console and look at what it was outputing? I have a v3 and v4 I have been trying to flash from the comipled meshforge firmware and they will both sit there in a boot loop. This took me a bit to diagnose as the discord told me that the screens aren't expected to work on the v3 now???
<!-- github-comment-id:3867372637 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I followed the instructions exactly as shown in the youtube video, however I cannot successfully enter the firmware and the display remains off. I have tried both versions available on the meshforge website. It flashes and verifies the firmware, then exits. I don't see any error messages nor do I see any serial output.
meshtastic-v2.7.16.a597230-heltec-v3-KOM0-20081788938-firmware
alex@alex-minty-desktop:~$ esptool -b 125000 write-flash 0x0 ~/Downloads/lobbs2.7/firmware.factory.bin
esptool v5.1.0
Connected to ESP32-S3 on /dev/ttyUSB0:
Chip type: ESP32-S3 (QFN56) (revision v0.2)
Features: Wi-Fi, BT 5 (LE), Dual Core + LP Core, 240MHz, Embedded Flash 8MB (GD)
Crystal frequency: 40MHz
MAC: 34:b7:da:54:7f:fc
Stub flasher running.
Changing baud rate to 125000...
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00205fff...
Compressed 2120512 bytes to 1315565...
Writing at 0x00000000 [ ] 0.0% 0/1315565 bytes...Writing at 0x000131d9 [ ] 1.2% 16384/1315565 byteWriting at 0x0001d350 [ ] 2.5% 32768/1315565 byteWriting at 0x00027486 [> ] 3.7% 49152/1315565 byteWriting at 0x00031709 [> ] 5.0% 65536/1315565 byteWriting at 0x0003beb3 [> ] 6.2% 81920/1315565 byteWriting at 0x00047e33 [=> ] 7.5% 98304/1315565 byteWriting at 0x00052805 [=> ] 8.7% 114688/1315565 bytWriting at 0x0005a1d3 [=> ] 10.0% 131072/1315565 bytWriting at 0x0006411d [==> ] 11.2% 147456/1315565 bytWriting at 0x00072edd [==> ] 12.5% 163840/1315565 bytWriting at 0x00082979 [===> ] 13.7% 180224/1315565 bytWriting at 0x00088540 [===> ] 14.9% 196608/1315565 bytWriting at 0x0008e0b1 [===> ] 16.2% 212992/1315565 bytWriting at 0x00093423 [====> ] 17.4% 229376/1315565 bytWriting at 0x00098a91 [====> ] 18.7% 245760/1315565 bytWriting at 0x0009dfac [====> ] 19.9% 262144/1315565 bytWriting at 0x000a3570 [=====> ] 21.2% 278528/1315565 bytWriting at 0x000a86b4 [=====> ] 22.4% 294912/1315565 bytWriting at 0x000ada27 [======> ] 23.7% 311296/1315565 bytWriting at 0x000b3515 [======> ] 24.9% 327680/1315565 bytWriting at 0x000b8c0b [======> ] 26.2% 344064/1315565 bytWriting at 0x000bdea5 [=======> ] 27.4% 360448/1315565 bytWriting at 0x000c3ac0 [=======> ] 28.6% 376832/1315565 bytWriting at 0x000c9107 [=======> ] 29.9% 393216/1315565 bytWriting at 0x000ce7d4 [========> ] 31.1% 409600/1315565 bytWriting at 0x000d3dcc [========> ] 32.4% 425984/1315565 bytWriting at 0x000d965e [=========> ] 33.6% 442368/1315565 bytWriting at 0x000de651 [=========> ] 34.9% 458752/1315565 bytWriting at 0x000e3777 [=========> ] 36.1% 475136/1315565 bytWriting at 0x000e9e45 [==========> ] 37.4% 491520/1315565 bytWriting at 0x000eebe9 [==========> ] 38.6% 507904/1315565 bytWriting at 0x000f3b67 [==========> ] 39.9% 524288/1315565 bytWriting at 0x000f8f73 [===========> ] 41.1% 540672/1315565 bytWriting at 0x000fea20 [===========> ] 42.3% 557056/1315565 bytWriting at 0x0010429f [============> ] 43.6% 573440/1315565 bytWriting at 0x00109f88 [============> ] 44.8% 589824/1315565 bytWriting at 0x0010f6ff [============> ] 46.1% 606208/1315565 bytWriting at 0x00114e69 [=============> ] 47.3% 622592/1315565 bytWriting at 0x0011aa84 [=============> ] 48.6% 638976/1315565 bytWriting at 0x00120017 [=============> ] 49.8% 655360/1315565 bytWriting at 0x00125aea [==============> ] 51.1% 671744/1315565 bytWriting at 0x0012abc5 [==============> ] 52.3% 688128/1315565 bytWriting at 0x0012fcd4 [===============> ] 53.6% 704512/1315565 bytWriting at 0x00134bf6 [===============> ] 54.8% 720896/1315565 bytWriting at 0x00139b19 [===============> ] 56.0% 737280/1315565 bytWriting at 0x0013f19c [================> ] 57.3% 753664/1315565 bytWriting at 0x001441e2 [================> ] 58.5% 770048/1315565 bytWriting at 0x00149179 [================> ] 59.8% 786432/1315565 bytWriting at 0x0014e482 [=================> ] 61.0% 802816/1315565 bytWriting at 0x0015380b [=================> ] 62.3% 819200/1315565 bytWriting at 0x00158f38 [==================> ] 63.5% 835584/1315565 bytWriting at 0x0015e50b [==================> ] 64.8% 851968/1315565 bytWriting at 0x00163548 [==================> ] 66.0% 868352/1315565 bytWriting at 0x00168540 [===================> ] 67.3% 884736/1315565 bytWriting at 0x0016d387 [===================> ] 68.5% 901120/1315565 bytWriting at 0x00173195 [===================> ] 69.7% 917504/1315565 bytWriting at 0x0017887f [====================> ] 71.0% 933888/1315565 bytWriting at 0x0017db30 [====================> ] 72.2% 950272/1315565 bytWriting at 0x00182ea1 [=====================> ] 73.5% 966656/1315565 bytWriting at 0x00187c7b [=====================> ] 74.7% 983040/1315565 bytWriting at 0x0018cdb6 [=====================> ] 76.0% 999424/1315565 bytWriting at 0x00191cc2 [======================> ] 77.2% 1015808/1315565 byWriting at 0x00197105 [======================> ] 78.5% 1032192/1315565 byWriting at 0x0019c597 [======================> ] 79.7% 1048576/1315565 byWriting at 0x001a20d6 [=======================> ] 81.0% 1064960/1315565 byWriting at 0x001a7687 [=======================> ] 82.2% 1081344/1315565 byWriting at 0x001adb76 [========================> ] 83.4% 1097728/1315565 byWriting at 0x001b42ab [========================> ] 84.7% 1114112/1315565 byWriting at 0x001bd7f0 [========================> ] 85.9% 1130496/1315565 byWriting at 0x001c6379 [=========================> ] 87.2% 1146880/1315565 byWriting at 0x001cb9c5 [=========================> ] 88.4% 1163264/1315565 byWriting at 0x001d11a7 [=========================> ] 89.7% 1179648/1315565 byWriting at 0x001d6ca1 [==========================> ] 90.9% 1196032/1315565 byWriting at 0x001dc144 [==========================> ] 92.2% 1212416/1315565 byWriting at 0x001e1dbd [===========================> ] 93.4% 1228800/1315565 byWriting at 0x001e80e9 [===========================> ] 94.7% 1245184/1315565 byWriting at 0x001f3321 [===========================> ] 95.9% 1261568/1315565 byWriting at 0x001f8832 [============================> ] 97.1% 1277952/1315565 byWriting at 0x001fe227 [============================> ] 98.4% 1294336/1315565 byWriting at 0x00203df9 [============================> ] 99.6% 1310720/1315565 byWrote 2120512 bytes (1315565 compressed) at 0x00000000 in 105.5 seconds (160.9 kbit/s).
Hash of data verified.
Hard resetting via RTS pin...
after this it exits without telling me the node ID
yeah, I have the same issue and compiling it manually doesn't work either (see issue # 4) hopefully someone can advise.
how is the node behaving post reboot - it sure looks like it flashed fine. i don't think using
esptoolis going to show the node id - note i never watched the video.as an aside, take a look at this article on including code blocks in markdown - results in much cleaner representation of things like command output.
I have succeded by manually compiling the source and flashing it. I think there is something wrong with the version downloaded from meshforge. if you follow the
local build script (bash)it should work. but make sure you either have python 3.14 or create a virtual environment with it. I ran into a few snags but they are detailed in issue #4After flashing did you connect to the Heltec's console and look at what it was outputing? I have a v3 and v4 I have been trying to flash from the comipled meshforge firmware and they will both sit there in a boot loop. This took me a bit to diagnose as the discord told me that the screens aren't expected to work on the v3 now???