Could you post your interrupt code (C) and the resulting assembler?
It's hard to debug problems without seeing those...
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
On 03/22/2017 10:43 AM, Bob von Knobloch wrote:
> On 22/03/17 16:24, David W. Schultz wrote:
>> Calling another function from the ISR was what triggers this bad
>> behaviour. Especially if the called function is in another file.
> Hi David,
> my code doesn't call a function in the interrupt, it mer
On 22/03/17 16:24, David W. Schultz wrote:
> Calling another function from the ISR was what triggers this bad
> behaviour. Especially if the called function is in another file.
Hi David,
my code doesn't call a function in the interrupt, it merely decrements a
count, tests it for zero and, if not,
On 03/22/2017 09:54 AM, Bob von Knobloch wrote:
> Inspecting the assembly, I found that the interrupt was suspect.
> The 'old' code pushed the registers that it needed, the 'new' TI
> compiler pushes (and, of course, later pulls) all of the registers from
> r4 - r15 inclusive.
I complained about
Further work:
having got the compilation under a size which fitted into the flash, I
found that the code did not run. (This is the same source code that
worked fine when compiled with the 'old' mspgcc compiler.)
Inspecting the assembly, I found that the interrupt was suspect.
The 'old' code pushe
