STM CircleOS forum / Timing analysis bug??

ntrf.zns · 2010-05-01 15:55:56

void SysTickHandler( void ) __attribute__ ((interrupt ("IRQ")));

void SysTickHandler( void )
{
s32 i;
#ifdef TIMING_ANALYSIS // to debug with a scope
// Systic flag.
GPIO_WriteBit( GPIOA, GPIO_Pin_6, Bit_RESET );
#endif

#ifdef PRIMER2
GPIO_WriteBit( GPIOA, GPIO_Pin_3, Bit_RESET ); //
#endif
....

I think second GPIO write must be inside TIMING_ANALYSIS block.

yrt · 2010-05-03 10:04:42

Of course the right code should be :

void SysTickHandler( void )
{
s32 i;
#ifdef TIMING_ANALYSIS // to debug with a scope
// Systic flag.
#ifdef PRIMER1
GPIO_WriteBit( GPIOA, GPIO_Pin_6, Bit_RESET );
#else
GPIO_WriteBit( GPIOA, GPIO_Pin_3, Bit_RESET ); //
#endif
#endif
....

# 1 2010-05-01 15:55:56 Timing analysis bug?? (project: Circle OS 4.62)

Timing analysis bug?? (project: Circle OS 4.62)

# 2 2010-05-03 10:04:42 Timing analysis bug?? (project: Circle OS 4.62)

Re: Timing analysis bug?? (project: Circle OS 4.62)

Board footer