Upon task watchdog timeout is there a way for code to know why task is blocked?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Upon task watchdog timeout is there a way for code to know why task is blocked?

574 Views
sodacan
Contributor II

I have an unfortunate situation where every few months a system watchdogs and we don't know why, so I'm looking into adding calls to _watchdog_create_component and in the expiry function dumping (hopefully useful) debug into to the console and to a file. I've been looking at what information is available for this purpose, and it seems like the TD_STRUCT is what I should try to use. However, looking at everything in this struct I don't see anything that is like a "this is the reason I'm blocked" member. Granted, I'm an MQX newbie, but I thought I should be able to find something other than using the task aware debugger to get this info (since a debugger almost certainly will not be connected to one of these systems when it watchdogs). So... my question boils down to... is there a way using MQX calls to know why a task is blocked?

0 Kudos
Reply
0 Replies