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

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

alwalker — Mon, 07 Feb 2022 15:57:59 GMT

Thank you very much Einar, I think we can close this case now.

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

Einarh — Mon, 07 Feb 2022 14:48:51 GMT

yes that sounds like expected behavior, glad to hear the update fixed your issue.

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

alwalker — Mon, 07 Feb 2022 13:18:37 GMT

Thanks Einar, that's a lot more successful.

I have two nRF5340 DK modules, labelled 1 and 2. This was the order that I originally tried them with Programmer.

The following was performed with Programmer official V2.3.1

Module 2 was tried first.

An Erase and then a Write was done with the two .hex files

Reset button pressed.

On nRF Toolbox on my iPad, I selected Heart Rate and then Connect

On the first connection the nRF5340 DK appeared as N/A which I selected. On subsequent connections it appears correctly as Zephyr Heartrate Monitor.

The Heart rate cycled between 90 BPM and 159 BPM in 1 BPM increments. Initially the graph line does not appear on the X-Y graph display, but does after perhaps 30 seconds and continues to do so.

The battery shows a numerical percentage value which does not change, variously 54%, 40% and 84% for each of the connection sessions. Note that the onboard Li-ion battery is not in-circuit with the shipping tab insulator still in place.

nRF Connect for Desktop was restarted and Module 1 was connected.

An Erase and then a Write was done with the two .hex files

Reset button pressed.

On nRF Toolbox on my iPad, I selected Heart Rate and then Connect

On the first connection the nRF5340 DK appeared as Nordic_HR which I selected. On subsequent connections it appears correctly as Zephyr Heartrate Monitor.

The Heart rate cycled between 90 BPM and 159 BPM in 1 BPM increments. Initially the graph line does not appear on the X-Y graph display, but does after perhaps 30 seconds and continues to do so.

The battery shows a numerical percentage value which does not change, showing 65%, 65% and 62% for each of the connection sessions. Note that the onboard Li-ion battery is not in-circuit with the shipping tab insulator still in place.

Is this all the expected behaviour please?

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

Einarh — Mon, 07 Feb 2022 10:09:07 GMT

Hello!

There is a new update to the programmer app available that I believe should fix the issue related to the nRF53.

Could you try downloading the new update and see if it fixes your issue?

Best regards,

Einar

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

alwalker — Thu, 03 Feb 2022 09:53:28 GMT

Hello Einar,

I've raised another ticket for the issues I've encountered with following the introductory videos:

https://devzone.nordicsemi.com/f/nordic-q-a/84319/nrf-connect-for-vs-code-youtube-videos-having-problems-with-include-paths-and-kconfig-in-mac-os

Kind regards,

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

alwalker — Sun, 30 Jan 2022 10:21:47 GMT

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?

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

alwalker — Fri, 28 Jan 2022 13:31:25 GMT

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

# 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

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

Einarh — Fri, 28 Jan 2022 10:26:34 GMT

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.

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

alwalker — Fri, 28 Jan 2022 10:26:31 GMT

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:

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

alwalker — Fri, 28 Jan 2022 09:32:49 GMT

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?

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

alwalker — Fri, 28 Jan 2022 09:28:12 GMT

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?

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

Einarh — Fri, 28 Jan 2022 08:45:37 GMT

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

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

alwalker — Thu, 27 Jan 2022 16:14:20 GMT

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 ***

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

Einarh — Thu, 27 Jan 2022 12:42:43 GMT

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"

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

alwalker — Thu, 27 Jan 2022 12:22:41 GMT

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?

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

Einarh — Thu, 27 Jan 2022 09:26:50 GMT

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

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

alwalker — Wed, 26 Jan 2022 16:46:56 GMT

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

devzone.nordicsemi.com/.../2022_2D00_01_2D00_25T18_5F00_53_5F00_50.846Z_2D00_log.txt

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

Einarh — Wed, 26 Jan 2022 13:29:06 GMT

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

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

alwalker — Wed, 26 Jan 2022 10:39:34 GMT

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?

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

Einarh — Tue, 25 Jan 2022 13:21:42 GMT

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:

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).
After starting nRF Connect for Desktop 3.7 a prompt will come up about an available upgrade. Click “No” on this.
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”.
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”.
Install the apps you need in the old versions and use them.

Best regards,

Einar