Sign in

username:

password:



Not a member?

Search motoroladsp



Search tips

Subscribe to motoroladsp



motoroladsp by Keywords

56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

Discussion Groups

Discussion Groups | Freescale DSPs | do loop execution corruption

Technical discussions about Freescale (Motorola) DSPs (including the DSP56000, DSP56300, DSP56600, 56800 DSPs).

  

Post a new Thread

do loop execution corruption - drea...@aptx.com - Dec 11 9:04:44 2007



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?



(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

Re: do loop execution corruption - palm...@hotmail.com - Dec 14 14:08:03 2007

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?



(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )