<?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: MEX file for azure rtos/usbx examples in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/MEX-file-for-azure-rtos-usbx-examples/m-p/2083225#M58099</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/246045"&gt;@steve5528&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You are right, that's because these examples are typically not configured using the MCUXpresso Config Tools , but instead use manually written SDK-provided functions for the EVK.&lt;/P&gt;
&lt;P&gt;The board setup code for lpcxpresso55s28_usbx_device_hid_mouse was not tool-generated using MCUXpresso Config Tools. The board initialization is done using standard SDK calls.&lt;/P&gt;
&lt;P&gt;For a custom board, generate your own .mex project with&amp;nbsp;MCUXpresso Config Tools and bring in USBX source files.&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Harry&lt;/P&gt;</description>
    <pubDate>Fri, 18 Apr 2025 09:17:47 GMT</pubDate>
    <dc:creator>Harry_Zhang</dc:creator>
    <dc:date>2025-04-18T09:17:47Z</dc:date>
    <item>
      <title>MEX file for azure rtos/usbx examples</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/MEX-file-for-azure-rtos-usbx-examples/m-p/2083101#M58096</link>
      <description>&lt;P&gt;Good Day!&lt;/P&gt;&lt;P&gt;the example "lpcxpresso55s28_usbx_device_hid_mouse" runs fine on LPC55S28-EVK, however there is no included MEX file for this example or other azure_rtos examples.&lt;/P&gt;&lt;P&gt;Was the board setup code for the above project tool generated? If I would like to adapt this example for a custom board, is there a MEX file i could use?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2025 06:52:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/MEX-file-for-azure-rtos-usbx-examples/m-p/2083101#M58096</guid>
      <dc:creator>steve5528</dc:creator>
      <dc:date>2025-04-18T06:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: MEX file for azure rtos/usbx examples</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/MEX-file-for-azure-rtos-usbx-examples/m-p/2083225#M58099</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/246045"&gt;@steve5528&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You are right, that's because these examples are typically not configured using the MCUXpresso Config Tools , but instead use manually written SDK-provided functions for the EVK.&lt;/P&gt;
&lt;P&gt;The board setup code for lpcxpresso55s28_usbx_device_hid_mouse was not tool-generated using MCUXpresso Config Tools. The board initialization is done using standard SDK calls.&lt;/P&gt;
&lt;P&gt;For a custom board, generate your own .mex project with&amp;nbsp;MCUXpresso Config Tools and bring in USBX source files.&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Harry&lt;/P&gt;</description>
      <pubDate>Fri, 18 Apr 2025 09:17:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/MEX-file-for-azure-rtos-usbx-examples/m-p/2083225#M58099</guid>
      <dc:creator>Harry_Zhang</dc:creator>
      <dc:date>2025-04-18T09:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: MEX file for azure rtos/usbx examples</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/MEX-file-for-azure-rtos-usbx-examples/m-p/2083956#M58111</link>
      <description>&lt;P&gt;Thank you Harry.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Apr 2025 16:45:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/MEX-file-for-azure-rtos-usbx-examples/m-p/2083956#M58111</guid>
      <dc:creator>steve5528</dc:creator>
      <dc:date>2025-04-21T16:45:04Z</dc:date>
    </item>
  </channel>
</rss>

