logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Configuring OpenBeken on ESP32 with 4MB Default Using sdkconfig.defaults.esp32

insmod 6666 150
ADVERTISEMENT
Reply | New topic
  • #121 21246289
    max4elektroda
    Level 20  
    divadiow wrote:
    dunno if mine's fake

    Looks exactly like mine - especially the printed text is very different to the original:
    Fragment of a purple circuit board with the label S2 Mini.
  • ADVERTISEMENT
  • #122 21246308
    insmod
    Level 24  
    Mine is a lot like original, except no wemos.cc on backside and a little thinner text.
    Also connects without powersave. Maybe some workload is needed? I remember, that even with only aht20 started it rebooted after about 1min of work (esphome, didn't test tasmota).
  • #123 21246473
    max4elektroda
    Level 20  
    Just a short feedback on my S2 Mini: Tried to do some "workload" and I think one of the GPIO changes maybe "broke" DS1820 so it needs some change?
    At least it seems it's no longer working on Pin 18, as it was with my old firmware from Sept 10th. Or is the pin no longer working with actual FW? I must admit I didn't follow all changes in detail ...
    Didn't find the time to have a closer look, and it's surely not the most important use case, just as a short feedback. Maybe also some stupid error on my side, will try to investigate further tomorrow.
  • #124 21246486
    divadiow
    Level 34  
    ah, I just tried DS18B20 too on S2 but couldn't get pins 2,3,7, 8 or 14 to work. Didn't try others.

    Added after 4 [minutes]:

    nor 18
    Screenshot from the OpenESP32S2_A288CE46 system showing temperature from the DS1820 sensor.

    will try some LEDs

    Added after 18 [minutes]:

    the vast majority are working and controllable with LEDs. (does anyone else find the GPIO finder a little temperamental?)
  • #125 21246542
    insmod
    Level 24  
    >>21246473 It's either setup pin input (try PUp?), or all those other setups causing some delay.

    Added after 28 [minutes]:

    Verified my GU10 bulb, BP5758D now works as expected.
  • ADVERTISEMENT
  • #127 21246766
    insmod
    Level 24  
    >>21246755 Default is currently 14mA for all channels, and i believe it's a little too much. ESPHome defaults to 10mA, and i think we should adapt it. Otherwise it looks all good.
    For GU10 i use 8mA on all channels, that is enough for me, and it doesn't overheat.
  • ADVERTISEMENT
  • #128 21246775
    DeDaMrAz
    Level 20  
    insmod wrote:
    >>21246755 Default is currently 14mA for all channels, and i believe it's a little too much. ESPHome defaults to 10mA, and i think we should adapt it. Otherwise it looks all good.
    For GU10 i use 8mA on all channels, that is enough for me, and it doesn't overheat.


    That is depending on the product of course :) in my case 14mA was waaaaay too low, data plucked form the tuyaFW for my device was 75mA (!!!!) and light was let's say anemic, I bumped it up to 50 and installed 5 such devices so far. I monitored the temp on BP and it was around 60-70'C after 1 hour with 50mA limit ( about 80-85 within enclosure).

    But yeah, you are aware of that and glad you adjusted it :)

    EDIT: I am talking about CW not RGB current.
  • #129 21247248
    divadiow
    Level 34  
    I was just checking my sanity with some sensor functionality between Tasmota and OBK and noticed this chimera appeared in the browser by itself flashing between the two
    Screenshot of the Tasmota interface for the OpenESP32S2_A288CE46 device displaying system information.
    a minor amusement
  • #130 21247693
    insmod
    Level 24  
    Try ds18b20/dht again, i pushed some changes to the way gpio is configured.

    EDIT: DHT probably wouldn't work, no interrupt disabling for esp in code yet.

    EDIT2: It doesn't even start. Pushed an update, now it will start on any platform that has ENABLE_DRIVER_DHT (it is enabled on LN, but 'disabled' in code).

    EDIT3: DHT11 works for me now.
  • ADVERTISEMENT
  • #131 21247756
    max4elektroda
    Level 20  
    Very good, you found it: DS1820 works again!
    Thanks a lot!
    OpenESP32S2 interface screen displaying temperature readings from the DS1820 sensor.

    Added after 36 [minutes]:

    How could I have missed that??
    Thanks for adding the temperature to the channel!
  • #132 21248037
    divadiow
    Level 34  
    5-sensor megamix. good work
    Screenshot of the OpenESP32C6 user interface displaying sensor data and temperatures.

    Added after 20 [minutes]:

    Screenshot of OpenESP32 interface displaying temperature and humidity readings from various sensors.

    Added after 23 [minutes]:

    Screenshot of the OpenESP32S3 software interface displaying sensor readings.

    Added after 22 [minutes]:

    and 2/3rds of a BME680
    Screenshot of OpenESP32S3_DAA2CE60 unit with readings from various temperature and humidity sensors.

    Added after 56 [seconds]:

    what's the maximum number of channels?
  • #133 21248137
    insmod
    Level 24  
    >>21248037 new_pins.h channels + channels2 (arrays size) = 100, or CHANNEL_MAX which is 64
  • #135 21262976
    DeDaMrAz
    Level 20  
    @insmod

    What are your thoughts on integrating this into main release, is it ready for that?

    Maybe we can bring more people into the test pool and have faster verification on changes and more bug tracking eyes on it :)

    Let us know what are your thoughts, thanks.
  • #136 21263595
    insmod
    Level 24  
    >>21262976 I believe it can be merged already. Most peripherals are working already.
    Not implemented: isr for bl0937, pindeepsleep, ws2812 spi.
    Problems: uart is working, but something is wrong. Sometimes it receives something (like product information from tuyamcu), but most of the times it receives nothing at all. Curiously enough, when starting ota - it receives everything. I first thought that it was a priority problem - uart task is started with idle priority. But changing it didn't help me. All of this was tested on TH01 with tuyamcu.

    General: we need something for the web interface, for pins that are input or output only, and pins that should not be used at all (like spi flash pins, etc.).

    Need to verify if anything is broken on other platforms before merge ofc.
  • #137 21291529
    p.kaczmarek2
    Moderator Smart Home  
    I've wanted to merge it today but it seems that commit 393eea8 broke W800 build, any ideas what's happening there?
    https://github.com/openshwprojects/OpenBK7231T_App/pull/1344
    Maybe wrong SDKs?
    Screenshot of configuration files and SDK folders.
    I had similiar issue recently, where Github gui insisted on pushing old version of sub repository...
    Helpful post? Buy me a coffee.
  • #138 21291667
    insmod
    Level 24  
    >>21291529 Pushed an update, git didn't update sdk's on merge
  • #139 21291671
    max4elektroda
    Level 20  
    It reversed the latest changes to the W800 SDK again (we moved the Makefile content to platform lately). So now the enabled drivers in W800 miss the source for drivers again.
  • #140 21332798
    p.kaczmarek2
    Moderator Smart Home  
    Tested with C3 today, Works, nice, we need to put those ESP files on Github Releases page as well..
    User interface of the OpenESP32C3 system with configuration buttons.
    Close-up of a PCB with electronic components, including a micro USB socket, integrated circuits, and I/O connectors. LCD display module on a wooden table. Image of a green circuit board with an ESP32-C3 and Winbond chip. Close-up of a circuit board with an ESP32-C3 microcontroller and Winbond chip.

    Added after 7 [hours] 17 [minutes]:

    That took some time:


    Helpful post? Buy me a coffee.
  • #141 21380511
    DeDaMrAz
    Level 20  
    @insmod

    I am testing ESP32 now and tested on S3 and C6, after setting WiFi credentials, module will just cycle on this

    Code: text Expand Select all Copy to clipboard
    [18:54:01]
