can/isotp: fix closing connection and improve flow control handling #12051
+41
−25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
This PR fixes closing an ISO TP connection if the user-supplied timeout is shorter than
CAN_ISOTP_TIMEOUT_N_Ar
. In short, xtimers were not removed properly when closing.This also add the ability to customize the flow control frame from the upper layers. We discovered some weird behavior with some vehicles that do not implement the protocol properly, so tweaking the flow control for a given connection can be useful.
Testing procedure
The bug was reproduced with the given configuration:
CAN_ISOTP_TIMEOUT_N_Ar
s (1s)