<?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 Byte shift between flexspi ahb bus read flash commands in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Byte-shift-between-flexspi-ahb-bus-read-flash-commands/m-p/1461244#M19659</link>
    <description>&lt;P&gt;I have an embedded design using an iMXRT1062 and an ISSI25LP512 flash.&amp;nbsp; Using this flash, I need to use 4 byte addressing.&amp;nbsp; There are two ways to do this, one setting the EXTADD bit in flash bank register to force all reads to require 4 byte addressing with the 0xEB quad command, the second to use a new 0xEC quad command which requires 4 byte addressing without the EXTADD bit set.&amp;nbsp; The LUT is setup to use one of these commands for the continuous read.&amp;nbsp; The problem I am having is if I have a location that has 0x55,0x42 in it, if I read that location with the 0xEB command with EXTADD set, I get the 0x55 as expected, but if I use the 0xEC command, I get 0x42 at the first location.&amp;nbsp; It is shifted by one byte.&amp;nbsp; I can change the offset value in the flexspi.c driver by one byte, but that seems more of a hack.&amp;nbsp; Not sure what this is or the proper way to address it.&amp;nbsp; Perhaps someone can enlighten me on it.&amp;nbsp; Thx&lt;/P&gt;</description>
    <pubDate>Fri, 20 May 2022 02:57:26 GMT</pubDate>
    <dc:creator>jautry</dc:creator>
    <dc:date>2022-05-20T02:57:26Z</dc:date>
    <item>
      <title>Byte shift between flexspi ahb bus read flash commands</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Byte-shift-between-flexspi-ahb-bus-read-flash-commands/m-p/1461244#M19659</link>
      <description>&lt;P&gt;I have an embedded design using an iMXRT1062 and an ISSI25LP512 flash.&amp;nbsp; Using this flash, I need to use 4 byte addressing.&amp;nbsp; There are two ways to do this, one setting the EXTADD bit in flash bank register to force all reads to require 4 byte addressing with the 0xEB quad command, the second to use a new 0xEC quad command which requires 4 byte addressing without the EXTADD bit set.&amp;nbsp; The LUT is setup to use one of these commands for the continuous read.&amp;nbsp; The problem I am having is if I have a location that has 0x55,0x42 in it, if I read that location with the 0xEB command with EXTADD set, I get the 0x55 as expected, but if I use the 0xEC command, I get 0x42 at the first location.&amp;nbsp; It is shifted by one byte.&amp;nbsp; I can change the offset value in the flexspi.c driver by one byte, but that seems more of a hack.&amp;nbsp; Not sure what this is or the proper way to address it.&amp;nbsp; Perhaps someone can enlighten me on it.&amp;nbsp; Thx&lt;/P&gt;</description>
      <pubDate>Fri, 20 May 2022 02:57:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Byte-shift-between-flexspi-ahb-bus-read-flash-commands/m-p/1461244#M19659</guid>
      <dc:creator>jautry</dc:creator>
      <dc:date>2022-05-20T02:57:26Z</dc:date>
    </item>
    <item>
      <title>Re: Byte shift between flexspi ahb bus read flash commands</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Byte-shift-between-flexspi-ahb-bus-read-flash-commands/m-p/1461401#M19674</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.&lt;BR /&gt;I'd like to suggest that it should assure that the EXTADD bit is 0 when using the introduction 0xEC, and you can use the oscilloscope to visualize the reading process, it might provide clues.&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&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;&amp;nbsp;&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;</description>
      <pubDate>Fri, 20 May 2022 07:58:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Byte-shift-between-flexspi-ahb-bus-read-flash-commands/m-p/1461401#M19674</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2022-05-20T07:58:19Z</dc:date>
    </item>
    <item>
      <title>Re: Byte shift between flexspi ahb bus read flash commands</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Byte-shift-between-flexspi-ahb-bus-read-flash-commands/m-p/1465682#M19812</link>
      <description>&lt;P&gt;EXTADD is off.&amp;nbsp; I do not have a scope that will work at this these frequencies.&amp;nbsp; Adjusted buffer read to offset this issue which seems to work.&amp;nbsp; I also put in an inquiry with ISSI on this issue as I suspect it lies with them.&lt;/P&gt;</description>
      <pubDate>Fri, 27 May 2022 15:25:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Byte-shift-between-flexspi-ahb-bus-read-flash-commands/m-p/1465682#M19812</guid>
      <dc:creator>jautry</dc:creator>
      <dc:date>2022-05-27T15:25:53Z</dc:date>
    </item>
  </channel>
</rss>

