<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Why the address of fuction printed is not same as the one mentioned in map file</title><link>https://community.arm.com/developer/ip-products/processors/f/cortex-m-forum/48094/why-the-address-of-fuction-printed-is-not-same-as-the-one-mentioned-in-map-file</link><description> In Cortex-M7,Why the address of fuction printed is not same as the one mentioned in map file. 
 i.e, My function address is 0x00473dbc in map fle, but it is diffrent, if we print it in my program. 
 </description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Why the address of fuction printed is not same as the one mentioned in map file</title><link>https://community.arm.com/thread/168930?ContentTypeID=1</link><pubDate>Wed, 02 Dec 2020 17:27:13 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:db87761d-c251-459b-8dd3-8828214fc41c</guid><dc:creator>42Bastian Schick</dc:creator><description>&lt;p&gt;Ouch, yes. :(&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the address of fuction printed is not same as the one mentioned in map file</title><link>https://community.arm.com/thread/168919?ContentTypeID=1</link><pubDate>Wed, 02 Dec 2020 13:24:37 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:e4fda3b6-c529-4b9c-b805-b9ff24a48e1d</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;If you look at it in a debugger, what address do you see ?&lt;/p&gt;
&lt;p&gt;To print a pointer, shouldn&amp;#39;t you be using &lt;strong&gt;%p&lt;/strong&gt; ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the address of fuction printed is not same as the one mentioned in map file</title><link>https://community.arm.com/thread/168911?ContentTypeID=1</link><pubDate>Wed, 02 Dec 2020 02:46:47 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:fa716951-5c8e-4ade-bc2d-653112be8367</guid><dc:creator>Bill Westfeild</dc:creator><description>&lt;p&gt;Could be a typo, but those two values differ by more than bit 0...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the address of fuction printed is not same as the one mentioned in map file</title><link>https://community.arm.com/thread/168754?ContentTypeID=1</link><pubDate>Mon, 23 Nov 2020 05:25:08 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f595d1de-6833-475c-81c2-e8d61ff710d8</guid><dc:creator>Gopu</dc:creator><description>&lt;p&gt;Thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the address of fuction printed is not same as the one mentioned in map file</title><link>https://community.arm.com/thread/168745?ContentTypeID=1</link><pubDate>Sat, 21 Nov 2020 05:24:25 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:bfeb687c-9672-49aa-a58b-95ce1bf67061</guid><dc:creator>42Bastian Schick</dc:creator><description>&lt;p&gt;Check out the Thumb-2 description. It explains, why bit 0 is set.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the address of fuction printed is not same as the one mentioned in map file</title><link>https://community.arm.com/thread/168744?ContentTypeID=1</link><pubDate>Sat, 21 Nov 2020 01:17:14 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:734bd6d1-9f45-4027-a84b-f8d08a392305</guid><dc:creator>Gopu</dc:creator><description>&lt;p&gt;Hardware used is SAMv70 from Microchip.&lt;/p&gt;
&lt;p&gt;From Map file address of the function &amp;quot;VhicDebugUartInit&amp;quot; is &amp;quot;0x00473dbc&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt; .ARM.exidx.text.VhicDebugUartInit&lt;br /&gt; 0x00473dbc 0x10 obj/gnu/release/ccuvhicdebug.o&lt;br /&gt; 0x8 (size before relaxing)&lt;/p&gt;
&lt;p&gt;If we print the address of the function in the program, it is &amp;quot;0x00473DCB&amp;quot;&lt;/p&gt;
&lt;p&gt;printf(&amp;quot;VhicDebugUartInit at 0x%x&amp;quot;, VhicDebugUartInit);&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the address of fuction printed is not same as the one mentioned in map file</title><link>https://community.arm.com/thread/168743?ContentTypeID=1</link><pubDate>Sat, 21 Nov 2020 01:16:48 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:e96833cd-6918-4a73-a1c2-a6c2157683db</guid><dc:creator>Gopu</dc:creator><description>&lt;p&gt;Thank you for looking into this. KIndly find more information as follows&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Hardware used is SAMv70 from Microchip.&lt;/p&gt;
&lt;p&gt;From Map file address of the function &amp;quot;VhicDebugUartInit&amp;quot; is &amp;quot;0x00473dbc&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt; .ARM.exidx.text.VhicDebugUartInit&lt;br /&gt; 0x00473dbc 0x10 obj/gnu/release/ccuvhicdebug.o&lt;br /&gt; 0x8 (size before relaxing)&lt;/p&gt;
&lt;p&gt;If we print the address of the function in the program, it is &amp;quot;0x00473DCB&amp;quot;&lt;/p&gt;
&lt;p&gt;printf(&amp;quot;VhicDebugUartInit at 0x%x&amp;quot;, VhicDebugUartInit);&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the address of fuction printed is not same as the one mentioned in map file</title><link>https://community.arm.com/thread/168741?ContentTypeID=1</link><pubDate>Fri, 20 Nov 2020 20:12:05 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f8dd180e-9e9a-458d-9041-9fa17f2f09c7</guid><dc:creator>42Bastian Schick</dc:creator><description>&lt;p&gt;Maybe you give us all the information? Not just the half.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>