blinky isn't

How do I resolve/update:
zephyr-sdk is outdated. Found 0.16.5, but 0.16.8 is required by the SDK.
Clock3 python is outdated. Found 3.9.13, but 3.12.4 is required by the SDK.
Blinky isn't blinking
:)
Parents
  • Hi Scott,

    Could you provide details of the board that you are using and the SDK that you are working with ?

    Regards,

    Priyanka 

  • Hello Priyanka and thank you.

    I am using a nRF52840 Development Kit Board.

    The SDK I am using is:

     Using the nRF Connect SDK v3.6.99 at c:\ncs\v2.7.99-cs2

    I am following DevAcadamy nRF Connect SDK Fundamentals Lesson 1 Exercise 2

    When I plug my USB cord in the board does not show up in the connected devices view:

    No devices found
    The "code view" shows:
    {
      "board": "nrf52840dk/nrf52840",
      "boardRevision": "",
      "boardDir": "c:/ncs/v2.7.99-cs2/zephyr/boards/nordic/nrf52840dk",
      "shouldBuild": true,
      "optimizations": "none",
      "cmakeArgs": [],
      "confFiles": [
        "prj.conf"
      ],
      "buildDirectory": "build",
      "kconfigFragments": [],
      "snippets": [],
      "dtcOverlays": [],
      "extraDtcOverlays": []
    }
    not sure the board statement is correct or does the board have a "off/on" switch?
    Output "view" is:
    [02:32:20] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.7.0 ===========
    [02:32:21] Update available nsscprodmedia.blob.core.windows.net/.../nrf-command-line-tools-10.24.2-x64.exe
    Package Using the nRF Connect SDK v3.6.99 at c:\ncs\v2.7.99-cs2
    Clock3 zephyr-sdk is outdated. Found 0.16.5-1, but 0.16.8 is required by the SDK.
    Clock3 python is outdated. Found 3.9.13, but 3.12.4 is required by the SDK.
    Exclamation️ nrfjprog couldn't be executed. Please ensure that SEGGER J-Link Software and Documentation Pack and nRF Command Line Tools are both installed.
Reply
  • Hello Priyanka and thank you.

    I am using a nRF52840 Development Kit Board.

    The SDK I am using is:

     Using the nRF Connect SDK v3.6.99 at c:\ncs\v2.7.99-cs2

    I am following DevAcadamy nRF Connect SDK Fundamentals Lesson 1 Exercise 2

    When I plug my USB cord in the board does not show up in the connected devices view:

    No devices found
    The "code view" shows:
    {
      "board": "nrf52840dk/nrf52840",
      "boardRevision": "",
      "boardDir": "c:/ncs/v2.7.99-cs2/zephyr/boards/nordic/nrf52840dk",
      "shouldBuild": true,
      "optimizations": "none",
      "cmakeArgs": [],
      "confFiles": [
        "prj.conf"
      ],
      "buildDirectory": "build",
      "kconfigFragments": [],
      "snippets": [],
      "dtcOverlays": [],
      "extraDtcOverlays": []
    }
    not sure the board statement is correct or does the board have a "off/on" switch?
    Output "view" is:
    [02:32:20] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.7.0 ===========
    [02:32:21] Update available nsscprodmedia.blob.core.windows.net/.../nrf-command-line-tools-10.24.2-x64.exe
    Package Using the nRF Connect SDK v3.6.99 at c:\ncs\v2.7.99-cs2
    Clock3 zephyr-sdk is outdated. Found 0.16.5-1, but 0.16.8 is required by the SDK.
    Clock3 python is outdated. Found 3.9.13, but 3.12.4 is required by the SDK.
    Exclamation️ nrfjprog couldn't be executed. Please ensure that SEGGER J-Link Software and Documentation Pack and nRF Command Line Tools are both installed.
