Posted by tang on 2017-07-17 17:22

Hi,

Can you verify the project optimization and debugging settings ?

Go to the project properties > C/C++ Build > Settings > Tool Settings

In Optimization : set the optimization level to “None (-O0)”
In Debugging : set the debug level to “Maximum (-g3)”

Hope it is where the problem comes from.
Kevin.

Posted by judoka_acl on 2017-07-18 09:01

Hi Kevin,

thank you for your answer. I’ve just checked and they are exactly the same. So this is not the problem. Any other suggestions?

Posted by judoka_acl on 2017-07-18 09:14

Hi,

I think it’s working now. It doesn’t jump to the interrupt handler, but at least it doesn’t jump to the wrong line either. So it’s looking good. I just need to find out why the interrupt is not working, though it’s working for Keil uVision, but that’s another topic. The problem was that in the optimization the tags Place the function in their own section and place the data in their own section was checked. Unchecking seems to fixed. Thanks for the support.

Posted by Andrei from The Great White North on 2017-07-18 18:01

Something is wrong with the previous answers.

The optimization option (-O) has a number (0-3). As the number increases, the optimization that the compiler does increases.

When debugging, you want to turn the optimization off (-O0).

When you release your code you want to test and release with higher levels of optimization (-O3).

If your toolchain is set with debug set to 3 and release set to 0, that’s just wrong.

Andrei