<?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>ColdFire/68K Microcontrollers and ProcessorsのトピックRe: Strange thing about the QSPI module in MCF5235</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132124#M1070</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hello,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;For information,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;QSPI Transmit RAM (0x00-0x0F) is WRITE ONLY,&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;QSPI&amp;nbsp;Receive RAM (0x10-0x1F) is READ ONLY,&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;QSPI&amp;nbsp;Command RAM (0x20-0x2F) is WRITE ONLY.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Bye&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Oct 2006 00:43:17 GMT</pubDate>
    <dc:creator>Arev</dc:creator>
    <dc:date>2006-10-06T00:43:17Z</dc:date>
    <item>
      <title>Strange thing about the QSPI module in MCF5235</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132117#M1063</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi all,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm trying to connect a spi-eeprom with the qspi module to the MCF5235. I wrote some code with the read/write functions which doesn't work correctly. When I did the step by step with BDM, I found a strange thing, that is the QAR is incremented by 2 at each write to QDR, that means:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;MCF_QSPI_QAR = 0x20; // set QAR to command RAM zone&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;MCF_QSPI_QDR = 0xC200;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;when I've passed the second line, QAR becomes 0x0022, so that I've got only 8 commands available instead of 16.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is that because of the definition:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#define MCF_QSPI_QAR (*(vuint16*)(void*)(&amp;amp;__IPSBAR[0x000350])) ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;How can I fix this problem?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's perhaps a stupid question but I wish someone could answer me, thanks a lot.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;--&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Ivy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Oct 2006 21:57:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132117#M1063</guid>
      <dc:creator>Ivychacha</dc:creator>
      <dc:date>2006-10-03T21:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: Strange thing about the QSPI module in MCF5235</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132118#M1064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi Ivy,&lt;BR /&gt;&lt;BR /&gt;I can't reproduce this behaviour on my system - at least not when running through the code.&lt;BR /&gt;&lt;BR /&gt;There is one possibility however to reproduce this within the debugger : If you have a register view of QDR open, then with each step (as this view is refreshed) you get an additional access to QDR thus incrementing QAR.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;stzari&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Oct 2006 17:06:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132118#M1064</guid>
      <dc:creator>stzari</dc:creator>
      <dc:date>2006-10-04T17:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: Strange thing about the QSPI module in MCF5235</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132119#M1065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Thank stzari for your answer, I think that's the problem. But without the register view I can't know what happens inside the QSPI module... is there any other way to be aware of what happens in each step?&lt;BR /&gt;&lt;BR /&gt;Thanks very much.&lt;BR /&gt;&lt;BR /&gt;---&lt;BR /&gt;Ivy&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Oct 2006 17:36:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132119#M1065</guid>
      <dc:creator>Ivychacha</dc:creator>
      <dc:date>2006-10-04T17:36:27Z</dc:date>
    </item>
    <item>
      <title>Re: Strange thing about the QSPI module in MCF5235</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132120#M1066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;PS. Another thing, is it normal that in 'register view' I've got the QDR always = 0 ? It aut-clear itself after putting the data into the QSPI RAM?&lt;BR /&gt;&lt;BR /&gt;thanks.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Ivy&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Oct 2006 18:04:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132120#M1066</guid>
      <dc:creator>Ivychacha</dc:creator>
      <dc:date>2006-10-04T18:04:48Z</dc:date>
    </item>
    <item>
      <title>Re: Strange thing about the QSPI module in MCF5235</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132121#M1067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi Ivy,&lt;BR /&gt;&lt;BR /&gt;Since the register view of QDR always accesses the next RAM position (since QAR has been incremented by the last access to QDR) I would guess that a readout of 0 would be ok.&lt;BR /&gt;Note that you would always write to even addresses while the register view would read the contents of odd addresses in the QSPI RAM.&lt;BR /&gt;&lt;BR /&gt;If you really need to know the contents of the QSPI RAM I would suggest the following (haven't tried it since I brought up my module with a scope and a lot of printf's ... &lt;IMG alt="Smiley Happy" class="emoticon emoticon-smileyhappy" id="smileyhappy" src="https://community.nxp.com/i/smilies/16x16_smiley-happy.png" title="Smiley Happy" /&gt; &lt;SPAN class="lia-unicode-emoji" title=":disappointed_face:"&gt;&lt;LI-EMOJI id="lia_disappointed-face" title=":disappointed_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE&gt;
