From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001897] lpc2xxx CAN driver improvements / enhancements
Date: Tue, 03 Sep 2013 12:31:00 -0000 [thread overview]
Message-ID: <bug-1001897-104-3GZOnsYhn7@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001897-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001897
--- Comment #12 from Bernard Fouché <bernard.fouche@kuantic.com> ---
FYI I obtained documents from NXP stating that the LPC1765 CAN cell is exactly
the same one than on the LPC2xxx, that conformance tests have been done by NXP
on the LPC2xxx and so that these tests apply to the LPC1765. NXP wrote that I'm
not allowed to give away these documents, but I got them simply by asking NXP
on their website, so I suppose anyone can get them too.
AFAIK the LPC1765 never had any CAN related errata reported. However I reported
an error in the documentation to NXP in January 2012 (CAN controller numbering
is wrong), they acknowledged the error but they never released an updated
version of UM10360.pdf. So maybe there are other reported problems that don't
make it to an errata document.
The NXP test document I have is dated September 2006 and includes bus off
testing.
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...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-09-03 12:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 9:37 [Bug 1001897] New: " bugzilla-daemon
2013-08-30 12:37 ` [Bug 1001897] " bugzilla-daemon
2013-08-30 12:38 ` bugzilla-daemon
2013-08-30 14:27 ` bugzilla-daemon
2013-09-02 7:22 ` bugzilla-daemon
2013-09-02 16:22 ` bugzilla-daemon
2013-09-03 6:18 ` bugzilla-daemon
2013-09-03 6:38 ` bugzilla-daemon
2013-09-03 8:20 ` bugzilla-daemon
2013-09-03 8:22 ` bugzilla-daemon
2013-09-03 9:06 ` bugzilla-daemon
2013-09-03 10:48 ` bugzilla-daemon
2013-09-03 12:20 ` bugzilla-daemon
2013-09-03 12:22 ` bugzilla-daemon
2013-09-03 12:31 ` bugzilla-daemon [this message]
2013-09-03 12:37 ` bugzilla-daemon
2013-09-03 12:53 ` bugzilla-daemon
2013-09-03 18:52 ` bugzilla-daemon
2013-09-06 8:19 ` bugzilla-daemon
2013-09-06 14:20 ` bugzilla-daemon
2013-09-11 21:23 ` bugzilla-daemon
2013-09-17 6:10 ` bugzilla-daemon
2013-09-17 6:35 ` bugzilla-daemon
2013-09-17 18:39 ` bugzilla-daemon
2013-09-17 18:42 ` bugzilla-daemon
2013-09-18 5:45 ` bugzilla-daemon
2013-09-18 6:46 ` bugzilla-daemon
2013-09-18 16:08 ` bugzilla-daemon
2013-11-05 15:41 ` bugzilla-daemon
2013-11-06 9:30 ` bugzilla-daemon
2013-11-06 15:28 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1001897-104-3GZOnsYhn7@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).