I followed instructions how to flash and I havent modified anything. Everything flashed successfully from Ubuntu 14.04 amd64 host pc. Now when I boot it every time its stuck at standard boot command line and I cant type anything. last line is … —[ end trace c027b283e120f07e ]—
Please help me to get it boot up to command line from which I can type.
Here is a screenshot of the screen which is stuck:
*** The target ardbeg has been flashed successfully. ***
Reset the board to boot from internal eMMC.
Personally, when I flashed I used a larger size, my -S 8GiB was instead -S 14GiB (the largest I could use without exceeding eMMC). I don’t think this should have mattered. I also used u-boot, but this too should not matter.
The last line says the flash worked, and there was no error from udev needing /dev/loop0. So I’m inclined to believe that the flash was correct, but the pre-flash setup was incorrect.
There was an apply_binaries.sh script to run prior to the flash.sh. What did you do for setup preparation?
I downloaded sample file system and l4t 47mb package, extracted them using gui, put extracted sample file system in rootfs.
In terminal i cd’d to rootfs directory and ran binaries.sh command as root. Thats it.
Try this…delete your entire L4T that you unpacked before, but unpack it again making sure you always do this as root or sudo root, and preserve file permissions in tar (in Ubuntu, sudo -s is convenient), e.g.:
bunzip2 < Tegra_Linux_Sample-Root-Filesystem_R19.3.0_armhf.tbz2 | tar xvp
When you use apply_binaries.sh, be sure to use root again.
Make sure your micro-B USB is seated, disconnect any unused USB devices (e.g., mouse and keyboard not needed on Jetson itself during flash), and flash again. Try more space:
flash.sh -S 14GiB jetson-tk1 mmcblk0p1
If you want to show logs, you can probably just mouse copy and paste (screenshots are the hard way to do it). If you have “tee” try:
flash.sh -S 14GiB jetson-tk1 mmcblk0p1 <b><i>2>&1 | tee flash.log</i></b>
If you are flashing an entire system to an 8 GB SD, this might be a cause of failure. The root file system itself is near 8 GB. I would not use an 8 GB SD for anything other than mounting later or for flashing boot loader and kernel.
Oh, dont worry, I wont flash the system on sd card. I just saw your post in another thread. Anyway I’m redownloading files now. Terminal failed to untar. That might be the problem, even though I’ve redownloaded files before already.
One cause for a tar unpack failure would be lack of permissions…for example, it may be blocked when producing a device special file. Permissions on the rootfs should be preserved as well from unpacking…the -p option of tar.
If Thunar can preserve permissions and create needed device special files, etc., it shouldn’t differ from directly using tar. Preserving permissions and being able to create device special files should not be considered optional.
NTFS is incapable of creating the linux file permissions, and has a high probability of causing the failure. Switch to ext4, try between 10 and 14 GiB on -S…I’ve tested 14 GiB.
Ok. I’m simply going to increase ext4 to 30gb. I can have use of that for other things, too. I completely forgot ntfs could be the problem. Jetson might just boot properly after I’ve done everything you mentioned, hopefully.
RCM communication completed
auxInfo->NCTBoardInfo->proc_board_id is 375
auxInfo->NCTBoardInfo->proc_sku is 0
auxInfo->NCTBoardInfo->proc_fab is 3
BCT sent successfully
sending file: tegra124-xxx-yyy.dtb