• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 25 subscribers
  • Views 570 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 281247
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Current state of supporting Apple M1

user106884

As mentioned here I installed the Intel versions:

But flashing the sample is not possible due to this error:

-- west flash: using runner nrfjprog
-- runners.nrfjprog: mass erase requested
-- runners.nrfjprog: Flashing file: /opt/nordic/ncs/v1.6.1/zephyr/samples/basic/blinky/build/zephyr/zephyr.hex
ERROR: Unable to connect to a debugger.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 33: nrfjprog --program /opt/nordic/ncs/v1.6.1/zephyr/samples/basic/blinky/build/zephyr/zephyr.hex --chiperase -f NRF52 --snr 685260830
The terminal process terminated with exit code: 33.

  • 0

    Using the nRF-Command-Line-Tools 10.15.1 with J-Link V7.58b for M1 will result in the following error:

    ERROR: JLinkARM DLL load failed.
    Try again. If it keeps failing, please ERROR: reinstall latest JLinkARM from Segger webpage.
    NOTE: For additional output, try running again with logging enabled (--log).
    NOTE: Any generated log error messages will be displayed.

    But it enables flashing via an external command line using the nrfjprog command directly.

  • +1 in reply to user106884

    Hi,

    You need to select the intel variant (x86 / x86_64) when installing the J-link drivers for nrfjprog to work when invoked through West. Please try this and let me know if you still get the same error.

    Thanks,

    Vidar

Related
Terms of service