Jetson AGX Xavier lost HDMI signal after Jetpack 4.4 update

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

Host machine: ubuntu 18.04
sdk manager version 1.2.0.6738
I have a agx xavier board which was running jetpack 4.3 without a problem. I put it into forced usb recovery mode and tried to update the jetpack to 4.4 using sdk manager. However, at the step where the sdk manager asks for you to complete system setup using the HDMI monitor to enter the username and password, there was NOTHING on the HDMI monitor. Obviously, I couldn’t continue, so I clicked ‘skip’ … expecting the board to remain at jetpack 4.3. However from that moment on, the HDMI monitor stopped detecting a signal from my board.

I am able to see output from the debug port, and I am able to manually flash it by cd to ~/nvidia/nvidia_sdk/JetPack_4.3_Linux_JETSON_AGX_XAVIER/Linux_for_Tegra using the command:

sudo ./flash.sh jetson-xavier mmcblk0p1 | tee flash_2020-09-05.out

It appears to flash successfully because my log flash_2020-09-05.out shows the message:

[ 310.9542 ] tegradevflash_v2 --write MEM_BCT_b mem_coldboot_sigheader.bct.encrypt
[ 310.9563 ] Bootloader version 01.00.0000
[ 310.9622 ] Writing partition MEM_BCT_b with mem_coldboot_sigheader.bct.encrypt
[ 310.9636 ] […] 100%
[ 310.9909 ]
[ 310.9910 ] Flashing completed
[ 310.9911 ] Coldbooting the device
[ 310.9954 ] tegrarcm_v2 --ismb2
[ 311.0020 ]
[ 311.0039 ] tegradevflash_v2 --reboot coldboot
[ 311.0054 ] Bootloader version 01.00.0000
[ 311.0118 ]
*** The target t186ref has been flashed successfully. ***
Reset the board to boot from internal eMMC.

However, when I reset the board, I see this message on the minicom

[0002.002] I> enabling ‘vdd-hdmi-5v0’ regulator
[0002.008] I> regulator ‘vdd-hdmi-5v0’ already enabled
[0002.008] I> hdmi cable connected
[0002.011] E> set volts not configured for ‘vdd-1v0’
[0002.013] E> set volts not configured for ‘vdd-1v8-hs’
[0002.018] E> invalid display type
[0002.023] E> invalid display type
[0002.025] E> cannot find any other nvdisp nodes
[0002.029] E> I2C: Timeout while polling for bus clear. Last value 0x00000000.
[0002.030] E> I2C: Failed to clear bus for instance 6.
[0002.031] E> I2C: Failed to clear bus for instance 6.
[0002.031] E> I2C_DEV: Failed to initialize instance 6.
[0002.033] E> read_edid, invalid i2c handle
[0002.041] I> hdmi_enable, starting HDMI initialisation
[0002.046] I> hdmi_enable, HDMI initialisation complete
…
[ 73.618133] tegra-i2c 31c0000.i2c: I2C_INT_STATUS - 0x2
[ 73.618231] tegra-i2c 31c0000.i2c: i2c transfer timed out addr: 0x50
[ 79.377142] Please complete system configuration setup on desktop to proceed…
ÿâWARNING: pll_d3 has no dyn ramp

How can I complete system configuration setup on desktop… when the monitor doesn’t detect hdmi signals from the board? I have tested the monitor and the cable with other sources, and the monitor displays images from other sources without a problem.

Any ideas on what could be the problem? Or any ideas on how to recovery to factory settings???

2

It sounds like the monitor is a true HDMI without adapters, but you might want to verify this is correct.

I don’t know if the 0x31c00000 address is for the HDMI i2c, but if it is, then address 0x50 is what queries EDID (the DDC wire). Provided this is the controller for HDMI, it implies there is no ability to query the monitor for its specs, and EDID is the only way various modes are supported on this driver. If it turns out that the 0x31c00000 i2c controller is something else, then you probably have bigger problems.

If you want a way to “cheat” and do first boot setup prior to ever flashing, and embed that into the image which is flashed, then see the script found here:
https://forums.developer.nvidia.com/t/jetson-nano-all-usb-ports-suddenly-stopped-working/75784/37

What that script does is to use QEMU chroot into the install image software of “Linux_for_Tegra/rootfs/”, and essentially set up that first boot account. Then you can at least get past first boot issues while debugging.

1 Like
3

You could use oem-config to configure your device by your host.

Please tell us if you are using adapters.

Also, will this issue get resolved immediately once you flash back to rel-32.3.1?

4

Thank you for the responses. My error was a silly one… I was given this board, and only told that it was a Xavier AGX. I was not told that it was running on a ‘Rogue Carrier Board’. so it needs an extra set of BSP’s for any jetpack updates to work.

I installed the additional bsp from supplier, and now the hdmi signal is working again.