You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think one can disable logs per component name using esp_log_level_set("cam_hal", ESP_LOG_INFO);, however some of logs generated by this library don't use standard way of logging in ESP, but ESP_CAMERA_ETS_PRINTF macro which is ets_printf.
Example:
cam_hal: EV-EOF-OVF
W (29504) cam_hal: NO-SOI // Can be disabled using the function described above
cam_hal: EV-EOF-OVF
cam_hal: EV-EOF-OVF
cam_hal: EV-EOF-OVF
cam_hal: EV-EOF-OVF
cam_hal: EV-VSYNC-OVF
Another small issue is they look not as nice in the logs (missing the standard prefix).
The only instance of this is at ll_cam_send_event function:
I guess there maybe is no way to efficiently use standard logging (ESP_LOGX) inside this IRAM_ATTR-marked function, but how about making some macro (configurable form Kconfig?) as option to disable this one log?
The text was updated successfully, but these errors were encountered:
I guess there maybe is no way to efficiently use standard logging (ESP_LOGX) inside this IRAM_ATTR-marked function
It should be possible to use ESP_DRAM_LOGx for this.
The only issue is that it was added in IDF v4.2, while this library has to support v4.1 and later, at least until February when IDF v4.1 will become EoL. I would probably suggest waiting until then, removing v4.1 support, and then replacing the logging macros with ESP_DRAM_LOGx.
I am trying to figure out how to full disable cam_hal messages. I am trying to view some output in the terminal put they are completely drowned out by constant cam_hal messages.
I think one can disable logs per component name using
esp_log_level_set("cam_hal", ESP_LOG_INFO);
, however some of logs generated by this library don't use standard way of logging in ESP, butESP_CAMERA_ETS_PRINTF
macro which isets_printf
.Example:
Another small issue is they look not as nice in the logs (missing the standard prefix).
The only instance of this is at
ll_cam_send_event
function:esp32-camera/driver/cam_hal.c
Lines 104 to 111 in 2478a5f
I guess there maybe is no way to efficiently use standard logging (
ESP_LOGX
) inside thisIRAM_ATTR
-marked function, but how about making some macro (configurable formKconfig
?) as option to disable this one log?The text was updated successfully, but these errors were encountered: