Update P4 config for C5 slaves

[me-no-dev]

This pull request updates several Wi-Fi RMT buffer and window configuration parameters in the configs/defconfig.esp32p4 file. The changes primarily reduce buffer sizes and the receive window, likely to optimize memory usage or improve performance for the ESP32-P4 platform.

Wi-Fi RMT buffer and window configuration adjustments:

• Reduced CONFIG_WIFI_RMT_STATIC_RX_BUFFER_NUM from 16 to 10, decreasing the number of static receive buffers allocated for Wi-Fi RMT operations.
• Reduced CONFIG_WIFI_RMT_DYNAMIC_RX_BUFFER_NUM from 64 to 32 and CONFIG_WIFI_RMT_DYNAMIC_TX_BUFFER_NUM from 64 to 32, lowering the dynamic buffer allocation for both RX and TX.
• Reduced CONFIG_WIFI_RMT_RX_BA_WIN from 32 to 16, decreasing the block acknowledgment receive window size.

Reference: #323

[lyusupov]

@me-no-dev

Currently used 2.0.12 ESP-HOSTED version is not up to date
https://components.espressif.com/components/espressif/esp_hosted/versions/2.0.12/readme?language=en

It could make sense to update this component first onto a more recent stable release,
then try to apply these new Wi-Fi settings.

[lyusupov]

I'll try to use the artifacts for this PR to boot Arduino Core on P4 host with C5 slave.
It will take some time....

When the boot sequence with W-Fi enabled will succeed - I'll let you know.

[me-no-dev]

@lyusupov the latest esp-hosted will be used when libs are built. If you get the ones from this PR, they will/should be the latest version

[lyusupov]

the latest esp-hosted will be used when libs are built

Yes. I can see it

[me-no-dev]

Uhmmm... some bad news: espressif/esp-hosted-mcu#71 (comment)
@Jason2866 @lyusupov seems that currently the slave type is a compile option for esp-hosted

[Jason2866]

@me-no-dev I think the currently most used (and configured) slave MCU is the C6. So the currently merged PR #323 can be kept.

All other slave setups have to use Arduino as an component of IDF and adopting the sdkconfig settings.

[lyusupov]

@Jason2866

I see no arguments to apply a breaking #323 PR with an imaginary "performance improvement" at cost of reducing compatibility with other products made by honorable Espressiif company.

I believe that : Espressiif products compatibility - first, performance -second.

@me-no-dev I've placed my comment in espressif/esp-hosted-mcu#71 (comment) thread.

[lyusupov]

@me-no-dev
I've used the P4 LIB binaries taken from artifacts section to this Actions build and applied them over current Core 3.3.2 installation.
Then I've built both STA and AP Wi-Fi demo sketches from this folder https://github.com/espressif/arduino-esp32/tree/master/libraries/WiFi/examples and ran them on P4 together with C5 slave.
Both STA and AP tests boot and work fine.

So I have no objections for you to apply this PR #324

[me-no-dev]

@lyusupov given that currently custom libs are required for C5 to be used as slave, I suggest we keep this open but not merged for the time being. You can adjust the values in your lib-builder manually, since you are using it anyway.

[lyusupov]

You can adjust the values in your lib-builder manually

No, that's not true.

I am not sure that you know or not - but the https://github.com/espressif/esp32-arduino-lib-builder since many months ago is failing to build the artifacts when a regular GitHub user makes a fork of the repo and executes the Actions script manually by pushing a commit.

It looks like there are certain permission restrictions on certain resources in use during the build.
And a regular GitHub user is not allowed to access these esp32-arduino-lib-builder private resources.

That's why to garb some binaries from master repo https://github.com/espressif/esp32-arduino-lib-builder/actions Actions build is the only way to take the updated libs created by someone else.

[me-no-dev]

@lyusupov I meant locally on your computer.

[lyusupov]

I meant locally on your computer.

No. I have neither enough resources nor knowledge on how to do that.