LAUNCHXL-F280049C: TMS320F280049C-MCU gets hang randomly

Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: TMS320F280049C

Hi there,

My MCU at random time gets hanged.

I have a Timer ISR that will make a LED toggle but when it hangs the LED was ON/OFF based on the toggling and all operations are stuck. This was my first visible observation. Then only if i do the POR it will run. After some days/months it will hang again. 

So to check whether it went to some trap function i have added the software reset function in all traps so that if it got reset we will get to know it has went to some illegal trap.

But even after adding the software reset line at random times it still hangs.

Do let me know why it is happening and how to solve it.

you can ask me the details like map file, linker file or any other details and we will give you the details.

Thank you.


  • Hi,

    I have a Timer ISR that will make a LED toggle but when it hangs the LED was ON/OFF based on the toggling and all operations are stuck. This was my first visible observation. Then only if i do the POR it will run. After some days/months it will hang again

    Do you have NMI ISR programmed ? If not add and configure it clear all NMI flags and add while 1 infinite loop at the end of ISR.

    Can you connect to the MCU when LED doesnt blink and check where the PC is or what CPU is executing by loading symbols ? When you connect to CPU remove GEL file so that reset is not triggered

    Have you check the NMISHDWFLG to see if there was NMI triggered ? 

    Thanks

  • Hi Prarthan,

    I have configured software reset in all traps inlcuding NMI handler and illegal trap but it still hang happens. This is our observation. We need to know why?

    Once the MCU hangs again we will try to connect the target without GEL file.

    Thank you.

  • Hi,

    configure it clear all NMI flags and add while 1 infinite loop at the end of ISR.

    Do you have your NMI and ITRAP ISR to do above ?

    We would need to reproduce the issue and debug the specific scenario under which the hang condition you are describing occurs, unless we know what error is occurring we cannot take any further debug steps.

    Once the MCU hangs again we will try to connect the target without GEL file.

    In previous hang scenario you never tried to connect and look at the errors ?

    Thanks

  • Hi Prarthan,


    In previous hang scenario you never tried to connect and look at the errors ?

    I tried to connect to the board but when i connect to the board using JTAG it gets reset so I couldn't figure out what happened.

    So if i remove the GEL file and try to upload the code, will it reset ?

    One more question is when i try to connect the JTAG (XDS110 USB probe), when it got hung, it automatically gets reset and it is because of the reset pin in JTAG I guess, and in this case how can i figure out  where exactly the code got hung ?

    can you explain the details step by step so it would be more helpful for me and also please tell me where will be the GEL file located i found the .CCXML in which the initialization script has a .gel file but i am unable to track the location and I searched my entire project. If i remove the .gel file and try to upload then some error occurs in C28xx_CPU1 and CLA1 in debug mode.  I have attached the screenshot of this for your reference. 



    I am using CCS 12.8.1 version and I am using TMS320F280049C IC in the PCB. If you want further details i can give you those details.

    Thank you.

  • One more question is when i try to connect the JTAG (XDS110 USB probe), when it got hung, it automatically gets reset and it is because of the reset pin in JTAG I guess, and in this case how can i figure out  where exactly the code got hung ?

    Step by step debug procedure would be as follows : 

    1) Monitor the XRSn on oscilloscope, with trigger set on falling edge of XRSn.

    If you see the hang condition with LED also check the scope if it captured the falling edge of XRSn

    2) Then connect to CPU, remove gel file so it doesn't create another debugger reset. If the reset was already triggered prior.

    You would look at the NMI Shadow flags and see if any error flags were set.

    .CCXML in which the initialization script has a .gel file but i am unable to track the location and I searched my entire project.

    Yes, you can just remove the gel file path from the initialization menu in target config xml and connect.

    Thanks

  • Hi Prarthan,


    2) Then connect to CPU, remove gel file so it doesn't create another debugger reset.

    I need to know how to do this. Because i have tried to remove the gel file and tired to upload using target configuration but it throwed me some errors which I have shown in my previous post so kindly refer to that post.

    Kindly tell me every details of steps on how to remove the gel file and then uplaod it when the MCU got hanged without resetting it.

    Thank you.