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

Is there any way to add a resource file or version number to a hex file

Hi,

I am compiling my firmware (hex) files using uVison2 and I was wondering is there any way to add a version number or resource file to this project so that when I right click on them in a windows environment that I can see version number or other information as I can do if I create a windows dll.

Thanks

  • Compile and link in debug mode. Have a label that changes with (includes) the revision. The loaders will ignore the debug info, but you can find it in the file.

    As to locating it in the same place every time, I have no idea.

    Erik

  • Windows has not the slightest idea what a .hex file is. Thus, no way of displaying any additional information about it without changing Windows itself --- nothing you do to a .hex file can possibly have any effect. The thing you're looking for is called an "explorer extension" for Windows.

    This has essentially nothing to do with Keil tools.

  • There's a Revision Number field as part of the standard Windows meta-data. (Right-mouse on a file, and see file Properties / Summary / Advanced.) You could set this field (a WSH script can no doubt do it, if only you can wade through the object model documentation to find out how to set a file property) Then find a shell extension to let you view it more easily than drilling down three clicks.

    I poked around a bit in Google and found too many choices. The first one I looked at was in German; the next couple integrated version control directly into Windows Explorer. There's probably already one out there if you search.

  • There's a Revision Number field as part of the standard Windows meta-data.

    Close, but no cigar. Those meta-data only exist for files stored on NTFS drives. This means it's not really a standard Windows feature. Among other things, these meta-data get lost as soon as you transfer the file in any way that involves a non-NTFS file system, which severely limits their applicability to the problem at hand.

  • Thanks for all the replies folks.
    Much appreciated.