Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

board frdm_kl25z build passed, but can't flash #21385

Closed
happymili opened this issue Dec 13, 2019 · 3 comments
Closed

board frdm_kl25z build passed, but can't flash #21385

happymili opened this issue Dec 13, 2019 · 3 comments
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Waiting for response Waiting for author's response

Comments

@happymili
Copy link

config env

cd ~/zephyrproject/zephyr/
source zephyr-env.sh

delete build folder

sudo rm build -r

build

west build -p auto -b frdm_kl25z  samples/basic/blinky/

output

-- west build: build configuration:
       source directory: /home/linux/zephyrproject/zephyr/samples/basic/blinky
       build directory: /home/linux/zephyrproject/zephyr/build (created)
       BOARD: frdm_kl25z (origin: command line)
-- west build: generating a build system
Zephyr version: 2.1.0
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.7.3", minimum required is "3.4") 
-- Selected BOARD frdm_kl25z
-- Found west: /home/linux/.local/bin/west (found suitable version "0.6.3", minimum required is "0.6.0")
-- Loading /home/linux/zephyrproject/zephyr/boards/arm/frdm_kl25z/frdm_kl25z.dts as base
Devicetree configuration written to /home/linux/zephyrproject/zephyr/build/zephyr/include/generated/generated_dts_board.conf
Parsing Kconfig tree in /home/linux/zephyrproject/zephyr/Kconfig
Loaded configuration '/home/linux/zephyrproject/zephyr/boards/arm/frdm_kl25z/frdm_kl25z_defconfig'
Merged configuration '/home/linux/zephyrproject/zephyr/samples/basic/blinky/prj.conf'
Configuration saved to '/home/linux/zephyrproject/zephyr/build/zephyr/.config'
-- The C compiler identification is GNU 9.2.0
-- The CXX compiler identification is GNU 9.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/linux/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Cache files will be written to: /home/linux/.cache/zephyr
-- Configuring done
-- Generating done
-- Build files have been written to: /home/linux/zephyrproject/zephyr/build
-- west build: building application
[2/116] Preparing syscall dependency handling

[111/116] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       10968 B       128 KB      8.37%
            SRAM:        3864 B        16 KB     23.58%
        IDT_LIST:          40 B         2 KB      1.95%
[116/116] Linking C executable zephyr/zephyr.elf

flash

west flash

output

-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner pyocd
WARNING: runners.pyocd: hex file (/home/linux/zephyrproject/zephyr/build/zephyr/zephyr.hex) does not exist; falling back on .bin (/home/linux/zephyrproject/zephyr/build/zephyr/zephyr.bin). Consider enabling CONFIG_BUILD_OUTPUT_HEX.
-- runners.pyocd: Flashing file: /home/linux/zephyrproject/zephyr/build/zephyr/zephyr.bin
No connected debug probes
0000476:CRITICAL:__main__:uncaught exception: 
Traceback (most recent call last):
  File "/home/linux/.local/lib/python3.7/site-packages/pyocd/__main__.py", line 338, in run
    self._COMMANDS[self._args.cmd](self)
  File "/home/linux/.local/lib/python3.7/site-packages/pyocd/__main__.py", line 468, in do_flash
    with session:
  File "/home/linux/.local/lib/python3.7/site-packages/pyocd/core/session.py", line 284, in __enter__
    assert self._probe is not None
AssertionError
ERROR: command exited with status 1: pyocd flash -e sector -t kl25z /home/linux/zephyrproject/zephyr/build/zephyr/zephyr.bin
@happymili happymili added the bug The issue is a bug, or the PR is fixing a bug label Dec 13, 2019
@jhedberg jhedberg added the priority: low Low impact/importance bug label Dec 17, 2019
@MaureenHelm
Copy link
Member

Hi @happymili , pyocd is not able to find your debug probe. You probably need to configure a udev rule. If that doesn't work, please check that you have the correct firmware programmed on the OpenSDA MCU. See here for more details.

@dleach02
Copy link
Member

dleach02 commented Jan 2, 2020

@happymili, can you provide feedback on @MaureenHelm suggested actions?

@dleach02 dleach02 added the Waiting for response Waiting for author's response label Jan 2, 2020
@MaureenHelm
Copy link
Member

Closing due to no response after >1 month. Please reopen if this is still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Waiting for response Waiting for author's response
Projects
None yet
Development

No branches or pull requests

4 participants