-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LPC15xx extended CAN fix (5.15) #14597
LPC15xx extended CAN fix (5.15) #14597
Conversation
@jetremblay, thank you for your changes. |
This pull request has automatically been marked as stale because it has had no recent activity. @ARMmbed/mbed-os-maintainers, please start CI to get the PR merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved.
CI started |
Test run: FAILEDSummary: 1 of 10 test jobs failed Failed test jobs:
|
CI restarted |
Test run: FAILEDSummary: 1 of 10 test jobs failed Failed test jobs:
|
Test run: FAILEDSummary: 1 of 10 test jobs failed Failed test jobs:
|
This pull request has automatically been marked as stale because it has had no recent activity. @jetremblay, please carry out any necessary work to get the changes merged. Thank you for your contributions. |
The failed test is related to another platform (K64F). I am not sure what to do for this? |
Correct, it should be restarted. CI restarted |
Test run: FAILEDSummary: 1 of 10 test jobs failed Failed test jobs:
|
CI restarted |
I run the job on incorrect CI instance, I'll need to restart |
Ci started |
Test run: SUCCESSSummary: 10 of 10 test jobs passed |
Summary of changes
This PR fixes an issue with parsing the identifier of received extended CAN frames on the LPC15xx targets. According to the user manual,
CANIF2_ARB2
contains the high bits whileCANIF2_ARB1
contains the low bits of the extended CAN identifier.Impact of changes
Migration actions required
Documentation
None
Pull request type
Test results
Reviewers