Replies: 4 comments 12 replies
-
You should not even look for |
Beta Was this translation helpful? Give feedback.
-
Basic steps updated. All done here. |
Beta Was this translation helpful? Give feedback.
-
Hi @SimonFili |
Beta Was this translation helpful? Give feedback.
-
Thank you so much , very informative. Plus i got my first custom compile
w/AHTX working !!!
…On Fri, May 3, 2024 at 10:20 AM sfromis ***@***.***> wrote:
The binaries with .factory in the name are for initial wired flashing,
and the ones without are for doing upgrades (typically OTA) when already
having Tasmota on the device. The .factory binaries *can* also come with
a pre-populated file system.
The .factory binaries also include a bootloader, partition scheme and the
safeboot partition used when upgrading.
—
Reply to this email directly, view it on GitHub
<#18745 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUKYINCK7XDUUR36JWL4I6LZAOMKHAVCNFSM6AAAAAAYTEQVA2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGMBWGMZTM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hi all,
Compilation steps for ESP32 with new options enabled. In this example, I added support for PCF8574 and Atlas Scientific EZO chips.
Here's the big steps I did to compile:
Then, using the web interface, upload the new firmware.
Example
I needed to add the support for the PCF8574 and some EZO chips.
So I copied those lines from my_user_config.h to user_config_override.h
and removed the // to enable them
Then I compiled with : platformio run -e tasmota32 on the command line
The firmware was in /build_output/firmware/tasmota.bin
So I downloaded and used the web interface to upload and update the firmware to my needs.
Beta Was this translation helpful? Give feedback.
All reactions