Dear Sir,
Sorry for very late reply ,
Actually I have facing FualtISR bug and I am not able to fixed this issue.
Please support me how to fixed this issue .
and after clear FaultISR bug then I will share reset resistors status .
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.
Dear Sir,
Sorry for very late reply ,
Actually I have facing FualtISR bug and I am not able to fixed this issue.
Please support me how to fixed this issue .
and after clear FaultISR bug then I will share reset resistors status .
Hi,
Are you getting a fault or getting reset? You have different posts describing different problem. Please be clear what you are getting? What does the RESC register show which I asked in my last reply?
If you are getting a reset then you need to check if it is due to the software reset you generate by your application. See your own code that you pasted last time. When you get a NMI, you create a software reset. You need to find out what triggers the NMI in your application.
You still have not answered me what does the RESC show?
If you are getting a fault then you need to find the root cause of the fault. Many times, the fault is due to insufficient stack of heap or if you are accessing a peripheral that is not yet enabled. If the code has been running for a while then it is likely due to memory issue. Trying increasing the heap and stack and see if makes a difference. If a fault is due to a peripheral access before it is enabled then you most likely will see the fault fairly quickly after the program starts running.
Use this app note to diagnose the faults.
Hi,
It shows that you have the s/w reset. This is generated by your own application, You need to find in your application where this s/w reset is asserted. I already asked before if the s/w reset is coming from the NMI handler. You didn't answer me.
If the s/w reset is coming from NMI handler then you need to find out in application where the NMI is coming from.
Dear Sir
Hope you are doing well ,
The S/w did not come from the NMI handler. Only the system is showing the ResetISR() trigger. I have observed this was triggered when TCP WebSocket was disconnected and the software tried to load data on WebSocket then the system generated ResetISR. I can not track the real-time connection status of WebSocket. I am using enet_weather example code for development .
Please help to how to track connection status in real time
You circle EMACTxDMADescriptorListSet() in your screenshot. Is there a reason for it? Are you suggesting after EMACTxDMADescriptorListSet is executed, it will jump to ResetISR? Can you put a breakpoint inside EMACTxDMADescriptorListSet so that after you disconnect the Ethernet cable you can then single step? Does it go to ResetISR after you come out of EMACTxDMADescriptorListSet?
Please also answer me the below questions:
- Have you tried to increase the stack and heap size?
- Do you see the same problem if running other enet examples like enet_lwip or enet_io when you disconnect Ethernet cable?
- I believe I have suggested this app note in the past for diagnosing faults. Have you had a chance to read it. https://www.ti.com/lit/pdf/spma043