Assertion failure after restarting application in debug mode

Matan Aloni

Other Parts Discussed in Thread: SYSBIOS

Hello,

Our application is running fine, without any assertion failures. After stoping in a break point and restarting the application, assertion failure occurs with the following error:

Internal exception: IERR=0x1

Instruction fetch exception

ti.sysbios.family.c64p.Exception: line 255: E_exceptionMin: pc = 0x00000000, sp = 0x11816a18.

To see more exception detail, use ROV or set 'ti.sysbios.family.c64p.Exception.enablePrint = true;'

xdc.runtime.Error.raise: terminating execution

The failure occurs before the application starts, immediately after restarting the application.

We are not using any malloc/printf in our project at all (and specifically not in any HWI/SWI).

Can you please advise on the issue? We have no idea how to debug this, and it becomes very hard to debug the application (after the assertion failure the only option is to reload the application and then start it again - this create long cycles of debug).

Thanks in advance,

Matan

over 11 years ago

0 Sivaraj Kuppuraj over 11 years ago

TI__Mastermind 35645 points

Hi Matan,

Thanks for your post.

Can you use ROV to check your application's Task stack values and the system ISR stack value? I suspect one of them has overflowed and needs to be increased in size.

Please refer the below E2E threads which is of more simillar issue as your above post:

http://e2e.ti.com/support/embedded/bios/f/355/p/185394/668158.aspx

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/106475.aspx

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/149427.aspx

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/97831/347019.aspx

Also, please refer the below wiki for DSP BIOS debugging:

http://processors.wiki.ti.com/index.php?title=DSP_BIOS_Debugging_Tips

Thanks & regards,

Sivaraj K

-------------------------------------------------------------------------------------------------------

Please click the Verify Answer button on this post if it answers your question.
--------------------------------------------------------------------------------------------------------

0 Matan Aloni over 11 years ago in reply to Sivaraj Kuppuraj

Prodigy 175 points

Hi Sivaraj,

I'm using SYS/BIOS, not DSP/BIOS.

Do you want me to get the values after the assertion failure happens?

Here's what I came up with, I hope this is the information you are referring to:

Task: Address: 0x1181c938 ; label: ti.sysbios.knl.Task.IdleTask ; priority: 0 ; mode: Running ; fxn: ti_sysbios_knl_Idle_loop ; arg0: 0x00000000 ; arg1: 0x00000000 ; stackSize: 2048 ; stackBase: 0x11817230 ; curCoreId: n/a ; affinity: n/a

I'm not sure where I find the information about "system ISR stack value" you were referring to. Can you give more detailed description of where to find it?

Thanks in advance,

Matan

0 Chris Jagielski over 11 years ago in reply to Matan Aloni

Expert 1630 points

Matan, did you ever get this understanding fixed?

I am having similar issues, and am curious regarding the advice given to you.

Processors

Processors forum

Assertion failure after restarting application in debug mode