Skip to main content

nRF93M1 Onboarding

The nRF93M1 runs the nRF Cloud client in the module firmware. You can onboard it using AT commands over the module's serial interface, without building a host application that includes a cloud library. The device proves its identity with a registration JSON Web Token (JWT), signed with a private key that never leaves the device.

For nRF9151 and nRF9161 devices, see nRF91 Series Onboarding.

Before you begin​

  • Supported hardware: nRF93M1.
  • Device: An nRF93M1 DK, with the supplied LTE antenna attached and the supplied SIM inserted.
  • Account: An nRF Cloud account with access to your organization's default project. nRF93M1 onboarding is available only from the default project. You cannot onboard an nRF93M1 to a non-default project.
  • Tools: nRF Util and the Serial Terminal app from nRF Connect for Desktop.
  • Device firmware: Module firmware v1.5.0 or later, which supports the %REGJWT command. Run AT+CGMR to check the installed version. No host firmware changes are required.
  • Network: A working LTE network connection.

Connect USB1 on the DK to your computer, then identify the AT command port:

nrfutil device list

In Serial Terminal, open the vcom1 port at 115200 bps. This is the port that communicates with the module. Enter AT and confirm that the module returns OK.

For more about the nRF93M1, see the nRF93M1 guide in the nRF Connect SDK documentation.

Device identity​

The module provides the following identities and credentials:

CommandWhat it returns
AT%DEVICEUUIDA 36-character device UUID, generated once and stored in non-volatile memory. This becomes the device ID in nRF Cloud.
AT%CLOUDACCESSKEYThe device's P-256 ECC public key in Base64-encoded DER format. The corresponding private key never leaves the device.
AT%REGJWTA signed registration JWT used for onboarding. The JWT contains the device UUID, so you do not need to enter the ID separately.
AT%JWTA short-lived authentication JWT for accessing cloud APIs after onboarding.
important

AT%REGJWT and AT%JWT serve different purposes. Use the registration JWT from AT%REGJWT in the onboarding wizard. The device's system time does not need to be set to generate a registration JWT.

How to add a device​

  1. In nRF Cloud, open your organization's default project.

  2. Go to Fleet → Devices.

  3. Select Add devices.

  4. Select nRF93M1, then select Continue.

    Device chooser with nRF93M1 selected

  5. On the Get Device Credentials step, copy the complete AT%REGJWT command. The command already includes your team ID.

    Get Device Credentials step showing where to copy the AT%REGJWT command

  6. Run the command in the serial terminal. The module returns the registration JWT:

    AT%REGJWT="<team-id>"
    %REGJWT: eyJhbGciOiJFUzI1NiJ9.eyJzdWIiOiJkZXZpY2UtaWQifQ.invalid-signature
    OK

    The command copied from the wizard contains your actual team ID instead of <team-id>.

  7. Copy only the token after %REGJWT:.

  8. Return to the nRF Cloud onboarding wizard and select Continue.

  9. On the Input Device Credentials step, select Manual, paste the registration JWT into the JWT token field, then select Continue. The wizard reads the device ID from the JWT.

    Input Device Credentials step with a registration JWT entered on the Manual tab

  10. On the Review step, check the device information, then select Continue to add the device.

nRF Cloud opens the device's details page once the device is available. This can take a few seconds. If the device does not appear in time, nRF Cloud opens the Devices list instead.

After onboarding​

Confirm that the device appears under Fleet → Devices. The device is now provisioned and authenticated.

To rename devices or move them between cohorts, see Edit and organize devices.

Troubleshooting​

  • The registration JWT is rejected. Confirm that you copied only the token after %REGJWT: and that you used the complete AT%REGJWT command shown in the wizard for the current team.
  • AT%REGJWT returns an error. Confirm that you copied the complete command from the wizard and that the team ID is enclosed in double quotation marks. Run AT+CGMR and verify that the module firmware is v1.5.0 or later.
  • The device does not appear after onboarding. Newly added devices can take a few seconds to appear. Wait, then reload the Devices list.
  • The wizard reports that the organization is not linked to nRF Cloud. You cannot add devices until an admin links the organization to nRF Cloud. The Get Device Credentials step also cannot fill in your team ID until then. Contact your organization admin.