• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 83 subscribers
  • Views 619 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.

TMS320F28379D: Break at address "0x3ff16a" with no debug information available, or outside of program code ın CPU2

aleyna yılmaz
Prodigy 205 points

Part Number: TMS320F28379D

Break at address "0x3ff16a" with no debug information available, or outside of program code.

I am running the led blink example in tms320f28379d, while the leds are blinking in cpu1, I get the error Break at address "0x3ff16a" with no debug information available, or outside of program code in cpu2 what is the reason for this? I make a selection on the cpu1 cpu2 screen before debugging the code, do I need to make another setting?

I select cpu1 from this screen and then the led blink example works, in the same way when I select cpu2 from this screen I get the following warning, although I run it, it does not work, how can I run this led blink example in cpu2

  • 0
    TI__Mastermind 30185 points

    Hello Aleyna,

    This message is usually provided when the code being executed is not directly accessible in CCS via a file such as those in driverlib. The code usually has not crashed when you see this message, but if you want to check this you can open the Disassembly window to view the assembly code which is executing. If an ITRAP or ESTOP has been reached, likely there has been a crash of some kind.

    Best regards,

    Omer Amir

  • 0 in reply to Omer Amir
    Prodigy 205 points

    hi omer

    why do i see this screen on cpu2 when the same code works on cpu1? do i need to make another setting to select cpu2?

    thanks

  • 0 in reply to Omer Amir
    Prodigy 205 points

    I see this on the dissambly window, if there was a problem as you say, shouldn't I have the same problem on cpu1? Could there be another reason why I work on cpu1 and get this screen on cpu2? Do I need to make other configurations when selecting cpu2, I only selected it on the first  screen.

  • 0 in reply to aleyna yılmaz
    TI__Mastermind 30185 points

    Hello Aleyna,

    I have seen this before, but I'm not familiar if there's a specific way to configure CCS to do this. As far as I know, this also happens when certain files/libraries are used which CCS can't link to properly. I will see if there is another expert who knows about this and if there is a solution.

    Best regards,

    Omer Amir

  • +1 in reply to aleyna yılmaz
    TI__Guru**** 481491 points

    This message:

    "Break at address "0x3ff16a" with no debug information available, or outside of program code ın CPU2"

    Means that there is no source code correlation with address 0x3ff16a in the debug symbols loaded for CPU2. 

    Do you have any debug symbols loaded for CPU2? Note that debug symbols are on a per CPU basis. If you have symbols loaded for CPU1, CPU2 does not have access to those symbols. 

    Thanks

    ki