<?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: Exception handling</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Exception-handling/m-p/141244#M2396</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;You could move your ram and flash (internal and external) and IO's out of the bottom of the memory space and then assign an unused chip select to zero, with write protect (read-only). You could also do it with an unused ACRx (cache controller). Null-pointer assigment would result in an access error exception (interrupt vector 2) in both cases. If you also want to trap null pointer de-referencing, don't assign any chip select to the zero range.&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Jun 2006 01:01:45 GMT</pubDate>
    <dc:creator>mvincent</dc:creator>
    <dc:date>2006-06-29T01:01:45Z</dc:date>
    <item>
      <title>Exception handling</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Exception-handling/m-p/141243#M2395</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi,&lt;/DIV&gt;&lt;DIV&gt;i am working on mcf5282, and i am tring to implement the exception for NULL pointer assignment using chip select module,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;can anybody suggest me what is the other way to implement it,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;thanx,&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Jun 2006 12:43:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Exception-handling/m-p/141243#M2395</guid>
      <dc:creator>pass</dc:creator>
      <dc:date>2006-06-28T12:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: Exception handling</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Exception-handling/m-p/141244#M2396</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;You could move your ram and flash (internal and external) and IO's out of the bottom of the memory space and then assign an unused chip select to zero, with write protect (read-only). You could also do it with an unused ACRx (cache controller). Null-pointer assigment would result in an access error exception (interrupt vector 2) in both cases. If you also want to trap null pointer de-referencing, don't assign any chip select to the zero range.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Jun 2006 01:01:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Exception-handling/m-p/141244#M2396</guid>
      <dc:creator>mvincent</dc:creator>
      <dc:date>2006-06-29T01:01:45Z</dc:date>
    </item>
    <item>
      <title>Re: Exception handling</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Exception-handling/m-p/141245#M2397</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I think you can also program the BDM to trap an access to a specific memory location, but this might interfere with BDM debugging.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Jun 2006 01:06:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Exception-handling/m-p/141245#M2397</guid>
      <dc:creator>mvincent</dc:creator>
      <dc:date>2006-06-29T01:06:17Z</dc:date>
    </item>
  </channel>
</rss>

