Technical discussions about Freescale (Motorola) DSPs (including the DSP56000, DSP56300, DSP56600, 56800 DSPs).
Hi, I'm writing assembly code for the DSP56371 but find that execution of my do loops loop counts are intermittently corrupted. I'm running the do loop code in the background, have several isr s running in the foreground and my stack has been extended into RAM. I've debug code to break when the loop count is out of range and when that happens, I see that the it has assumed a value equal to or at least close to the magnitude of the loop address value. I've been through all the loop restrictions and DSP56371 errata sheet several times now and believe I've removed all violations but still my execution sticks in different hardware loops. Has anyone seen a similar problem before? How did you sort it out?
Hi, I've written several assembly codes for this processor and I've never had that problem. I wouldn't put the blame on the processor. Advice: comment all the routines and then uncomment every routine one by one. May be you're overwriting some register. Why do you send us a little code with the problem? Regards, Pablo Hi, I'm writing assembly code for the DSP56371 but find that execution of my do loops loop counts are intermittently corrupted. I'm running the do loop code in the background, have several isr s running in the foreground and my stack has been extended into RAM. I've debug code to break when the loop count is out of range and when that happens, I see that the >it has assumed a value equal to or at least close to the magnitude of the loop address value. I've been through all the loop restrictions and DSP56371 errata sheet several times now and believe I've removed all violations but still my execution sticks in different hardware loops. Has anyone seen a similar problem before? How did you sort it out?