can't compile an ESP32 on releas and devekopent version #342

Mark-Muc · 2023-02-27T10:54:06Z

Mark-Muc
Feb 27, 2023

I tried to compile a ESP32 verson with following switches:

#ifdef LATITUDE
  #undef LATITUDE
#endif
#define LATITUDE 48.105061

#ifdef LONGITUDE
  #undef LONGITUDE
#endif
#define LONGITUDE 11.518247

#ifdef APP_TIMEZONE
  #undef APP_TIMEZONE
#endif
#define APP_TIMEZONE 99

#ifdef USE_EXPRESSION 
#undef USE_EXPRESSION
#endif
#define USE_EXPRESSION

#ifdef SUPPORT_IF_STATEMENT 
#undef SUPPORT_IF_STATEMENT
#endif
#define SUPPORT_IF_STATEMENT

#ifndef USE_SHUTTER
#define USE_SHUTTER     
#endif

#define MOTOR_STOP_TIME 750

normaly it works fine but these days no compile possible in both versions

Error:

Compiling .pio/build/tasmota32/liba89/lvgl/extra/libs/gif/gifdec.c.o
*** [.pio/build/tasmota32/src/tasmota.ino.cpp.o] Error 1
========================= [FAILED] Took 71.24 seconds =========================

Environment    Status    Duration
-------------  --------  ------------
tasmota32      FAILED    00:01:11.241
==================== 1 failed, 0 succeeded in 00:01:11.241 ====================
Finished. Exit code: 1.

anyone knows whats happens?
Thx & Regards
Mark

benzino77 · 2023-02-27T13:17:17Z

benzino77
Feb 27, 2023
Maintainer

Have a look here: https://github.com/benzino77/tasmocompiler/blob/master/FEATURES_DESC.md
You don't have to define USE_EXPRESSION and SUPPORT_IF_STATEMENT - they are already included in "Rules" feature
You don't have to define USE_SHUTTER and MOTOR_STOP_TIME - they are already included in "Shutters and Blinds" feature.

0 replies

Mark-Muc · 2023-02-27T13:25:03Z

Mark-Muc
Feb 27, 2023
Author

Ok ..thanks .. I'll test and let u know!! The thing is: I need to MOTOR_STOP_TIME set to 750ms ,, this can be done? Regards and thank u ver much!! Mark Von: benzino77 ***@***.***> Gesendet: Montag, 27. Februar 2023 14:17 An: benzino77/tasmocompiler ***@***.***> Cc: Mark-Muc ***@***.***>; Author ***@***.***> Betreff: Re: [benzino77/tasmocompiler] can't compile an ESP32 on releas and devekopent version (Discussion #342) Have a look here: https://github.com/benzino77/tasmocompiler/blob/master/FEATURES_DESC.md<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbenzino77%2Ftasmocompiler%2Fblob%2Fmaster%2FFEATURES_DESC.md&data=05%7C01%7C%7Cc00e6987b081488e678108db18c4f994%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638131006495827311%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dNfaE1aVEsrkTSQ51T4BVlPiPniXnWCMfbhNsR6uvV4%3D&reserved=0> You don't have to define USE_EXPRESSION and SUPPORT_IF_STATEMENT - they are already included in "Rules" feature You don't have to define USE_SHUTTER and MOTOR_STOP_TIME - they are already included in "Shutters and Blinds" feature. - Reply to this email directly, view it on GitHub<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbenzino77%2Ftasmocompiler%2Fdiscussions%2F342%23discussioncomment-5122640&data=05%7C01%7C%7Cc00e6987b081488e678108db18c4f994%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638131006495827311%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=I5vAfMOh8jIowyrIoampNmt6Qf3SFO8nnUFivqYGVMY%3D&reserved=0>, or unsubscribe<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQCJXH2ZVR7UYEACIMPOXRTWZSSOPANCNFSM6AAAAAAVJHT77I&data=05%7C01%7C%7Cc00e6987b081488e678108db18c4f994%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638131006495827311%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Rn%2FQIEVbZItINMubGHN9c3JI7Fez4MUcO0oe%2Fe1yJMw%3D&reserved=0>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

3 replies

Mark-Muc Feb 27, 2023
Author

so I tested: only this checked:

nothing else NO #define anywere:
same resuult:

Compiling .pio/build/tasmota32/liba89/lvgl/draw/nxp/pxp/lv_gpu_nxp_pxp.c.o
*** [.pio/build/tasmota32/src/tasmota.ino.cpp.o] Error 1
========================= [FAILED] Took 37.37 seconds =========================

Environment    Status    Duration
-------------  --------  ------------
tasmota32      FAILED    00:00:37.371
==================== 1 failed, 0 succeeded in 00:00:37.371 ====================
Finished. Exit code: 1.

using TasmoCompiler v10-development

Regards
Mark

benzino77 Feb 27, 2023
Maintainer

Development version is... development. You can expect unexpected ;)
Try to use v10.2.0 version of TasmoCompiler which forces you to use stable version of Tasmota. There are probably some changes in Tasmota development branch causing those problems.

