<?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>Model-Based Design Toolbox (MBDT)のトピックMBDT toolbox using Simulink model module exception</title>
    <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MBDT-toolbox-using-Simulink-model-module-exception/m-p/2349509#M10710</link>
    <description>&lt;P&gt;Now using the MBDT tool of S32k3, the top-level model contains the MBDT toolbox module, and the top-level module contains the Simulink model module. Using the subsystem is normal. The model loads the SLX model containing pure algorithms, but there are two issues:&lt;BR /&gt;(1) Under each algorithm model, MBDT toolbox driven *. c *. h *. o will be generated, but theoretically speaking, pure algorithm modules do not have these??&lt;BR /&gt;(2) Compile all generated code once in S32 ds and report the error shown in the figure (make: * * * No rule to make target'D:/Work/APP.Merge/test260409/s32k3xx_dious32ct_Cnfig/../slprj/ert/_stharedutils/rtwshare d ', needed by' s32k3xx_dious32ct. elf '. Stop)&lt;BR /&gt;"make -j8 all" terminated with exit code 2. Build might be incomplete.）， What's the reason?&lt;/P&gt;</description>
    <pubDate>Sat, 11 Apr 2026 01:25:18 GMT</pubDate>
    <dc:creator>zuozuo</dc:creator>
    <dc:date>2026-04-11T01:25:18Z</dc:date>
    <item>
      <title>MBDT toolbox using Simulink model module exception</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MBDT-toolbox-using-Simulink-model-module-exception/m-p/2349509#M10710</link>
      <description>&lt;P&gt;Now using the MBDT tool of S32k3, the top-level model contains the MBDT toolbox module, and the top-level module contains the Simulink model module. Using the subsystem is normal. The model loads the SLX model containing pure algorithms, but there are two issues:&lt;BR /&gt;(1) Under each algorithm model, MBDT toolbox driven *. c *. h *. o will be generated, but theoretically speaking, pure algorithm modules do not have these??&lt;BR /&gt;(2) Compile all generated code once in S32 ds and report the error shown in the figure (make: * * * No rule to make target'D:/Work/APP.Merge/test260409/s32k3xx_dious32ct_Cnfig/../slprj/ert/_stharedutils/rtwshare d ', needed by' s32k3xx_dious32ct. elf '. Stop)&lt;BR /&gt;"make -j8 all" terminated with exit code 2. Build might be incomplete.）， What's the reason?&lt;/P&gt;</description>
      <pubDate>Sat, 11 Apr 2026 01:25:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MBDT-toolbox-using-Simulink-model-module-exception/m-p/2349509#M10710</guid>
      <dc:creator>zuozuo</dc:creator>
      <dc:date>2026-04-11T01:25:18Z</dc:date>
    </item>
  </channel>
</rss>

