• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 225 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.

TMS320F280039C: CLA Task1 cannot debug in one step and the starting address does not match

Jiahui Gao
Expert 7150 points
Part Number: TMS320F280039C

Tool/software:

Hi team，

The CLA interrupt cannot step through debugging, and its starting address is 0x00, which is not the 0x9000 I defined in the cmd file

At the same time, there will also be the following error messages

CLA1_0: Can't Run Target CPU: (Error -2134 @ 0x0) Unable to control device execution state. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)

But by adding IO judgment in the TASK1 interrupt, it was found that cla TASK1 was running normally.

Could you please clarify my confusion?

Thank you.

Best regards，

Jiahui

  • 0
    TI__Mastermind 19155 points

    Hi Jiahui,

    Can you verify that you are following the below steps when debugging with the CLA:

    1. Launch target configuration
      1. both cores should be disconnected
    2. "Connect Target" for the c28x
      1. c28x will be suspended  
      2. It may throw an error about not having the debug information at this point, that can be ignored
    3. Load the .out file onto the c28x (Run >> Load >> Load Program >> [navigate to the .out file])
      1. c28x will be suspended still
    4. "Connect Target" for the CLA
      1. both cores will be suspended
    5. Load the .out symbols onto the CLA (Run >> Load >> Load symbols >> [navigate to the .out file])
    6. Switch context to the c28x (click on it in the debug window) and Resume
    7. Switch context back to the CLA and you should see it stop at the __mdebugstop();

    Best Regards,

    Delaney