Posted on April 18, 2012 at 13:49 When this sort of thing happens,
Check that the interrupt is being set-up properly.
To set up an interrupt, you need to enable the interrupt with its priority & pre-emption.
Such as:
//***************************** START ***************************
//SPI2 Interrupt setup
NVIC_InitStructure.NVIC_IRQChannel = SPI2_IRQn;
NVIC_InitStructure.NVIC_IRQChannelPreemptionPriority = SPI2_IRQ_PREEMPTION;
NVIC_InitStructure.NVIC_IRQChannelSubPriority = SPI2_IRQ_SUBPRIORITY;
NVIC_InitStructure.NVIC_IRQChannelCmd = ENABLE;
NVIC_Init(&NVIC_InitStructure);
//***************************** END ***************************
When running your code, use your development tools to inspect the NVIC peripheral registers.
You're looking to see if the interrupt bits are set & enabled properly. If they're not, you won't trigger the interrupt.
Refer to the 'RM0008 STM32 Reference (Section 10.1.2 Interrupt & Exception Vector table)' & 'ARM Cortex M3 (NVIC Programmers Model)' manuals for details on these.
If you use the ST library, that should take care of it for you. Refer to ST Library examples for more code.
Hope this helps.
Stuart
