• State Verified Answer
  • Replies 8 replies
  • Subscribers 75 subscribers
  • Views 3449 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 311060
Options

west debug FATAL ERROR required program JLink.exe not found

snowuyl

Procedure to reproduce this issue is as follows.
1. Unzipping minimal_log.zip
2. cd minimal_log
3. west build -b nrf5340dk_nrf5340_cpuapp
4. west debug

west log messages are as follows.

D:\ncs\v2.3.0\nrf\samples\minimal_log>west build -b nrf5340dk_nrf5340_cpuapp
-- west build: generating a build system

...

[181/181] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 36640 B 1 MB 3.49%
RAM: 9808 B 448 KB 2.14%
IDT_LIST: 0 GB 2 KB 0.00%

D:\ncs\v2.3.0\nrf\samples\minimal_log>west debug
-- west debug: rebuilding
ninja: no work to do.
-- west debug: using runner jlink
FATAL ERROR: required program JLink.exe not found; install it or add its location to PATH

Parents
  • 0 in reply to snowuyl

    Fullscreen JLink.exe_not_found.txt Download 
    D:\ncs\v2.3.0\nrf\samples\minimal_log>west build -b nrf5340dk_nrf5340_cpuapp
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: D:/ncs/v2.3.0/nrf/samples/minimal_log
-- Using NCS Toolchain 2.3.0 for building. (D:/ncs/toolchains/v2.3.0/cmake)
-- Found Python3: D:/ncs/toolchains/v2.3.0/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Cache files will be written to: D:/ncs/v2.3.0/zephyr/.cache
-- Zephyr version: 3.2.99 (D:/ncs/v2.3.0/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf5340dk_nrf5340_cpuapp
-- Found host-tools: zephyr 0.15.2 (D:/ncs/toolchains/v2.3.0/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.15.2 (D:/ncs/toolchains/v2.3.0/opt/zephyr-sdk)
-- Found Dtc: D:/ncs/toolchains/v2.3.0/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: D:/ncs/v2.3.0/nrf/boards/arm/mdbt53db_nrf5340/nrf5340dk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: D:/ncs/v2.3.0/nrf/samples/minimal_log/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: D:/ncs/v2.3.0/nrf/samples/minimal_log/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: D:/ncs/v2.3.0/nrf/samples/minimal_log/build/zephyr/dts.cmake
Parsing D:/ncs/v2.3.0/zephyr/Kconfig
Loaded configuration 'D:/ncs/v2.3.0/nrf/boards/arm/mdbt53db_nrf5340/nrf5340dk_nrf5340_cpuapp_defconfig'
Merged configuration 'D:/ncs/v2.3.0/nrf/samples/minimal_log/prj.conf'
Configuration saved to 'D:/ncs/v2.3.0/nrf/samples/minimal_log/build/zephyr/.config'
Kconfig header saved to 'D:/ncs/v2.3.0/nrf/samples/minimal_log/build/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 12.1.0
-- The CXX compiler identification is GNU 12.1.0
-- The ASM compiler identification is GNU
-- Found assembler: D:/ncs/toolchains/v2.3.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- Configuring done
-- Generating done
-- Build files have been written to: D:/ncs/v2.3.0/nrf/samples/minimal_log/build
-- west build: building application
[1/181] Generating include/generated/version.h
-- Zephyr version: 3.2.99 (D:/ncs/v2.3.0/zephyr), build: v3.2.99-ncs2
[171/181] Linking C executable zephyr\zephyr_pre0.elf

[175/181] Linking C executable zephyr\zephyr_pre1.elf

[181/181] Linking C executable zephyr\zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       36640 B         1 MB      3.49%
             RAM:        9808 B       448 KB      2.14%
        IDT_LIST:          0 GB         2 KB      0.00%

D:\ncs\v2.3.0\nrf\samples\minimal_log>west debug
-- west debug: rebuilding
ninja: no work to do.
-- west debug: using runner jlink
FATAL ERROR: required program JLink.exe not found; install it or add its location to PATH

  • 0 in reply to snowuyl

    Hi,

    For debugging, I suggest that you use Our VS Code extension.
    You should still be able to use "west debug", but if the VS Code extension solves the issue for you, then lets not dig down into debugging

    Regards,
    Sigurd Hellesvik

Reply Children
Related
Terms of service