Hey noob here. So my issue is that I have an Advantech MIC-733-AO6A1which contains an AGX Orin 64GB module. Now after some long and difficult searching I was able to find the BSP (6.1) they provide for the AO6A1 and was able to successfully install it (onto the EMMC) using their provided flash.sh script. Naturally I tried to install it onto the NVME (1TB SN850X WD_BLACK) for more space. After “successfully” (who knows if I can really even call it successful) installing it and booting into it I decided to reboot (NVME installation). After rebooting into the NVME however it would only show a black screen. The EMMC installation works fine still. So basically I can flash L4T onto the NVME and boot into it ONLY once. If I attempt to reboot back into it I am met with a black screen and am forced to flash it again. Here is the command I used to flash onto the NVME.
Any insight or suggestions are greatly appreciated since I am a complete noob to the Jetson environment. My goal is to be able to use the NVME as the main storage device since the internal EMMC is very limited. Any information I can provide or that would be helpful just let me know and I will try my best to upload it. Thanks
*** Please note that this reply is generated by LLM automatically ***
I’d be happy to help you troubleshoot the issue with your Jetson AGX Orin module.
Firstly, congratulations on successfully installing the BSP 6.1 on the eMMC and NVMe storage devices. However, it’s concerning that you’re experiencing a black screen after rebooting from the NVMe installation.
Based on the command you provided, it seems like you’re using the l4t_initrd_flash.sh script to flash the L4T image onto the NVMe device. The command looks correct, but there might be some underlying issues that are causing the problem.
Here are a few potential causes and suggestions to help you troubleshoot:
UEFI Boot Order: Ensure that the UEFI boot order is set to prioritize the NVMe device. You can check the UEFI settings by pressing the corresponding key (usually F2, F12, or Del) during boot-up. Make sure that the NVMe device is set as the first boot device.
NVMe Device Configuration: Verify that the NVMe device is properly configured in the UEFI settings. Check that the device is recognized and configured correctly.
L4T Image Configuration: Double-check that the L4T image is configured to use the NVMe device as the root file system. You can do this by checking the flash_l4t_t234_nvme.xml file, which should contain the correct configuration for the NVMe device.
Device Tree Configuration: Ensure that the device tree configuration is correct for the NVMe device. You can check the flash_t234_qspi.xml file, which should contain the correct configuration for the NVMe device.
Firmware Issues: It’s possible that there are firmware issues with the NVMe device. Try updating the firmware to the latest version.
Power Management: Some NVMe devices have power management issues that can cause problems during boot-up. Try disabling power management for the NVMe device in the UEFI settings.
Bootloader Configuration: Verify that the bootloader configuration is correct for the NVMe device. You can check the bootloader/generic/cfg/flash_t234_qspi.xml file, which should contain the correct configuration for the NVMe device.
To help you further, I’d like to know more about your setup and the exact error messages you’re seeing. Please provide the following information:
The exact command you used to flash the L4T image onto the NVMe device
The output of the l4t_initrd_flash.sh script during the flashing process
The UEFI settings for the NVMe device
The device tree configuration for the NVMe device
Any error messages you’re seeing during boot-up
Additionally, you can try the following:
Try flashing the L4T image onto the NVMe device using the flash.sh script instead of l4t_initrd_flash.sh.
Try booting from the NVMe device using the bootloader/generic/cfg/flash_t234_qspi.xml file instead of the flash_l4t_t234_nvme.xml file.
Try disabling the eMMC device in the UEFI settings to ensure that the NVMe device is the only boot device.
I hope this helps you troubleshoot the issue. If you have any further questions or need more assistance, feel free to ask.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
After going back through my web searches I decided to try this version of the command which at first did not work until I tried the AI suggestion to add the “-- external-only” flag. I have been struggling to get this working for more than 2 weeks now but after much trial and error I have finally figured it out! Shoutout to the suggestions from carolyuu otherwise I would not have tried to disable the EMMC which is what led me to this final command.