RTOS/EVMK2H: Debug a crash or hang in TI-RTOS using CCS

Krishna Mohan

Part Number: EVMK2H

Tool/software: TI-RTOS

Hi,

I am having one K2EVM-HK and using TI RTOS on it. I am using CCS 7.3.0.00019. I have created two threads and facing some issue. It seems like one of the thread crashes while the other one is in infinite loop. I am not getting any crash logs on CCS or any kind of notification. If I do a pause, in Disassembly I can see a single instruction repeating throughout, suggesting that thread is in infinite loop. I am also doubting that while this thread is running in infinite loop, my other thread has crashed.

Can you suggest me some debugging techniques to find out where the crash is happening and in which loop the thread is getting hung.

Thank You

over 7 years ago

0 Cvetolin Shulev-XID over 7 years ago

TI__Guru 65405 points

The team is notified. They will post their feedback directly here.

BR
Tsvetolin Shulev

0 Sahin Okur over 7 years ago

TI__Mastermind 27355 points

Hello,

CCS offers the RTOS Object View (ROV) to debug programs built with TI-RTOS. To open it in CCS, go to Tools -> ROV Classic.

You can also add logs by doing Log_print and viewing them in the LoggerBuf window of ROV. I've attached a program that uses this, for reference.

/cfs-file/__key/communityserver-discussions-components-files/791/3007.1070.Server.c

You can also track kernel events using CCS's RTOS Analyzer. Refer to this guide for help with it: www.ti.com/.../spruh43f.pdf

I hope this helps.

Best,
Sahin

0 Krishna Mohan over 7 years ago in reply to Sahin Okur

Intellectual 485 points

Hi Sahin,

I am trying to use ROV and to first understand it, I have introduced de-referencing of NULL character. I can see the following under the task section:
"Target memory read failed at address 0x6563784d, length = 76.
This read is at an INVALID address according to the applications's section map. The application is likely either uninitialized or corrupt."

How can I map it to my code i.e is there any way I can know which line number in which file has lead to the crash?

Thanks You,
Krishna Mohan

0 Sahin Okur over 7 years ago in reply to Krishna Mohan

TI__Mastermind 27355 points

Hi Krishna

I'm looping in the TI-RTOS team to help answer your question.

Regards,
Sahin

0 ToddMullanix over 7 years ago in reply to Sahin Okur

TI__Guru* 96960 points

Hi Krishna,

I'd watch/review this page first: training.ti.com/debugging-common-application-issues-ti-rtos

Can you look at ROV before something bad happens (e.g. before calling BIOS_start) to make sure everything is ok? The common things to look for are blown system and/or task stacks and exceptions.

Todd

0 Krishna Mohan over 7 years ago in reply to ToddMullanix

Intellectual 485 points

Hi Todd,

Thanks for your response.

I checked the above video. From what I understood, to map my crash to my code I should use minimal or enhanced exception decoding handler. In order to do so, I should set enableException flag as true. But the example used in video was for MCU devices. I have K2H EVM which has ARM cores and the HWI module does not have any such flag.

0 Sahin Okur over 7 years ago in reply to Krishna Mohan

TI__Mastermind 27355 points

Hi Krishna,

For the Cortex-A15, there's an "Exception call stack" in the Exception module of the ROV. That might be what you are looking for.

Regards,
Sahin

Processors

Processors forum

RTOS/EVMK2H: Debug a crash or hang in TI-RTOS using CCS