Flashed via command line - Can't display X/Gnome GUI

We’ve been trying to flash our Xavier’s via the command-line, as in:

./tegraflash.py --bl nvtboot_recovery_cpu_t194.bin --sdram_config tegra194-mb1-bct-memcfg-p2888.cfg,tegra194-memcfg-sw-override.cfg  --odmdata 0x9190000 --applet mb1_t194_prod.bin --cmd "flash; reboot" --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg  --cfg flash.xml --chip 0x19 --uphy_config tegra194-mb1-uphy-lane-p2888-0000-p2822-0000.cfg --device_config tegra19x-mb1-bct-device-sdmmc.cfg --misc_cold_boot_config tegra194-mb1-bct-misc-l4t.cfg --misc_config tegra194-mb1-bct-misc-flash.cfg --pinmux_config tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg --gpioint_config tegra194-mb1-bct-gpioint-p2888-0000-p2822-0000.cfg --pmic_config tegra194-mb1-bct-pmic-p2888-0001-a01-p2822-0000.cfg --pmc_config tegra19x-mb1-padvoltage-p2888-0000-a00-p2822-0000-a00.cfg --prod_config tegra19x-mb1-prod-p2888-0000-p2822-0000.cfg --scr_config tegra194-mb1-bct-scr-cbb-mini.cfg --scr_cold_boot_config tegra194-mb1-bct-scr-cbb-mini.cfg --br_cmd_config tegra194-mb1-bct-reset-p2888-0000-p2822-0000.cfg --dev_params tegra194-br-bct-sdmmc.cfg  --bin "mb2_bootloader nvtboot_recovery_t194.bin; mts_preboot preboot_c10_prod_cr.bin; mts_mce mce_c10_prod_cr.bin; mts_proper mts_c10_prod_cr.bin; bpmp_fw bpmp_t194.bin; bpmp_fw_dtb tegra194-a02-bpmp-p2888-a01.dtb; spe_fw spe_t194.bin; tlk tos-mon-only_t194.img; eks eks.img; bootloader_dtb tegra194-p2888-0001-p2822-0000.dtb"

The flash seems to work correctly (no errors) and the Xavier is then able to boot, however it cannot display the Gnome GUI via HDMI. Instead, just when it would normally switch to the graphical interface, the display starts flashing on and off at the attached.

However, the system has otherwise booted correctly: I can SSH to it over ethernet and it appears to be working correctly. Any tips on what could lead to such an issue? It is worth noting that if I flash via Jetpack I don’t have the same problem, so I guess I’m doing something wrong while flashing…

Attached are:

  • Dmesg log - xav-dmesg.log
  • Serial log - xav-minicom.log
  • Boot screen shot - xav-boot-screen.jpg

Thank you!

xav-minicom.log (88.4 KB)
xav-dmesg.log (82.5 KB)

After I posted this, I saw this post:


Sounds like this is the same problem (with a solution). Will try shortly and close this thread if so.

If you compile your own kernel image, then this issue should be the same.