Part Number: TMS320F280039C Hello
we used ECC error Test available in the Ti library to generate ECC flash/RAM uncorrectable errors. After an uncorrectable flash/ram error occurs the NMI we setup interrupt fires as expected, inside the NMI routine we…
Part Number: TMS320F28P650DK Tool/software: Hi TI experts!
i am using DEVICE_DELAY_US in cpu2 in tms320f28p650dk i am getting into __interrupt void Interrupt_illegalOperationHandler(void) after the function call what should i do to use this function…
Yes i read that example but in that as well I was not ablt to generate the NMI even after adding the
Interrupt_register ( INT_NMI , nmiISR );
So instead trying that I went to try "Comparator Error Force Test" which if passed triggers an nmi right…
Part Number: TMS320F28P650DH Hi Experts,
My customer is seeing illegal operation issues. Their program would stuck in
void Interrupt_illegalOperationHandler(void) during the power test, we are trying to find out the which address is triggering the…
Part Number: TMS320F28P650DK Other Parts Discussed in Thread: SYSCONFIG , C2000WARE
Tool/software:
Hello TI Community,
I'm new to using the CLA on C2000 devices and recently started working with the CLA example cla_ex4_pwm_control. I successfully…
Hi Sira, I think I solved the problem by reshuffling my memory sectors definitions. I was probably trying to write 2 times the same 64 bits block per Flash erase cycle.
So I succeedded to flash the kernel and transmit the Image 1 using the kernel. However…
Part Number: TMS320F28386D When the program enter into the static void Interrupt_illegalOperationHandler(void).
Is there method to check the cause source?
static void Interrupt_illegalOperationHandler(void) { // // Something has gone wrong. The…
Part Number: TIDM-02010 Other Parts Discussed in Thread: SFRA , C2000WARE Tool/software: Hi Experts,
I am working on a proof of concept (PoC) using the C2000Ware_MotorControl_SDK_5_03_00_00 with the F2800137 microcontroller. Currently, I am attempting…
problem solved, the Interrupt_illegalOperationHandler was caused because of the ram sections that was initialized by the generateECCMemCorrError() had the it_ram_func , just changing the ram sections and everything works fine thanks
Johnny,
Interrupt.c has a function "Interrupt_initVectorTable" which initializes the PIEVECTTABLE . All the interrupt vectors are initialized to "Interrupt_defaultHandler" in this function.
The exception handlers like Interrupt_illegalOperationHandler…
