Keil Logo

µVISION: How to generate a build log file


Information in this knowledgebase article applies to:

  • µVision IDE
  • MDK-ARM

QUESTION

I have some compiler and linker issues during a project build, which requires helps from Keil support team. Can I generate any kind of build log files from the µVision license management process, which I can forward to the Keil support team to provide more details of the issue?

BACKGROUND INFORMATION

There are many benefits to using a build log:

ARM: How to archive your MDK project: include the full build log with the project code when archiving the project code. Since the full build log records the software pack versions and file versions used in a project, it self documents what is needed to recreate this project.

µVision: Using different versions of the ARM Compiler: The build log shows which compiler and libraries were used. There can be multiple compilers loaded in µVision, and this file shows the one used to make the project.

Record the last build output: the full build log also lists all the warning messages in the last build. If a project gets checked in with warnings, see the last build output will greatly benefit future programmers that need to edit this code. Those programmers will not waste time solving warnings that can be ignored.

Avoid future Licensing Errors: the build log lists the type of license used to make this project. Since there are many different Keil MDK editions, future programmers can make sure to use the proper license on their machine to avoid licensing issues.

Raise a technical support request: the full build log is a great tool for technical support cases, since it includes most of the background information a support analyst needs to understand an issue.

ANSWER

Yes. A *.build_log.htm file is generated after you have built your project.

However, to create a full build log, do a rebuild all, instead of a build. This will record all the information of a project.

To retrieve more details from the compiler output, you can specify --echo option to Options for Target - C/C++ - Misc Controls.

To view the build_log file, in the Project window on the right side of the screen, right-click the target folder in the and choose Open Build Log in the context menu - the *.build_log.htm file opens in the web browser.

This *.build_log.htm file is usually located in the same directory of your objects output folder, such as '.\Flash' or '.\RAM' folder. Please send this log file with a description of your issue to the keil support team.

The build log will look similar like this:

µVision Build Log

Tool Versions:
IDE-Version: µVision V5.15
Copyright (C) 2015 ARM Ltd and ARM Germany GmbH. All rights reserved.
License Information: Bruce Lee, Arm, LIC=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Tool Versions:
Toolchain:       MDK-ARM Professional  Version: 5.15.0
Toolchain Path:  C:\Keil_v515\ARM\ARMCC\Bin
C Compiler:      Armcc.exe V5.05 update 2 (build 169)
Assembler:       Armasm.exe V5.05 update 2 (build 169)
Linker/Locator:  ArmLink.exe V5.05 update 2 (build 169)
Library Manager: ArmAr.exe V5.05 update 2 (build 169)
Hex Converter:   FromElf.exe V5.05 update 2 (build 169)
CPU DLL:         SARMCM3.DLL V5.15.0
Dialog DLL:      DARMP1.DLL V1.25.0.0
Target DLL:      UL2CM3.DLL V1.155.8.0
Dialog DLL:      TARMP1.DLL V1.24.0.0

Project:

C:\MDK5_Projects\Boards\Keil\MCB1700\Blinky\Blinky.uvprojx
Project File Date:  06/05/2015

Output:

*** Using Compiler 'V5.05 update 2 (build 169)', folder: 'C:\Keil_v515\ARM\ARMCC\Bin'
Rebuild target 'LPC1768 Flash'
compiling Blinky.c...
compiling LED_MCB1700.c...
compiling GPIO_LPC17xx.c...
compiling PIN_LPC17xx.c...
assembling startup_LPC17xx.s...
compiling system_LPC17xx.c...
linking...
Program Size: Code=2046 RO-data=254 RW-data=16 ZI-data=512
".\Flash\Blinky.axf" - 0 Error(s), 0 Warning(s).

Software Packages used:

Package Vendor: ARM
                http://www.keil.com/pack/ARM.CMSIS.4.3.0.pack
                ARM::CMSIS:CORE:4.1.0
                CMSIS (Cortex Microcontroller Software Interface Standard)
   * Component: CORE Version: 4.1.0

Package Vendor: Keil
                http://www.keil.com/pack/Keil.LPC1700_DFP.2.0.0.pack
                Keil::Device:Startup:1.0.0
                NXP LPC1700 Series Device Support, Drivers and Examples for MCB1700
   * Component: Startup Version: 1.0.0
   * Component: PIN Version: 1.00
   * Component: GPIO Version: 1.00
   * Component: LED Version: 1.0.0

Package Vendor: Keil
                http://www.keil.com/pack/Keil.MDK-Middleware.6.4.0.pack
                ::Board Support:LED:1.00 (API)
                Keil MDK-ARM Professional Middleware for ARM Cortex-M based devices
   * Component: LED Version: 1.00

Collection of Component include folders:

  C:\MDK5_Projects\Boards\Keil\MCB1700\Blinky\RTE
  C:\MDK5_Projects\Boards\Keil\MCB1700\Blinky\RTE\Device\LPC1768
  C:\Keil_v515\ARM\PACK\ARM\CMSIS\4.3.0\CMSIS\Include
  C:\Keil_v515\ARM\PACK\Keil\LPC1700_DFP\2.0.0\Device\Include
  C:\Keil_v515\ARM\PACK\Keil\LPC1700_DFP\2.0.0\RTE_Driver
  C:\Keil_v515\ARM\PACK\Keil\MDK-Middleware\6.4.0\Board

Collection of Component Files used:

   * Component: ARM::CMSIS:CORE:4.1.0

   * Component: Keil::Device:Startup:1.0.0
      Include file:  Device\Include\LPC17xx.h
      Source file:   Device\Source\ARM\startup_LPC17xx.s
      Source file:   Device\Source\system_LPC17xx.c
      Include file:  RTE_Driver\Config\RTE_Device.h

   * Component: Keil::Device:PIN:1.00
      Include file:  RTE_Driver\PIN_LPC17xx.h
      Source file:   RTE_Driver\PIN_LPC17xx.c

   * Component: Keil::Device:GPIO:1.00
      Include file:  RTE_Driver\GPIO_LPC17xx.h
      Source file:   RTE_Driver\GPIO_LPC17xx.c

   * Component: Keil.MCB1700::Board Support:LED:1.0.0
      Source file:   Boards\Keil\MCB1700\Common\LED_MCB1700.c

   * Component: ::Board Support:LED:1.00 (API)
      Include file:  Board\Board_LED.h

MORE INFORMATION

SEE ALSO

FORUM THREADS

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

Last Reviewed: Monday, April 30, 2018


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.