PDK API Guide for J721E
CPSW TRACE API

Introduction

Enumerations

enum  CpswTrace_TraceLevel {
  CPSW_TRACE_NONE = 0U, CPSW_TRACE_ERROR = 1U, CPSW_TRACE_WARN = 2U, CPSW_TRACE_INFO = 3U,
  CPSW_TRACE_DEBUG = 4U, CPSW_TRACE_VERBOSE = 5U
}
 Enumerates the types of trace level. More...
 

Enumeration Type Documentation

Enumerates the types of trace level.

Enumerator
CPSW_TRACE_NONE 

All traces are disabled at runtime

CPSW_TRACE_ERROR 

Error trace level

CPSW_TRACE_WARN 

Warning trace level

CPSW_TRACE_INFO 

Info trace level: enables only important informational messages for the user (i.e. PHY link is up or down, NIMU layer is ready, etc).

The amount of info logs is not invasive in nature so this trace level may be enabled by applications at init time.

CPSW_TRACE_DEBUG 

Debug trac level: enables further information messages about operations taking place in the driver (i.e. a submodule is being opened, PHY auto-negotiation is started, etc).

The debug level should be enabled by the user on a need basis (i.e. for debugging or tracing execution flow, etc) as the number of messages will increase considerably with respect to CPSW_TRACE_INFO level.

This trace level can be enabled at runtime only in 'debug' builds.

CPSW_TRACE_VERBOSE 

Verbose trace level: enables even further messages about operations taking place in the driver (i.e. PHY state transitions, DMA transfer completion, etc) that are periodic in nature or simply happen very often during normal execution.

The amount of messages will increase drastically when the verbose level is enabled, so it's recommended to set it only if really needed.

This trace level can be enabled at runtime only in 'debug' builds.