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

I am working on DSP56807, with SDK2.5 with uCOS-II RTOS. till now I was working with CW5.1 and everything was great. However I recently switched to CW6.1 and since then I can not see the Stack window properly, instead of showing me the order of the function calls, it shows me garbage, either interrupts call (like "configInterruptVector" function) or some unknown addresses 0x000ff78 or different addresses, or is just show me functions that I have no clue how they appear there since it isn't part of the normal function calls, and the function I am debugging definitely didn't reach them before starting to run. I also can not use the button "Step Out" since it doesn't know which function called the current function and to what function to return to. How can I solve this bug? without it, it is almost impossible to debug code in CW6.1 Thanks Tomer

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