• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 89 subscribers
  • Views 2210 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 277251
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

Issues with Apple M1 in nRF Connect -> Programmer.

paul.lander

I am encountering a problem with programming an nRF52840 DK:

1. I've installed nRF Connect for Desktop version 3.7.1, nrfjprog version 10.14 and Segger JLinkARM.dll version 7.54d (directly from Segger's website). In the Programmer v1.4.11, the PCA10056 is recognized at serial port: /dev/tty.usbmodem0006838233401 but the log has errors:

Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6

Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: JLINKARM_DLL_COULD_NOT_BE_OPENED (ffffff9b)

Where does Programmer look for JlinkARM (it's failing) and nrfjprog (it's using an older version)?  In my terminal I get:

~ % nrfjprog --version  

nrfjprog version: 10.14.0 external

JLinkARM.dll version: 7.54d

2. Separately, in VS Code I cannot connect to the nRF52840 DK using the nRF Terminal extension, presumably because usb-native-mode does not support M1 processors.

Do you have advice for either of these issues? Thanks, Paul

Parents
  • 0

    Hi,

    For 1 could you try to download and install j-link for M1? I think that should be available on the segger web pages.

    2. Seems there is some discussion her, unfortunately it boils down to: "Unfortunately there is no fix at the moment to this issue since there are some parts in this setup that have no M1 support. In any case we are aware and we try to work out the solution."

  • 0 in reply to run_ar

    Nordic bundles 2 Segger JLinkARM DLLs, for x86/M1 computers, with the command line tools, but my package contained only the x86 DLL. I downloaded JLinkARM for M1 directly from Segger. There are 2 issues:

    1. The Programmer in nRF Connect is not using the JLinkARM DLL for M1 and so cannot read the target.

    2. The nRF Connect extension for Visual Studio Code relies on a 3rd party module that does not currently support M1.

    I am not able to connect nRF Terminal in VS Code to a target. I can download to flash, run and debug, but it's inconsistent.

    To the Nordic folks:

    1. Is there a timetable for M1 support? I understand this may not be a priority, in which case it would be helpful to indicate that there is not yet M1 support for the nRF Connect extension for VS Code. I did use the Toolchain Manager in nRF Connect 1.7.0 and the extension for VS Code on macos (x86) and it works wonderfully well - thanks!

    2. Are there plans to host tools in the cloud, say with Docker, so that we could use VS Code with a virtual container and live play? <-- the developer's dream setup.

  • 0 in reply to paul.lander

    What should work is downgrading the nRF Command Line tools to 10.13.0. The key here is to have the whole toolset in x86 version. The situation will be rectified with a release of new version of nrfjprog in a few weeks.

    We'll look into nRF Terminal on M1. It's not the top priority, so I think we're looking end of year here.

    The Docker would be nice indeed but to my knowledge accessing USB from containers is not available on all platforms we support.

    Wojtek

    VSC Team

Reply
  • 0 in reply to paul.lander

    What should work is downgrading the nRF Command Line tools to 10.13.0. The key here is to have the whole toolset in x86 version. The situation will be rectified with a release of new version of nrfjprog in a few weeks.

    We'll look into nRF Terminal on M1. It's not the top priority, so I think we're looking end of year here.

    The Docker would be nice indeed but to my knowledge accessing USB from containers is not available on all platforms we support.

    Wojtek

    VSC Team

Children
No Data
Related
Terms of service