• State Not Answered
  • Replies 7 replies
  • Subscribers 27 subscribers
  • Views 282 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 290344
Options

nRF Connect v2.0.0 installation hangs at "Updating memfault repository" on macOS

user113934

My laptop is running the latest macOS 12.4.  It is a 2021 Macbook 14" with M1 Max.

I updated nRF Connect For Desktop and Toolchain Manager to the latest versions, then I tried to install nRF Connect SDK v2.0.0.  Most stages of the process completed in a matter of minutes, but it's been stuck on the memfault stage for over half an hour and I'm not sure what to do now:

Parents Reply Children
  • 0 in reply to user107729

    I just restarted the whole process.  Might want to look into why the installer sometimes hangs, though, since multiple people have seen this bug.

  • 0 in reply to user113934

    Hi,

    Such problems can arise if the installation process is not properly completed maybe due to some VPN or firewall issues. There have been similar issues and similar solutions can be viewed here.

    But thank you for your feedback. Slight smile

    -Priyanka

  • 0 in reply to user107729

    I don't have a VPN or firewall on this Mac, so that definitely wasn't the problem here.

    Also the toolchain did show up in a weird location (/opt/nordic/ncs/toolchains instead of /opt/nordic/ncs/v2.0.0/toolchain) after I repeated the installation.  Is this the same problem described at the link?  I'm not sure whether I should manually move it over or not.

    Could you please file internal bug tickets for both of these issues so that they can be fixed in a future NCS release?

  • 0 in reply to user107729

    I don't think this installation is completing properly.  I've tried 3 times:

    1. Launch nRF Connect for Desktop
    2. Enter Toolchain Manager
    3. Install 2.0.0
    4. <hangs at memfault stage>
    5. Quit
    6. Launch nRF Connect for Desktop
    7. Enter Toolchain Manager
    8. Remove 2.0.0 environment
    9. Quit
    10. Repeat the process

    The hang in #4 happens every time.  It's not a fluke.

    It is the git process that is getting wedged:

    # ps auxwww | grep memfault
    admin 21905 0.0 0.0 34421664 5108 ?? S 4:25PM 0:00.03 git fetch -f --tags -- github.com/.../memfault-firmware-sdk 0.29.1

    lsof shows that it doesn't have any sockets open, which means it's not caused by a network connection getting stalled:

    # lsof -n | grep ^git
    git 21905 admin cwd DIR 1,15 96 21527642 /opt/nordic/ncs/v2.0.0/modules/lib/memfault-firmware-sdk
    git 21905 admin txt REG 1,15 3033288 21431331 /opt/nordic/ncs/toolchains/v2.0.0/Cellar/git/2.32.0_1/bin/git
    git 21905 admin txt REG 1,15 4376160 21466510 /private/var/db/oah/0b833e18ecef0e9978fe7e49ac779dfffc2d441c9d93d8ab63ab224abc515f59/e20bb4c3db2bbdcbfffe26d96bb986c6556a61d8e3531c6d1580422d993a51ca/git.aot
    git 21905 admin txt REG 1,15 233056 1152921500312788000 /usr/libexec/rosetta/runtime
    git 21905 admin txt REG 1,15 381680 19267166 /Library/Apple/usr/libexec/oah/libRosettaRuntime
    git 21905 admin txt REG 1,15 59156 21449869 /opt/nordic/ncs/toolchains/v2.0.0/Cellar/gettext/0.21/lib/libintl.8.dylib
    git 21905 admin txt REG 1,15 59416 21466514 /private/var/db/oah/0b833e18ecef0e9978fe7e49ac779dfffc2d441c9d93d8ab63ab224abc515f59/48e5f74d07549aebd9346c19f80c7edb4b028f1213ec387215e9f9600c215d27/libintl.8.dylib.aot
    git 21905 admin txt REG 1,15 46864 19266539 /Library/Preferences/Logging/.plist-cache.DrKORzJo
    git 21905 admin txt REG 1,15 572112 21439663 /opt/nordic/ncs/toolchains/v2.0.0/Cellar/pcre2/10.37_1/lib/libpcre2-8.0.dylib
    git 21905 admin txt REG 1,15 662792 21466512 /private/var/db/oah/0b833e18ecef0e9978fe7e49ac779dfffc2d441c9d93d8ab63ab224abc515f59/2ab2f015a791b7cda2f74d3b5043c2115027930855e009667b9e5a2fd45247e8/libpcre2-8.0.dylib.aot
    git 21905 admin txt REG 1,15 142696 21527681 /opt/nordic/ncs/v2.0.0/modules/lib/memfault-firmware-sdk/.git/objects/pack/pack-ea43bc9869bb0c8dd373be2ebf1fa3e7048aa424.idx
    git 21905 admin txt REG 1,15 1994288 21527680 /opt/nordic/ncs/v2.0.0/modules/lib/memfault-firmware-sdk/.git/objects/pack/pack-ea43bc9869bb0c8dd373be2ebf1fa3e7048aa424.pack
    git 21905 admin txt REG 1,15 2160656 1152921500312781597 /usr/lib/dyld
    git 21905 admin txt REG 1,15 812723 19297118 /private/var/db/oah/0b833e18ecef0e9978fe7e49ac779dfffc2d441c9d93d8ab63ab224abc515f59/51d62da53a337e9df4a5182e605fa09682db158d34d7f285356069d2009afcf7/dyld.aot
    git 21905 admin 0u unix 0x5d449eafc79ecf1b 0t0 ->0x5d449eafc79ece53
    git 21905 admin 1u unix 0x5d449eafc79ed623 0t0 ->0x5d449eafc79ed55b
    git 21905 admin 2u unix 0x5d449eafc79edb9b 0t0 ->0x5d449eafc79ed6eb
    git 21905 admin 3w REG 1,15 0 21527679 /opt/nordic/ncs/v2.0.0/modules/lib/memfault-firmware-sdk/.git/FETCH_HEAD


    This seems to be getting invoked from west.  Running this manually completes without error and I see that /opt/nordic/ncs/v2.0.0/modules/lib/memfault-firmware-sdk gets populated:

    cd /opt/nordic/ncs/v2.0.0
    /opt/nordic/ncs/toolchains/v2.0.0/Cellar/[email protected]/3.9.6/Frameworks/Python.framework/Versions/3.9/Resources/Python.app/Contents/MacOS/Python /opt/nordic/ncs/toolchains/v2.0.0/bin/west update

    Maybe update to a newer version of git in the SDK?  I've seen some git versions from a few months ago inexplicably hanging too, on AWS Ubuntu Linux hosts.

  • 0 in reply to user113934

    Hi,

    This is an issue that will be fixed in the new release. The current workaround is just to reopen the app and try "Update SDK". Sorry for the trouble.

    -Priyanka

Related
Terms of service