My Jetson hardware was working fine for 2 weeks, but all of a sudden it is having booting issue, even though the flashing is successful from the host PC.
Please find the image for more details:
Please let me know , what could be the root cause all of a sudden,
Note: I am following the same kernel build and flashing process.
I am updating some dtsi files for configuring my CANs , GPIOS and I2S audio related interfaces. Is there any chance this is causing any problem?
I tried loading my old working image file/dtb files/ cfg file, but still the boot issue pertains. But if we replace this SOM module and put another SOM module on the same customized carrier board, it boots fine. so we are clear that the issue is with the SOM module.
sorry I am not in a position to get the boot log now urgently, will try to provide later.
but need to fix this boot issue as soon as possible. Kindly request you to let me know if you have any vague idea why booting is stopping in the middle. Thanks.
Thanks for the info.
I assume this problem started appearing after:
I executed flash command to flash only my. DTB file passing it as parameter like as shown below:
$ sudo ./flash.sh -d ./kernel/dtb/tegra194-p2888-0008-p2822-0000.dtb jetson-agx-xavier-industrial mmcblk0p1
or
I executed flash prerequisites .sh script ( for the first time before flashing, Earlier I was directly executing Flash command ) as shown below:
$sudo tools/l4t_flash_prerequisites.sh
Any idea about this. Please let me know. If either of these are causing any problems after booting and once it enters the kernel.
To fix my booting issue , was trying to load the kernel image file alone separately but getting this failed flashing error.
using the below command:
sudo ./flash.sh -K /home/trident/Downloads/r35_4_1/Jetson_Linux_R35.4.1_aarch64/Linux_for_Tegra/kernel/Image.gz jetson-agx-xavier-industrial mmcblk0p1
I think the commands you are using are incorrect and probably have flashed more than you think. I don’t know enough about the options such as “-d”, but that command very likely flashes more than the DTB, and uses a specific DTB you named while adding more than the DTB.