• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 3048 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.

CCS/TMS320F28379D: Break at address "0x3fe44e" with no debug information available, or outside of program code.

user5901273
Prodigy 120 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

hi:

     when debugging my code on the 28379D,  I encounterd an issue. Once the code are downloaded into cpu1 and cpu2 respectively, cpu2 work automatically and the process

is abnormal. cpu1 can work wll. when i reset cou2 and restart, there is a tip that Break at address "0x3fe44e" with no debug information available, or outside of program code.

I don't know the real reason and confuse me. I hope you can help me  and give me a solution as soon as possibel.

    Thank you !

   Best Regards

  • 0
    TI__Guru**** 465891 points

    Hello,

    Please repost your screenshots.

    user5901273 said:
    there is a tip that Break at address "0x3fe44e" with no debug information available, or outside of program code.

    This is a common message from the debugger that is informing you that the CPU is halted at a program address where there is no source code correlation or debug information. 

    The rest of your questions are device or application specific. I will move this thread to the C2000 forum. The device experts there can help you further

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 465891 points
    Hello,
    My apologies, I never moved this to the device forum. I will do so now. Sorry for the delay.

    Ki
  • 0
    TI__Guru 53845 points

    Thanks for your patience. Were you able to make progress debugging this? That address is in boot ROM. You can actually load the ROM symbols (they're in C2000Ware under libraries->boot_rom) to see what code it is. It sounds like there's some issue with the sequence in which you're booting the CPUs. Here's a thread on the subject:

    e2e.ti.com/.../350359

    Whitney