Info:MAIN:Time 4156, idle 0/s, free 32560, MQTT 0(260), bWifi 1, secondsWithNoPing 4090, socks 0/0
Info:MAIN:Time 4157, idle 0/s, free 32560, MQTT 0(260), bWifi 1, secondsWithNoPing 4091, socks 0/0
Info:MAIN:Time 4158, idle 0/s, free 32560, MQTT 0(260), bWifi 1, secondsWithNoPing 4092, socks 0/0
Info:MAIN:Time 4159, idle 0/s, free 30648, MQTT 0(260), bWifi 1, secondsWithNoPing 4093, socks 0/0 while(1)
{
int len = uart_read_bytes(uartnum, data, 512, 20 / portTICK_RATE_MS);
if(len)
{
for(int i = 0; i < len; i++)
{
UART_AppendByteToReceiveRingBuffer(data[i]);
}
}
}
[00:43:42]Info:MAIN:Time 411, idle 0/s, free 27140, MQTT 0(26), bWifi 1, secondsWithNoPing 344, socks 0/0
[00:43:43]Info:MAIN:Time 412, idle 0/s, free 27140, MQTT 0(26), bWifi 1, secondsWithNoPing 345, socks 0/0 
insmod wrote:Didn't fix OTA (and i have no idea why it doesn't
insmod wrote:What platforms need PWM duty update every 25ms? I had to hack ESP8266 and ESP-IDF pwm code so that it would update duty only once. Otherwise it spams the console.
insmod wrote:Fixed OTA
insmod wrote:What to do with 8mb flash? Max firmware size, from what i remember, is 1MB. 6mb LFS?
(Cfg size: 3584, change counter: 6, ota counter: 1, incomplete boots: 1 (might change to 0 if you wait to 30 sec)!insmod wrote:You did have BW20, i remember you posted an ali order screenshot with it.
insmod wrote:There is a possibility to OTA from Tasmota, but firmware must be built manually with this guide
"why does it take two back click to go back from config to home page??""does flag 37 actually work??"
HTTP/1.1 200 OK
Content-Type: text/html
Content-Encoding: gzip
Content-Length: 1234
TL;DR: OpenESP8266 now boots on 1MB, 2MB, 4MB, and 8MB ESP8266/ESP8285 boards, and one developer called the OTA fix "merge-ready" after partition issues were corrected. This FAQ helps builders flash, size, and troubleshoot OpenBeken on ESP8266-class hardware with ESP-Flasher or esptool. [#21597042]
Why it matters: ESP8266 support is usable for testing and many real devices, but flash mode, partition size, OTA headroom, and pin indexing still decide whether a build boots cleanly or crashes.
| Topic | 1MB flash | 2MB flash | 4MB/8MB flash |
|---|---|---|---|
| Firmware style seen in thread | factory app | OTA layout | OTA layout |
| Example boot result | confirmed boot | confirmed boot after DOUT flashing | confirmed boot |
| LFS space seen | 64KB | 128KB | 192KB in shown 4MB/8MB layouts |
| OTA status in thread | fixed build exists | fixed after partition change | fixed after partition change |
Key insight: Most "bad firmware" symptoms in this thread were not random. They came from three concrete causes: wrong flash mode, wrong partition layout, or too little free flash/RAM for OTA and runtime features. [#21596825]
write_flash 0 ...bin. 3. If boot fails on ESP8285-class boards, retry with --flash_mode dout. One tester said the ESP-12F process was the same as ESP-01: GPIO0 low, normal serial wiring, flash to 0x0, and boot succeeded. [#21757469]unaligned segment length 0xffffffff and Image validation failed. Later testing showed OTA started working again after removing some compiled drivers and, in practice, stopping running drivers before update. The thread ties this to image size and memory pressure, not to Wi-Fi alone. [#21758993]lfs is absent because the partition exists in the table but no files have been uploaded yet. The same logs also show failed to get file autoexec.bat, which matches an empty LFS rather than a bad firmware flash. [#21595385]GPIO_NUM_NC, labeled NC, and hidden in the UI so the index numbers could line up with real IO names like IO12 and IO16. The same discussion added a separate ADC entry while keeping unusable flash-connected pins out of normal configuration. [#21759275]esptool write_flash 0 ... --flash_mode dout, even though the later log still printed SPI Mode : QIO. A separate 2MB case also failed until a flasher run produced a boot log that explicitly showed SPI Mode : DOUT. The practical fix was simple: use DOUT when the module refuses to boot after normal flashing. [#21599222]startDriver, not 12. A proposed fix used NC placeholders for missing pins so index 12 equals IO12 and index 16 equals IO16. Another maintainer preferred parsing names like IO12 directly in commands, which avoids platform-specific mental math entirely. [#21759160]Content-Encoding: gzip. The thread proposed an LFS lookup that checks for filename.gzip first, then streams that compressed file while keeping a normal fallback path. A maintainer then implemented an "upload as GZIP" button and simple gzip header handling in firmware so the browser decodes the file on the fly. This matters because the fully minified WebApp was measured at 195,261 bytes, which is large for small-flash targets. [#21601376]DS1820, while Tasmota used DS18B20, forcing external scripts to handle both keys. Maintainers agreed that OBK should follow the Tasmota standard, then changed it and also checked Tasmota’s multi-sensor format using names like DS18B20-1 with an Id field. That keeps MQTT consumers and simple PHP or Home Assistant tooling more portable. [#21702907]