-
Notifications
You must be signed in to change notification settings - Fork 806
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
H7: fix GMLAN bitbang timer #1542
Conversation
48156ff
to
9d9c1d4
Compare
@@ -119,6 +119,14 @@ def test_gmlan_bad_toggle(p): | |||
assert comp_kbps_normal > (0.6 * SPEED_NORMAL) | |||
assert comp_kbps_normal < (1.0 * SPEED_NORMAL) | |||
|
|||
@pytest.mark.panda_expect_can_error | |||
@pytest.mark.skip_panda_types(PandaGroup.GMLAN) | |||
def test_gmlan_bitbang(p): |
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.
does this test catch the bug? it was pretty subtle
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.
bug was caused by wrong timer settings, so yes, was caught on RP everytime
for _ in range(10): | ||
p.can_send(0x10, b"data", 3) | ||
time.sleep(0.1) | ||
assert p.health()['gmlan_send_errs'] == 0 |
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.
also check the messages were sent on the loopback bus? do they get added there?
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.
don't think we ever forwarded those back, only rejected messages by safety mode.
Can we finish this? |
be923c8
to
7d49141
Compare
This reverts commit 5778c0a.
This reverts commit 5778c0a.
This reverts commit 5778c0a.
No description provided.