Skip to main content
sheng yang
Senior
March 23, 2018
Solved

Why no systick interrupt happen??

  • March 23, 2018
  • 4 replies
  • 2135 views
Posted on March 23, 2018 at 13:11

I ported u-boot 2018.03 to my own board based on stm32f767igt,i set some register with systick timer as below:

0690X0000060ABiQAM.png

as the above picture, the systick timer count is changed,but i couldn't get in systick handler?besides register on 0xe000e010,is there some other registers will influence systick timers performance??I get confused ...

    This topic has been closed for replies.
    Best answer by Tesla DeLorean
    Posted on March 23, 2018 at 13:59

    Vector Table Address

    Entry in Vector Table

    Other interrupts with higher priority blocking

    System Handler settings in SCB

    Interrupts Disabled

    4 replies

    Tesla DeLorean
    Tesla DeLoreanBest answer
    Guru
    March 23, 2018
    Posted on March 23, 2018 at 13:59

    Vector Table Address

    Entry in Vector Table

    Other interrupts with higher priority blocking

    System Handler settings in SCB

    Interrupts Disabled

    Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
    sheng yang
    Senior
    March 23, 2018
    Posted on March 23, 2018 at 14:56

    I solved this problem,as your advice .I check my scb relate register status :

    0690X0000060AB0QAM.png

    i find systick is always pending , then i thought my systick handler function waste too long time ,so i remove much codes in the handler.then i found it's still pending,after i check shcrs register, i notice i set bit 11 before.after i remove thie code,the handler is ok.no pending as below

    0690X0000060ADxQAM.png
    henry.dick
    Associate II
    March 28, 2018
    Posted on March 28, 2018 at 12:22

    '

    after i remove thie code...'

    lesson learned here: it is stupid not to post the code when looking for help in debugging the said code.