ARM Technical Support Knowledge Articles

HEX PROGRAMMING APPENDS .AXF?

Applies to: ULINK USB-JTAG Debugger

Answer


Information in this knowledgebase article applies to:


SYMPTOM

After upgrading to V4.13a, when using uVision as a hex file programmer, the .AXF extension is always appended to the name of the .HEX file (e.g. Blinky.HEX.AXF). This did not happen in previous MDK-ARM versions.

CAUSE

This is a known issue in MDK-ARM V4.13a.

RESOLUTION

For a workaround, do the following:

  1. Use the Function Editor to write a small, 1-line ".INI" script file that loads the HEX file for you. For example:
    Load "C:\\Keil\\ARM\\Boards\\Keil\\MCB1700\\LCD_Blinky\\Flash\\Blinky.HEX"
    
  2. Add the name of your script file to the Init File text box in in Options for Target — Utilities.
  3. Uncheck Load Application at Startup in Options for Target — Debug.

STATUS

This will be corrected in the next MDK-ARM release.

MORE INFORMATION

SEE ALSO

ATTACHED FILES

Request the files attached to this knowledgebase article.

Article last edited on: 2010-11-24 09:14:07

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