Children
  • Hi,

    Let us go through the issues sequentially. First, I would suggest you to uninstall everything and then start again the installation as I mention below:

    1. Install nRF Command Line Tools (latest version)

    2.Install the latest version of SEGGER J-Link. 

    3. Install nRF Connect for Desktop application.

    4. Within the application, install the Toolchain Manager.

    5. Within Toolchain Manager, install the nRF Connect SDK v2.7.0

    6. Now open the VSCode via the Toolchain Manager:

    7. Make sure you have installed the nRF Connect for VSCode extension pack. and now you should be able to build and run your applications.

    Next we can look into the DK detection issue:

    Could you try with different USB cables just to cross out whether it's a USB issue. Please make sure that you are inserting the cord into the right USB port on the DK.

    What is your DK revision? (details on the white sticker on the DK)

    Regards,

    Priyanka

  • i also get the same output
    Package Using the nRF Connect SDK v2.7.99 at c:\ncs\v2.7.99-cs2
    Clock3 zephyr-sdk is outdated. Found 0.16.5, but 0.16.8 is required by the SDK.
    Clock3 python is outdated. Found 3.9.13, but 3.12.4 is required by the SDK.
    [14:30:21] nrfutil-toolchain-manager uninstall v2.6.2: Remove version
    [14:30:21] nrfutil-toolchain-manager uninstall v2.6.2: Removed version v2.6.2: success
    [14:30:21] nrfutil-toolchain-manager uninstall v2.6.2: Remove toolchain
    [14:30:32] nrfutil-toolchain-manager uninstall v2.6.2: Removed toolchain at C:\ncs\toolchains\cf2149caf2: success
    [14:36:56] nrfutil-toolchain-manager install v2.7.0: Download toolchain
    [14:36:59] nrfutil-toolchain-manager install v2.7.0: Finished, using previously downloaded file: success
    [14:36:59] nrfutil-toolchain-manager install v2.7.0: Unpack toolchain
    [14:37:54] nrfutil-toolchain-manager install v2.7.0: Toolchain unpacked to C:\ncs\tmp\.tmpD3AtkB: success
    [14:37:54] nrfutil-toolchain-manager install v2.7.0: Install toolchain
    [14:37:55] nrfutil-toolchain-manager install v2.7.0: Toolchain installed at C:\ncs\toolchains\ce3b5ff664: success
    [14:37:56] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.7.0 ===========
    Package Using the nRF Connect SDK v2.7.99 at c:\ncs\v2.7.99-cs2
    Clock3 zephyr-sdk is outdated. Found 0.16.5-1, but 0.16.8 is required by the SDK.
    Clock3 python is outdated. Found 3.9.13, but 3.12.4 is required by the SDK.
  • Please check the previous comment in the ticket and follow the steps. Do let me know if you still face the issue after trying those. You could also try to update python, in addition to those.

    -Priyanka

  • Thanks to your valuable help the prior issues are resolved

    Now it looks like it is compiling but fatal-ing on the flash:

    ERROR: No debuggers were discovered.
    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 41: nrfjprog --program 'C:\nordic\myapps\fund_less1_ecer2\build\fund_less1_ecer2\zephyr\zephyr.hex' --sectoranduicrerase --verify -f NRF52 --snr 1050265833

    It seems to me like my nRF Connect needs some issue fixes - can you advise

  • Latest error:

    [error] [ Client] - Encountered error -90: Command erase_file executed for 28 milliseconds with result -90
    [error] [ nRF52] - Failed while erasing device. -90: Access protection is enabled, can't read device version.
    [error] [ Worker] - Access protection is enabled, can't read device version.
    ERROR: The operation attempted is unavailable due to readback protection in
    ERROR: your device. Please use --recover to unlock the device.
    NOTE: For additional output, try running again with logging enabled (--log).
    NOTE: Any generated log error messages will be displayed.
    ERROR: runners.nrfjprog: Flashing failed because the target must be recovered.
    To fix, run "west flash --recover" instead.
    Note: this will recover and erase all flash memory prior to reflashing.
    FATAL ERROR: command exited with status 24: nrfjprog --program 'C:\nordic\myapps\fund_less1_ecer2\build\fund_less1_ecer2\zephyr\zephyr.hex' --chiperase --verify -f NRF52 --snr 1050265833

    * The terminal process terminated with exit code: 24.
    * Terminal will be reused by tasks, press any key to close it.

    How do I deactivate device protection?

Related