[18:54:02]I (119137) OpenBeken: Info:MAIN:Time 119, idle 0/s, free 249584, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 0/0 
[18:54:02]
[18:54:03]I (120127) OpenBeken: +--------------- net device info ------------+
[18:54:03]
[18:54:03]I (120127) OpenBeken: |netif type    : STA                         |
[18:54:03]
[18:54:03]I (120127) OpenBeken: |netif ip      = 0.0.0.0                     |
[18:54:03]
[18:54:03]I (120137) OpenBeken: Info:MAIN:Time 120, idle 0/s, free 249584, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 0/0 
[18:54:03]
[18:54:03]I (120147) OpenBeken: |netif mask    = 0.0.0.0                     |
[18:54:03]
[18:54:03]I (120147) OpenBeken: |netif gateway = 0.0.0.0                     |
[18:54:03]
[18:54:03]I (120157) OpenBeken: |netif mac     : [24:EC:4A:2A:D6:B8]         |
[18:54:03]
[18:54:03]I (120167) OpenBeken: +--------------------------------------------+
[18:54:03]


    And will only get IP from DHCP after maybe a minute or more (will test more and report back).
  • #142 21450257
    groove6j
    Level 8  
    >>21380511
    DeDaMrAz wrote:
    after setting WiFi credentials, module will just cycle on this


    I seem to have the same problem. But in my case it doesn't get an address at all. ESP32 C3
  • Helpful post
    #143 21450268
    insmod
    Level 24  
    Some router problem? Or perhaps you are using esp32-c3-supermini? Those are known for their wifi problems. You would have to reduce tx power, command is powersave 1 10, where 10 is dbm.
  • #144 21450298
    groove6j
    Level 8  
    insmod wrote:
    reduce tx power, command is powersave 1 10, where 10 is dbm.

    Seems to have helped, after reducing to 6dBm, it finally connected. Yes, it was a "supermini". Thanks!
  • #146 21500647
    XJ_
    Level 11  
    DeDaMrAz wrote:
    Just to chime in, ESP8266 support would be super nice!

    I would be very happy too, I have lots of different ESP8266s here.
    And besides, the ESP02S is also an 8266 and is pin-compatible with lots of small SOCs
    ESP-02S WiFi module

    The internal flash of ESP-02S is 16 Mbits

    Code: text Expand Select all Copy to clipboard
    Detecting chip type... ESP8266
