ADSP_W015 — Eavb Underrun

Causes

• Intermittent or low supply voltage to the Eavb module (battery, precharge, auxiliary supply)
• Faulty or loose power/ground connections or corroded connectors at the module
• CAN/LIN/bus communication errors, high bus error rate or missing messages
• Software/firmware mismatch, recent update or ECU reflash that introduced timing issues
• High CPU/memory load on ADSP causing buffer underruns or scheduling delays
• Faulty Eavb module (internal electronics, watchdog, buffer) or failing sensors/actuators it controls

Symptoms

• Warning message or amber warning light in the instrument cluster referencing ADSP/Eavb
• Degraded or loss of function for the circuit(s) controlled by the Eavb (may be subsystems such as valves, actuators or HVAC functions)
• Intermittent operation that may return after vehicle power cycle
• Reduced vehicle functionality or limp/limited mode for related systems
• Stored event data and increased bus error counters in vehicle diagnostic logs

What to check

• Read Tesla diagnostic logs with factory or approved scan tool; capture full event timestamp and freeze frame data
• Check vehicle 12 V and high-voltage auxiliary supply voltages at rest and during fault occurrence
• Inspect Eavb module connector and harness for corrosion, bent pins, water ingress, or mechanical damage
• Check fuses, fusible links and power distribution for the Eavb circuit
• Monitor CAN/LIN bus health and error counters while attempting to reproduce the fault
• Confirm current software/firmware levels of ADSP and Eavb and check for known bulletins or recent updates

Signal parameters

• Supply voltage to Eavb: nominal 9–16 V (monitor for drops below threshold during events)
• CAN message frequency: expected periodicity for Eavb messages (watch for missing frames or increased interval)
• Message timeout threshold: module declares underrun if no valid data within configured timeout (vehicle-specific)
• Bus error rate: CRC/frame error counts per minute (elevated indicates communication issues)
• Module supply ripple/noise: excessive noise can cause buffer underruns or resets
• CPU load/memory usage on ADSP (if available) showing spikes or saturation prior to event

Similar codes