<?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: Memory Write or Read 64 bytes access Issue. in T-Series</title>
    <link>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896349#M3095</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It can mean that cache is still enabled for VME memory. Check you settings once again. Use a debugger for that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bulat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 May 2019 04:22:57 GMT</pubDate>
    <dc:creator>Bulat</dc:creator>
    <dc:date>2019-05-17T04:22:57Z</dc:date>
    <item>
      <title>Memory Write or Read 64 bytes access Issue.</title>
      <link>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896346#M3092</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;I use to T2080 CPU.&amp;nbsp;&lt;/P&gt;&lt;P&gt;development environment is 32 bit, UP.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CS1 is setting VME bus system.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;write access function is below.&amp;nbsp;&lt;/P&gt;&lt;P&gt;*(unsigned short *)(vmeVt + DOM01A +0x8) = 0x0101;&lt;/P&gt;&lt;P&gt;As above function, I need to only 2-bytes access.&lt;/P&gt;&lt;P&gt;but, CPU is access read 64 bytes and write 64 bytes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;because cache line size = 64 bytes?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IFC setting value is ..&lt;/P&gt;&lt;P&gt;WRITEADR(r6, r7, T4_IFC_CSPR1_EXT, 0x00000000)&lt;BR /&gt; WRITEADR(r6, r7, T4_IFC_FTIM0_CS1, 0xe00e000e)&amp;nbsp;&lt;BR /&gt; WRITEADR(r6, r7, T4_IFC_FTIM1_CS1, 0x0E001F00)&lt;BR /&gt; WRITEADR(r6, r7, T4_IFC_FTIM2_CS1, 0x0E00001F)&amp;nbsp;&lt;BR /&gt; WRITEADR(r6, r7, T4_IFC_FTIM3_CS1, 0x00000000)&amp;nbsp;&lt;BR /&gt; WRITEADR(r6, r7, T4_IFC_CSPR1, (VMEBUS_ADRS | 0x0105))&amp;nbsp;&lt;BR /&gt; WRITEADR(r6, r7, T4_IFC_AMASK1, ~(VMEBUS_SIZE - 1))&lt;BR /&gt; WRITEADR(r6, r7, T4_IFC_CSOR1, 0x400c000c)&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TLB setting value is below.&lt;/P&gt;&lt;P&gt;addis r4, 0, 0x1009&amp;nbsp; &amp;nbsp;/* TLBSEL = TLB1(CAM) , ESEL = 0 */&lt;BR /&gt; addis r5, 0, HI(_MMU_TLB_VALID | _MMU_TLB_IPROT)&lt;BR /&gt; ori r5, r5, _MMU_TLB_SZ_16M /* TS = 0, TSIZE = 16 MByte page size*/&lt;BR /&gt; addis r6, 0, HI(VMEBUS_ADRS) /* EPN */&lt;BR /&gt; ori r6, r6,&amp;nbsp;_MMU_TLB_ATTR_G&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;lt;=== write back setting&lt;BR /&gt; addis r7, 0, HI(VMEBUS_ADRS) /* RPN */&lt;BR /&gt; ori r7, r7, 0x0015 /* Supervisor XWR*/&lt;BR /&gt; li r8, 0x0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to know 2-bytes access method. about read and write access.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 May 2019 02:12:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896346#M3092</guid>
      <dc:creator>kimpilyeon</dc:creator>
      <dc:date>2019-05-16T02:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: Memory Write or Read 64 bytes access Issue.</title>
      <link>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896347#M3093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, the core always reads/writes burst lines (64 bytes) when accesses cacheable memory region. You need to change TLB settings and set VME address space as cache-Inhibit and Guarded for proper operations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bulat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 May 2019 04:15:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896347#M3093</guid>
      <dc:creator>Bulat</dc:creator>
      <dc:date>2019-05-16T04:15:56Z</dc:date>
    </item>
    <item>
      <title>Re: Memory Write or Read 64 bytes access Issue.</title>
      <link>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896348#M3094</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your help.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was trying TLB setting cache-Inhibit and Guarded for proper operations. like below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#define MMU_UNCACHED (_MMU_TLB_ATTR_I | \&lt;BR /&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;_MMU_TLB_ATTR_G)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#define MMU_IO_ACCESS MMU_UNCACHED /* WIMGE bits for IO */&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;addis r4, 0, 0x1009 /* TLBSEL = TLB1(CAM) , ESEL = 0 */&lt;BR /&gt; addis r5, 0, HI(_MMU_TLB_VALID | _MMU_TLB_IPROT)&lt;BR /&gt; ori r5, r5, _MMU_TLB_SZ_16M /* TS = 0, TSIZE = 16 MByte page size*/&lt;BR /&gt; addis r6, 0, HI(VMEBUS_ADRS) /* EPN */&lt;BR /&gt; ori r6, r6, MMU_IO_ACCESS /*MMU_ROM_ACCESS*/&lt;BR /&gt; addis r7, 0, HI(VMEBUS_ADRS) /* RPN */&lt;BR /&gt; ori r7, r7, 0x0015 /* Supervisor XWR*/&lt;BR /&gt; li r8, 0x0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But, write access operation is same before.&lt;/P&gt;&lt;P&gt;hmm....&amp;nbsp;What another point that needed confirm?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;help me.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 May 2019 07:34:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896348#M3094</guid>
      <dc:creator>kimpilyeon</dc:creator>
      <dc:date>2019-05-16T07:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Memory Write or Read 64 bytes access Issue.</title>
      <link>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896349#M3095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It can mean that cache is still enabled for VME memory. Check you settings once again. Use a debugger for that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bulat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 May 2019 04:22:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896349#M3095</guid>
      <dc:creator>Bulat</dc:creator>
      <dc:date>2019-05-17T04:22:57Z</dc:date>
    </item>
    <item>
      <title>Re: Memory Write or Read 64 bytes access Issue.</title>
      <link>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896350#M3096</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you're right.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was enabled cache at os booting.&lt;/P&gt;&lt;P&gt;I was used pmapGlobalMap() function for VME memory initialization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appreciate your help and support.&lt;/P&gt;&lt;P&gt;Best Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 May 2019 08:27:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/Memory-Write-or-Read-64-bytes-access-Issue/m-p/896350#M3096</guid>
      <dc:creator>kimpilyeon</dc:creator>
      <dc:date>2019-05-17T08:27:24Z</dc:date>
    </item>
  </channel>
</rss>

