This is the mail archive of the
mailing list for the eCos project.
[Bug 1001897] lpc2xxx CAN driver improvements / enhancements
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: ecos-patches at ecos dot sourceware dot org
- Date: Tue, 03 Sep 2013 12:37:03 +0000
- Subject: [Bug 1001897] lpc2xxx CAN driver improvements / enhancements
- Authentication-results: sourceware.org; auth=none
- Auto-submitted: auto-generated
- References: <bug-1001897-104 at http dot bugs dot ecos dot sourceware dot org/>
Please do not reply to this email, use the link below.
--- Comment #13 from Uwe Kindler <firstname.lastname@example.org> ---
> I can't test on the LPC1765 before next week at the earliest and the driver
> I use is different because of the LPC1765 "pending interrupt problem", but
> what you describe should appear here also if we have the same CAN cell.
> Can you describe what you do on the CAN bus to reach bus off? I could try to
> reproduce here and see if I also see RM staying at zero.
> Did you check the value of EWL? If is 0 or 255 I wonder what happens...
Create a thread that prints a debug message in a loop via diag_printf (i.e. one
message per second). Create a second thread that simply sends CAN messages
(i.e. one message per second). When this application is running, simply unplug
the CAN bus cable from the CAN connector.
If your debug message from the thread stops, then you know you are spinning in
the CAN ISR. You can activate the debug output in the driver to see register
contents and ISR reason (ICR_BUS_OFF) - it will be printed again and again ...
You are receiving this mail because:
You are on the CC list for the bug.