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

Compiler/TMS320F28388D: System abort due to some reasons

user6114104
Intellectual 720 points

Part Number: TMS320F28388D

Tool/software: TI C/C++ Compiler

Hi all,

The CPU1 core running on SYS/BIOS goes to  _abort function due to uncertain reasons, the result is just like below:

Based on the debug information above, is there any useful instruction for us to pinpoint the problem?  I thought that the stack is not enough, so I change the stack size from 0x100 to 0x200, 0x300, and 0x400.

However, the _abort() information remains. I don't know what cause the problem, and is there any utilities in CCS environment to assist to resolve the problem?

Thanks a lot!

QL

  • 0
    TI__Guru 50611 points

    Hi,

    Looking the picture above, it is crashing in function Fapi_setActiveFlashBank(). You can set the breakpoint in the caller of the function and step-through the code. Check the function parameters.

  • 0 in reply to Santosh Jha
    TI__Guru 50611 points

    Are you able to resolve the abort issue?

  • 0 in reply to Santosh Jha
    Intellectual 720 points

    Hi Santosh,

    Exactly as you said, the function Fapi_SetActiveFlashBank() executed crash. When I did't call it, the program was running well.

    However, I still don't know what cause the crash, and the program alse runs to _abort position even if I set breakpoint at the flash API ahead and debug step by step. But now there is a good news that the program becomes normal when I add following instruction in the cmd file like this:

       GROUP
   {
	   .TI.ramfunc
	   { -l F2838x_C28x_FlashAPI.lib}

   }

    Please help me review it. Is it really OK now.

    Thanks a lot!

    QL

  • 0 in reply to user6114104
    TI__Guru* 87155 points

    Hi,

    On this device (where this is only one Flash bank per core), Flash API functions should be executed from RAM.  Hence when you grouped it with .TI.ramfunc and assign a Flash address for load and RAM address for RUN, crash did not happen.

    Thanks and regards,
    Vamsi