<?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>JTAG uploaded code vs. IAP code from ELF binary</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/29676/jtag-uploaded-code-vs-iap-code-from-elf-binary</link><description> 
My binary code file produced by Keil&amp;#39;s ELF tool has about 320
bytes more than the &amp;#39;same&amp;#39; JTAG upload code file. It looks like the
last 320 bytes are the same as the previous 320 in the binary file.
i.e. From 0 to 0x34DCB, both JTAG uploaded file (CPU</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: JTAG uploaded code vs. IAP code from ELF binary</title><link>https://community.arm.com/thread/105357?ContentTypeID=1</link><pubDate>Thu, 13 Oct 2011 09:00:18 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:8552f69a-4e29-4515-a42e-35677065201d</guid><dc:creator>@Marc Crandall</dc:creator><description>&lt;p&gt;&lt;p&gt;
As far as I know there should be no difference as to what is
programmed into the flash.&lt;/p&gt;

&lt;p&gt;
Of course when using the debugger interface of uVision with a JTAG
there may be some initialization code that is run?&lt;/p&gt;

&lt;p&gt;
Also what micro are you using? Are you modifying the CRP? Are you
writing to the entire flash from IAP? If so is the code that writes
to the flash executing from RAM?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JTAG uploaded code vs. IAP code from ELF binary</title><link>https://community.arm.com/thread/91276?ContentTypeID=1</link><pubDate>Thu, 13 Oct 2011 08:54:57 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:1aa95b06-cbb3-464c-9b34-84f8fe301f60</guid><dc:creator>Sutton Mehaffey</dc:creator><description>&lt;p&gt;&lt;p&gt;
I am using the &amp;#39;FROMELF&amp;#39; tool to generate the binary file from a
.AXF file. That binary file is uploaded using IAP into CPU Flash.
However, the JTAG upload is different. Because sometimes my automatic
upload process hangs upon CPU restart (but is fixed by uploading the
same code via JTAG), I&amp;#39;m trying to understand the difference between
the JTAG upload and the IAP upload of the binary file.&lt;/p&gt;

&lt;p&gt;
Sutton&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JTAG uploaded code vs. IAP code from ELF binary</title><link>https://community.arm.com/thread/59928?ContentTypeID=1</link><pubDate>Thu, 13 Oct 2011 08:46:42 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:b5c1d20b-fa8a-486f-a744-a193349913ee</guid><dc:creator>@Marc Crandall</dc:creator><description>&lt;p&gt;&lt;p&gt;
I&amp;#39;m not sure if I fully got your post but the ELF file is not the
same as the bin (binary file).&lt;/p&gt;

&lt;p&gt;
The ELF file contains extra information such as the location of
where to load the code.&lt;/p&gt;

&lt;p&gt;
There is a tools called fromelf that converts ELF files to binary
files that could be used for firmware upgrades using IAP.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>