Chip is ESP8285N08
Features: WiFi, Embedded Flash
Crystal is 26MHz
MAC: 9c:9c:1f:97:64:1f
Uploading stub...
Running stub...
Stub running...
Chip ID: 0x0097641f
Hard resetting via RTS pin...
  • #147 21500665
    insmod
    Level 24  
    >>21500647 ESP8285N08 - N08 means 8 mbit.
    That is probably not enough for RTOS sdk with dual partition ota.
  • #148 21500843
    XJ_
    Level 11  
    insmod wrote:
    That is probably not enough for RTOS sdk with dual partition ota.

    Hmm, you're right, I didn't notice that.
    However, I have other 8266 ESP-12Es and ESP01Ss here, so I'd still appreciate it.

    Added after 25 [minutes]:

    >>21500843
    But I also have some ESP-02S with 16Mbit, that would work, right?

    Code: text Expand Select all Copy to clipboard
    Detecting chip type... ESP8266
Chip is ESP8285H16
Features: WiFi, Embedded Flash
Crystal is 26MHz
MAC: 70:03:9f:c9:3d:fc
Uploading stub...
Running stub...
Stub running...
Chip ID: 0x00c93dfc
Hard resetting via RTS pin...
  • #149 21537112
    divadiow
    Level 34  
    >>21476005

    had a tiny power cut yesterday but this stayed up. posting update in case a proper one happens

    Control panel of the ESP32C2 device showing status, WiFi info, and control buttons.
Reply | New topic
Report a violation of the law

Topic summary

The discussion centers on configuring OpenBeken firmware for ESP32 devices with a default 4MB flash size using sdkconfig.defaults.esp32. Initial issues included missing sdkconfig.defaults.esp32 and bootloader offset misconfiguration, which were resolved to enable successful compilation and flashing. Various ESP32 variants were tested, including ESP32-C3, ESP32-C6, ESP32-CAM, ESP32-C2, ESP32-D0WDQ5-V3 (ESP-WROOM-32), and ESP32-S3, with reports on flash size detection, bootloader behavior, and peripheral support. Challenges encountered involved stack overflows on reboot, watchdog timer resets, and GPIO functionality inconsistencies, particularly on non-C/S ESP32 boards. Solutions included adjusting makefiles for 4MB flash, fixing bootloader offsets, increasing task stack sizes, and replacing software timers with hardware timers for improved timing accuracy. Peripheral drivers such as BMP280, AHT2x, DS1820, DHT11/22, PWM, UART, and NTP were tested with varying success; some required specific pin assignments or additional delays to prevent crashes. Deep sleep support was added without GPIO wakeup. The firmware uses the Espressif ESP-IDF SDK for ESP32 and plans for ESP8266 porting were discussed, noting SDK differences and RAM constraints. Continuous integration (CI) and online build availability were confirmed. Users shared flashing tools, partition table considerations, and debugging tips including esptool flash_id and efuse burning. The community actively tested and reported logs, crashes, and feature functionality, contributing to iterative fixes and enhancements.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT