<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>MQX Software SolutionsのトピックUpon task watchdog timeout is there a way for code to know why task is blocked?</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/Upon-task-watchdog-timeout-is-there-a-way-for-code-to-know-why/m-p/1983977#M18873</link>
    <description>&lt;P&gt;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). &lt;STRONG&gt;So... my question boils down to... is there a way using MQX calls to know why a task is blocked?&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Oct 2024 15:30:44 GMT</pubDate>
    <dc:creator>sodacan</dc:creator>
    <dc:date>2024-10-29T15:30:44Z</dc:date>
    <item>
      <title>Upon task watchdog timeout is there a way for code to know why task is blocked?</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Upon-task-watchdog-timeout-is-there-a-way-for-code-to-know-why/m-p/1983977#M18873</link>
      <description>&lt;P&gt;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). &lt;STRONG&gt;So... my question boils down to... is there a way using MQX calls to know why a task is blocked?&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2024 15:30:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Upon-task-watchdog-timeout-is-there-a-way-for-code-to-know-why/m-p/1983977#M18873</guid>
      <dc:creator>sodacan</dc:creator>
      <dc:date>2024-10-29T15:30:44Z</dc:date>
    </item>
  </channel>
</rss>

