public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001683] New: Cortex-M3: Startup Code does not initialize last of available interrupts vectors Date: Wed, 10 Oct 2012 09:37:00 -0000 [thread overview] Message-ID: <bug-1001683-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001683 Summary: Cortex-M3: Startup Code does not initialize last of available interrupts vectors Product: eCos Version: CVS Platform: Other (please specify) OS/Version: Cortex-M Status: UNCONFIRMED Severity: normal Priority: low Component: HAL AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: martin.hopfeld@sse-erfurt.de CC: ecos-bugs@ecos.sourceware.org Class: Advice Request Created an attachment (id=1954) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1954) Fix Cortex-M interrupt vector initialization Using an STM32F103 I ran into a HardFault exception when using DMA2_CH5 with interrupts enabled. It seems no interrupt handler is registered by the startup code for this particular interrupt source. The DMA2_CH5 interrupt is the last entry in the interrupt list according to STM32F103 reference manual. Please see attached patch to the startup code on Cortex-M architecture to use the correct constant (CYGNUM_HAL_VSR_COUNT) when iterating over all interrupts and installing hal_default_interrupt_vsr(). This patch works for me and allows DMA2_CH5 to signal transfer complete by interrupt. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-10-10 9:37 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-10 9:37 bugzilla-daemon [this message] 2012-10-10 9:37 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-1001683-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-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).