<?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 CODE analysis in OSBDM and TBDML</title>
    <link>https://community.nxp.com/t5/OSBDM-and-TBDML/CODE-analysis/m-p/163052#M990</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;HI ... i have tryed to analysed&amp;nbsp; code of usbdm V4.6 for jm60 but i am not able to understand some of them please help me in this the codes sentance which i have not understood are&amp;nbsp; #pragma DATA_SEG DEFAULT﻿&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#if (DEBUG&amp;amp;RESET_DEBUG)---------------------------------------------------------not understood&lt;BR /&gt;&amp;nbsp;&amp;nbsp; DEBUG_PIN&amp;nbsp;&amp;nbsp; = 1;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; DEBUG_PIN&amp;nbsp;&amp;nbsp; = 0;&lt;BR /&gt;#endif---------------------------------------------------------not understood﻿&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; if (RESET_IN==0)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; // RESET failed to rise&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; return(BDM_RC_RESET_TIMEOUT_RISE);&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; CLEAR_RESET_SENSE_FLAG(); // Clear RESET IC Event&lt;BR /&gt;&amp;nbsp;&amp;nbsp; ENABLE_RESET_SENSE_INT(); // Enable RESET IC interrupts&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; return(BDM_RC_OK);&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;#endif //(HW_CAPABILITY&amp;amp;CAP_RST_IO)---------------------------------------------------------not understood﻿&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;#if (DEBUG&amp;amp;SYNC_DEBUG))---------------------------------------------------------not understood﻿﻿&lt;BR /&gt;&amp;nbsp;&amp;nbsp; DEBUG_PIN&amp;nbsp;&amp;nbsp; = 1;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; DEBUG_PIN&amp;nbsp;&amp;nbsp; = 0;&lt;BR /&gt;#end﻿﻿)---------------------------------------------------------not understood﻿﻿&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#pragma MESSAGE DEFAULT C4003﻿&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>Tue, 30 Aug 2011 12:06:43 GMT</pubDate>
    <dc:creator>usbdmjm60</dc:creator>
    <dc:date>2011-08-30T12:06:43Z</dc:date>
    <item>
      <title>CODE analysis</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/CODE-analysis/m-p/163052#M990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;HI ... i have tryed to analysed&amp;nbsp; code of usbdm V4.6 for jm60 but i am not able to understand some of them please help me in this the codes sentance which i have not understood are&amp;nbsp; #pragma DATA_SEG DEFAULT﻿&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#if (DEBUG&amp;amp;RESET_DEBUG)---------------------------------------------------------not understood&lt;BR /&gt;&amp;nbsp;&amp;nbsp; DEBUG_PIN&amp;nbsp;&amp;nbsp; = 1;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; DEBUG_PIN&amp;nbsp;&amp;nbsp; = 0;&lt;BR /&gt;#endif---------------------------------------------------------not understood﻿&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; if (RESET_IN==0)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; // RESET failed to rise&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; return(BDM_RC_RESET_TIMEOUT_RISE);&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; CLEAR_RESET_SENSE_FLAG(); // Clear RESET IC Event&lt;BR /&gt;&amp;nbsp;&amp;nbsp; ENABLE_RESET_SENSE_INT(); // Enable RESET IC interrupts&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; return(BDM_RC_OK);&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;#endif //(HW_CAPABILITY&amp;amp;CAP_RST_IO)---------------------------------------------------------not understood﻿&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;#if (DEBUG&amp;amp;SYNC_DEBUG))---------------------------------------------------------not understood﻿﻿&lt;BR /&gt;&amp;nbsp;&amp;nbsp; DEBUG_PIN&amp;nbsp;&amp;nbsp; = 1;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; DEBUG_PIN&amp;nbsp;&amp;nbsp; = 0;&lt;BR /&gt;#end﻿﻿)---------------------------------------------------------not understood﻿﻿&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#pragma MESSAGE DEFAULT C4003﻿&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>Tue, 30 Aug 2011 12:06:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/CODE-analysis/m-p/163052#M990</guid>
      <dc:creator>usbdmjm60</dc:creator>
      <dc:date>2011-08-30T12:06:43Z</dc:date>
    </item>
    <item>
      <title>Re: CODE analysis</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/CODE-analysis/m-p/163053#M991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some description:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;#if (DEBUG&amp;amp;RESET_DEBUG)-&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;There is a #defined constant &lt;STRONG&gt;DEBUG&lt;/STRONG&gt; which is used to control various debug features in the code.&amp;nbsp; It is a bit vector with each bit representing a different debug feature.&amp;nbsp; These are used to control condition code generation and would usually be disabled in the release version (by setting &lt;STRONG&gt;DEBUG&lt;/STRONG&gt; to 0)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;HW_CAPABILITY&lt;/STRONG&gt;&amp;amp;&lt;STRONG&gt;CAP_RST_IO﻿&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The same code is used to build for various versions of the hardware.&amp;nbsp; These have different features which are controlled by&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;STRONG&gt;HW_CAPABILITY&lt;/STRONG&gt;﻿ bit vector in a similar fashion to above.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you are having trouble understanding &lt;STRONG&gt;#if&lt;/STRONG&gt; in general you would be advised to have a look at almost any C programming book for a discussion of preprocessing macros etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;#pragma DATA_SEG&amp;nbsp; ....&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;This controls in which segment data are allocated.&amp;nbsp; This is specific to the Codewarrior C compiler.&amp;nbsp; More information can be found in the Codewarrior help files.&amp;nbsp; The USBDM uses it mostly to control BOOT area code &amp;amp; data along with making sure some critical data is allocated in the near segment for fast access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;bye&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Aug 2011 09:58:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/CODE-analysis/m-p/163053#M991</guid>
      <dc:creator>pgo</dc:creator>
      <dc:date>2011-08-31T09:58:51Z</dc:date>
    </item>
  </channel>
</rss>

