构建源代码时，中断处理程序未声明错误

的cy_isr关键词必须用来写你的interrupt_routines。您使用的是CysiISR1和CysISR2，这是不正确的。你有在两botht例程使用interrupt_handler中断。重命名它说interrupt_handler_1和interrupt_handler_2。
谢谢，
SRIM



     以下为原文
   The CY_ISR keyword must be used to write your interrupt_routines. You used CY_ISR_1 and CY_ISR_2 which is incorrect. You have used Interrupt_Handler in botht routines of the two interrupts. Rename it to say Interrupt_handler_1 and interrupt_handler_2.
    Thanks,
    srim

你好，
我用自由来纠正和重新安排你项目中的一些错误。CysISR是宏，它的参数是中断处理程序的名称，所以您切换它们都会给您带来错误。
还有2条警告，其中一条是我的，来自评论。
第二个是关于在时钟/启用时违反设置时间的警告。首先，这应该是致命的（有时是错误的）第二：目标不是时钟或使能，它是来自输入引脚的（同步）复位。我相应地改变了你的一个频道，这样你可以更好地比较它们。可能需要用FF延长/缩短复位信号以获得更好的结果。
鲍勃
定时器11Zip
437.3 K



     以下为原文
  Hi,
    I took the freedom to correct and re-arrange some errors / lines in your project. The CY_ISR is a macro and its parameter is the name of the interrupt-handler, so you switched them both giving you the errors.
    There are still 2 warnings, one of them is mine, coming from a comment.
    The second is a warning about violating setup-times on clock/enable. First: this should be considerd to be fatal (misfunction sometimes) Second: the target is not clock or enable, it is your (synchronus) reset coming from an input - pin. I changed one of your channels accordingly, so that you may compare them both better. It might turn out that you need to lengthen/shorten your reset-signal with a FF to get better results.
     
    Bob

•   Timer11.zip 437.3 K  
  
  

亲爱的各位，
谢谢你的回复。
嗨，Bob Marlowe先生，
我无法完全理解你的回复。
“第二个警告是关于在时钟/启用时违反设置时间的警告。第一：这beconsiderd是致命的（失效有时）二：目标没有时钟或使，这是你的（同步）复位输入引脚来。我改变了你的一个渠道，因此，这样你可以比较他们更好。也许会发现你需要延长/缩短与FF得到更好的结果你的复位信号。”
你的意思是复位输入引脚必须同步时钟吗？如果是，为什么重置必须与时钟同步？这是因为如果不同步，复位不能工作？
对不起，这个问题，我刚开始一个月前在PSoC开发，希望能把它用在我的申请。
当做



     以下为原文
  Dear all,
    Thanks for all the reply.
    Hi Mr Bob Marlowe,
    I cannot quite understand your reply below.
    "The second is a warning about violating setup-times on clock/enable. First: this should be considerd to be fatal (misfunction sometimes) Second: the target is not clock or enable, it is your (synchronus) reset coming from an input - pin. I changed one of your channels accordingly, so that you may compare them both better. It might turn out that you need to lengthen/shorten your reset-signal with a FF to get better results."
    Do you mean that the reset input pin must be synchronise to the clock? If yes, why must the reset be synchronise to the clock? Is it because if it is not synchronise, the reset will not be able to work?
    Sorry for the question, as I have just started on PSoC development about 1 month ago and is hoping to use it in my application.
    Regards