Hi,
Do we have any example code for the SYS.ABORTFXN and SYS.ERRORFXN functions? Customer is trying to use it but they are facing problem in doing that.
Regards,
Bhavin
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.
Hi,
Do we have any example code for the SYS.ABORTFXN and SYS.ERRORFXN functions? Customer is trying to use it but they are facing problem in doing that.
Regards,
Bhavin
Hi Bhavin,
Could you please provide some more details on the problem the customer is having?
Also, which version of BIOS are they using?
Thanks,
Steve
Hi Steve,
Customer Normal 0 false false false EN-US X-NONE X-NONE
implemented the functionality as mentioned below.
// XX.cfg
var SYS = xdc.useModule('ti.bios.SYS');
SYS.ABORTFXN = "Lte_SysAbort";//_Lte_SysAbort;//"_Lte_SysAbort";
// XX.main
#include "assert.h"
void main()
{
start_bios();
}
Task_fxn()
{
assert(0);
}
void Lte_SysAbort()
{
int i;
while(1)
{
i++;
}
}
// But after exwcution of assert functionality, PC is not going to Lte_SysAbort().
Please let us know what is missing?
Regards,
Bhavin
Hi,
I've created an example to demonstrate the usage of these features. I've verified that they are working. Please give the attached examples to the customer.
Thanks,
Steve
Thanks Steve,
I will send this to customer and let you know the result soon.
Regards,
Bhavin
Steve,
Customer tried with the same file what u have provided. It works fine.
But he is not able to view the stack contents when the system is in the myAbort function (* he has put the breakpoint in myAbort func.)
Please let us know how to view the stack contents when system is going to abort or any exception handle.
Regards,
Bhavin
Steve,
Please let me know if you have any update on this? Customer is waiting on your response.
Regards,
Bhavin
Bhavin,
This is a bug. I have filed the following for it:
SDOCM00079857 Stack view does not show who called SYS_abort for user defined SYS.ABORTFXN in BIOS 6
Steve
Steve,
Is there any workaround for this bug? Is there anyway by adding some piece of code or something which can workaround this bug and allow us to view the stack?
Regards,
Bhavin
Bhavin,
Yes, it seems that there's a possible work around. Can you have the customer try the following?
The customer needs to specify some compiler options for *all* C source files that they are building. This includes any generated files from the BIOS configuration:
add the following options when building _any_ source file that may be involved in the call chain (this includes the generated config .c file):
--symdebug:dwarf --optimize_with_debug
To add this option to the build of the generated config file you must add these options to the XDCtools "Build Properties" of your project:
Hello,
I would like to use the functionality invoked by SYS.ABORTFXN and SYS.ERRORFXN in DSP/BIOS 5 with an example usage with "xdc.runtime.System" in case of SYS/BIOS 6.
In short, SYS.ABORTFXN and SYS.ERRORFXN are present in DSP/BIOS 5 and "NOT" available in SYS/BIOS 6, so please suggest an example of such kind using "System" APIs in SYS/BIOS 6 application.
Thanks
Santosh