<?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 MPC5675 EBI application issue in MPC5xxx</title>
    <link>https://community.nxp.com/t5/MPC5xxx/MPC5675-EBI-application-issue/m-p/1770292#M24596</link>
    <description>&lt;P&gt;in our EBI application, we only used these low address pins (A27-A31), so we have designed the other unused addr pins as GPIO function.&amp;nbsp;&lt;/P&gt;&lt;P&gt;so, in our software, we configured the EBI addr pins A27-A31 as EBI function, while A8-A26 as GPIO function.&amp;nbsp;&lt;/P&gt;&lt;P&gt;the problem is that it would lead to a address-access-error-liking exception when CPU want to operate a EBI reading/writing. to fix this problem, i tried to configure all EBI addr pins as EBI function, and the issue got solved, meanwhile, the GPIO function can not work.&lt;/P&gt;&lt;P&gt;in our EBI usage, we only used a small number of addr pins, if the other ADDR pins can not be used as other functions, the pin resourse would get very strained.&amp;nbsp;&lt;/P&gt;&lt;P&gt;can anybody help me with this problem?&lt;/P&gt;&lt;P&gt;thanks a lot.&lt;/P&gt;</description>
    <pubDate>Thu, 07 Dec 2023 01:51:23 GMT</pubDate>
    <dc:creator>GaoYuann</dc:creator>
    <dc:date>2023-12-07T01:51:23Z</dc:date>
    <item>
      <title>MPC5675 EBI application issue</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC5675-EBI-application-issue/m-p/1770292#M24596</link>
      <description>&lt;P&gt;in our EBI application, we only used these low address pins (A27-A31), so we have designed the other unused addr pins as GPIO function.&amp;nbsp;&lt;/P&gt;&lt;P&gt;so, in our software, we configured the EBI addr pins A27-A31 as EBI function, while A8-A26 as GPIO function.&amp;nbsp;&lt;/P&gt;&lt;P&gt;the problem is that it would lead to a address-access-error-liking exception when CPU want to operate a EBI reading/writing. to fix this problem, i tried to configure all EBI addr pins as EBI function, and the issue got solved, meanwhile, the GPIO function can not work.&lt;/P&gt;&lt;P&gt;in our EBI usage, we only used a small number of addr pins, if the other ADDR pins can not be used as other functions, the pin resourse would get very strained.&amp;nbsp;&lt;/P&gt;&lt;P&gt;can anybody help me with this problem?&lt;/P&gt;&lt;P&gt;thanks a lot.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2023 01:51:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC5675-EBI-application-issue/m-p/1770292#M24596</guid>
      <dc:creator>GaoYuann</dc:creator>
      <dc:date>2023-12-07T01:51:23Z</dc:date>
    </item>
    <item>
      <title>Re: MPC5675 EBI application issue</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC5675-EBI-application-issue/m-p/1770889#M24599</link>
      <description>&lt;P&gt;If you are using 8-bit data bus, this would be correct setting. However there are also data pins that is needed to use (can also be muxed with addresses).&lt;/P&gt;
&lt;P&gt;Following signals are also routed to he same pins where adx is either address/data or data and addx are address lines only.&lt;BR /&gt;&lt;BR /&gt;ad8-add24&lt;BR /&gt;ad9-add25&lt;BR /&gt;ad10-add26&lt;BR /&gt;ad11-add27&lt;BR /&gt;ad12-add28&lt;BR /&gt;ad13-add29&lt;BR /&gt;ad14-add30&lt;BR /&gt;ad15-add31&lt;/P&gt;
&lt;P&gt;Pay attention to DBM bit in EBI_MCR. Only pins that are not used for any EBI purpose may be used as GPIO.&lt;/P&gt;
&lt;P&gt;Could you show me you connection schematic (only EBI pins and memory)?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2023 15:49:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC5675-EBI-application-issue/m-p/1770889#M24599</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-12-07T15:49:24Z</dc:date>
    </item>
    <item>
      <title>Re: MPC5675 EBI application issue</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC5675-EBI-application-issue/m-p/1771367#M24601</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="GaoYuann_1-1702018229955.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/253552iF1E64E7ECCB1E06F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="GaoYuann_1-1702018229955.png" alt="GaoYuann_1-1702018229955.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks，david.&lt;/P&gt;&lt;P&gt;here is our EBI application schematic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Dec 2023 06:54:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC5675-EBI-application-issue/m-p/1771367#M24601</guid>
      <dc:creator>GaoYuann</dc:creator>
      <dc:date>2023-12-08T06:54:59Z</dc:date>
    </item>
  </channel>
</rss>

