ESPHome 2026.11.0-dev
Loading...
Searching...
No Matches
esphome::zephyr_coredump Namespace Reference

Data Structures

class  Coredump
 

Functions

 ESPHOME_LOG_TAG (TAG, "zephyr_coredump")
 
bool coredump_pending ()
 Whether a dump from before this boot is waiting to be printed.
 
void print_coredump ()
 A log reader is present: serial at boot, USB CDC when the port opens, an API or MQTT client subscribing.
 
void stop_coredump ()
 The reader went away (the USB port was closed); the print stops and the dump stays for the next one.
 

Variables

constexpr const char * CRASH_LOG_TAG = "zephyr_coredump"
 The tag the dump is logged under, so a client can check the level in force for it.
 

Function Documentation

◆ coredump_pending()

bool esphome::zephyr_coredump::coredump_pending ( )

Whether a dump from before this boot is waiting to be printed.

Definition at line 35 of file coredump.cpp.

◆ ESPHOME_LOG_TAG()

esphome::zephyr_coredump::ESPHOME_LOG_TAG ( TAG ,
"zephyr_coredump"  )

◆ print_coredump()

void esphome::zephyr_coredump::print_coredump ( )

A log reader is present: serial at boot, USB CDC when the port opens, an API or MQTT client subscribing.

The stored dump is printed from the start and erased once it has gone out; a print already under way carries on.

Definition at line 37 of file coredump.cpp.

◆ stop_coredump()

void esphome::zephyr_coredump::stop_coredump ( )

The reader went away (the USB port was closed); the print stops and the dump stays for the next one.

Readers are not told apart: closing the USB port also stops a print an API or MQTT client is receiving, and a client that disconnects does not stop one, the same as the other platforms' crash records.

Definition at line 43 of file coredump.cpp.

Variable Documentation

◆ CRASH_LOG_TAG

const char* esphome::zephyr_coredump::CRASH_LOG_TAG = "zephyr_coredump"
inlineconstexpr

The tag the dump is logged under, so a client can check the level in force for it.

Definition at line 7 of file coredump.h.