<?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 LPC55S69 : CASPER and Core1 in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S69-CASPER-and-Core1/m-p/975249#M38560</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In UM mentioned:&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;ARMv8-M architecture (ARM M33) introduces co-processor interface allowing CASPER&lt;BR /&gt;access via MCR (Move from Coprocessor to Register) and MRC (Move from Register to&lt;BR /&gt;Coprocessor) opcodes. Using this, up to two registers can be transferred between ARM&lt;BR /&gt;M33 core and CASPER.&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If Casper act as coprocessor and Core1 dosn't supports coprocessors, it means CASPER can't be used from Core1 ?&lt;/P&gt;&lt;P&gt;Is this so ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #172b4d; background-color: #ffffff;"&gt;MPU, FPU, DSP, ETM, Trustzone (SECEXT), Secure Attribution Unit (SAU) or co-processor interface are not avaible on Core1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What other peripherals can't be used from Core1 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What areas of SRAM are recommended for code execution for Core1 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Eugene&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 Oct 2019 07:07:19 GMT</pubDate>
    <dc:creator>EugeneHiihtaja</dc:creator>
    <dc:date>2019-10-29T07:07:19Z</dc:date>
    <item>
      <title>LPC55S69 : CASPER and Core1</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S69-CASPER-and-Core1/m-p/975249#M38560</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In UM mentioned:&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;ARMv8-M architecture (ARM M33) introduces co-processor interface allowing CASPER&lt;BR /&gt;access via MCR (Move from Coprocessor to Register) and MRC (Move from Register to&lt;BR /&gt;Coprocessor) opcodes. Using this, up to two registers can be transferred between ARM&lt;BR /&gt;M33 core and CASPER.&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If Casper act as coprocessor and Core1 dosn't supports coprocessors, it means CASPER can't be used from Core1 ?&lt;/P&gt;&lt;P&gt;Is this so ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #172b4d; background-color: #ffffff;"&gt;MPU, FPU, DSP, ETM, Trustzone (SECEXT), Secure Attribution Unit (SAU) or co-processor interface are not avaible on Core1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What other peripherals can't be used from Core1 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What areas of SRAM are recommended for code execution for Core1 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Eugene&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Oct 2019 07:07:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S69-CASPER-and-Core1/m-p/975249#M38560</guid>
      <dc:creator>EugeneHiihtaja</dc:creator>
      <dc:date>2019-10-29T07:07:19Z</dc:date>
    </item>
    <item>
      <title>Re: LPC55S69 : CASPER and Core1</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S69-CASPER-and-Core1/m-p/975250#M38561</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Eugene&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;What do you mean " it means CASPER can't be used from Core1 "?&lt;/P&gt;&lt;P&gt;Casper is a accelerator engine. it's not a coprocessor.&lt;BR /&gt;Casper Sits on Cortex-M33 co-processor bus. An AHB bus and ARMv8-M Coprocessor (CP) interface to allow loading information to perform operations.&lt;BR /&gt;It works standalone from co-processor. Using CASPER can free up the ARM M33 to do other tasks while CASPER does the computation.&lt;/P&gt;&lt;P&gt;Fast shared RAM access 2x 32b RAMs which are allocated for CASPER RAM interface and shared with System Memory.&lt;/P&gt;&lt;P&gt;For Casper engine, I recommend a useful document:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/docs/en/application-note/AN12445.pdf" title="https://www.nxp.com/docs/en/application-note/AN12445.pdf"&gt;https://www.nxp.com/docs/en/application-note/AN12445.pdf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/docs/en/application-note-software/AN12445SW.zip" title="https://www.nxp.com/docs/en/application-note-software/AN12445SW.zip"&gt;https://www.nxp.com/docs/en/application-note-software/AN12445SW.zip&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Jun Zhang&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Oct 2019 09:15:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC55S69-CASPER-and-Core1/m-p/975250#M38561</guid>
      <dc:creator>ZhangJennie</dc:creator>
      <dc:date>2019-10-30T09:15:50Z</dc:date>
    </item>
  </channel>
</rss>

