Open
Conversation
Set CanardCANFrame::iface_id to zero, as it is currently not set in STM32 driver, but compared in canardHandleRxFrame().
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Set CanardCANFrame::iface_id to zero, as it is currently not set in STM32 driver, but compared in canardHandleRxFrame().
Found this issue when implementing the receive loop as in the example "battery_node.c", which declares the
rx_frameon the stack without zeroing it. Depending on the stack content, the code works (ififace_idhappens to be the same on each call), or frames are lost/dropped sometimes.