This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ADUC832 with C51 9.52 version .axf not generated

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).

Is there any problem with settings?

How to generate executable file with compiler?

*We are using default settings which came from installation.

Thank You
Eswar

  • Thank you for the immediate reply...

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

    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

    Is .Hex file is ok to download?

    Thank You
    Eswar

  • 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?

  • 8051 is a very different, and very much older, architecture than ARM - as laready noted, there isn't really much reason at all to assume that they will be in any way similar.

    "is .HEX file supports by ADUc832?"

    A processor neither knows nor cares anything about file formats - it's a matter for the programming tool, not the chip.

  • But the compiler is not generating .axf file after build.

    It would be awfully strange if it did, given 'axf' rather obviously stands for something along the lines of "ARM Executable File" ;-> Clearly neither your '51 itself nor any of the Keil tools you're using for it would have the slightest idea what to do with a file in that format.

    What you've been caught by is that Keil, a very long time ago, opted to use no extension whatsoever for the default linker output file in its '51 tools. I.e. if your program is called "Foo" in the uVision project, the default output file is actually called just that: "Foo", without any filename extension. Particularly if you've forgot to turn Windows Explorer's (spectacularly idiotic) default option "Hide extensions for known file types" off, this file can be hard to notice in the project directory.

  • We are using wsd.exe from AD website. is is accepting HEX file as input. We'll try to load and getback with results....

    Thanks For the reply.

    Thank You
    Eswar

  • We have a file with no extention. We'll try this.

    Thanks for reply and support.

    ~Eswar