• State Verified Answer
  • Locked Locked
  • Replies 20 replies
  • Subscribers 74 subscribers
  • Views 4462 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 283136
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

nRF Connect for Desktop Programmer V2.2.0 and Heart Rate Monitor Demo

alwalker

I have connected a nRF5340 DK board which the Programmer can connect to. I then drag the two .hex files for the Heart Rate Monitor demo over to the File Memory Layout window, however the following commands are still grayed out:

  • Erase all
  • Erase & write
  • Save as file
  • Reset
  • Write
  • Read

What am I missing please?

Fullscreen 2022-01-24T18_11_10.370Z-log.txt Download 
2022-01-24T18:11:10.585Z INFO Application data folder: /Users/alwalker/Library/Application Support/nrfconnect/pc-nrfconnect-programmer
2022-01-24T18:11:10.768Z DEBUG iface: en0
2022-01-24T18:11:10.769Z DEBUG IP4: 
2022-01-24T18:11:10.769Z DEBUG IP6: 
2022-01-24T18:11:10.769Z DEBUG MAC: f4:5c:89:8a:4c:71
2022-01-24T18:11:10.770Z DEBUG Client Id: 5f1d8708c90a91adf6b1603fb7250edf40e5ca2f
2022-01-24T18:11:10.771Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2022-01-24T18:11:10.858Z DEBUG App pc-nrfconnect-programmer v2.2.0 official
2022-01-24T18:11:10.859Z DEBUG App path: /Users/alwalker/.nrfconnect-apps/node_modules/pc-nrfconnect-programmer
2022-01-24T18:11:10.859Z DEBUG nRFConnect 3.9.3, required by the app is (^3.9.2)
2022-01-24T18:11:10.859Z DEBUG nRFConnect path: /Applications/nRF Connect for Desktop.app/Contents/Resources/app.asar
2022-01-24T18:11:10.859Z DEBUG HomeDir: /Users/alwalker
2022-01-24T18:11:10.859Z DEBUG TmpDir: /var/folders/gt/fzbprb7j48b7rm6dmdcdx2q00000gn/T/
2022-01-24T18:11:21.384Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-01-24T18:11:21.384Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Jul  2 2021 10:55:25
2022-01-24T18:11:21.384Z DEBUG Sending usage data...
2022-01-24T18:11:21.385Z DEBUG Category: pc-nrfconnect-programmer
2022-01-24T18:11:21.385Z DEBUG Action: Open jlink OB version
2022-01-24T18:11:21.385Z DEBUG Label: J-Link OB-nRF5340-NordicSemi compiled Jul  2 2021 10:55:25
2022-01-24T18:11:21.385Z DEBUG Usage data has not been sent. isSendingUsageData is set to false.
2022-01-24T18:11:21.385Z INFO Device family 
2022-01-24T18:11:21.385Z DEBUG Sending usage data...
2022-01-24T18:11:21.385Z DEBUG Category: pc-nrfconnect-programmer
2022-01-24T18:11:21.385Z DEBUG Action: Open jlink device family
2022-01-24T18:11:21.385Z DEBUG Label: null
2022-01-24T18:11:21.385Z DEBUG Usage data has not been sent. isSendingUsageData is set to false.
2022-01-24T18:11:21.385Z INFO Device version 
2022-01-24T18:11:21.385Z DEBUG Sending usage data...
2022-01-24T18:11:21.385Z DEBUG Category: pc-nrfconnect-programmer
2022-01-24T18:11:21.385Z DEBUG Action: Open jlink device version
2022-01-24T18:11:21.385Z DEBUG Label: null
2022-01-24T18:11:21.386Z DEBUG Usage data has not been sent. isSendingUsageData is set to false.
2022-01-24T18:11:21.386Z INFO Board version PCA10095
2022-01-24T18:11:21.386Z DEBUG Sending usage data...
2022-01-24T18:11:21.386Z DEBUG Category: pc-nrfconnect-programmer
2022-01-24T18:11:21.386Z DEBUG Action: Open jlink device board version
2022-01-24T18:11:21.386Z DEBUG Label: PCA10095
2022-01-24T18:11:21.386Z DEBUG Usage data has not been sent. isSendingUsageData is set to false.
2022-01-24T18:11:21.387Z DEBUG Sending usage data...
2022-01-24T18:11:21.387Z DEBUG Category: pc-nrfconnect-programmer
2022-01-24T18:11:21.387Z DEBUG Action: Open device
2022-01-24T18:11:21.387Z DEBUG Label: jlink
2022-01-24T18:11:21.387Z DEBUG Usage data has not been sent. isSendingUsageData is set to false.
2022-01-24T18:11:53.159Z INFO Parsing HEX file:  /Users/alwalker/Desktop/Peripheral_Heart_Rate_nRF5340_DK/peripheral_hr.hex
2022-01-24T18:11:53.173Z INFO File was last modified at  02/12/2020, 09:36:50
2022-01-24T18:11:53.224Z INFO Update files regions according to NRFDL_DEVICE_CORE_APPLICATION core
2022-01-24T18:11:53.224Z INFO Parse memory regions for file
2022-01-24T18:11:53.241Z INFO Parsing HEX file:  /Users/alwalker/Desktop/Peripheral_Heart_Rate_nRF5340_DK/hci_open_amp.hex
2022-01-24T18:11:53.241Z INFO File was last modified at  02/12/2020, 09:36:52
2022-01-24T18:11:53.326Z INFO Update files regions according to NRFDL_DEVICE_CORE_APPLICATION core
2022-01-24T18:11:53.326Z INFO Parse memory regions for file
2022-01-24T18:11:53.326Z INFO Update files regions according to NRFDL_DEVICE_CORE_NETWORK core
2022-01-24T18:11:53.326Z INFO Parse memory regions for file

