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

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

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?

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

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

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?

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"

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

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

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

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?

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?

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:

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.