my_qspiram_readfunction()
{
  U16 ram[RAM_LENGTH];
  U16 save_qar;

  save_qar = QAR;
  QAR      = 0x20;
  for(i=0; i .LT. 0x10; ++i) ram[i] = QDR;
  QAR      = save_QAR;
}
&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;You could then insert this function wherever you want to know the contents of the QSPI RAM.&lt;BR /&gt;HTH&lt;BR /&gt;stzari&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Nov 2020 14:45:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132121#M1067</guid>
      <dc:creator>stzari</dc:creator>
      <dc:date>2020-11-02T14:45:31Z</dc:date>
    </item>
    <item>
      <title>Re: Strange thing about the QSPI module in MCF5235</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132122#M1068</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi stzari,&lt;BR /&gt;&lt;BR /&gt;Thank you for your answer, I've tried your function but I've got only zeros...that means I haven't written in the command RAM registers at all &lt;IMG alt=":smileysad:" class="emoticon emoticon-smileysad" id="smileysad" src="http://freescale.i.lithium.com/i/smilies/16x16_smiley-sad.gif" title="Smiley Sad" /&gt;&lt;BR /&gt;&lt;BR /&gt;I'll put my function here perhaps there's something that is missing.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Oct 2006 19:43:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132122#M1068</guid>
      <dc:creator>Ivychacha</dc:creator>
      <dc:date>2006-10-05T19:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: Strange thing about the QSPI module in MCF5235</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132123#M1069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;To correct what I've said, now I manage to view something other than 0 in the command RAM registers, but instead of what I've put with QDR, I got somme 0xFF.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Oct 2006 21:31:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132123#M1069</guid>
      <dc:creator>Ivychacha</dc:creator>
      <dc:date>2006-10-05T21:31:22Z</dc:date>
    </item>
    <item>
      <title>Re: Strange thing about the QSPI module in MCF5235</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132124#M1070</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hello,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;For information,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;QSPI Transmit RAM (0x00-0x0F) is WRITE ONLY,&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;QSPI&amp;nbsp;Receive RAM (0x10-0x1F) is READ ONLY,&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;QSPI&amp;nbsp;Command RAM (0x20-0x2F) is WRITE ONLY.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Bye&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Oct 2006 00:43:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132124#M1070</guid>
      <dc:creator>Arev</dc:creator>
      <dc:date>2006-10-06T00:43:17Z</dc:date>
    </item>
    <item>
      <title>Re: Strange thing about the QSPI module in MCF5235</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132125#M1071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;i'll resume the answer of my own question:&lt;BR /&gt;&lt;BR /&gt;it's not a good idea to work with the spi without a scope &lt;IMG alt=":smileyvery-happy:" class="emoticon emoticon-smileyvery-happy" id="smileyvery-happy" src="http://freescale.i.lithium.com/i/smilies/16x16_smiley-very-happy.gif" title="Smiley Very Happy" /&gt; because the register view gives an extra access to the QDR and that disturbes the program running normally.&lt;BR /&gt;&lt;BR /&gt;also, we can't see what's inside the QCR because it's not readable by the user (thanks arev).&lt;BR /&gt;&lt;BR /&gt;so the best way: get a scope &lt;IMG alt=":smileyvery-happy:" class="emoticon emoticon-smileyvery-happy" id="smileyvery-happy" src="http://freescale.i.lithium.com/i/smilies/16x16_smiley-very-happy.gif" title="Smiley Very Happy" /&gt;&lt;BR /&gt;&lt;BR /&gt;i'll put here my code, it's for the spi-eeprom st95640w. hope it will help those who need.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Oct 2006 15:45:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Strange-thing-about-the-QSPI-module-in-MCF5235/m-p/132125#M1071</guid>
      <dc:creator>Ivychacha</dc:creator>
      <dc:date>2006-10-13T15:45:03Z</dc:date>
    </item>
  </channel>
</rss>

