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

BIN file instead of Hexb

Is there a way in Uvision3 to obtain a .bin file instead of the .hex file, as the executable file format?

Parents
  • "It does not compile the file because not enough arguments errors."

    Again, note that HEX2BIN has nothing to do with compiling - it runs after the compiler (and assembler, and linker) have all done their jobs!

    Then you need to supply all the necessary arguments - that's an input file name & an output file name at the minimum.

    See the HEX2BIN documentation for a description of the required arguments & options;
    See the uVision Manual for details of how to supply arguments to utilities like this - In particular look at the section on Key Sequences for Tool PArameters.

    Application Note 159 illustrates the use of Key sequences (it's for a Triscend E5, but the principles remain the same):
    http://www.keil.com/appnotes/files/apnt_159.pdf

Reply
  • "It does not compile the file because not enough arguments errors."

    Again, note that HEX2BIN has nothing to do with compiling - it runs after the compiler (and assembler, and linker) have all done their jobs!

    Then you need to supply all the necessary arguments - that's an input file name & an output file name at the minimum.

    See the HEX2BIN documentation for a description of the required arguments & options;
    See the uVision Manual for details of how to supply arguments to utilities like this - In particular look at the section on Key Sequences for Tool PArameters.

    Application Note 159 illustrates the use of Key sequences (it's for a Triscend E5, but the principles remain the same):
    http://www.keil.com/appnotes/files/apnt_159.pdf

Children
No data