<?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: the indexing confusion in k358BMU774A reading example in Model-Based Design Toolbox (MBDT)</title>
    <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/the-indexing-confusion-in-k358BMU774A-reading-example/m-p/1866075#M9089</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/232900"&gt;@primo&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This TD Handler Block has been introduced to help you access the data from the TD Handler structure. The idea behind this is that you are composing a transaction descriptor full of commands, then you send the transaction descriptor using the Bms_Common -&amp;gt; Bms_TD_Send, and then you request, via the same procedure the data standing from some particular registers. Now, the TD Handler helps you to get the actual TPL vector of uint16 responses. Now the TPL has 6 x uint16, where only the bytes 2, 3, 4, and 5 have meaningful data, like for example the voltages, while the other bytes 0, 1, and 6 contain TPL-specific data. To understand more, please check the&amp;nbsp;&lt;A id="relatedDocsClickPDF_1" class="dtmcustomrulelink" href="https://www.nxp.com/webapp/sd/collateral/1659024528596690339460?version=3.0" target="_blank" rel="noopener" data-dtmaction="Documentation Section - Results Link Click" data-dtmsubaction="MC33665A Datasheet V3.0 - Secure Files - Data Sheet - English"&gt;&lt;SPAN&gt;MC33665A Datasheet V3.0&lt;/SPAN&gt;&lt;/A&gt;&amp;nbsp;, from the NXP website. So basically with the TD Handler, you have access to all the bytes transferred via the TPL bus, and with those indexes, you only select the position of the DATA to be transferred.&lt;/P&gt;
&lt;P&gt;Now, an alternative for this block is to use the Bms SL E2E block which receives the address of the register and the number of registers to be returned, but the MBDT only integrates the DEMO version of the Safety Library which provides this block, so you only be able to use this block for a limited amount of time.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Marius&lt;/P&gt;</description>
    <pubDate>Wed, 15 May 2024 07:58:35 GMT</pubDate>
    <dc:creator>mariuslucianand</dc:creator>
    <dc:date>2024-05-15T07:58:35Z</dc:date>
    <item>
      <title>the indexing confusion in k358BMU774A reading example</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/the-indexing-confusion-in-k358BMU774A-reading-example/m-p/1863670#M9077</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Recently, i have been working on the example using bmu_k358 to communicate with Bcc_774a over TPL. However, i am confused on the choice of indexes when accessing the data in the TD package. According to the result observed on freemaster, the readings are correct. The question is, what is the reasoning behind the index, and which part of the datasheet specifies the location of data? I have checked through the datasheets I can find, and i did not establish any connections.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The answers will help a lot, thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="primo_0-1715369483808.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/278289i0A02937C95C877B4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="primo_0-1715369483808.png" alt="primo_0-1715369483808.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 19:40:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/the-indexing-confusion-in-k358BMU774A-reading-example/m-p/1863670#M9077</guid>
      <dc:creator>primo</dc:creator>
      <dc:date>2024-05-10T19:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: the indexing confusion in k358BMU774A reading example</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/the-indexing-confusion-in-k358BMU774A-reading-example/m-p/1866075#M9089</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/232900"&gt;@primo&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This TD Handler Block has been introduced to help you access the data from the TD Handler structure. The idea behind this is that you are composing a transaction descriptor full of commands, then you send the transaction descriptor using the Bms_Common -&amp;gt; Bms_TD_Send, and then you request, via the same procedure the data standing from some particular registers. Now, the TD Handler helps you to get the actual TPL vector of uint16 responses. Now the TPL has 6 x uint16, where only the bytes 2, 3, 4, and 5 have meaningful data, like for example the voltages, while the other bytes 0, 1, and 6 contain TPL-specific data. To understand more, please check the&amp;nbsp;&lt;A id="relatedDocsClickPDF_1" class="dtmcustomrulelink" href="https://www.nxp.com/webapp/sd/collateral/1659024528596690339460?version=3.0" target="_blank" rel="noopener" data-dtmaction="Documentation Section - Results Link Click" data-dtmsubaction="MC33665A Datasheet V3.0 - Secure Files - Data Sheet - English"&gt;&lt;SPAN&gt;MC33665A Datasheet V3.0&lt;/SPAN&gt;&lt;/A&gt;&amp;nbsp;, from the NXP website. So basically with the TD Handler, you have access to all the bytes transferred via the TPL bus, and with those indexes, you only select the position of the DATA to be transferred.&lt;/P&gt;
&lt;P&gt;Now, an alternative for this block is to use the Bms SL E2E block which receives the address of the register and the number of registers to be returned, but the MBDT only integrates the DEMO version of the Safety Library which provides this block, so you only be able to use this block for a limited amount of time.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Marius&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2024 07:58:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/the-indexing-confusion-in-k358BMU774A-reading-example/m-p/1866075#M9089</guid>
      <dc:creator>mariuslucianand</dc:creator>
      <dc:date>2024-05-15T07:58:35Z</dc:date>
    </item>
  </channel>
</rss>