Mark-Muc Feb 28, 2023
Author

Thx very much i got it compiled as a shutter and working .. thx again..
but still . als mentioned in an other thread:
to compile a esp32 version for NSPanel dont work anymore:
switches to be used:

#define FIRMWARE_NSPANEL
#define FRAMEWORK_ARDUINO_ITEAD

//Thermostat
#define USE_THERMOSTAT                           // Add support for Thermostat
    #define THERMOSTAT_CONTROLLER_OUTPUTS         1         // Number of outputs to be controlled independently
//    #define THERMOSTAT_SENSOR_NAME                "DS18B20" // Name of the local sensor to be used <-- check MQTT!! "ANALOG"
//   MQTT = "ANALOG": {"Temperature1": 20.6}
   #define THERMOSTAT_SENSOR_NAME                "ANALOG" //internal name 
//    #define THERMOSTAT_SENSOR_NAME                "ATCaf4a0b" //BlueTooth ID ATCaf4a0b

    #define THERMOSTAT_SENSOR_NUMBER              1         // Number of local sensors to be used
    #define THERMOSTAT_RELAY_NUMBER               1         // Default output relay number for the first controller (+i for following ones)
    #define THERMOSTAT_SWITCH_NUMBER              1         // Default input switch number for the first controller (+i for following ones)
    #define THERMOSTAT_TIME_ALLOW_RAMPUP          300       // Default time after last target update to allow ramp-up controller phase in minutes
    #define THERMOSTAT_TIME_RAMPUP_MAX            960       // Default time maximum ramp-up controller duration in minutes
    #define THERMOSTAT_TIME_RAMPUP_CYCLE          30        // Default time ramp-up cycle in minutes
    #define THERMOSTAT_TIME_SENS_LOST             30        // Maximum time w/o sensor update to set it as lost in minutes
    #define THERMOSTAT_TEMP_SENS_NUMBER           1         // Default temperature sensor number
    #define THERMOSTAT_TIME_MANUAL_TO_AUTO        60        // Default time without input switch active to change from manual to automatic in minutes
    #define THERMOSTAT_TIME_RESET                 12000     // Default reset time of the PI controller in seconds
    #define THERMOSTAT_TIME_PI_CYCLE              30        // Default cycle time for the thermostat controller in minutes
    #define THERMOSTAT_TIME_MAX_ACTION            20        // Default maximum thermostat time per cycle in minutes
    #define THERMOSTAT_TIME_MIN_ACTION            4         // Default minimum thermostat time per cycle in minutes
    #define THERMOSTAT_TIME_MIN_TURNOFF_ACTION    3         // Default minimum turnoff time in minutes, below it the thermostat will be held on
    #define THERMOSTAT_PROP_BAND                  4         // Default proportional band of the PI controller in degrees celsius
    #define THERMOSTAT_TEMP_RESET_ANTI_WINDUP     8         // Default range where reset antiwindup is disabled, in tenths of degrees celsius
    #define THERMOSTAT_TEMP_HYSTERESIS            1         // Default range hysteresis for temperature PI controller, in tenths of degrees celsius
    #define THERMOSTAT_TEMP_FROST_PROTECT         40        // Default minimum temperature for frost protection, in tenths of degrees celsius
    #define THERMOSTAT_TEMP_RAMPUP_DELTA_IN       4         // Default minimum delta temperature to target to get into rampup mode, in tenths of degrees celsius
    #define THERMOSTAT_TEMP_RAMPUP_DELTA_OUT      2         // Default minimum delta temperature to target to get out of the rampup mode, in tenths of degrees celsius
    #define THERMOSTAT_TEMP_PI_RAMPUP_ACC_E       200       // Default accumulated error when switching from ramp-up controller to PI in hundredths of degrees celsius
    #define THERMOSTAT_TIME_OUTPUT_DELAY          180       // Default output delay between state change and real actuation event (f.i. valve open/closed)
    #define THERMOSTAT_TEMP_INIT                  180       // Default init target temperature for the thermostat controller
    #define THERMOSTAT_TIME_MAX_OUTPUT_INCONSIST  3         // Default maximum time where the input and the output shall differ (for diagnostic) in minutes
    #define THERMOSTAT_TIME_MAX_AUTOTUNE          21600     // Maximum time for the PI autotune function to complete in seconds
    #define THERMOSTAT_DUTYCYCLE_AUTOTUNE         35        // Default duty cycle (in % over PI cycle time) for the step response of the autotune PI function
    #define THERMOSTAT_PEAKNUMBER_AUTOTUNE        8         // Default number of peak temperatures (max or min) to be used for the autotune PI function
    #define THERMOSTAT_TEMP_BAND_NO_PEAK_DET      1         // Default temperature band in thenths of degrees celsius within no peak will be detected
    #define THERMOSTAT_TIME_STD_DEV_PEAK_DET_OK   10        // Default standard deviation in minutes of the oscillation periods within the peak detection is successful    

    #define USE_PI_AUTOTUNING // (Ziegler-Nichols closed loop method)

