Unable to flash nrf9160 - is my design correct?

[galook]

Hello,

I have designed this schematic according to reference designs provided by Nordic Semi, however I might have failed as I am unable to flash the main module. I should mention I am a beginner, however not a complete beginner, as I've created functioning PCBs in the past.

I am flashing it using the nrf9161DK via SPI and I am sure the connections are correct. Still, the Programmer app of Nordic SDK doesnt recognize the new board with the nrf9160

Below is the schematic:

Thank you for your help

Matej Holubec

[mathiaso]

Hi, Matej.

When using the nRF9161 DK to program an external board, you should use the SWD connection, as described in the nRF9161 DK's documentation.

If you want to perform DFU on your board using a connection different from SWD, you should check out the Bootloaders and DFU lesson in DevAcademy.

Best regards,
Mathias

[galook]

Yes, sorry I used the wrong term. Of course I used the SWD connectors, in my design headers SWDCLK1 and SWDIO1. What I'd like to know if there is a flaw in this schematic that would explain why it does not work

[mathiaso]

Nothing to worry about, Matej.

galook said:

In my design, I'm connecting them to the same names as on the DK, with the only difference of VTG => 3V3

But VDD and VTG on the DK are still connected to the same net, right?

[galook]

To be honest I don't fully understand your question - are you asking about how the Nordic product is wired? I'd guess the answer to your question is yes - and both should provide nice power supply to the board being programmed. However I'm already using VTG and my board that's being programmed seems unresponsive.

[mathiaso]

I'm sorry if I was unclear, Matej. I was just referring to VDD and VTG on the DK being connected to the same VDD net on your custom board, as shown in the documentation.

Do you get the same error when using nrfutil?

nrfutil device erase --serial-number <serial_number>

And then program the device using

nrfutil device program --serial-number <serial_number> --firmware /path/fw.hex

You could also try to recover your board.

nrfutil device recover --core Network
nrfutil device recover

[galook]

I can confirm my connection is the exact same as on the picture you attached.

Here is the output from the commands provided:

PS C:\Users\matej\Downloads> ./nrfutil device erase --serial-number 1050987041
❌ Failed to erase 1050987041, Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (erro
Error: One or more erase tasks failed:
 * 1050987041: Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic)
 
 PS C:\Users\matej\Downloads> ./nrfutil device recover --core Network
❌ Failed to recover 1050987041, Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (er
Error: One or more recover tasks failed:
 * 1050987041: Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic)

PS C:\Users\matej\Downloads> ./nrfutil device recover
❌ Failed to recover 1050987041, Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (er
Error: One or more recover tasks failed:
 * 1050987041: Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic)

And here is the ouput of the device list:

PS C:\Users\matej\Downloads> ./nrfutil device list
1050987041
Product         J-Link
Board version   PCA10153
Ports           COM6, vcom: 0
                COM5, vcom: 1
Traits          usb, boardController, seggerUsb, devkit, modem, serialPorts, jlink

Supported devices found: 1

[mathiaso]

Thank you, Matej.

You are able to flash the DK itself when the custom board isn't connected to it?

Have you tried powering the custom board externally, rather than from the DK?