#include <busfault_screen.h>

Data Fields
busfault_kind_t	kind
can_selftest_verdict_t	verdict
uint32_t	sent
uint32_t	echoed
uint32_t	corrupt
uint32_t	lost
uint32_t	tx_errors
uint32_t	rx_errors
uint32_t	bus_errors
bool	bus_off
busfault_bus_t	bus
uint32_t	down_s
uint32_t	recoveries
uint32_t	polls
uint32_t	timeouts
bool	have_remote
bool	remote_up
uint8_t	remote_tx_errors
uint8_t	remote_rx_errors
uint8_t	remote_flags
uint16_t	remote_overflows

Detailed Description

What the start-up test found, as the screen needs it.

Both ends, because the pair is what separates the faults: frames the far end answered and this end never heard are a return-path fault, and frames it never answered are an outbound one.

Field Documentation

◆ bus

busfault_bus_t busfault_report_t::bus

what this panel's controller is doing

◆ down_s

uint32_t busfault_report_t::down_s

seconds since the link last answered

◆ have_remote

bool busfault_report_t::have_remote

the IOmcu answered a status request

◆ polls

uint32_t busfault_report_t::polls

requests this panel has sent

◆ recoveries

uint32_t busfault_report_t::recoveries

times the bus has been asked back

◆ remote_up

bool busfault_report_t::remote_up

and said its own controller came up

◆ timeouts

uint32_t busfault_report_t::timeouts

and how many got no answer

◆ tx_errors

uint32_t busfault_report_t::tx_errors

the panel's controller

The documentation for this struct was generated from the following file:

shared/ui/include/busfault_screen.h

Data Fields