• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 471 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

problem to execute a program on DSP TMS320C6474 in CCStudio v3.3

youir youir
Prodigy 90 points

Other Parts Discussed in Thread: TMS320C6474, CCSTUDIO

Hello,

I am working on a DSP TMS320C6474 , this morning I ran a program on this DSP under CCStudio v3.3 but I had this message:

Error: Illegal opcode (00001001) at pc = 0x00800000 Illegal opcode at pc = 0x00800000 

Please help me to solve this problem

thanks

  • 0
    TI__Guru* 84110 points

    Your PC (Program Counter) is set to 0x00800000 which is the beginning of the local-mapped L2 memory and there is the value 0x00001001 at that location. You can observe this in the Disassembly Window if you view that address. If you try to execute by running or single-stepping at this instruction, CCS will make this report message to tell you that invalid program code is being executed.

    You will need to determine one or both of

    1. Why is 0x00001001 at this location? Is this the expected value for your program or is this unexpected behavior?

    Immediately after loading your program, look at this location and determine if this value is there. If so, your program load caused it to be there; if not, then it gets written later by your program or other operation and you must determine that source.

    2. Why is the PC at this location? Is this the expected location for your program to be running?

    Immediately after loading your program, look in the Disassembly Window to see where your PC is set. Be sure to turn off the option to Go Main automatically. The entry point will usually have the label _c_int00.

    Depending on all of these answers, you will be closer to solving your problem.

  • 0
    Intellectual 265 points

    Today I met the same problem. When I execute a function, that memory location(and memory near it) is overwritten. When I set the heap and stack size bigger, everything runs well. I guess the stack is not enough for the program, so it crashes other memory location.