System Abort - after begin dynamic SWI

YTE

Intellectual 800 points

Hi,

We are working on a system with C6415.

System suffers from "random" system abort due to instruction fetch exception.

Using are able to stop the system in the system abort function, and try to get some useful data.

Stack is empty.

Execution graph and execution graph details seem to hold some usefull information.

see attached, on the left side is a propper functioning, and on the right side is the problematic scenario.

It seems instead of:

SWI: begin KNL_Swi (TSK scheduler)

system gets:

SWI: begin dynamic SWI (0xfffffff5)

than gets an exception as this address is probably not valid.

We want to understand why begin dymaic occurs? and were is this address coming from.

we don't use any dynamic interrupts in our application.

also, any tips for further debugging would be highly appreciated

Thanks,

yuval.

over 10 years ago

0 Arvind Singh over 10 years ago

Mastermind 6115 points

Hi Yuval,

Let me check onto this Will get back to you.
Thanks for your patience.

0 Arvind Singh over 10 years ago in reply to Arvind Singh

Mastermind 6115 points

Hi Yuval,

Which software package you are working with ?
Have you modified anything or developed your own code, and seeing this behavior.

0 YTE over 10 years ago in reply to Arvind Singh

Intellectual 800 points

Hi Arvind,

Regarding S/W develpment tools, we use code composer 3.3.81.6.
BIOS - 5.31.07.
CGT-6.1.19

The applicattion was developed by us, for many years, using DSP/BIOS and drivers from TI.
The question is what can cause such behaviour? and how can it be debugged.
How come Task Scheduler is trying to run a dynamic interrupt from (probabbly) a corrupted address.

Thanks,
yuval.

0 Sivaraj Kuppuraj over 10 years ago in reply to YTE

TI__Mastermind 35645 points

Hi,

Moving your post to right forum to be better answered.

Thanks & regards,
Sivaraj K

0 YTE over 10 years ago in reply to Sivaraj Kuppuraj

Intellectual 800 points

Thanks Sivaraj,

Can anyone assist by helping understand this error?:

SWI: begin dynamic SWI (0xfffffff5)

We are working on this bug for too long now, and we do not understand the output from the execution graph.
Thanks,
yuval.

0 Steven Connell over 10 years ago in reply to YTE

TI__Mastermind 45025 points

Hi Yuval,

At first glance, this looks like some kind of memory corruption problem (some code overwriting a piece of memory that it shouldn't be).

yuval tepper said:
The applicattion was developed by us, for many years, using DSP/BIOS and drivers from TI.

Can you provide some more details on what you mean here?

Do you mean that, this app was developed a long time ago, and has been running for many years, and now you are seeing this issue?

Or, have you been continuously making changes to the code over the years, and this problem was recently introduced?

Steve

Processors

Processors forum

System Abort - after begin dynamic SWI