Flashing fails, Jetson screen flickers

Hello,

A few days ago the screen I use for the Jetson started flickering, immediately I checked with a different monitor if the problem is with it or with the board, the problem persisted.

On Ctrl+Alt+F2 I checked all that seemed relevant and saw no errors.

The last resort was to flash the system, i tried Jetpack 3.3 and two versions before that. All of them have the same problem “CPU bootloader is not running on device”. I tried to power it on desipte the failed flash, and it booted, but the problem was the same.

Do you have any suggestions?

vukca95,

Did you ever change the cboot.bin on your tx2 before? Please share the full flash log with us.

No, didn’t change anything. And also forgot to mention the flash log didn’t generate ever although it said it did and where to find it. I checked after every fail.

vukca95,

If there is no flash log, how did you know the error is “CPU Bootloader is not running on device.”??

Hi WayneWWW,

It was written in the console.

vukca95,

Then please share it with us…

Did the “flickering” look like the GUI crashing and restarting constantly? Did you use command line or JetPack to install? If you used command line, did you use “sudo” to unpack sample rootfs and run “apply_binaries.sh”? For either command line flash or JetPack flash, was your file system type on the PC host a native Linux type and not something like NTFS?

Okay, so the problem was solved flashing the 28.2 image I got from the guys at leopard imaging along with the driver for the camera. After that it functions normally. The flicker looked like the GUI restarting, yes, I should have phrased that better. Yes, I used the command line, and sudo, it didn’t work with the downloaded Jetpack 3.1, 3.2.1 or 3.3, I can’t even say why it worked with their image for sure. And ext4 partitions on the host.

The last error I got before the next time it worked was like this:

[ 2.8503 ]
[ 2.8517 ] tegrahost_v2 --generateblob blob.xml blob.bin
[ 2.8528 ] number of images in blob are 9
[ 2.8536 ] blobsize is 3749384
[ 2.8543 ] Added binary blob_nvtboot_recovery_cpu_sigheader.bin.encrypt of size 190048
[ 2.8582 ] Added binary blob_nvtboot_recovery_sigheader.bin.encrypt of size 79600
[ 2.8598 ] Added binary blob_preboot_d15_prod_cr_sigheader.bin.encrypt of size 63024
[ 2.8614 ] Added binary blob_mce_mts_d15_prod_cr_sigheader.bin.encrypt of size 2076832
[ 2.8644 ] Added binary blob_bpmp_sigheader.bin.encrypt of size 529440
[ 2.8672 ] Added binary blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb.encrypt of size 466160
[ 2.8697 ] Added binary blob_tos_sigheader.img.encrypt of size 62976
[ 2.8718 ] Added binary blob_eks_sigheader.img.encrypt of size 1488
[ 2.8734 ] Added binary blob_tegra186-quill-p3310-1000-c03-00-base_sigheader.dtb.encrypt of size 279664
[ 2.8863 ]
[ 2.8865 ] Sending bootloader and pre-requisite binaries
[ 2.8881 ] tegrarcm_v2 --download blob blob.bin
[ 2.8895 ] Applet version 01.00.0000
[ 2.9133 ] Sending blob
[ 2.9133 ] […] 100%
[ 3.3949 ]
[ 3.3960 ] tegrarcm_v2 --boot recovery
[ 3.3976 ] Applet version 01.00.0000
[ 3.4383 ]
[ 3.4416 ] tegrarcm_v2 --isapplet
[ 4.1863 ]
[ 4.1892 ] tegradevflash_v2 --iscpubl
[ 4.1902 ] CPU Bootloader is not running on device.
[ 4.2104 ]
[ 35.3944 ] Retrieving storage infomation
[ 35.3956 ] tegrarcm_v2 --oem platformdetails storage storage_info.bin
[ 35.3967 ] Applet is not running on device. Continue with Bootloader
[ 35.4304 ]
[ 35.4319 ] tegradevflash_v2 --oem platformdetails storage storage_info.bin
[ 35.4328 ] CPU Bootloader is not running on device.
[ 35.4431 ]
Error: Return value 4
Command tegradevflash_v2 --oem platformdetails storage storage_info.bin
Failed flashing t186ref.

Basically I suspect the libglx.so was not installed correctly, and this leads to the GUI crashing when it attempts to start…followed by an attempt to restart…infinite loop.

The apply_binaries.sh step is what installs this when using command line. If either the unpack of the rootfs was done without sudo, or the apply_binaries.sh was done without sudo, or if unpack was to a non-Linux file system, then this happens.

vukca95,

Do you only flash the image or the whole BSP from Leopard?

The log below is from my host with successfully flash.

[   3.3097 ] tegrarcm_v2 --download blob blob.bin
[   3.3107 ] Applet version 01.00.0000
[   3.3152 ] Sending blob
[   3.3153 ] [................................................] 100%
[   3.7515 ] 
[   3.7530 ] tegrarcm_v2 --boot recovery
[   3.7544 ] Applet version 01.00.0000
[   3.7606 ] 
[   3.7621 ] tegrarcm_v2 --isapplet
[   4.4250 ] 
[   4.5054 ] tegradevflash_v2 --iscpubl
[   4.5068 ] CPU Bootloader is not running on device.
[   4.5423 ] 
[   5.5921 ] Retrieving storage infomation
[   5.5935 ] tegrarcm_v2 --oem platformdetails storage storage_info.bin
[   5.5948 ] Applet is not running on device. Continue with Bootloader
[   5.5992 ] 
[   5.6006 ] tegradevflash_v2 --oem platformdetails storage storage_info.bin
<b>[   5.6019 ] Bootloader version 01.00.0000</b>
[   5.6064 ] Saved platform info in storage_info.bin
[   5.6136 ] 
[   5.6137 ] Flashing the device
[   5.6151 ] tegraparser_v2 --storageinfo storage_info.bin --generategpt --pt flash.xml.bin
[   5.6169 ] 
[   5.6182 ] tegradevflash_v2 --pt flash.xml.bin --create

According to the source of tegradevflash_v2, error “CPU Bootloader is not running on device.” only shows when some check (sending message, receiving message, BL version mismatch …) is false.

Thus, if you can flash device through leopard’s BSP, but not official jetpack, please compare the bootloader version.