ESP32-P4-ETH: Difference between revisions
| (13 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{GD Template Impl}} | {{GD Template Impl}} | ||
==Important Notes== | ==Important Notes== | ||
<font color=red> | <font color=red> | ||
* This documentation describes ESP32-P4-ETH bare board. | |||
* The board is equipped with PoE expansion header ONLY. External PoE module must be purchased separately to achieve PoE power supply. | |||
* Onboard microphone and speaker connector are provided. Audio codec and amplifier are NOT assembled on the board. | |||
* MIPI-DSI display, MIPI-CSI camera and speaker are peripherals, NOT included with bare board. | |||
</font> | </font> | ||
| Line 73: | Line 69: | ||
* [https://docs.waveshare.com/ESP32-P4-ETH/Development-Environment-Setup-IDF Working with ESP-IDF] | * [https://docs.waveshare.com/ESP32-P4-ETH/Development-Environment-Setup-IDF Working with ESP-IDF] | ||
* [https://docs.waveshare.com/ESP32-P4-ETH/Firmware-Flashing Firmware Flashing and Erasing] | * [https://docs.waveshare.com/ESP32-P4-ETH/Firmware-Flashing Firmware Flashing and Erasing] | ||
==FAQ== | ==FAQ== | ||
| Line 84: | Line 79: | ||
A: Please first check the component documentation to confirm compatible screen types: [https://github.com/waveshareteam/Waveshare-ESP32-components/tree/master/bsp/esp32_p4_platform esp32_p4_platform] | A: Please first check the component documentation to confirm compatible screen types: [https://github.com/waveshareteam/Waveshare-ESP32-components/tree/master/bsp/esp32_p4_platform esp32_p4_platform] | ||
</div> | |||
</div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
<div style="font-weight:bold;line-height:1.0;"> | |||
Q2: How do I determine my ESP32-P4 chip revision? | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
A: Check the silkscreen marking on the chip and the boot log from the serial port. The ESP32-P4 Platform examples provide build configurations for rev v3.0 and later chips, rev v3.1 and later chips, and rev v0.x / v1.x engineering samples. Before flashing, make sure the firmware configuration matches the actual chip revision. | |||
</div> | </div> | ||
</div> | </div> | ||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
<div style="font-weight:bold;line-height:1.0;"> | |||
Q3: Which ESP-IDF version is recommended for ESP32-P4? | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
A: ESP-IDF v5.5.1 ~ v5.5.4 is recommended. The ESP32-P4 Platform examples are primarily maintained for ESP-IDF release/v5.4 and later versions. Some advanced UI examples may retain compatibility notes for release/v5.3; please refer to the README in the example directory for details. | |||
</div> | |||
</div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
<div style="font-weight:bold;line-height:1.0;"> | |||
Q4: Which ESP-IDF version is recommended for ESP32-P4? | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
A:This message means the firmware's ESP32-P4 chip revision configuration doesn't match the chip on your board. Do not use <code>--force</code>to skip the check — rebuild with the correct chip revision instead. | |||
The ESP32-P4 Platform repository provides shared configuration files: | |||
* rev v3.1 or later: <code>config/esp32p4_rev_v3_1.defaults</code> | |||
* rev v3.0 or later: <code>config/esp32p4_rev_v3_0.defaults</code> | |||
* rev v0.x / v1.x engineering sample: <code>config/esp32p4_rev_pre_v3.defaults</code> | |||
Specify the matching config in the example directory via SDKCONFIG_DEFAULTS. See the detailed instructions under [https://docs.waveshare.com/ESP32-P4-ETH/Development-Environment-Setup-IDF#p4-revision-config ESP-IDF examples.] | |||
[[File:ESP32-P4-ETH-10.jpg| 700px]] | |||
</div> | |||
</div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
<div style="font-weight:bold;line-height:1.0;"> | |||
Q5: Can the development board be powered by both USB Type-C and PoE at the same time? | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
A: Yes, it does not affect power delivery. | |||
</div> | |||
</div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
<div style="font-weight:bold;line-height:1.0;"> | |||
Q6: What is the maximum camera resolution supported by ESP32-P4? | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
A: During functionality testing, we have validated several features. Currently, there are developments such as using a Cat-4 module to provide network connectivity for the P4, or using the P4's MIPI-DSI to extend a host screen. However, for stability reasons, related example programs are not yet provided. They will be added to the wiki once the features and solutions are more mature. | |||
</div> | |||
</div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
<div style="font-weight:bold;line-height:1.0;"> | |||
Q7: Can I develop using PlatformIO or MicroPython? | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
A: | |||
* For stability, support for ESP32-P4 in PlatformIO requires the PlatformIO community to support the Arduino-esp32 SDK version 3.1x. | |||
* During development, we have experimented with using MPY firmware for the ESP32-P4, which can run simple commands. However, this is still in the validation phase. Actual interfaces and peripheral applications are not yet fully adapted. Once adaptation is complete and stable, usage examples for ESP32-P4 in MicroPython will be released. | |||
</div> | |||
</div> | |||
<!--Add review function! --> | <!--Add review function! --> | ||