<?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>MPC5xxx中的主题 Re: CSE2 MPC5777C MCAL 4.3 : CSM Stack (Missing 'Job config structure')</title>
    <link>https://community.nxp.com/t5/MPC5xxx/CSE2-MPC5777C-MCAL-4-3-CSM-Stack-Missing-Job-config-structure/m-p/984857#M14841</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My understanding here is&amp;nbsp;&lt;STRONG&gt;JOB_CONFIGURATION_STRUCTURE&lt;/STRONG&gt;, which is in responsible of Csm, cannot be a part generated by Crypto, i.e., appears in Crypto_Cfg.c and Crypto_Cfg.h. As Csm is a stub in MCAL's perspective, it is also not generated by NXP Csm itself. So developers need to manually update the structure and passing&amp;nbsp;it to&amp;nbsp;&lt;STRONG&gt;Crypto_ProcessJob&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Mar 2020 07:52:38 GMT</pubDate>
    <dc:creator>namnguyenviet</dc:creator>
    <dc:date>2020-03-23T07:52:38Z</dc:date>
    <item>
      <title>CSE2 MPC5777C MCAL 4.3 : CSM Stack (Missing 'Job config structure')</title>
      <link>https://community.nxp.com/t5/MPC5xxx/CSE2-MPC5777C-MCAL-4-3-CSM-Stack-Missing-Job-config-structure/m-p/984856#M14840</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1) Hi Team NXP,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We need your answer for the following query:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Query] Is the second param that needs to be passed for below API i.e Job Configuration Structure shall be auto-generated by &lt;STRONG&gt;EB_Tresos&lt;/STRONG&gt; &lt;STRONG&gt;configuration&lt;/STRONG&gt; or it needs to be defined manually by Developer using type: &lt;STRONG&gt;Crypto_JobType&lt;/STRONG&gt;.&amp;nbsp;&lt;/P&gt;&lt;P&gt;---&amp;gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; [&lt;STRONG&gt;API&lt;/STRONG&gt;] :&amp;nbsp;&lt;STRONG&gt;&lt;EM&gt;Crypto_ProcessJob&lt;/EM&gt;&lt;/STRONG&gt; ( &lt;EM&gt;uint32 objectId&lt;/EM&gt;&lt;STRONG&gt;, &lt;EM&gt;Crypto_JobType*&amp;nbsp;&lt;/EM&gt; job&lt;/STRONG&gt;);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[&lt;STRONG&gt;Context&lt;/STRONG&gt;] For a CSM Stack : (CSM, Cry-If, Crypto) configured using &lt;STRONG&gt;MCAL4.3_CRYPTO_P1&lt;/STRONG&gt;, to achieve Job Processing for &lt;STRONG&gt;SYNC_AES_ENCRYPT_AND_DECRYPT&lt;/STRONG&gt;,&amp;nbsp;the &lt;STRONG&gt;JOB_CONFIGURATION_STRUCTURE&lt;/STRONG&gt; is not generated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;[&lt;STRONG&gt;Explanation&lt;/STRONG&gt;] The following image shows the &lt;STRONG&gt;CSM_JOB_CONFIG_INSTANCE&lt;/STRONG&gt; which is expected to generate a &lt;STRONG&gt;CONFIG_STRUCTURE&lt;/STRONG&gt; post generation&amp;nbsp;but is found missing in : '&lt;STRONG&gt;Crypto_Cfg.c'&lt;/STRONG&gt;, '&lt;STRONG&gt;Crypto_Cfg.h'.&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_28.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/98320i336EFAA740E5373F/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_28.png" alt="pastedImage_28.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;[Query]&lt;/STRONG&gt; So, with ref to above image, Can I expect a &lt;STRONG&gt;'JOB_CONFIG_STRUCTURE'&lt;/STRONG&gt; to get generated in &lt;STRONG&gt;'Crypto_Cfg.c'&lt;/STRONG&gt; file as per above config and references given in it for Keys and Cry_Primitives&amp;nbsp;?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;-&lt;/STRONG&gt; If not a job is generated&amp;nbsp;of type '&lt;EM&gt;&lt;STRONG&gt;Crypto_JobType Job&lt;/STRONG&gt;' based on the configuration already made in tool, do developer need to manually update the structure&amp;nbsp;and pass it to below API.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;&lt;SPAN style="font-weight: 400;"&gt;---&amp;gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; [&lt;/SPAN&gt;&lt;STRONG&gt;API&lt;/STRONG&gt;&lt;SPAN style="font-weight: 400;"&gt;] :&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;EM&gt;Crypto_ProcessJob&lt;/EM&gt;&lt;/STRONG&gt;&lt;SPAN style="font-weight: 400;"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN style="font-weight: 400;"&gt;&lt;EM&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;uint32 objectId&lt;/EM&gt;&lt;/SPAN&gt;&lt;STRONG&gt;,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;Crypto_JobType*&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/EM&gt;job&lt;/STRONG&gt;&lt;SPAN style="font-weight: 400;"&gt;);&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-weight: 400; "&gt;&lt;STRONG&gt;- Also, please let me know on next CRYPTO_MCAL_Plugins update if possible which might address this issue. :smileyhappy:&amp;nbsp;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-weight: 400; "&gt;&lt;STRONG&gt;- Request you to respond ASAP :smileyhappy:&amp;nbsp;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: 400;"&gt;&lt;STRONG&gt;Thanks in advance for understanding our need.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-weight: 400; "&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: 400;"&gt;&lt;STRONG&gt;Regards&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;EM style="font-weight: 400; "&gt;&lt;STRONG&gt;,&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-weight: 400; "&gt;&lt;STRONG&gt;Lakshmi Kanth (Senior Research Engineer)&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/lukaszadrapa"&gt;lukaszadrapa&lt;/A&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-weight: 400; "&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2020 12:22:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/CSE2-MPC5777C-MCAL-4-3-CSM-Stack-Missing-Job-config-structure/m-p/984856#M14840</guid>
      <dc:creator>lakshmikanth</dc:creator>
      <dc:date>2020-03-18T12:22:04Z</dc:date>
    </item>
    <item>
      <title>Re: CSE2 MPC5777C MCAL 4.3 : CSM Stack (Missing 'Job config structure')</title>
      <link>https://community.nxp.com/t5/MPC5xxx/CSE2-MPC5777C-MCAL-4-3-CSM-Stack-Missing-Job-config-structure/m-p/984857#M14841</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My understanding here is&amp;nbsp;&lt;STRONG&gt;JOB_CONFIGURATION_STRUCTURE&lt;/STRONG&gt;, which is in responsible of Csm, cannot be a part generated by Crypto, i.e., appears in Crypto_Cfg.c and Crypto_Cfg.h. As Csm is a stub in MCAL's perspective, it is also not generated by NXP Csm itself. So developers need to manually update the structure and passing&amp;nbsp;it to&amp;nbsp;&lt;STRONG&gt;Crypto_ProcessJob&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Mar 2020 07:52:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/CSE2-MPC5777C-MCAL-4-3-CSM-Stack-Missing-Job-config-structure/m-p/984857#M14841</guid>
      <dc:creator>namnguyenviet</dc:creator>
      <dc:date>2020-03-23T07:52:38Z</dc:date>
    </item>
    <item>
      <title>Re: CSE2 MPC5777C MCAL 4.3 : CSM Stack (Missing 'Job config structure')</title>
      <link>https://community.nxp.com/t5/MPC5xxx/CSE2-MPC5777C-MCAL-4-3-CSM-Stack-Missing-Job-config-structure/m-p/984858#M14842</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nam Nguyen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Thanks for the response&lt;/STRONG&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I take the inference that developer needs to update the structure. (I'm going as per that).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;One last query&lt;/STRONG&gt; : Do you expect it to be&amp;nbsp; auto generated in next '&lt;STRONG&gt;CRYPTO MCAL PLUGINS RELEASE&lt;/STRONG&gt;' ? (is should be possible I guess, as all details need for job configuration are statically configured by developer and hence available).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, I'm updating manually now. If possible please respond to above query.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Thanks &amp;amp; Regards,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Lakshmi Kanth,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Senior Research Engineer.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2020 07:36:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/CSE2-MPC5777C-MCAL-4-3-CSM-Stack-Missing-Job-config-structure/m-p/984858#M14842</guid>
      <dc:creator>lakshmikanth</dc:creator>
      <dc:date>2020-03-26T07:36:45Z</dc:date>
    </item>
    <item>
      <title>Re: CSE2 MPC5777C MCAL 4.3 : CSM Stack (Missing 'Job config structure')</title>
      <link>https://community.nxp.com/t5/MPC5xxx/CSE2-MPC5777C-MCAL-4-3-CSM-Stack-Missing-Job-config-structure/m-p/984859#M14843</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as I know, I don't expect that the Job configuration structure is auto generated in&amp;nbsp;future Crypto release,&amp;nbsp;since CSM is (at least for now) always a stub and only aim to avoid compile error. With CSM package provided by other integrator (Vector DaVinci, for example), I assumed that Job configuration structure is auto generated, but anyway you should contact to provider for better usage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Nam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2020 07:47:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/CSE2-MPC5777C-MCAL-4-3-CSM-Stack-Missing-Job-config-structure/m-p/984859#M14843</guid>
      <dc:creator>namnguyenviet</dc:creator>
      <dc:date>2020-03-26T07:47:49Z</dc:date>
    </item>
  </channel>
</rss>

