I know this issue is already found in some jetson devices. But I am not able to fix it.
Please share is there any solution to overcome this. I have tried 3 different USB cables and I am using ubuntu 16.04 (No VM).
L4T BSP Information:
R32 , REVISION: 4.2
[ 10.5036 ] tegrarcm_v2 --download blob blob.bin
[ 10.5047 ] Applet version 01.00.0000
[ 10.5175 ] Sending blob
[ 10.5176 ] [................................................] 100%
[ 11.3014 ]
[ 11.3046 ] tegrarcm_v2 --boot recovery
[ 11.3076 ] Applet version 01.00.0000
[ 11.3308 ]
[ 12.3352 ] tegrarcm_v2 --isapplet
[ 1012.3476 ]
[ 1012.3510 ] tegrarcm_v2 --ismb2
Full Log - emmc flash failure log
It is interesting that there is a large gap of time from 12.3352 seconds and then starting again at 1012.3476 seconds. Was there content in that time, or is this the exact log? Then the log just stops and no error is shown.
Is this the dev kit, or is this using a third party carrier board? I am wondering if you have the micro-B USB cable from the dev kit since that cable works well and many “charger” type cables fail. On the other hand, if a cable failed, then I would expect to see an error, and not see the log just stop.
I see this in the logs, which is “good”:
populating rootfs from /home/econsys7/econ/code/Linux_for_Tegra/rootfs ... done.
Sync'ing system.img ... done.
Converting RAW image to Sparse image... done.
system.img built successfully.
What is the exact byte size of
ls -l bootloader/system.img.raw
Its my mistake. The SOM in the devkit does not comes with eMMC. I found that only the standalone Xavier NX SOMs have the eMMC.
Thanks for your response again.