• State Not Answered
  • Replies 19 replies
  • Subscribers 87 subscribers
  • Views 1402 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 352342
Options

nRF9151 custom board – GNSS sample fails with “Failed to activate GNSS functional mode”

Arun538

Hi Nordic Team,

I have developed a custom board using the nRF9151 controller.
I am testing the GNSS sample from nRF Connect SDK v3.0.0.
When I flash and run the firmware, I see the following output in RTT Viewer:

Hardware Details:

  • SoC: nRF9151

  • Board: Custom design (based on nRF9151 DK reference)

Software Details:

  • nRF Connect SDK: v3.0.0

  • Toolchain: nRF Connect for VS Code

  • Sample Used: nrf/samples/nrf9160/gnss

  • Build target: nrf9151dk_nrf9151

    How can I solve this issue?


Best regards

Arun

  • 0 in reply to Arun538

    Hi Arun,

    Arun538 said:
    When I run the unmodified GNSS sample, I don’t see any logs in the RTT Viewer.

    If you do not modify the sample, you can use your terminal emulator program to connect to available COM port to see the output.

    Best regards,
    Dejan

  • 0 in reply to dejans

    Hi Dejan,

    I tried connecting to all the available COM ports using different terminal programs (like PuTTY, serial terminal and Tera Term), but I’m still not getting any serial output from my custom nRF9151 board. That’s why I switched to RTT Viewer to check if any logs were available.

  • 0 in reply to dejans

    Hi Dejan,

    Can we please connect on a call? I’m running behind schedule and really need to complete this project.
    Please help me when you’re available — I’ll be available until 10 PM (India time).

    Thank you for your support.

    Best regards,
    Arun

  • 0 in reply to Arun538

    Hi Arun,

    Maybe you have older version of nRF52-dk. Your nrf52-dk should have nrf5340 on it. You could try to program your board using either newer nrf52-dk or for example nrf9151-dk.

    Best regards,
    Dejan

  • 0 in reply to dejans

    Hi Dejan,

    When I try to connect my custom board to the NRF52 DK, it connects and I am able to upload code.

    15:09:08.717	Using nrfutil device to communicate with target via JLink
15:09:08.717	JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Jul 8 2025 10:15:34
15:09:08.717	Device family NRF52_FAMILY
15:09:08.717	Device version NRF9151_xxCA_REV3
15:09:08.717	Board version PCA10040
15:09:08.903	Reading readback protection status for Application core
15:09:08.904	Reading readback protection status for Application core 0%
15:09:08.905	Reading readback protection status for Application core 100%
15:09:08.905	Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
15:09:08.906	Reading readback protection status for Application core completed
15:09:09.142	Loading core information for Application core
15:09:09.143	Loading core information for Application core 0%
15:09:09.143	Loading core information for Application core 100%
15:09:09.145	Loading core information for Application core completed
15:09:09.629	Reading readback protection status for Application core
15:09:09.629	Reading readback protection status for Application core 0%
15:09:09.631	Reading readback protection status for Application core 100%
15:09:09.631	Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
15:09:09.631	Reading readback protection status for Application core completed
15:09:09.682	Device is loaded and ready for further operation


    However, when I try to connect my custom board to the NRF9151 DK, it does not connect and shows this error.

    15:14:04.396	Initialising the bundled nrfutil device
15:14:04.555	Using the bundled core version for nrfutil device: 8.0.0
15:14:04.583	Using nrfutil-device version: 2.12.3
15:14:04.584	Using nrf-device-lib version: 0.17.81
15:14:04.584	Using nrf-probe version: 0.40.1
15:14:04.584	Using JLink version: JLink_V8.76
15:14:04.584	Your version of SEGGER J-Link (8.76) is newer than the one this app was tested with (8.18). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.
15:14:04.601	Getting serial port options from the persistent store for 001051231268.pc-nrfconnect-programmer
15:14:04.602	Device connected with the serial number 001051231268
15:14:06.422	Selecting device with the serial number 001051231268
15:14:06.801	Error: Failed with exit code 1. One or more device info tasks failed: * 1051231268: Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)). This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn't disabled (Generic) Message: Operation device-info failed, Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)). This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn't disabled.
15:14:06.801	Selected device with the serial number 001051231268
15:14:06.802	Using nrfutil device to communicate with target via JLink
15:14:07.085	Reading readback protection status for Application core
15:14:07.086	Reading readback protection status for Application core 0%
15:14:07.211	Failed "reading readback protection status for application core". Error: code: 1, description: Generic, message: Batch task protection-get failed, Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)). This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn't disabled
15:14:07.228	Error: Failed with exit code 1. One or more batch tasks failed: * 1051231268: Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)). This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn't disabled (Generic) Message: Batch task protection-get failed, Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)). This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn't disabled.
15:14:07.228	Error: Failed with exit code 1. One or more batch tasks failed: * 1051231268: Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)). This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn't disabled (Generic) Message: Batch task protection-get failed, Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown Error in J-Link DLL (error code =-1)). This might indicate that the debug port is unavailable. Please double-check device power supply and SWD lines, and that SWD isn't disabled.

    Best regards,
    Arun

Related
Terms of service