ON Semiconductor
www.onsemi.com
23
Figure 23. Example of Build Output
3. The key resulting output in Project Explorer in the IDE includes:
•
blinky.hex
: HEX file for loading into Flash memory
•
blinky.axf
: Arm
®
executable file, run from RAM, used for debugging
•
blinky.map
: map file of the sections and memory usage
4.3.3 Debugging the Sample Code
4.3.3.1 Preparing J-Link for Debugging
Before debugging with J-Link, go to
C:\Keil_v5\ARM\Segger
and make sure that the folder contains a
JL2CM3.dll
file. As well, make sure that you have installed the latest version of J-Link and have run the J-Link DLL Updater, as
shown in Section 2.3, “Prerequisite Software” on page 6.
4.3.3.2 Debugging Applications
The IDE’s debug configurations are already set in the CMSIS-Pack. To debug an application:
1. Make sure the Evaluation and Development Board is connected to the PC via a micro USB cable.
2. Select
Debug > Start/Stop Debug Session
or click the icon shown in Figure 24.
Figure 24. Start/Stop Debug Session Icon
If you are having trouble downloading firmware because an application with Sleep Mode is on the Evaluation
and Development Board, see Section 6.4.1, “Downloading Firmware in Sleep Mode” on page 40.
3. The application runs up to the first breakpoint in
main
, as shown in Figure 25. You can press F11 multiple
times to step through the code and observe that the LED changes its state when the application executes the
function
Sys_GPIO_Toggle(LED_DIO)
.
