[Bug]: Flashing Custom 2.6.1 firmware on custom hardware error #6288
Replies: 3 comments
-
rem'd out the three lines and it works now. @Rem Ensure target files exist before flashing operations. |
Beta Was this translation helpful? Give feedback.
-
This has to do with the By using something like dos2unix it's possible to convert from I'll see if I can find a fix, sure looks like |
Beta Was this translation helpful? Give feedback.
-
no worries I figured it out, but someone else might have trouble and I wanted to save them some time. using GitCMD, windows and visual studio code w platformio if it matters. Also, they could just use the device-install.bat from firmware release 2.5.21 or below, it seems to have changed after that. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Category
Other
Hardware
T-Beam
Firmware Version
2.6.1
Description
how would i fix this? I flash custom edited firmware for my tbeam clone. Suddenly with 2.6.1 flashing errors out....
c:\meshtastic\firmware\bin>device-install.bat -f firmware-factory2.6.1.7c3edde-e22.bin -p COM5
INFO | 9:04:55 5 Using esptool baud: 115200.
ERROR | 9:04:55 6 File does not exist: "". Terminating.
ERROR | 9:04:55 12 File does not exist: "bleota.bin". Terminating.
ERROR | 9:04:55 14 File does not exist: "bleota.bin". Terminating.
INFO | 9:04:55 16 Using esptool port: COM5.
INFO | 9:04:55 17 Using esptool baud: 115200.
ERROR | 9:04:55 18 File does not exist: "littlefs-factory2.6.1.7c3edde-e22.bin". Terminating.
ERROR | 9:04:55 24 File does not exist: "bleota.bin". Terminating.
Relevant log output
Beta Was this translation helpful? Give feedback.
All reactions