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
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
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
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

# 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

Parents
  • 0

    Hello!

    There is a known issue with the newest version of the programmer app and the nRF53. This will be fixed in a future update of the app.

    Meanwhile you should be able to program your DK if you roll back to nRF Connect 3.7 and Programmer v1.4.11 following these steps:

    1. Download the latest 3.7 version of nRF Connect for Desktop from https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-for-desktop/Download?lang=en#infotabs (for macOS this is 3.7.2).
    2. After starting nRF Connect for Desktop 3.7 a prompt will come up about an available upgrade. Click “No” on this.
    3. In the Settings, click on “Add source”, enter the URL http://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/3.7-apps/apps.json and click “Add”.
    4. Back in the list of all apps, all apps should show up twice now, one with “official” below them and one with “3.7 compatible apps” below them. If you want to hide the incompatible versions, click on “Filter” and deselect “Official”.
    5. Install the apps you need in the old versions and use them.

    Best regards,

    Einar

  • 0 in reply to Einarh

    Thanks very much Einar, I was able to follow your instructions fully and the board does now appear to be programmed based on doing a memory read.

    Per the instructions, I've pressed the reset button on the board and the green LED5 pulses periodically. No other LEDs illuminate.

    However when I start the latest version of nRF Toolbox just downloaded from the iOS App Store on either my 1st gen iPad Pro or iPhone 12 mini, when I try to connect via Bluetooth, no entries appear.

    All that is displayed is 

    SCANNING...

    Am I missing something please?

  • 0 in reply to alwalker

    Can you link me to the instructions you are talking about?

    Just to clarify, you press restart after flashing, and you're then unable to find the DK from your phone, correct?

    -Einar

  • 0 in reply to Einarh

    Thanks very much Einar, it's Section 3 - 'Running a first test' of this document:

    https://infocenter.nordicsemi.com/pdf/getting_started_NCS_nRF53_20210211.pdf

    Yes, I press reset after flashing and the nRF Toolbox app is unable to connect.on either my iPhone or iPad Pro.

    As confirmation that Bluetooth is functional on my iPad Pro, I was able to connect to my Bose SoundLink Mini speaker and stream music to it.

    Programmer log file attached

    Fullscreen 2022-01-25T18_53_50.846Z-log.txt Download
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    2022-01-25T18:53:51.078Z INFO Application data folder: /Users/alwalker/Library/Application Support/nrfconnect/pc-nrfconnect-programmer
    2022-01-25T18:53:51.142Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
    2022-01-25T18:53:51.197Z DEBUG App pc-nrfconnect-programmer v1.4.11 official
    2022-01-25T18:53:51.197Z DEBUG App path: /Users/alwalker/.nrfconnect-apps/external/3.7 compatible apps/node_modules/pc-nrfconnect-programmer
    2022-01-25T18:53:51.197Z DEBUG nRFConnect 3.7.2, required by the app is (^3.6.0)
    2022-01-25T18:53:51.197Z DEBUG nRFConnect path: /Applications/nRF Connect.app/Contents/Resources/app.asar
    2022-01-25T18:53:51.197Z DEBUG HomeDir: /Users/alwalker
    2022-01-25T18:53:51.199Z DEBUG TmpDir: /var/folders/gt/fzbprb7j48b7rm6dmdcdx2q00000gn/T/
    2022-01-25T18:53:52.079Z VERBOSE Could not fetch serial number for serial port at /dev/tty.Bluetooth-Incoming-Port
    2022-01-25T18:54:07.148Z INFO Using nrfjprog to communicate with target
    2022-01-25T18:54:08.246Z INFO Using J-Link Software version 7.58
    2022-01-25T18:54:09.121Z INFO Segger serial: 1050072527
    2022-01-25T18:54:09.121Z INFO Segger speed: 2000 kHz
    2022-01-25T18:54:09.121Z INFO Segger version: J-Link OB-nRF5340-NordicSemi compiled Jul 2 2021 10:55:25
    2022-01-25T18:54:09.122Z INFO Core probed: 1050072527
    2022-01-25T18:54:09.122Z INFO Core RAM: 512KiB
    2022-01-25T18:54:09.122Z INFO Core ROM: 1024KiB in pages of 4KiB
    2022-01-25T18:54:09.151Z INFO Device is closed without reset due to app protection
    2022-01-25T18:54:09.152Z INFO Model: NRF5340_xxAA_ENGD.
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to alwalker

    OK I see.

    Could you show me what your DK is printing over serial? Maybe it's giving you error messages.

    You can access this for example in the nRF Connect SDK for VS Code while your device is connected through USB.

    -Einar

  • 0 in reply to Einarh

    Thanks again Einar, I have launched the terminal monitor in nRF Connect SDK for VS Code, but am not seeing USB traffic, what connection and display options should I be using please?

     

  • 0 in reply to alwalker

    In the nRF Connect tab of VS Code you should find a "Connected devices" section.

    There you can choose the COM port of your device, and VS Code will display the serial traffic under "nRF Terminal"

Reply
  • 0 in reply to alwalker

    In the nRF Connect tab of VS Code you should find a "Connected devices" section.

    There you can choose the COM port of your device, and VS Code will display the serial traffic under "nRF Terminal"

Children
  • 0 in reply to Einarh

    There's definitely something not right!

    The terminal window continuously scrolls with the same block:

    *** Booting Zephyr OS build v2.4.0-ncs1-1706-ga89f951e1eb8  ***

    [00:00:00.005,737] <err> os: ***** BUS FAULT *****

    [00:00:00.005,737] <err> os:   Precise data bus error

    [00:00:00.005,737] <err> os:   BFAR Address: 0x20070000

    [00:00:00.005,737] <err> os: r0/a1:  0x21001820  r1/a2:  0x00000001  r2/a3:  0x00000001

    [00:00:00.005,767] <err> os: r3/a4:  0x20070000 r12/ip:  0x2100041c r14/lr:  0x01021cab

    [00:00:00.005,767] <err> os:  xpsr:  0x69000000

    [00:00:00.005,767] <err> os: Faulting instruction address (r15/pc): 0x0101d166

    [00:00:00.005,767] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0

    [00:00:00.005,767] <err> os: Current thread: 0x21001b30 (unknown)

    *** Booting Zephyr OS build v2.4.0-ncs1-1706-ga89f951e1eb8  ***

  • 0 in reply to alwalker

    Oh, that doesn't look good

    Could you try to compile and flash the Heart Rate Monitor Demo in VS Code, and see if you still get these errors?

    -Einar

  • 0 in reply to Einarh

    Hi Einar,

    Thank you for your reply, I can't find the source code files for the Heart Rate Monitor online, just a link for the folder with the two .hex files

                                          Peripheral_Heart_Rate_nRF5340_DK.zip                                     

    Do you have a URL for the application project please?

  • 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:

Terms of service