<?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>ADUC832 with C51 9.52 version .axf not generated</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/32369/aduc832-with-c51-9-52-version-axf-not-generated</link><description> 
Hello, 

 
We are using ADUC832 on one of our development project. We
have downloaded and installed C51 9.52 version to compile. But
the compiler is not generating .axf file after build. We
written a sample code to toggle LED ( connected to GPIO). </description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: ADUC832 with C51 9.52 version .axf not generated</title><link>https://community.arm.com/thread/81679?ContentTypeID=1</link><pubDate>Mon, 27 Jan 2014 20:43:26 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f6374860-7b43-42e2-b225-6500029170de</guid><dc:creator>eswar g</dc:creator><description>&lt;p&gt;&lt;p&gt;
We have a file with no extention. We&amp;#39;ll try this.&lt;/p&gt;

&lt;p&gt;
Thanks for reply and support.&lt;/p&gt;

&lt;p&gt;
~Eswar&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ADUC832 with C51 9.52 version .axf not generated</title><link>https://community.arm.com/thread/120234?ContentTypeID=1</link><pubDate>Mon, 27 Jan 2014 20:42:09 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:81764727-9532-4f7c-8a65-ba999487d846</guid><dc:creator>eswar g</dc:creator><description>&lt;p&gt;&lt;p&gt;
We are using wsd.exe from AD website. is is accepting HEX file as
input. We&amp;#39;ll try to load and getback with results....&lt;/p&gt;

&lt;p&gt;
Thanks For the reply.&lt;/p&gt;

&lt;p&gt;
Thank You&lt;br /&gt;
Eswar&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ADUC832 with C51 9.52 version .axf not generated</title><link>https://community.arm.com/thread/62525?ContentTypeID=1</link><pubDate>Mon, 27 Jan 2014 13:46:22 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:42e13cb7-1e65-4c20-9328-10bfc6dd02a4</guid><dc:creator>HansBernhard Broeker</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;But the compiler is not generating .axf file after
build.&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
It would be awfully strange if it did, given &amp;#39;axf&amp;#39; rather
obviously stands for something along the lines of &amp;quot;&lt;b&gt;ARM&lt;/b&gt;
Executable File&amp;quot; ;-&amp;gt; Clearly neither your &amp;#39;51 itself nor any of
the Keil tools you&amp;#39;re using for it would have the slightest idea what
to do with a file in that format.&lt;/p&gt;

&lt;p&gt;
What you&amp;#39;ve been caught by is that Keil, a very long time ago,
opted to use &lt;b&gt;no extension whatsoever&lt;/b&gt; for the default linker
output file in its &amp;#39;51 tools. I.e. if your program is called &amp;quot;Foo&amp;quot; in
the uVision project, the default output file is actually called just
that: &amp;quot;Foo&amp;quot;, without any filename extension. Particularly if you&amp;#39;ve
forgot to turn Windows Explorer&amp;#39;s (spectacularly idiotic) default
option &amp;quot;Hide extensions for known file types&amp;quot; off, this file can be
hard to notice in the project directory.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ADUC832 with C51 9.52 version .axf not generated</title><link>https://community.arm.com/thread/107481?ContentTypeID=1</link><pubDate>Mon, 27 Jan 2014 11:23:26 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:b00aea43-9ad5-4194-bd92-d8c12e62d92d</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
8051 is a very different, and very much older, architecture than
ARM - as laready noted, there isn&amp;#39;t really much reason at all to
assume that they will be in any way similar.&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;&amp;quot;is .HEX file supports by ADUc832?&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
A processor neither knows nor cares anything about file formats -
it&amp;#39;s a matter for the programming tool, not the chip.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ADUC832 with C51 9.52 version .axf not generated</title><link>https://community.arm.com/thread/118467?ContentTypeID=1</link><pubDate>Mon, 27 Jan 2014 02:23:24 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:8a8bfd90-4ea6-49e9-a175-d3d7867a97ef</guid><dc:creator>Westonsupermare Pier</dc:creator><description>&lt;p&gt;&lt;p&gt;
As a casual observer AXF is a very ARM centric format. 8051s
almost certainly want BIN or HEX files. What does your device
programming tool expect? What other types of files are in your output
directory?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ADUC832 with C51 9.52 version .axf not generated</title><link>https://community.arm.com/thread/81678?ContentTypeID=1</link><pubDate>Sun, 26 Jan 2014 22:33:27 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:eddf43cb-4bec-482c-8c19-bc8227fb5f1f</guid><dc:creator>eswar g</dc:creator><description>&lt;p&gt;&lt;p&gt;
Thank you for the immediate reply...&lt;/p&gt;

&lt;p&gt;
.HEX is generating if once we enabled Hex o/p on compiler
configuration. But is .HEX file supports by ADUc832?&lt;/p&gt;

&lt;p&gt;
Upto now we have used KeilU3 with LPC3250 and generated .axf file.
So we are under same impression that the o/p file will be in the form
of .axf and we have to convert into bin using fromelf.exe&lt;/p&gt;

&lt;p&gt;
Is .Hex file is ok to download?&lt;/p&gt;

&lt;p&gt;
Thank You&lt;br /&gt;
Eswar&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>