ULINK: HEX PROGRAMMING APPENDS .AXF?

Information in this knowledgebase article applies to:

• MDK-ARM Version 4.13a

SYMPTOM

After upgrading to V4.13a, when using µVision 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

• Refer to HEX Files in the µVision User's Guide.
• Refer to Creating Functions in the µVision4 User's Guide.

SEE ALSO

• ULINK: USING ULINK AS A DEVICE PROGRAMMER

FORUM THREADS

The following Discussion Forum threads may provide information related to this topic.

• flashing hex file to 2478 using keil

Last Reviewed: Wednesday, November 24, 2010