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

Ads

Discussion Groups

See Also

Embedded SystemsFPGAElectronics

Discussion Groups | Freescale DSPs | Metrowerks CodeWarrior Debugger Problem

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

  

Post a new Thread

Metrowerks CodeWarrior Debugger Problem - ljube20022000 - Jun 19 15:58:00 2002

Hi Everyone!
I have a problem with CodeWarrior Debugger. It seems that my program
stalls when I hit run from the menu. If I step over the code until
while (1) loop and then hit run it works fine. Also, sometimes i just
need to recompile(not making any changes)and then it starts working
fine.
I figured out when it stalls, that is trying to execute this
instruction at
P:0000F006: 324A .short 0x324a ; Invalid opcode
I haven't link anything in program RAM (between F000-F7FF).I am using
only internal flash and i am not using Embedded SDK. I started my
project with DSP56800 EABI Stationery.
Any help is appreciate!
Thanks
Ljubisa




______________________________
Start your Android Ice Cream Sandwich development on TI's AM35x Sitara ARM Cortex-A8 processor today.



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

RE: Metrowerks CodeWarrior Debugger Problem - Leonard N. Elevich - Jun 19 20:36:00 2002

I wouldn't blame CodeWarrior debugger for this behavior. It looks to me that
your code has a bug, and it crushes with unpredictable results. Normally, if
your code execution ends up in the memory area where you don't have any
code, this is due to corruption of the Program Counter. This can happen if
your software stack is corrupted, and on return from subroutine, PC didn't
get loaded properly. There are some other ways you can be jumping to wrong
code locations, for example if you have an interrupt but don't have ISR
associated with it.

What ever it is, debugger is not your problem.

Leonard N. Elevich
Motorola DSPD
-----Original Message-----
From: ljube20022000 [mailto:]
Sent: Wednesday, June 19, 2002 8:58 AM
To:
Subject: [motoroladsp] Metrowerks CodeWarrior Debugger Problem

Hi Everyone!
I have a problem with CodeWarrior Debugger. It seems that my program
stalls when I hit run from the menu. If I step over the code until
while (1) loop and then hit run it works fine. Also, sometimes i just
need to recompile(not making any changes)and then it starts working
fine.
I figured out when it stalls, that is trying to execute this
instruction at
P:0000F006: 324A .short 0x324a ; Invalid opcode
I haven't link anything in program RAM (between F000-F7FF).I am using
only internal flash and i am not using Embedded SDK. I started my
project with DSP56800 EABI Stationery.
Any help is appreciate!
Thanks
Ljubisa _____________________________________
/groups.php3


______________________________
Start your Android Ice Cream Sandwich development on TI's AM35x Sitara ARM Cortex-A8 processor today.



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