public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.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-777-mLSThuQvYh@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001897-777@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 the assignee for the bug. >From ecos-bugs-return-10555-listarch-ecos-bugs=sources.redhat.com@sourceware.org Tue Sep 03 12:37:16 2013 Return-Path: <ecos-bugs-return-10555-listarch-ecos-bugs=sources.redhat.com@sourceware.org> Delivered-To: listarch-ecos-bugs@sources.redhat.com Received: (qmail 24010 invoked by alias); 3 Sep 2013 12:37:16 -0000 Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <ecos-bugs.sourceware.org> List-Subscribe: <mailto:ecos-bugs-subscribe@sourceware.org> List-Post: <mailto:ecos-bugs@sourceware.org> List-Help: <mailto:ecos-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs> Sender: ecos-bugs-owner@sourceware.org Delivered-To: mailing list ecos-bugs@sourceware.org Received: (qmail 23988 invoked by uid 89); 3 Sep 2013 12:37:16 -0000 Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 03 Sep 2013 12:37:16 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,NO_RELAYS autolearn=ham version=3.3.2 X-HELO: mail.ecoscentric.com Received: by mail.ecoscentric.com (Postfix, from userid 48) id 0651A4680001; Tue, 3 Sep 2013 13:37:13 +0100 (BST) X-Original-To: unassigned@bugs.ecos.sourceware.org Delivered-To: unassigned@bugs.ecos.sourceware.org From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001897] lpc2xxx CAN driver improvements / enhancements Date: Tue, 03 Sep 2013 12:37:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: Patches and contributions X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: uwe_kindler@web.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: low X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: <bug-1001897-777-aIIyrK9Jpt@http.bugs.ecos.sourceware.org/> In-Reply-To: <bug-1001897-777@http.bugs.ecos.sourceware.org/> References: <bug-1001897-777@http.bugs.ecos.sourceware.org/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.ecos.sourceware.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013/txt/msg00586.txt.bz2 Content-length: 1209 Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id\x1001897 --- Comment #13 from Uwe Kindler <uwe_kindler@web.de> --- > 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 the assignee for the bug.
next prev parent reply other threads:[~2013-09-03 12:31 UTC|newest] Thread overview: 27+ 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:39 ` 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 12:22 ` bugzilla-daemon 2013-09-03 12:31 ` bugzilla-daemon [this message] 2013-09-03 12:53 ` bugzilla-daemon 2013-09-03 18:52 ` bugzilla-daemon 2013-09-06 8:20 ` 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 15:30 ` 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-777-mLSThuQvYh@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.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: linkBe 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).