#ifdef LATITUDE
  #undef LATITUDE
#endif
#define LATITUDE 48.105061

#ifdef LONGITUDE
  #undef LONGITUDE
#endif
#define LONGITUDE 11.518246

#ifdef APP_TIMEZONE
  #undef APP_TIMEZONE
#endif
#define APP_TIMEZONE 99

ERROR:

Linking .pio/build/tasmota32/firmware.elf
/tmp/Tasmota/tasmota/tasmota_xsns_sensor/xsns_62_esp32_mi_ble.ino: In function 'HandleMI32Key':
/tmp/Tasmota/tasmota/tasmota_xsns_sensor/xsns_62_esp32_mi_ble.ino:2672:10: warning: 'strncat' specified bound 64 equals destination size [-Wstringop-overflow=]
   strncat(key, mac, sizeof(key));
          ^
/home/gitpod/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: .pio/build/tasmota32/firmware.elf section `.iram0.text' will not fit in region `iram0_0_seg'
/home/gitpod/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: IRAM0 segment data does not fit.
/home/gitpod/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: region `iram0_0_seg' overflowed by 32 bytes
collect2: error: ld returned 1 exit status
*** [.pio/build/tasmota32/firmware.elf] Error 1
========================= [FAILED] Took 281.57 seconds =========================

Environment    Status    Duration
-------------  --------  ------------
tasmota32      FAILED    00:04:41.567
==================== 1 failed, 0 succeeded in 00:04:41.567 ====================
Finished. Exit code: 1.

Can someone compile??
Thx & Regards
Mark

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

can't compile an ESP32 on releas and devekopent version #342

{{title}}

Replies: 2 comments 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

can't compile an ESP32 on releas and devekopent version #342

Mark-Muc Feb 27, 2023

Replies: 2 comments · 3 replies

benzino77 Feb 27, 2023 Maintainer

Mark-Muc Feb 27, 2023 Author

Mark-Muc Feb 27, 2023 Author

benzino77 Feb 27, 2023 Maintainer

Mark-Muc Feb 28, 2023 Author

Mark-Muc
Feb 27, 2023

Replies: 2 comments 3 replies

benzino77
Feb 27, 2023
Maintainer

Mark-Muc
Feb 27, 2023
Author

Mark-Muc Feb 27, 2023
Author

benzino77 Feb 27, 2023
Maintainer

Mark-Muc Feb 28, 2023
Author