# ESP32-C5 Boot Failure with Shared External Clock

**URL:** <https://forum.digikey.com/t/esp32-c5-boot-failure-with-shared-external-clock/69516>\
**Category:** Support\
**Created:** [June 8, 2026, 8:53am UTC](https://forum.digikey.com/t/esp32-c5-boot-failure-with-shared-external-clock/69516 "2026-06-08T08:53:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![matteo.schembri](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@matteo.schembri](https://forum.digikey.com/u/matteo.schembri)\
**Post date:** [June 8, 2026, 8:53am UTC](https://forum.digikey.com/t/esp32-c5-boot-failure-with-shared-external-clock/69516/1 "2026-06-08T08:53:23Z")

</div>

Hello everyone,

We are currently developing an 8-node phase-coherent WiFi CSI (Channel State Information) channel sounder using the **ESP32-C5** for academic MIMO propagation research.

To maintain phase coherence across all receiver nodes and eliminate inter-node Carrier Frequency Offset (CFO), we must share a common frequency reference. According to Espressif’s ESP-Techpedia documentation, the **“esp-crab”** project handles multi-antenna RF phase synchronization via a common crystal.

However, we have run into a critical hardware roadblock, and the hardware design files (schematics, BOM) for the `esp-crab` example are missing from Espressif’s repository [[https://github.com/espressif/esp-csi/tree/master/examples/esp-crab\](https://github.com/espressif/esp-csi/tree/master/examples/esp-crab%5C)].

**The Problem:** We are attempting a master/slave clock topology, but **the slave ESP32-C5 microcontrollers fail to boot** when driven by the shared clock source.

Because the reference schematics are unavailable, we are flying blind regarding the specific hardware requirements for external clocking on this chip. We have also opened an issue on GitHub ([Issue #259 on espressif/esp-csi](https://github.com/espressif/esp-csi/issues/259)) but are hoping someone in the community or the DigiKey engineering team might have experience with this.

**Our specific questions are:**

- **Boot Requirements:** Are there specific eFuse configurations, strapping pin states, or input voltage swing requirements on `XTAL_P` to allow the ESP32-C5 to boot successfully without a dedicated crystal?

- **Pin Treatment:** What is the proper hardware treatment of the `XTAL_P` and `XTAL_N` pins on the slave chips? (e.g., should `XTAL_N` be left floating, AC-coupled to GND, or actively driven?)

- **Internal Oscillator:** How does the internal Pierce oscillator behave when driven externally, and does it need to be explicitly disabled to prevent startup hangs?

- **Topology:** Is a dedicated clock fanout buffer strictly required to scale this reliably to an 8-node setup, or can the master drive them directly with appropriate impedance matching?

If anyone has successfully implemented a shared clock architecture on the ESP32-C5 (or similar ESP32-C series) or has insights into the undocumented boot requirements for external clocking, your guidance would be greatly appreciated. We are finalizing our custom PCB design and this is our last major hurdle.

Thank you in advance!

---

<div class="post-metadata">

**Author:** ![Kaleb\_Kohlhase](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/kaleb_kohlhase/32/59963_2.png) [@Kaleb\_Kohlhase](https://forum.digikey.com/u/Kaleb_Kohlhase)\
**Post date:** [June 8, 2026, 1:49pm UTC](https://forum.digikey.com/t/esp32-c5-boot-failure-with-shared-external-clock/69516/2 "2026-06-08T13:49:56Z")

</div>

Hello matteo.schembri, welcome to the TechForum! I do appreciate the detailed description of the problem you are facing. However, this is a pretty advanced ESP32-C6 hardware/boot topic. You may have better visibility and more directed answers if you were to look through their ESP32 forum and even look at their technical inquiry page:

[ESP32 Forum](https://esp32.com/viewforum.php?f=23&sid=f54c3b9e1965af2b62681f1e480e5352)

[Technical Inquiries](https://www.espressif.com/en/contact-us/technical-inquiries)

I apologize as I do not have this amount of experience to know how to approach your questions directly.

---

<div class="post-metadata">

**Author:** ![David\_1528](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/david_1528/32/47212_2.png) [@David\_1528](https://forum.digikey.com/u/David_1528)\
**Post date:** [June 12, 2026, 4:36pm UTC](https://forum.digikey.com/t/esp32-c5-boot-failure-with-shared-external-clock/69516/3 "2026-06-12T16:36:18Z")

</div>

I’m not an expert on the subject matter, but from this source:

> **[Schematic Checklist - ESP32-C5 - — ESP Hardware Design Guidelines latest...](https://docs.espressif.com/projects/esp-hardware-design-guidelines/en/latest/esp32c5/schematic-checklist.html)**

It states the following:

> ## Clock Source
> 
> ESP32-C5 supports two external clock sources:
> 
> - [External crystal clock source (Compulsory)](https://docs.espressif.com/projects/esp-hardware-design-guidelines/en/latest/esp32c5/schematic-checklist.html#external-crystal-clock-source-compulsory)
> 
> - [RTC clock source (Optional)](https://docs.espressif.com/projects/esp-hardware-design-guidelines/en/latest/esp32c5/schematic-checklist.html#rtc-clock-source-optional)
> 
> ### External Crystal Clock Source (Compulsory)
> 
> The ESP32-C5 firmware only supports 48 MHz crystal.

That implies that, at a minimum, that they don’t expect one to be adding an external clock source, and that it would require delving deep into the firmware to figure out how to reconfigure it to accept an external clock.

---

<div class="post-metadata">

**Author:** ![n.i.c.laboratories](https://avatars.discourse-cdn.com/v4/letter/n/9d8465/32.png) [@n.i.c.laboratories](https://forum.digikey.com/u/n.i.c.laboratories)\
**Post date:** [November 14, 2026, 6:15pm UTC](https://forum.digikey.com/t/esp32-c5-boot-failure-with-shared-external-clock/69516/4 "2026-11-14T18:15:52Z")

</div>

Hi Matteo,  
we are building something close to your sounder — a hand-held array of ten ESP32-C5 receivers whose CSI is combined — and we hit the same wall with a shared 48 MHz clock. We have no boards on the bench yet, so all of this is reading and physics, not measurement; but it may save you some time, and the second half may spare you the clock altogether.  
David is right that Espressif’s checklist calls the crystal compulsory and the firmware supports only 48 MHz. We read that as the frequency, though, not a ban: a clean 48 MHz on the oscillator’s input should look to the firmware like its crystal, and Espressif’s own esp-crab runs two C5s on one crystal. What is unknown is the hardware, so that is what the points below are about.  
If you keep the shared clock  
One crystal will not drive eight chips. Hung on the master’s crystal node, seven more pin capacitances, seven 24 nH inductors and the traces between them pull its swing below what the chips need (Espressif asks for a crystal amplitude above 500 mV), or stop it. Espressif’s own esp-crab (esp-csi, examples/esp-crab) shares one crystal between two C5s only. For eight: a 48 MHz TCXO into an LVCMOS fan-out buffer, one output per chip, series-terminated, AC-coupled, short traces — and the clock running before CHIP\_PU rises.  
Drive the amplifier’s input. XTAL\_P/XTAL\_N are a Pierce oscillator; the datasheet (v1.5, Table 2-9) does not say which pin is the inverter’s input — only “External clock input/output connected to chip’s crystal or oscillator. P/N means differential clock positive/negative”. With a scope: on a working board the input usually carries the smaller, cleaner sine (use the lowest-capacitance probe you have); with the crystal removed, try ~100 pF into XTAL\_P, then XTAL\_N, then both in antiphase, and see which boots.  
Keep the 24 nH on XTAL\_P. Espressif puts it there to keep the crystal’s harmonics off the radio; at 48 MHz it is ~7 ohms and does not stop the clock. An injected square clock needs it more — its 51st harmonic is 2448 MHz.  
A shared clock gives a common frequency, not a fixed phase. The ESPARGOS authors (arXiv 2502.09405) report that the phase changes after every reset and every change of channel. So a calibration after each lock is needed whatever the clock: a common reference signal (ESPARGOS), one element sending to the rest, or — if your array moves — fitting each receiver’s fixed phase out of the data. Power save off and no retune during a measurement keep one calibration good.  
If amplitude is enough: no shared clock  
That is where we ended. With every chip on its own crystal the phase between receivers is new in every frame, but the amplitudes, with the gain held fixed, carry nearly everything we need:  
on each frame, set the receivers against one another — the sender’s power and the room’s fading cancel;  
let the sender alternate two crossed antennas a frame each: in one receiver the ratio of the two frames has no receiver gain in it at all;  
if the array moves, level each receiver against its own record over the motion;  
for focusing, use the sender’s own wave as the reference of an in-line (Gabor) hologram: the change in amplitude is the part of the scattered wave in step with the illumination, and it can be propagated back.  
Our model of this (rough: a 2D wall, single frequencies, assumed materials) draws a cable a few centimetres deep in a wall about as well as with full phase; what it loses is depth. It is open, with the scripts — principle.md and calc/nosync.py in the repository below. For angle-of-arrival or true MIMO you will need the phase, so this may not fit you, but if part of your work is sensing it may spare you the clock.  
What else is published about clocks on these chips: ESPARGOS’s docs (“Phase-Coherent Multi-Array Systems”) — a 40 MHz reference on a coax shared with a 2.4 GHz phase signal, a star of identical cables from a resistive splitter, an amplifier beyond two boards, “1 Vpp at the SYNC IN … is definitely sufficient”, and a slave without the clock “cannot boot its sensors” (their chips are 40 MHz ones, not the C5). The esp-crab hardware files are not out; GitHub issue #259 on esp-csi asks for them.  
If you try the checks in point 2, we would be glad to hear what you find — it would settle the question for everyone building such an array on the C5. And if we get there first, we will post it here.  
Best regards,  
Pavel  
Project-NIC — [GitHub - Project-NIC/NIC-Sluchalo: A hand-held wall scanner: what is in a wall, seen by the shadow Wi-Fi casts through it, with a knock and microphones for masonry. A concept — nothing built yet. · GitHub](https://github.com/Project-NIC/NIC-Sluchalo)
