This MR adds the following; currently DRAFT for experiments:
standardize logging tags:
io={TYPE}; TYPE is either read or write
proto={PROTO}; PROTO is one of the supported protocols in gallia, e.g. uds or doip.
encoding={ENCODING}; optional; ENCODING could be hex or base64
add a dissector API
a dissector could be used in the hr commands to interpret the tagged messages
The motivation of this is, we have currently a "works somehow" dissector in cursed_hr for UDS. This dissector uses a best effort heuristic to detect UDS messages. However, this is not useful for messages of other types.
gallia recently gained FlexRay support and a standardized dissection API in our hr commands would help everybody. For instance, for FlexRay there is already an own tool to help debugging.
So, this MR is an attempt to standardize dissection in our toolchain by adding metadata to our logfiles and an extendable API for hr.
Open Questions:
API for dissector: How should protocol metadata be handled? e.g. FlexRay Slot ID or CAN IDs?
This MR adds the following; currently DRAFT for experiments:
io={TYPE};TYPEis eitherreadorwriteproto={PROTO};PROTOis one of the supported protocols in gallia, e.g.udsordoip.encoding={ENCODING}; optional;ENCODINGcould behexorbase64hrcommands to interpret the tagged messagesThe motivation of this is, we have currently a "works somehow" dissector in
cursed_hrfor UDS. This dissector uses a best effort heuristic to detect UDS messages. However, this is not useful for messages of other types.gallia recently gained FlexRay support and a standardized dissection API in our
hrcommands would help everybody. For instance, for FlexRay there is already an own tool to help debugging.So, this MR is an attempt to standardize dissection in our toolchain by adding metadata to our logfiles and an extendable API for
hr.Open Questions: