定时器1使用激励中断无法设法让中断触发

如果你展示你的代码，你会更容易帮助。你设置了TMR1IE、PEIE和GIE吗？



      以下为原文

    It would be easier to help if you showed your code.
Have you set TMR1IE, PEIE and GIE ?
 
 

我已经使用MCC来为我生成配置代码。在我的主要功能中，我启用了中断：它涵盖了我相信的各个GIE和PEI比特。PIC18F26K40的文档表示，GIL和PEI位在ITCCON寄存器中是相同的位。在THETMR1X初始化方法中，下面的代码运行：这似乎覆盖了TMR1IE标志。简而言之，我认为我已经正确地启用了中断和TMR1，并且可以使用一个指针。正确的方向。目前我的项目只是一个为PIC18F26K40创建的香草MCC项目；如果你愿意，易于复制。



      以下为原文

    I have used the MCC to generate configuration code for me. In my main function I have enabled interrupts:
// Enable high priority global interrupts
INTERRUPT_GlobalInterruptHighEnable();
// Enable low priority global interrupts.
INTERRUPT_GlobalInterruptLowEnable();That covers the respective GIE and PEIE bits I believe. The documentation for the PIC18F26K40 says that the GIEL and PEIE bits are the same bit in the INTCON register.
In the TMR1_Initialize method the following code is run:
// Clearing IF flag before enabling the interrupt.
PIR4bits.TMR1IF = 0;
// Enabling TMR1 interrupt.
PIE4bits.TMR1IE = 1;This seems to cover the TMR1IE flag.
 
In short, I think that I have properly enabled interrupts and TMR1 and could use a pointer in the right direction. At the moment my project is just a vanilla MCC project created for the PIC18F26K40; easy to reproduce if you want to.

我用MPLAB X V3.45尝试TMR1中断，它工作。请尝试使用“INTCONbits.PEIE=1;”和“INTCONbits.GIE=1;”代替MCC来生成配置代码，以查看TMR1中断是否工作。如果更改有效，请在使用MCC生成配置代码时再次检查INTCON值。



      以下为原文

    I try the TMR1 interrupt with MPLAB X v3.45 and it works. Please try to use "INTCONbits.PEIE = 1;" and "INTCONbits.GIE = 1;" instead of the MCC to generate configuration code to see whether TMR1 interrupt works or not. If the change works, please double check what the INTCON value is when you use the MCC to generate configuration code.

看起来，不管我做什么，直接设置INTCON位，或者使用MCC生成的代码，我仍然没有得到触发的中断。我一定是做错了什么，还不能肯定。我在这里附上了截图：http://imgur.com/a/pyaI1



      以下为原文

    It seems like, no matter what I do, setting the INTCON bits directly or using the MCC generated code, I still get no triggered interrupt. I must be doing something wrong, not sure what yet.
 
I've attached a screenshot here: http://imgur.com/a/pyaI1