ck: Portable CM script failed (name = flash-tinyml-binary, return code = 256)

Hi, I am trying to reproduce the tiny results v1.0 by OctoML and flash the microcontroller board but the following issue is triggered. Can anyone please help?

-- west flash: using runner openocd
-- runners.openocd: Flashing file: /home/saheli/CM/repos/local/cache/747a9e81fbc348e1/NUCLEO_L4R5ZI/ic/build/zephyr/zephyr.hex
Open On-Chip Debugger 0.11.0+dev-00244-g7e3dbbbe2 (2021-11-18-07:14)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : DEPRECATED target event trace-config
Info : clock speed 500 kHz
Error: open failed


FATAL ERROR: command exited with status 1: /home/saheli/CM/repos/local/cache/2fe55e8b2e5244ac/zephyr-sdk-0.13.2/sysroots/x86_64-pokysdk-linux/usr/bin/openocd -s /home/saheli/zephyrproject/zephyr/boards/arm/nucleo_l4r5zi/support -s /home/saheli/CM/repos/local/cache/2fe55e8b2e5244ac/zephyr-sdk-0.13.2/sysroots/x86_64-pokysdk-linux/usr/share/openocd/scripts -f /home/saheli/zephyrproject/zephyr/boards/arm/nucleo_l4r5zi/support/openocd.cfg -c init -c targets -c 'reset halt' -c 'flash write_image erase /home/saheli/CM/repos/local/cache/c948e587e6d445ec/NUCLEO_L4R5ZI/kws/build/zephyr/zephyr.hex' -c 'reset halt' -c 'verify_image /home/saheli/CM/repos/local/cache/c948e587e6d445ec/NUCLEO_L4R5ZI/kws/build/zephyr/zephyr.hex' -c 'reset run' -c shutdown

CM error: Portable CM script failed (name = flash-tinyml-binary, return code = 256)

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 15 (4 by maintainers)

Most upvoted comments

@sahelib25 try installing these udev rules, then unplugging/replugging the board: https://github.com/stlink-org/stlink/blob/develop/config/udev/rules.d/49-stlinkv2-1.rules

areusch on Jan 3, 2023

Hi @areusch, I have tried updating the udev rules once again. Now it is working fine. Thank you for your help.

sahelib25 on Jan 4, 2023

@gfursin no objection and no discussion needed on my side as long as this solution fixes the problem. @sahelib25 can you let us know if that fixed your problem?

areusch on Jan 3, 2023