<?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>topic Re: MCUXpresso SDK API thread safe in MCUXpresso SDK</title>
    <link>https://community.nxp.com/t5/MCUXpresso-SDK/MCUXpresso-SDK-API-thread-safe/m-p/745912#M540</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi grzegorzkonopko&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Answering your questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Actually the fsl_debug_console are already thread safe, if you check the code in DbgConsole_Printf() in our latest SDK, you will find some APIs like LOG_TAKE_MUTEX_SEMAPHORE_NONBLOCKING. Any case, if you want DbgConsole_Printf() with interrupt, you can look into the macro DEBUG_CONSOLE_TRANSFER_NON_BLOCKING.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. MCUXpresso SDK is the latest SDK drivers for kinetis devices, so I would recommend you this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this could help&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Feb 2018 21:29:00 GMT</pubDate>
    <dc:creator>jorge_a_vazquez</dc:creator>
    <dc:date>2018-02-20T21:29:00Z</dc:date>
    <item>
      <title>MCUXpresso SDK API thread safe</title>
      <link>https://community.nxp.com/t5/MCUXpresso-SDK/MCUXpresso-SDK-API-thread-safe/m-p/745911#M539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear community members/ NXP supporters&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Is a API of MCUXpresso SDK thread safe, e.g.: I would like to use DbgConsole_Printf() from interrupt routine but there is nothing about in documentation: (&lt;A class="link-titled" href="http://mcuxpresso.nxp.com/api_doc/dev/271/group__debugconsole.html#ga7f9e0678f4c708ed5640b0823c07dc35" title="http://mcuxpresso.nxp.com/api_doc/dev/271/group__debugconsole.html#ga7f9e0678f4c708ed5640b0823c07dc35"&gt;MCUXpresso SDK API Reference Manual: Debug Console&lt;/A&gt; )&lt;/P&gt;&lt;P&gt;From code inspection seems it is not possible, however it is good idea to ask&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. what is general recommendation of using SDK API in threads environment (not RTOS only, very general), I can not find any guide yet and documentation (which API is safe, which is not)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. What is recommended for new design, &lt;STRONG&gt;MCUXpresso SDK&lt;/STRONG&gt; or &lt;STRONG&gt;Kinetis SDK&lt;/STRONG&gt;?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Feb 2018 12:19:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-SDK/MCUXpresso-SDK-API-thread-safe/m-p/745911#M539</guid>
      <dc:creator>grzegorzkonopko</dc:creator>
      <dc:date>2018-02-14T12:19:32Z</dc:date>
    </item>
    <item>
      <title>Re: MCUXpresso SDK API thread safe</title>
      <link>https://community.nxp.com/t5/MCUXpresso-SDK/MCUXpresso-SDK-API-thread-safe/m-p/745912#M540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi grzegorzkonopko&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Answering your questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Actually the fsl_debug_console are already thread safe, if you check the code in DbgConsole_Printf() in our latest SDK, you will find some APIs like LOG_TAKE_MUTEX_SEMAPHORE_NONBLOCKING. Any case, if you want DbgConsole_Printf() with interrupt, you can look into the macro DEBUG_CONSOLE_TRANSFER_NON_BLOCKING.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. MCUXpresso SDK is the latest SDK drivers for kinetis devices, so I would recommend you this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this could help&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Feb 2018 21:29:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-SDK/MCUXpresso-SDK-API-thread-safe/m-p/745912#M540</guid>
      <dc:creator>jorge_a_vazquez</dc:creator>
      <dc:date>2018-02-20T21:29:00Z</dc:date>
    </item>
    <item>
      <title>Re: MCUXpresso SDK API thread safe</title>
      <link>https://community.nxp.com/t5/MCUXpresso-SDK/MCUXpresso-SDK-API-thread-safe/m-p/2269289#M5420</link>
      <description>&lt;P&gt;Actually, the blocking debug console functions are NOT thread safe.&amp;nbsp; Only the non-blocking RTOS ones are.&amp;nbsp; In the blocking implementation, multiple threads can end up writing to the UART at the same time causing interleaving (and possibly other problems).&amp;nbsp; I've proven this to be the true with a test case.&lt;/P&gt;&lt;P&gt;The non-blocking RTOS safe implementation may not be a good idea to call from inside an interrupt handler.&amp;nbsp; You really don't want to block inside an interrupt handler.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Dec 2025 20:02:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-SDK/MCUXpresso-SDK-API-thread-safe/m-p/2269289#M5420</guid>
      <dc:creator>nxp16</dc:creator>
      <dc:date>2025-12-26T20:02:14Z</dc:date>
    </item>
  </channel>
</rss>

