<?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>MQX Software SolutionsのトピックRe: MQX_ROM_VECTORS</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-ROM-VECTORS/m-p/187679#M3411</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Master_szumi,&lt;/P&gt;&lt;P&gt;It depends on how the application is implementing the interrupts.&amp;nbsp; MQX can build a interrupt table so that the MQX master inerrupt routine can determine if a valid user interrupt was registered and then jump to it.&amp;nbsp; Interrupts can be setup such that they are added directly to the vector table so if the vector table is in RAM is would be different from the ROM version.&amp;nbsp; But in general it should be mostly the same.&lt;/P&gt;&lt;P&gt;Read up on the various interrupt registering methods in the MQXUG.pdf in the MQX/doc/mqx path/ called "Handling Interrupts and Exceptions".&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Dec 2011 22:45:49 GMT</pubDate>
    <dc:creator>DavidS</dc:creator>
    <dc:date>2011-12-05T22:45:49Z</dc:date>
    <item>
      <title>MQX_ROM_VECTORS</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-ROM-VECTORS/m-p/187678#M3410</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I definied MQX_ROM_VECTORS = 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;after execute my mqx project I stopped in debugger and look into memory.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rom vector (at adress 0x0) is different than ram vector (at start of ram).&lt;/P&gt;&lt;P&gt;They shouldnt be the same?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Dec 2011 23:04:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-ROM-VECTORS/m-p/187678#M3410</guid>
      <dc:creator>master_szumi</dc:creator>
      <dc:date>2011-12-02T23:04:16Z</dc:date>
    </item>
    <item>
      <title>Re: MQX_ROM_VECTORS</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-ROM-VECTORS/m-p/187679#M3411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Master_szumi,&lt;/P&gt;&lt;P&gt;It depends on how the application is implementing the interrupts.&amp;nbsp; MQX can build a interrupt table so that the MQX master inerrupt routine can determine if a valid user interrupt was registered and then jump to it.&amp;nbsp; Interrupts can be setup such that they are added directly to the vector table so if the vector table is in RAM is would be different from the ROM version.&amp;nbsp; But in general it should be mostly the same.&lt;/P&gt;&lt;P&gt;Read up on the various interrupt registering methods in the MQXUG.pdf in the MQX/doc/mqx path/ called "Handling Interrupts and Exceptions".&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Dec 2011 22:45:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-ROM-VECTORS/m-p/187679#M3411</guid>
      <dc:creator>DavidS</dc:creator>
      <dc:date>2011-12-05T22:45:49Z</dc:date>
    </item>
  </channel>
</rss>

