Refer to this section for nRF Util device and trace troubleshooting
tips.
- nRF52840 dongle not found
- The dongle is listed with the trait nordicDfu. If not found, put it into
programming mode by holding in the reset button and reconnecting the dongle to the
system.
- Nordic Thingy:91™ not found
- When programming the application firmware for the nRF9160 System in Package (SiP) of a Nordic Thingy:91, make sure that you build the application for the nRF9160
SiP, and put the Nordic Thingy:91 in
application serial recovery mode by holding in the SW3 button
while powering it off and on. If
nrftil device fails with a timeout error during the erase step, put it
into application serial recovery mode using the previous procedure.
Note: The device can become unusable if, while programming, you use the wrong button and put it into
the application serial recovery mode for the nRF52840
System on Chip (SoC). In
this case, it no longer appears in
nrfutil device list, and you must
reprogram the nRF52 connectivity bridge firmware from the Nordic Thingy:91 download page through the
external debug probe of the nRF9160
Development Kit (DK). See the programming
instructions in
Thingy:91 firmware images.
- Nordic Thingy:53™ not found
- If the Nordic Thingy:53 device does not show
up, put it in application serial recovery mode by holding in the SW2 button while
powering the device off and on. You can verify that the Nordic Thingy:53 is in bootloader mode by running
nrfutil device list
--json and verifying that the product name of the device is Bootloader
Thingy:53.
- No output when tracing
-
- Make sure that your modem firmware is up to date:
- Check that your device’s application has modem tracing enabled.
- Note that the KConfig flag for modem tracing varies depending on nRF Connect SDK version.
- Check the serial port used for trace. Normally the serial port with the
highest VCOM value should be chosen. Make sure that your application does not allocate
this serial port for anything else.