nRF53 PDK/ peripheral_uart

[KentOverton]

So ...

I'm still trying to get peripheral_uart running.

I'm using a nRF53 PDK (PCA 10095 - rev 0.8.0) (I've received two 0.11.0 boards, both of which died).

I'm using SDK 1.5.0

I've done the following.

Using ses I loaded and compiled zephyr/samples/bluetooth/hci_rpmsg as nrf5340pdk_nrf5340_cpunet. It compiles with no problems, but can't be loaded via target-> Download zephyr/zephyr.elf.

I've attached the ses log to this message as log1.txt.

I am able to download zephyr.hex o the board via NRF CONNECT->PROGRAMMER

I've attached the PROGRAMMER log as log2.txt.

Using ses I loaded and compiled peripheral_uart as nrf5340pdk_nrf5340_cpuappns. It compiles fine. When I start a debug session it fires up nicely - I've attached the debug output as log3.txt. Note that there is a warning message.

The advertising led flashes, I can see the board from my phone using the nRF Toolbox Uart app. When I try to connect the log on the phone shows it connecting, then disconnecting.

Any help would be appreciated.

Fullscreen 7652.log2.txt Download

2021-04-13T09:33:24.383Z INFO Application data folder: C:\Users\kover\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2021-04-13T09:33:24.602Z DEBUG App pc-nrfconnect-programmer v1.4.8 official
2021-04-13T09:33:24.602Z DEBUG App path: C:\Users\kover\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2021-04-13T09:33:24.603Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-04-13T09:33:24.603Z DEBUG nRFConnect path: C:\Users\kover\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-04-13T09:33:24.603Z DEBUG HomeDir: C:\Users\kover
2021-04-13T09:33:24.606Z DEBUG TmpDir: C:\Users\kover\AppData\Local\Temp
2021-04-13T09:33:24.682Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-04-13T09:33:32.127Z INFO Using nrfjprog to communicate with target
2021-04-13T09:33:33.283Z INFO Using J-Link Software version 6.88
2021-04-13T09:33:34.368Z INFO Segger serial:  960125438
2021-04-13T09:33:34.368Z INFO Segger speed:  2000  kHz
2021-04-13T09:33:34.368Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-04-13T09:33:34.369Z INFO Core probed: 960125438
2021-04-13T09:33:34.369Z INFO Core RAM: 512KiB
2021-04-13T09:33:34.369Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-04-13T09:33:34.617Z INFO Model: NRF5340_xxAA_ENGA.
2021-04-13T09:33:36.924Z INFO Segger serial:  960125438
2021-04-13T09:33:36.924Z INFO Segger speed:  2000  kHz
2021-04-13T09:33:36.925Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-04-13T09:33:36.927Z INFO Core probed: 960125438:1
2021-04-13T09:33:36.928Z INFO Core RAM: 64KiB
2021-04-13T09:33:36.928Z INFO Core ROM: 256KiB in pages of 2KiB
2021-04-13T09:33:38.388Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-04-13T09:33:39.668Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-04-13T09:33:39.785Z INFO Core1: Reading device non-volatile memory. This may take a few seconds.
2021-04-13T09:33:41.191Z INFO Core1: UICR has been read. Click read button to read full non-volatile memory.
2021-04-13T09:34:14.328Z INFO Using nrfjprog to communicate with target
2021-04-13T09:34:15.445Z INFO Using J-Link Software version 6.88
2021-04-13T09:34:16.586Z INFO Segger serial:  960125438
2021-04-13T09:34:16.586Z INFO Segger speed:  2000  kHz
2021-04-13T09:34:16.586Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-04-13T09:34:16.587Z INFO Core probed: 960125438
2021-04-13T09:34:16.587Z INFO Core RAM: 512KiB
2021-04-13T09:34:16.587Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-04-13T09:34:16.841Z INFO Model: NRF5340_xxAA_ENGA.
2021-04-13T09:34:19.342Z INFO Segger serial:  960125438
2021-04-13T09:34:19.342Z INFO Segger speed:  2000  kHz
2021-04-13T09:34:19.343Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-04-13T09:34:19.343Z INFO Core probed: 960125438:1
2021-04-13T09:34:19.343Z INFO Core RAM: 64KiB
2021-04-13T09:34:19.344Z INFO Core ROM: 256KiB in pages of 2KiB
2021-04-13T09:34:20.813Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-04-13T09:34:31.121Z INFO Core0: Non-volatile memory has been read. 5 non-empty memory blocks identified 
2021-04-13T09:34:31.239Z INFO Core1: Reading device non-volatile memory. This may take a few seconds.
2021-04-13T09:34:35.072Z INFO Core1: Non-volatile memory has been read. 2 non-empty memory blocks identified 
2021-04-13T09:34:50.828Z INFO Parsing HEX file:  C:\Users\kover\ncs\v1.5.0\zephyr\samples\bluetooth\hci_rpmsg\build_nrf5340pdk_nrf5340_cpunet\zephyr\zephyr.hex
2021-04-13T09:34:50.857Z INFO File was last modified at  4/13/2021, 4:54:53 AM
2021-04-13T09:38:26.607Z INFO Does not need to be reloaded:  C:\Users\kover\ncs\v1.5.0\zephyr\samples\bluetooth\hci_rpmsg\build_nrf5340pdk_nrf5340_cpunet\zephyr\zephyr.hex
2021-04-13T09:38:26.608Z INFO Writing procedure starts for core0
2021-04-13T09:38:26.626Z INFO Writing procedure starts for core1
2021-04-13T09:38:43.168Z INFO Write procedure finished
2021-04-13T09:38:43.176Z INFO Using nrfjprog to communicate with target
2021-04-13T09:38:44.268Z INFO Using J-Link Software version 6.88
2021-04-13T09:38:45.390Z INFO Segger serial:  960125438
2021-04-13T09:38:45.390Z INFO Segger speed:  2000  kHz
2021-04-13T09:38:45.391Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-04-13T09:38:45.391Z INFO Core probed: 960125438
2021-04-13T09:38:45.391Z INFO Core RAM: 512KiB
2021-04-13T09:38:45.392Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-04-13T09:38:45.649Z INFO Model: NRF5340_xxAA_ENGA.
2021-04-13T09:38:47.955Z INFO Segger serial:  960125438
2021-04-13T09:38:47.955Z INFO Segger speed:  2000  kHz
2021-04-13T09:38:47.955Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-04-13T09:38:47.956Z INFO Core probed: 960125438:1
2021-04-13T09:38:47.956Z INFO Core RAM: 64KiB
2021-04-13T09:38:47.956Z INFO Core ROM: 256KiB in pages of 2KiB
2021-04-13T09:38:49.344Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-04-13T09:38:50.598Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-04-13T09:38:50.715Z INFO Core1: Reading device non-volatile memory. This may take a few seconds.
2021-04-13T09:38:52.192Z INFO Core1: UICR has been read. Click read button to read full non-volatile memory.
2021-04-13T09:39:13.465Z INFO Using nrfjprog to communicate with target
2021-04-13T09:39:14.608Z INFO Using J-Link Software version 6.88
2021-04-13T09:39:15.671Z INFO Segger serial:  960125438
2021-04-13T09:39:15.671Z INFO Segger speed:  2000  kHz
2021-04-13T09:39:15.671Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-04-13T09:39:15.674Z INFO Core probed: 960125438
2021-04-13T09:39:15.674Z INFO Core RAM: 512KiB
2021-04-13T09:39:15.674Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-04-13T09:39:15.928Z INFO Model: NRF5340_xxAA_ENGA.
2021-04-13T09:39:18.300Z INFO Segger serial:  960125438
2021-04-13T09:39:18.300Z INFO Segger speed:  2000  kHz
2021-04-13T09:39:18.300Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-04-13T09:39:18.301Z INFO Core probed: 960125438:1
2021-04-13T09:39:18.301Z INFO Core RAM: 64KiB
2021-04-13T09:39:18.301Z INFO Core ROM: 256KiB in pages of 2KiB
2021-04-13T09:39:19.752Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-04-13T09:39:30.097Z INFO Core0: Non-volatile memory has been read. 5 non-empty memory blocks identified 
2021-04-13T09:39:30.219Z INFO Core1: Reading device non-volatile memory. This may take a few seconds.
2021-04-13T09:39:33.960Z INFO Core1: Non-volatile memory has been read. 2 non-empty memory blocks identified 

