Skip to content

Conversation

legoabram
Copy link
Contributor

The code is designed to handle RF0L and RF1L in line 1, but they were being sent to line 0. Becuase they weren't handled, the interrupts would never be handled which locked up the chip.

Additionally, I'd like some additional guidance on how to backport this to v3.4.

The code is designed to handle RF0L and RF1L in
line 1, but they were being sent to line 0. Becuase
they weren't handled, the interrupts would never
be handled which locked up the chip.

Signed-off-by: Abram Early <abram.early@gmail.com>
@henrikbrixandersen
Copy link
Member

Additionally, I'd like some additional guidance on how to backport this to v3.4.

Hi @legoabram - thank you for this contribution. In order to have any bug fix backported (or even merged into main right now, as we are currently in feature freeze for v3.5.0) you will need to open an issue using our bug report template first.

@henrikbrixandersen
Copy link
Member

@legoabram Thanks. Now that the bug report is in place and linked, I have added the needed labels to this PR to have our bot automatically (attempt) backporting the fix.

@henrikbrixandersen henrikbrixandersen added this to the v3.5.0 milestone Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MCAN's RF0L and RF1L Interrupts not Handled
5 participants