custom_IR_ESP8266_1M builds help needed
Moderators: grovkillen, Stuntteam, TD-er
custom_IR_ESP8266_1M builds help needed
Hey @TDer,
can you tell what the differences are. I don´t know which one i should use....
can you tell what the differences are. I don´t know which one i should use....
Last edited by chromo23 on 24 Jan 2024, 15:34, edited 1 time in total.
Re: differences in custom ESP8266_1M builds
and in addition to that, how would i nowadays make a "custom_IR_ESP8266_1M" build.
I wanted to update an WiFi-socket of mine and realized, that there is no custom ir build anymore for 1M units...
I wanted to update an WiFi-socket of mine and realized, that there is no custom ir build anymore for 1M units...
Re: differences in custom ESP8266_1M builds
274 refers to the Arduino SDK version 2.7.4
"Beta" refers to the latest Arduino SDK version (currently 3.1.2 I think)
Both have their pros and cons.
For example the versions that came after 2.7.4 were flaky at best and quite a bit larger in build size, but the latest ones do have improved significantly. Both in build size as well as stability.
However the 'beta' ones do use quite a bit more RAM.
I have experimented with "2nd heap". It does allow for quite a bit more free memory, but code execution is slower and on some boards (I think it is related to the flash chip used) it may result in quite a lot of watchdog resets.
I have 2nd heap build running on one node here which is running for over a month now, fully packed with sensors and no crashes.
But for IR I don't think you should use a 2nd heap build as the decoding is rather time-sensitive.
I think I have turned off the custom 1M IR build as it didn't fit anymore.
You can change the board definition in the 4M variant and try to make a build.
"Beta" refers to the latest Arduino SDK version (currently 3.1.2 I think)
Both have their pros and cons.
For example the versions that came after 2.7.4 were flaky at best and quite a bit larger in build size, but the latest ones do have improved significantly. Both in build size as well as stability.
However the 'beta' ones do use quite a bit more RAM.
I have experimented with "2nd heap". It does allow for quite a bit more free memory, but code execution is slower and on some boards (I think it is related to the flash chip used) it may result in quite a lot of watchdog resets.
I have 2nd heap build running on one node here which is running for over a month now, fully packed with sensors and no crashes.
But for IR I don't think you should use a 2nd heap build as the decoding is rather time-sensitive.
I think I have turned off the custom 1M IR build as it didn't fit anymore.
You can change the board definition in the 4M variant and try to make a build.
Re: differences in custom ESP8266_1M builds
That's actually explained in the README.md (frontpage) on Github...
/Ton (PayPal.me)
Re: differences in custom ESP8266_1M builds
Thanks!
It builds fine, so maybe i give it a try....
The term "beta" is explained as "Arduino Beta release" which was not very clear for me what it exactly means.
Do you think this is ok?
Code: Select all
[env:custom_IR_ESP8266_1M]
extends = esp8266_1M
platform = ${ir.platform}
platform_packages = ${ir.platform_packages}
build_flags = ${ir.build_flags}
${esp8266_1M.build_flags}
-DPLUGIN_BUILD_CUSTOM
lib_ignore = ${esp8266_custom_common_274.lib_ignore}
ESP8266SdFat
SD(esp8266)
SD
SDFS
LittleFS(esp8266)
extra_scripts = ${esp8266_custom_common_274.extra_scripts}
Not quite...
The term "beta" is explained as "Arduino Beta release" which was not very clear for me what it exactly means.
Re: differences in custom ESP8266_1M builds
At first glance the config looks OK.
Make a backup of your settings before uploading, as it might destroy the file system if you pick the wrong layout.
Make a backup of your settings before uploading, as it might destroy the file system if you pick the wrong layout.
Re: differences in custom ESP8266_1M builds
Flash was successful but I should have made a backup of the whole firmware since there is now no way of going back.
Problem is, that P016 is missing.
So when i try to add it either "#define PLUGIN_BUILD_NORMAL_IR 1" in custom.h or "-DPLUGIN_BUILD_IR" as a build flag i get the same error: Then i thought i just download the old source of the time the build was made and compile myself a new firmware ( the old firmware was called ESP_Easy_mega_20220224_custom_ir_ESP8266_1M)
But no luck either. There is no custom_ir_ESP8266_1M...
How was i able to compile something that was not an option? Strange...
Any help is really appreciated.
Re: custom_IR_ESP8266_1M builds help needed
Code: Select all
[env:custom_IR_ESP8266_1M]
extends = esp8266_1M
platform = ${ir.platform}
platform_packages = ${ir.platform_packages}
build_flags = ${ir.build_flags}
${esp8266_1M.build_flags}
-DPLUGIN_BUILD_CUSTOM
-DPLUGIN_BUILD_IR
lib_ignore = ESP32_ping
ESP32WebServer
ServoESP32
ESP32HTTPUpdateServer
adafruit/Adafruit GFX Library@^1.11.1
LOLIN_EPD
Adafruit ILI9341 ESPEasy
adafruit/Adafruit BusIO
Adafruit NeoPixel
NeoPixelBus_wrapper
NeoPixelBus by Makuna
Adafruit NeoMatrix via NeoPixelBus
Adafruit Motor Shield V2 Library
Adafruit_ST77xx
Adafruit NeoMatrix
I2C AXP192 Power management
EspSoftwareSerial
extra_scripts = pre:tools/pio/pre_custom_esp82xx_IR.py
${extra_scripts_esp8266.extra_scripts}
pre:tools/pio/ir_build_check.py
Code: Select all
custom_defines=[
"-DCONTROLLER_SET_ALL",
"-DNOTIFIER_SET_NONE",
"-DPLUGIN_SET_NONE",
"-DUSES_P001", # Switch
"-DUSES_P002", # ADC
"-DUSES_P003", # Generic Pulse Counter
"-DUSES_P004", # Dallas DS18b20
"-DUSES_P016", # IR
"-DUSES_P026", # System info
# "-DUSES_P027", # INA219
"-DUSES_P028", # BME280
# "-DUSES_P033", # Dummy
# "-DUSES_P036", # FrameOLED
# "-DUSES_P045", # MPU6050
# "-DUSES_P049", # MHZ19
# "-DUSES_P052", # SenseAir
# "-DUSES_P056", # SDS011-Dust
# "-DUSES_P059", # Encoder
# "-DUSES_P080", # Dallas iButton
"-DUSES_P081", # Cron
# "-DUSES_P082", # GPS
# "-DUSES_P085", # AcuDC24x
# "-DUSES_P098", # PWM motor
# "-DUSES_P100", # Pulse Counter - DS2423
# "-DUSES_P087", # Serial Proxy
# "-DUSES_P094", # CUL Reader
# "-DUSES_P095", # TFT ILI9341
# "-DUSES_P106", # BME680
# "-DUSES_P107", # SI1145 UV index
# "-DUSES_P146", # Cache Reader
# "-DUSES_C016", # Cache Controller
# "-DUSES_C018", # TTN/RN2483
# "-DUSES_C015", # Blynk
# "-DFEATURE_MDNS=1",
# "-DFEATURE_SD=1",
# "-DFEATURE_EXT_RTC=1",
"-DFEATURE_I2CMULTIPLEXER=0",
"-DFEATURE_TRIGONOMETRIC_FUNCTIONS_RULES=0",
# "-DFEATURE_CUSTOM_PROVISIONING=1",
"-DFEATURE_ESPEASY_P2P=1",
"-DFEATURE_SETTINGS_ARCHIVE=0"
]
Re: custom_IR_ESP8266_1M builds help needed
THANK YOU!
It worked fine.
The only odd thing was, that in AP mode the device was not password protected and the name was also not the same as in the config.h file
What do you think about readding the custom_IR_ESP8266_1M back.
There seems to be no issue regarding the size:
It worked fine.
The only odd thing was, that in AP mode the device was not password protected and the name was also not the same as in the config.h file
This i did not need to change.
What do you think about readding the custom_IR_ESP8266_1M back.
There seems to be no issue regarding the size:
Re: custom_IR_ESP8266_1M builds help needed
When stripping almost all from the Python file, then it will fit indeed
I will have a look at the factory default settings for the password.
I will have a look at the factory default settings for the password.
Who is online
Users browsing this forum: No registered users and 0 guests