Creating a Jetson Orin Nano Dev Board Environment Without Default User Account

Issue Overview

Users, particularly manufacturers of carrier boards, are encountering challenges when attempting to create a custom environment for the Nvidia Jetson Orin Nano Dev board. The primary issue revolves around the creation of a default user account during the setup process using the SDK manager. This default account is automatically generated and becomes the login credentials upon system boot-up. However, some users desire to create an environment without any pre-configured accounts, allowing end-users to set up their own credentials during the first boot.

Possible Causes

1. Outdated SDK Version: Some older releases of the L4T (Linux for Tegra) SDK, specifically versions R28.x and earlier, included default user accounts.

2. Misunderstanding of Current BSP Behavior: There seems to be confusion about the default behavior of the current BSP (Board Support Package), which actually does not provide a default account.

3. Custom Script Execution: The use of a specific script (l4t_create_default_user.sh) on the host PC during the setup process may be creating an unexpected default user account.

4. Incorrect SDK Manager Configuration: Users might be inadvertently selecting options in the SDK manager that lead to the creation of a default account.

Troubleshooting Steps, Solutions & Fixes

1. Verify L4T Version:

   • Check your current L4T release version by running the following command on your Jetson device:

     head -n 1 /etc/nv_tegra_release
     

   • Ensure you are using a recent version of L4T, as versions after R28.x do not include default accounts.

2. Reinstall Sample Rootfs:
   If you suspect that a default user account was created unintentionally, follow these steps:

   • Delete the existing rootfs directory:

     sudo rm -rf Linux_for_Tegra/rootfs/
     

   • Reapply the binaries:

     sudo ./apply_binaries.sh
     

   • Flash the system again. This should result in a setup without any default username or password.

3. Avoid Custom User Creation Scripts:

   • Do not run the l4t_create_default_user.sh script on your host PC during the setup process, as this creates a default user account.

4. Use Latest SDK Manager:

   • Ensure you are using the most recent version of the SDK Manager, as older versions might have different default behaviors.
   • During the SDK Manager setup process, carefully review all options and avoid selecting any that might create a default user account.

5. Custom First Boot Setup:

   • To allow users to set up their own credentials on first boot, you may need to implement a custom first-boot script or service.
   • This script should prompt the user to create their account and set up initial system configurations.
   • Consider using tools like cloud-init or creating a custom systemd service that runs on first boot to handle user creation.

6. Consult Official Documentation:

   • Review the latest Nvidia Jetson documentation for any specific instructions on creating custom environments without default accounts.
   • Look for any recent updates or changes in the BSP that might affect user account creation.

7. Community Support:

   • If the issue persists, consider reaching out to the Nvidia Jetson developer community or official support channels for more specific guidance tailored to your use case.

Remember that recent versions of the Jetson BSP do not include default user accounts due to security considerations and compliance with regulations like California law. If you’re experiencing default account creation, it’s likely due to a specific configuration or script being used in your setup process.