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

Question

ESP32 fixed, it lacked sdkconfig.defaults.esp32. Now configured with 4MB by default.

insmod · Accepted Answer

I messed up the merge on c3 (bootloader must be at 0x0, instead of 0x1000), here is the fixed one

insmod · Accepted Answer

Regarding tasmota partitions: doubtful, as modern versions use "safeboot" partition, which is not applicable here. Pre v12 it have been possible, but not now. Also, i've looked at the csv files in tasmota, and they're only for 4MB flash.
CI is ready, binaries are available at github.

p.kaczmarek2 · Answer

very nice, it would be also nice to get basics running on ESP8266. I can help, especially if we get online builds to work. They help me a lot because they allow me to develop anywhere without having a toolchain. As far as I can tell, most of the ESP8266 devices have 2MB flash on the board so it should be enough for basic functionality.

DeDaMrAz · Answer

Can I join the topic by asking for any progress update on this? And also to second the @p.kaczmarek2 thought on most of 8266 boards running on 2Mb Vs rare 4Mb boards.

p.kaczmarek2 · Answer

So what kind of ESP32 modules do you guys have? I've found that one: Looks like ESP32-C3

insmod · Answer

I have an ESP32-C3 Supermini, which isn't without its troubles (solved with esp_wifi_set_max_tx_power(13 * 4) under a define), and WeAct ESP32-C6-Mini.
Also have an ESP32-CAM module, + i can spare an ESP32-CAM, where i replaced tho stock module with an ESP32-S3.
Additionally have 2 of the fake ESP32-S2 Mini
Don't have any devkits with ESP32-C2 modules, only 01C with combo flashing board (32-wroom, esp-12, esp-01).

p.kaczmarek2 · Answer

I can try to flash some test binaries in a moment. I also have this ESP32 device: It has ESP32-DOWD inside it seems.

insmod · Answer

Hm, it is in my plan to port as my esp32-c6 has a single ws2812b led.

divadiow · Answer

>>21220858
4mb ESP32-C2-12 (revision v1.0) dev board
4mb ESP32-D0WDQ5-V3 (revision v3.1) (ESP-WROOM-32) dev board
4mb ESP32-C3 on PCB in SPI/PWM LED device (about to solder up to flash)

older
2x 4mb ESP8266EX dev boards
other 1/2/4mb ESP8285/8266 in devices and loose modules

DeDaMrAz · Answer

I stay corrected, most of the ESP-12E modules I've taken from devices have 25q32FV chips which are 32Mbits (aka 4Mbytes) and I was drawn to 2Mb because BK7231 chips have that as the base.

p.kaczmarek2 · Answer

I may be wrong, but as far as I remember, it's very easy to swap SPI flash to larger one in ESP, or at least for ESP's that have external flash, of course. So not for ESP8285, etc... but for ESP8266, etc, you can solder an SPI Flash chip and it should work, correct me if I'm wrong.
https://www.instructables.com/ESP-03-Upgrade-Flash-Memory-to-128-M-Bit/
https://github.com/micropython/micropython/issues/2335

insmod · Answer

>>21220976 Correct, I have done it once. It was an ESP-01 with 1MB flash, I successfully replaced it for 4MB, which then correctly showed up in esptool flash_id.

DeDaMrAz · Answer

My concern was that most of the OBK users will not be able to do a chip swap as they find it difficult to flash the device in situ in the first place.

But more is better and i think 4Mb base would be perfect, at least for those who are trying to run OBK on the common ESP devices.

divadiow · Answer

Code: TextLog in, to see the code but sadly Code: TextLog in, to see the code

p.kaczmarek2 · Answer

How do you flash it? I have C3 as well, I can test

divadiow · Answer

Added after 1 [minutes]:posted too soon perhaps. Tasmota32C3 2mb does the same. I investigate

p.kaczmarek2 · Answer

Some early OBK printfs are there, but then it crashes:

divadiow · Answer

my issue relates to encryption flags. Code: TextLog in, to see the code vs dev board: Code: TextLog in, to see the code Added after 54 : unique to my device so I'll deal with that on its own

p.kaczmarek2 · Answer

Very promising, I'll check more:

Added after 29 [seconds]:

Added after 1 [minutes]:

Congratulations, you did it! Now, which basic features are missing and how I can help? I personally consider online builds to be pretty high priority... I need to revise the PR code to know more, I will do it in the morning, as it's midnight here.

DeDaMrAz · Answer

No luck with the dev board I got


my EPS32 dev board log
Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-D0WDQ6-V3 (revision v3.0)
 - Number of Cores: 2
 - Max CPU Frequency: 240MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: NO
 - Has Factory-Calibrated ADC: YES

p.kaczmarek2 · Answer

Even scan works: Added after 3 [minutes]:it also connects to WiFi successfully:

divadiow · Answer

burnt efuse with espefuse.exe --port com9 burn_efuse DIS_DOWNLOAD_MANUAL_ENCRYPT espefuse.exe --port com9 burn_efuse SPI_BOOT_CRYPT_CNT to make Code: TextLog in, to see the code anyway. the import thing is Code: TextLog in, to see the code Added after 3 [minutes]:

p.kaczmarek2 · Answer

Nice, I didn't notice that LFS works:


again:
addChannel 1 1
delay_s 1
goto again

However, I am now confused, it seems to increase less frequently than every second.

divadiow · Answer

Some stuff to be worked out I guess. How does one account for the different frequency crystals? Is that related? I see 40 and 26 in my esptool info returns for different dev boards

p.kaczmarek2 · Answer

The issue with script counting too slowly seem to be ESP-related. It works good on WB3S:

On ESP increase is every few seconds:

It seems that delta time of the scripts tick is invalid:

Log in, to see the code

it is called from user_main.c:

Log in, to see the code

Maybe g_deltaTimeMS is invalid on ESP globally.

Here is a larger snippet:

Log in, to see the code

Does that mean the QuickTick thread gets fired not often enough?

Log in, to see the code

I am not sure right now....

insmod · Answer

>>21221104 The code


#if defined(PLATFORM_BEKEN) || defined(WINDOWS)
	g_time = rtos_get_time();
#elif defined (PLATFORM_ESPIDF)
	g_time = esp_timer_get_time() / 1000;
#else
	g_time += QUICK_TMR_DURATION;
#endif

mitigates this somewhat, but it's still a little slower (MAIN:Time 150, channel 1 has changed to 121)

p.kaczmarek2 · Answer

But what is the core source of the problem? Is the QUICK_TMR_DURATION tick frequency too high for used SDK? rtos_init_timer is not that precise?

I would try to setup an empty timer (or a timer toggling pin) with QUICK_TMR_DURATION duration and check on scope/logic analyzer how often in reality it toggles.

Or simplify the experiment and insert pin toggle in Quicktick entry.

Added after 3 [minutes]:

Maybe something like CONFIG_FREERTOS_HZ setting is needed? Just guessing, I've done a very little research so far.

insmod · Answer

>>21221113 in quick_timer_thread vTaskDelay(QUICK_TMR_DURATION / portTICK_RATE_MS); instead of vTaskDelay(QUICK_TMR_DURATION); is now almost alright, 1-2 sec error.

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

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Post #30

Topic summary