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 06:18:00 -0000 [thread overview] Message-ID: <bug-1001897-777-WreZySSITP@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 #5 from Uwe Kindler <uwe_kindler@web.de> --- > SYNOPSIS > > http://www.nxp.com/documents/application_note/AN10674.pdf | Fig. 14 > > May we presume that description from AN is not true for some LPC2294 > revisions? It seems so. I only have one single LPC2294 here and it definitely don't works like written on page 16 of the application note. The RM bit is not set, so controller dont't go into reset mode and also the TX RX counters are not changed. I would not have put so much time into this patch if the CAN controller would have worked the way it should. > Perhaps, http://www.nxp.com/documents/errata_sheet/2294.pdf > See CAN.5 (pp. 11,12) "Normal operation cannot be resumed after reset". > May we presume that they did not raise "Reset Mode" for "Bus Off" error > as an early "workaround"? Though, I found no such reassurances on Net. I think CAN.5 has nothing to do with the problem I see - this is something different. > > On the other hand the driver uses lpc2xxx_enter_reset_mode() in a few > places without (?) issue. Manually entering reset mode via lpc2xxx_enter_reset_mode() is not a problem. The problem is, that the controller does not automatically enters reset mode in case of a bus off condition (bus error). lpc2xxx_enter_reset_mode() works fine and controller properly enters reset mode. > Uwe, did you noticed any strange behaviors > after this call? If you did not, then my guess is wrong. And if CAN.5 > issue can be the reason then we can use your workaround by a condition > is set according some CDL option. Sorry, I cannot help in testing any > more due lack a CAN adapter. Ok. Shall I change the patch and make the code conditional via a CDL option? That would be o.k. for me as long as no one confirmed that this problem exists for other LPCxxxx devices? -- You are receiving this mail because: You are the assignee for the bug.
next prev parent reply other threads:[~2013-09-03 6:18 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 [this message] 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 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-WreZySSITP@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).