This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1001683] New: Cortex-M3: Startup Code does not initialize lastof available interrupts vectors
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: unassigned at bugs dot ecos dot sourceware dot org
- Date: Wed, 10 Oct 2012 10:37:40 +0100
- Subject: [Bug 1001683] New: Cortex-M3: Startup Code does not initialize lastof available interrupts vectors
- Auto-submitted: auto-generated
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 the assignee for the bug.