Issues programming nRF5340 on a Custom Board

RE: Issues programming nRF5340 on a Custom Board

Øyvind — Thu, 25 Mar 2021 07:24:31 GMT

Then my next question is why you are connecting to the device using Cortex-M4, the nRF53 is a Cortex-M33. Please change the device to corresponding device:

Here is my output from J-Link Commander, connected to Debug-In on the nRF5340 DK:

SEGGER J-Link Commander V6.96 (Compiled Feb 19 2021 09:57:05)
DLL version V6.96, compiled Feb 19 2021 09:55:51

Connecting to J-Link via USB...O.K.
Firmware: J-Link V11 compiled Feb  4 2021 12:59:17
Hardware version: V11.00
S/N: 821002299
License(s): GDB
VTref=3.038V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: NRF5340_XXAA_APP
Type '?' for selection dialog
Device>
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "NRF5340_XXAA_APP" selected.


Connecting to target via SWD
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[0]: Core found
AP[0]: 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: implemented
Secure debug: enabled
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][3]: E0000000, CID: B105900D, PID: 000BBD21 ITM
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 002BBD21 ETM
ROMTbl[0][6]: E0042000, CID: B105900D, PID: 000BBD21 CSS600-CTI
Cortex-M33 identified.

RE: Issues programming nRF5340 on a Custom Board

RPDben — Wed, 24 Mar 2021 15:29:56 GMT

No, I only received the board today. I am running at +3V and have verified the board is powered (caps around the nRF53 are at +3V) and also that the VTref on J-Link Commander is reading +3V.

The schematic and board layout have been reviewed by a Nordic engineer.

Thanks!

RE: Issues programming nRF5340 on a Custom Board

Øyvind — Wed, 24 Mar 2021 15:09:06 GMT

Have you been able to program the board before? What voltage are you running, and have you verified that the board is powered? Have you had any review of the board layout?
-Øyvind

RE: Issues programming nRF5340 on a Custom Board

RPDben — Wed, 24 Mar 2021 14:08:40 GMT

Hi Øyvind,

I am using a Segger J-Link v11.0, this is connected to the board via a TAG-Connect cable wired to SWD.

Thanks,

Ben

RE: Issues programming nRF5340 on a Custom Board

Øyvind — Wed, 24 Mar 2021 14:07:10 GMT

Hi Ben,

What are you using to program the custom board? How are you connecting the custom board to the programmer?

Kind regards,
Øyvind