Fullscreen log1.txt Download

Connecting �J-Link� using �USB�
Connecting to target using SWD
Loaded C:/Users/kover/ncs/v1.5.0/toolchain/segger_embedded_studio/bin/JLink_x64.dll
Firmware Version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
DLL Version: 6.94a
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF5340_XXAA_NET" selected.
ConfigTargetSettings() start
ConfigTargetSettings() end
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: AHB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
AP[3]: MEM-AP (IDR: Not set)
AP[1]: Core found
AP[1]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
Found Cortex-M33 r0p4, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: not implemented
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33
ROMTbl[0][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT
ROMTbl[0][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB
ROMTbl[0][6]: E0042000, CID: B105900D, PID: 000BBD21 CSS600-CTI
Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
ResetTarget() start
ResetTarget() end
Downloading �zephyr.elf� to J-Link
Programming 174.5 KB of addresses 01000000 � 0102ba23
Programming 1.3 KB of addresses 0102ba24 � 0102bfbb
T-bit of XPSR is 0 but should be 1. Changed to 1.
Timeout while preparing target, RAMCode did not respond in time. (PC = 0x00000000, CPSR = 0x00000000, LR = 0x61000003)!
Failed to prepare RAMCode using RAM
Failed to download application.
Generic error.
Please check J-Link and target connection.
Illegal value 0x21009F90 written to register 67 (PSP_NS) ignored

Fullscreen 0045.log3.txt Download

[00:00:00.007,110] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.007,141] <inf> fs_nvs: alloc wra: 0, fd8
[00:00:00.007,141] <inf> fs_nvs: data wra: 0, 1c
[00:00:00.034,576] <wrn> bt_hci_core: ECC HCI commands not available
[00:00:00.034,606] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.034,606] <inf> peripheral_uart: Bluetooth initialized

[Kenneth]

Hi,

Sorry, but please check out: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.0/nrf/ug_nrf5340.html# 

"The nRF5340 PDK has been deprecated with the introduction of the production-level nRF5340 DK. To determine if you have a PDK or DK, check the version number on the sticker on your kit. If the version is 0.11.0 or higher, the kit is an nRF5340 DK."

If you want to use nRF5340 PDK you need to use NCS v1.4, but it is not recommended to continue working with the PDK (or v1.4) for the nRF5340.

Kenneth

[AndreHarris]

Kenneth, can you please close this ticket.  We are going to get Martin transitioned from PDKs to DKs.