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] New: lpc2xxx CAN driver improvements / enhancements Date: Thu, 29 Aug 2013 09:37:00 -0000 [thread overview] Message-ID: <bug-1001897-777@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001897 Bug ID: 1001897 Summary: lpc2xxx CAN driver improvements / enhancements Product: eCos Version: CVS Target: Other (please specify) Architecture/Host HostOS: Win XP/7 OS: Status: UNCONFIRMED Severity: enhancement Priority: low Component: Patches and contributions Assignee: unassigned@bugs.ecos.sourceware.org Reporter: uwe_kindler@web.de CC: ecos-patches@ecos.sourceware.org Created attachment 2349 --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2349&action=edit lpx2xxx CAN driver fix The following patch fixes some issues discovered while porting the CANopen Node project (http://sourceforge.net/projects/canopennode/) to the eCos CAN framework. The following problems have occurred, when the node has been disconnected / connected physically from the CAN bus while the CANopen stack was runnning: 1. Disconnecting the node physically from CAN bus causes a bus off condition for the CAN controller. This caused an endless invocation of the error ISR because of the remaining bus off error condition. The fast ISR invokation blocked the application from running. 2. When the node was reconnected physically to CAN bus again, it could not always properly recover from bus off condition. This also happened after a reset of the CANopen application. The attached patch fixes both issues for lpc2xxx CAN driver. -- You are receiving this mail because: You are the assignee for the bug.
next reply other threads:[~2013-08-29 9:37 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-29 9:37 bugzilla-daemon [this message] 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 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@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).