I am trying to boot from the SD on my AGX-Xavier board. I followed the blog by jetsonhacks.
However I couldn’t get this running on my jetson as it was running on the latest Jetpack, i.e JP4.6 and this blog supports only versions before this.
So I had to modify the /boot/extlinux/extlinux.conf on my eMMC to the below
**************************************************************************************************************************************
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet root=/dev/mmcblk1p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4
# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot
LABEL backup
MENU LABEL backup kernel
LINUX /boot/Image.backup
INITRD /boot/initrd
APPEND ${cbootargs}
**************************************************************************************************************************************
Here I changed from root=/dev/mmcblk0p1 to root=/dev/mmcblk1p1 to enable it to boot from the SD. This settings work, however, when I remove the SD card, it wouldn’t boot from the eMMC.
I understand that there is a LABEL backup, however this didn’t work.
Can you please help, as my data on the SD card is at stake here. Sometimes the SD card fails to boot and I have to remove and insert again by turning the device off. This is costing me so much time and if it fails to boot at all, then I have to flash the whole Jetson board using the SDKmanager to restore it to the default settings. This costs be minimum 2 hours to flash a Jetson board and if I don’t have a backup all my data is gone.
Reset the extlinux.conf file on the emmc back to the original state, so that it now boots from the emmc.
**************************************************************************************************************************************
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4
# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot
LABEL backup
MENU LABEL backup kernel
LINUX /boot/Image.backup
INITRD /boot/initrd
APPEND ${cbootargs}
**************************************************************************************************************************************
Note : i have now changed this to root=/dev/mmcblk0p1, i.e to emmc
Now as suggested above I will configure the boot-configuration and flash it to the emmc using a host PC.
Assuming that I have my SD card still in the Jetson AGX, it should boot up from my SD card.
Is my understanding right?
I have a doubt in the last step. Maybe this is a silly question. Apologies.
When I execute this → sudo ./flash.sh jetson-xavier mmcblk0p1, will any of the data on the jetson be lost.
I tried changing the boot-order and flashed the jetson. But no luck.
Current situation
I have mounted the SD card by mentioning the same configuration root=/dev/mmcblk1p1 in the extlinux.conf file. Everything works fine and boots from the SD card.
I removed the SD card and booted the Jetson, but then it wouldn’t boot from the emmc. I get the below error message and it wouldn’t boot any further.