(2024-12-15, 10:45 PM)jacqueline Wrote: Hey Gamers,
As promised, I have written some docs on how to flash new firmware manually, either with the companion CLI, or via esptool. Check it out: https://cooltech.zone/tangara/docs/flashing/
Let me know any issues, comments, additional things you'd like covered!
Updated mine a week ago.
Went smooth apart from the esp-idf from my Linux distro (Arch) is newer and did not work.
Using the older one, which the companion app uses as subrepro worked fine.
(2025-01-20, 12:22 AM)jacqueline Wrote: We mostly just use `idf.py flash` for local development as well. It's fine. If you're doing *just* C/C++ changes (no lua changes) then `idf.py app-flash` just flashes the C/C++ firmware partition. In theory there should also be a magical incantation you can pass to flash just the C/C++ and Lua partitions, but we've never been bothered enough by flashing times to look into it too hard.
The on-board flash is rated for at least 100,000 cycles so durability shouldn't be an issue. If in a few decades you start seeing flash write failures then mail us your Tangara and we'll replace the chip :p
Bonusquestion: "If you're doing *just* C/C++ changes (no lua changes) then `idf.py app-flash` just flashes the C/C++ firmware partition."
When one doing some code changes, where versioning is embedded in the firmware (version, branch, tag, sha,...)
And where to look this up in the firmware?