# nRFConnect System Report - 2022-01-25T07-26-56.445Z

- System: Apple Inc. MacBookPro12,1
- BIOS: Apple Inc. 428.60.3.0.0
- CPU: 1 x IntelRegistered CoreTm i7-5557U 3.1 GHz 4 cores (2 physical)
- Memory: 425.4 MB free of 16 GB total
- Filesystem: /dev/disk1s5 (APFS) 931.6 GB 2.2% used

- OS: Mac OS X (10.15.7) darwin x64

- Versions
- kernel: 19.6.0
- git: 2.24.3
- node: 14.16.0
- python: 2.7.16
- python3: 3.8.2
- nrfjprog: 10.15.1
- jlink: 7.58b

- Connected devices:
- 001050072527 PCA10095: /dev/tty.usbmodem0010500725271, /dev/tty.usbmodem0010500725273

- Current device:
- name: nRF5340 DK
- serialNumber: 001050072527
- cores: 2
- website: www.nordicsemi.com/.../nRF5340-DK

  • 0 in reply to alwalker

    I also saw something about an issue with macOS where the data packets over USB were getting truncated, but I can't immediately find it. Could this be the problem please?

  • 0 in reply to alwalker

    https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-connect-v10-release#osxissue

    https://wiki.segger.com/J-Link_OB

    Workaround 2

    If MSD and VCOM are not needed at the same time, it is possible to disable the MSD component on the J-Link, freeing 2 EPs so that these ones can be used for VCOM to support 512 byte packets. In order to disable the MSD component, please do the following:

    • Connect the J-Link-OB to your PC
    • Start J-Link Commander
    • execute the following command (without quotes): "MSDDisable"
    • Quit J-Link Commander
    • Power-cycle J-Link-OB

    To re-enable the MSD component, please perform the same procedure as above but use the "MSDEnable" command instead.

    This is what I get when I open JLinkConfig, it's not obvious how to follow the workaround instructions:

  • 0 in reply to alwalker

    You should find it in VS Code, under the nRF Connect side panel, if you choose "Create new application from sample"

    The sample is found as samples/bluetooth/central_and_peripheral_hr

    https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/central_and_peripheral_hr/README.html

    It looks like you're receiving data over USB just fine, as your error messages are displayed correctly, this seems more like an error in kernel settings in the program you're flashing, which could be because you've rollbacked the programmer.

  • 0 in reply to Einarh

    Thanks Einar, some progress with VS Code. I was able to find and build the application although as I'm still on a learning code with VS Code for nRF Connect I may not have done all the steps correctly.

    When I do an Erase and Flash, this is what is displayed in nRF Terminal:

    *** Booting Zephyr OS build v2.7.0-ncs1 ***
    Starting Bluetooth Central and Peripheral Heart Rate relay example
    I: 2 Sectors of 4096 bytes
    I: alloc wra: 0, fe8
    I: data wra: 0, 0
    I: No ID address. App must call settings_load()
    Scanning started
    Advertising started
    W: opcode 0x200a status 0x09
    Connected: 76:B3:56:1B:D7:0E (random)
    W: Ignoring data for unknown channel ID 0x003a
    I: HRS notifications enabled

    When I select Heart Rate in nRF Toolbox on my iPad Pro, the following is displayed which I can connect to:

    Nordic_HR

    But then in the HEART RATE window it then just sits on Retrieving data...

    In the Nordic Kconfig (build) tab it states:

    Unable to find Kconfig information to display. Please select a Kconfig file first.

    One problem is shown in the Terminal:

    soc/arm/atmel_sam/Kconfig.defconfig:11: error: couldn't parse 'default $(dt_node_int_prop_int,/cpus/cpu@0,clock-frequency)': macro expanded to blank string

    # Atmel SAM MCU family default configuration options

    # Copyright (c) 2016 Piotr Mienkowski
    # SPDX-License-Identifier: Apache-2.0

    source "soc/arm/atmel_sam/*/Kconfig.defconfig.series"

    if SOC_FAMILY_SAM

    config SYS_CLOCK_HW_CYCLES_PER_SEC
    default $(dt_node_int_prop_int,/cpus/cpu@0,clock-frequency)

    config WATCHDOG
    default y

    endif # SOC_FAMILY_SAM
  • 0 in reply to Einarh

    Hello Einar,

    As an experiment, reinstalled nRF Connect 3.7.2 and tried programming a completely new nRF5340 DK straight from the box, result was the same so my thought is that the two .hex files may have been compiled for a different processor. Could I ask that this zip file is re-uploaded with files targeting the nRF5340 please? I will confirm if operation is correct with the Programmer.

                                          Peripheral_Heart_Rate_nRF5340_DK.zip                                     

    If it doesn't work then it suggest that there is an issue with the 3.7.2 Programmer.

    In the meantime, based on the below, I don't feel confident that I have VS Code for nRF Connect fully configured, so I will go back through the installation and configuration process. Is it right to use nRF Connect 3.7.2 to configure VS Code please?

Related
Terms of service