/var/www/restricted/ssh/stm32/www/stm32circle/ STM CircleOS forum / Timing analysis bug??

Username:     
Password:     
             

Forum

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

ntrf.zns
Member
From: Belgorod, Russia
Registered: 2009-11-01
Posts: 134

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

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.

Offline

 

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

yrt
Administrator
From: Grenoble-France
Registered: 2008-06-11
Posts: 520
Website

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

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
....

Offline

 

Board footer