中断不能设置全局变量？

我很确定还有另外一个代码，除了你在这里发布的代码......
 
无论如何，我建议你在test == 0时放一个数据断点。当断点触发时，您将能够看到哪个代码重置此变量。
 
祝你好运！
E.L。



以下为原文





I'm quite sure there is yet another code except the code you've published here...

Anyway, I would suggest you to put a data breakpoint when test==0. When the breakpoint triggers, you would be able to see which code resets this variable.

Good luck!
E.L.

是的，我正在使用STM8系列的标准库。
 
 
我正在使用SVDT - 我如何设置这样的数据中断？

编译器输出的代码包含问题的答案。
 
 
 您的代码包含ISR和主代码之间的访问冲突。
 
 当您指定测试是易失性时，编译器假定其值可能在两次连续读取之间发生变化，但它不会使分配成为原子，即ISR可能会中断它。
 
 只有汇编指令是原子的（有一些例外，例如DIVW指令可能被中断，但它们只影响核心寄存器），而赋值通常包含两个汇编指令：一个读取指令（例如LD A，test）和写一个（例如LD测试，A）。
 
 编译器有时输出MOV测试，测试是原子指令。
 
 这意味着您应该注意汇编代码以了解发生的情况并对代码进行正确的更正。
 
 如果在分配之前禁用中断并在之后启用它们，则访问冲突将消失，但此修复程序会将两个字节添加到可执行文件大小。
 
 BR
 
 EtaPhi



以下为原文





The code which your compiler outputs contains the answer to your question.


Your code contains an access conflict between the ISR and the main code.

When you specify that test is volatile, the compiler assumes that its value may change between two consecutive reads, but it doesn't make the assignment atomic, i.e. the ISR may interrupt it.

Only assembler instructions are atomic (there ase some exceptions, for instance a DIVW instruction may be interrupted, but they affect only core registers), while an assignment consists usually in two assembly instructions: a read one (eg. LD A,test) and a write one (eg. LD test,A).

The compiler sometimes outputs a MOV test,test which is an atomic instruction.

This means that you should watch at the assembler code to know what happens and to take the right correction to your code.

If you disable interrupts before the assignment and enable them afterwards, the access conflict disappears, but this fix adds two bytes to the executable size.

BR

EtaPhi

当变量设置为0时（我永远不会发生），我试图设置一个数据中断，并在装配线处断开：



以下为原文





I tried to set a data break when the variable was set = 0 (Which never should happen) and it breaks at a assembly line saying:

当初始化所有全局变量（即设置为零）时，断点在初始化阶段停止了代码。
 
 这意味着你的main（）仍然会被执行，所以这个汇编程序转储是没用的......



以下为原文





The breakpoint stopped your code in the initialization phase when all global variables are initialized, i.e. set to zero.

This means that your main() is still going to be executed, so this assembler dump is useless...

你可以试试这个。
 
main.c在主模块之前声明变量。
char test = 0x00; （不要只使用test = 0，这是非常重要的）
 
在interupt文件模块中，
外部测试;
 
祝你好运



以下为原文





you may try this.

main.c declare the variable before main module.
char test = 0x00; (don't use just test = 0, it is very impotant)

at interupt file module,  
extern test;

good luck