ARM Technical Support Knowledge Articles

HEX FILE NOT CREATED MESSAGE

Applies to: uVision (Version 1) IDE

Answer


Information in this article applies to:


QUESTION

In the C166 tools, I configure uVision to run the L166 Linker and the OH166 HEX Converter after building my project. The linker runs OK but the HEX file is never created and uVision Reports, "HEX File Not Created." What's wrong?

ANSWER

Check the path where you installed the C166 toolset. If one of the directory names has more than 8 characters, OH166 will not work. For example, if you installed the C166 compiler under "C:PROGRAMFILESKEILC166", the OH166 HEX Converter will not work. You must re-install the tools under a different directory name like, "C:KEILC166".

Article last edited on: 2004-05-16 17:15:40

Rate this article

[Bad]
|
|
[Good]
Disagree? Move your mouse over the bar and click

Did you find this article helpful? Yes No

How can we improve this article?

Link to this article
Copyright © 2011 ARM Limited. All rights reserved. External (Open), Non-Confidential