Workflow for using local firmware #391
jonesea
started this conversation in
TTGO firmware
Replies: 2 comments 1 reply
-
Currently this should be no problem at all. If you just "run" (upload via serial) in Arduino IDE (or, using PlatformIO, do a "pio run --target=upload" on the command line, or the equivalent in the GUI), then this is equivalent to just an upgrade, leaving the SPIFFS partition unmodified. (For also flashing the SPIFSS, you have to manually do this either in Arduino IDE or pio run target=uploadfs) |
Beta Was this translation helpful? Give feedback.
1 reply
-
Tried again, and I succeed. I'm unsure why I had failures before. Thank you for the hint on the local web upload. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What's everyone's workflow for using their own complied firmware?
I'm using the Arduino IDE method as that's what I'm more familiar with. I compiled from untouched firmware successfully, but uploading via the traditional Arduino serial yielded a soft-bricked LoRa32 board (it was first loaded with the full dev branch image from git).
Ideally, I would like to have upgrade images so that I can keep my settings on the SPIFF partition.
I also didn't see a traditional way of working with local upgrade images via the built-in web based update, I even tried modifying update.html file with local references and a local web server to host the image... But there seems to be some hardcoded behaviour in the source that prevent this for working.
What are some ways to upload locally generated firmware?
Apologies if this is obvious...
Beta Was this translation helpful? Give feedback.
All reactions