Closed mquade closed 1 month ago
Duplicate of #6261
The Board/Sensor works with the additional Flag
esphome:
platformio_options:
build_flags:
- -DPIO_FRAMEWORK_ARDUINO_MMU_CACHE16_IRAM48_SECHEAP_SHARED
But RAM isn't full - so I don't get the issue... 😕
Archiving .pioenvs/esphome-02/libFrameworkArduino.a
Linking .pioenvs/esphome-02/firmware.elf
RAM: [===== ] 47.7% (used 39064 bytes from 81920 bytes)
Flash: [====== ] 55.9% (used 583957 bytes from 1044464 bytes)
Building .pioenvs/esphome-02/firmware.bin
But RAM isn't full - so I don't get the issue...
That is the static RAM usage. That's how much is being used before anything is running, so that's actually a surprisingly large amount.
that's actually a surprisingly large amount.
Thanks for clearification. If I remove all sensors, additional modules etc. I still end up with 32 kb used SRAM:
Linking .pioenvs/esphome-02/firmware.elf
RAM: [==== ] 39.5% (used 32372 bytes from 81920 bytes)
Flash: [==== ] 42.5% (used 444171 bytes from 1044464 bytes)
Building .pioenvs/esphome-02/firmware.bin
esp8266_copy_factory_bin([".pioenvs/esphome-02/firmware.bin"], [".pioenvs/esphome-02/firmware.elf"])
So the difference with enabled web server, captive portal, i2c and bme680 library is ~7 kb I don't know whats in those 32k but the compiler is doing a lot of stuff :-D
The problem
Using an BME680 connected via i2c to an ESP8266 (Wemos D1 Mini Clone) leads to boot loops but only if the BME680 is really connected. If I compile and install the code without connection the sensor everything boots up fine.
Which version of ESPHome has the issue?
2024.9.2
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2024.9.3
What platform are you using?
ESP8266
Board
D1 Mini (Clone), board: d1_mini
Component causing the issue
i2c / bme68x_bsec2_i2c
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
When the sensor is not connected everything starts up normaly.