eMMC Image Availability for v2.0.1 and HDMI TX0 Issue on v1.0

Namitjain07 · June 24, 2026, 10:05pm

I have two questions regarding the AXON Ubuntu images.

First, is there an eMMC image available for v2.0.1? I could only find the raw image file for this release and have been unable to locate an eMMC-flashable image.

Second, after flashing the v1.0 image, I am experiencing an issue with the HDMI TX0 port. The board successfully detects the monitor, but no video output is displayed after boot. DisplayPort works correctly, including when using a DP-to-HDMI adapter.

Monitor details:

Resolution: 1920 × 1080
Refresh Rate: 240 Hz

This issue was not present on the Ubuntu 22.04 image.

As a workaround, I found that reinitializing the display after login restores video output. Running the following commands makes HDMI TX0 start working immediately:

xrandr --output HDMI-1 --off
sleep 2
xrandr --output HDMI-1 --auto --primary

However, the issue returns after every reboot.

Based on the logs, HDMI-1 is detected correctly and reported as connected, and the display mode is set to 1920×1080. This suggests the HDMI link may not be initializing properly during boot.

Could you please let me know:

Whether an eMMC image is available for v2.0.1.
If this HDMI TX0 behavior on v1.0 is a known issue.
Whether there is a recommended fix or workaround.

Avi_Shihora · June 25, 2026, 3:35am

Here is your question’s answer.

Raw image can be flashed in eMMC as well, as also mentioned in documentation.
Flashing Guide on How to Flash Raw image in eMMC Windows & Linux.
Yes, it is known issue.
Flashed Latest V2.0.1_vicharak_axon_6.1._07052026-ubuntu-noble-24.04-raw.tar.gz

peonix · June 25, 2026, 3:56am

This issue has been resolved in the newer image version.

The problem was caused by HDMI not being properly initialized after U-Boot handed over control to the Linux kernel. When we run the xrandr --off command, it reinitializes the HDMI output, which is why the display starts working again.

The root cause was related to DTB packaging in the previous image. U-Boot also requires a DTB to initialize the board, but it was using a different DTB version instead of the same DTB used by the kernel. This mismatch caused the HDMI TX0 initialization issue.

In the latest image, the DTB packaging has been corrected, so HDMI initialization works properly without needing the manual xrandr --off workaround.

Namitjain07 · June 25, 2026, 7:12am

on trying to flash raw image how to fix

Avi_Shihora · June 25, 2026, 7:14am

Kindly Go through documentation.
https://docs.vicharak.in/vicharak_sbcs/axon/axon-linux/linux-usage-guide/windows-rkdevtool/#flash-raw-image-in-emmc-to-axon-board

Namitjain07 · June 25, 2026, 7:24am

thanks , please tell one more thing how can i enable ssh after the install of ubuntu withut connecting keyboard or mouse basically a first boot service or something

Namitjain07 · June 25, 2026, 7:53am

just flashed v2.0.1 and now when i connect to dp2 and also to tx0 only 1 display is detected and when i remove dp2 it detects tx0. idk its super weird. also sometimes tx0 not even work after removing dp2

Avi_Shihora · June 25, 2026, 8:56am

When you used type C as DP port, it will take more time to detect.
If you wait for a while, Display will show on Type C as well.

Namitjain07 · June 25, 2026, 11:35pm

Its showing on type c actually not on tx0 thats the issue. on older version it was showing correctly

Avi_Shihora · June 26, 2026, 4:24am

Thanks @Namitjain07 for clarifying we are looking this issue."
Could you send the logs using below command !?

dmesg > axon.log

Send logs after connecting Both Display and also when issue has been shown ( dmesg > axon-issue.log )

Namitjain07 · June 26, 2026, 7:27am

Will share by evening

Namitjain07 · June 26, 2026, 7:45pm

axon_tx0.txt (71.7 KB)
axon_both.txt (70.8 KB)
axon_dp2.txt (77.4 KB)
look at these logs tx0 dont work only dp2 and yet tx0 shows connected

vk092 · June 27, 2026, 4:26am

Does these commands fix everything ??

xrandr --output HDMI-1 --off
sleep 2
xrandr --output HDMI-1 --auto --primary

Namitjain07 · June 27, 2026, 6:56am

The display issue can be temporarily fixed by running:

xrandr --output HDMI-1 --offsleep 2xrandr --output HDMI-1 --auto --primary

However, this is only a workaround. On every boot, the monitor is detected as connected, but it shows “No Signal” until the above commands are executed.

After running:

xrandr --output HDMI-1 --off

the display turns off as expected. Running xrandr at this point shows:

vicharak@vicharak:~$ xrandrScreen 0: minimum 320 x 200, current 320 x 200, maximum 16384 x 16384HDMI-1 connected primary (normal left inverted right x axis y axis)   1920x1080     60.00 + 239.65   164.92   143.98   120.00   119.88    50.00    59.94   3840x2160     60.00    50.00    59.94   1680x1050     59.88   1600x900      60.00   1280x1024     75.02    60.02   1440x900      59.90   1280x720     120.00   119.88    60.00    50.00    59.94   1024x768      75.03    70.07    60.00   832x624       74.55   800x600       72.19    75.00    60.32   720x576       50.00   720x480       60.00    59.94   640x480       75.00    72.81    66.67    60.00    59.94   720x400       70.08HDMI-2 disconnected (normal left inverted right x axis y axis)DP-1 disconnected (normal left inverted right x axis y axis)DP-2 disconnected (normal left inverted right x axis y axis)

Notice that HDMI-1 is still reported as connected, but the current screen size is only 320×200, indicating that no display mode has been activated.

After running:

xrandr --output HDMI-1 --auto --primary

the display starts working immediately. Running xrandr now shows:

vicharak@vicharak:~$ xrandrScreen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm   1920x1080     60.00*+ 239.65   164.92   143.98   120.00   119.88    50.00    59.94   3840x2160     60.00    50.00    59.94   1680x1050     59.88   1600x900      60.00   1280x1024     75.02    60.02   1440x900      59.90   1280x720     120.00   119.88    60.00    50.00    59.94   1024x768      75.03    70.07    60.00   832x624       74.55   800x600       72.19    75.00    60.32   720x576       50.00   720x480       60.00    59.94   640x480       75.00    72.81    66.67    60.00    59.94   720x400       70.08HDMI-2 disconnected (normal left inverted right x axis y axis)DP-1 disconnected (normal left inverted right x axis y axis)DP-2 disconnected (normal left inverted right x axis y axis)

At this point, the desktop is displayed correctly at 1920×1080.

This suggests that the HDMI monitor is successfully detected during boot, but the display mode is not initialized correctly. Manually disabling and re-enabling the HDMI output forces the driver to reinitialize the display pipeline and set the correct mode, after which HDMI works normally.

So, while the above commands consistently restore the display, the underlying issue appears to be that HDMI is not being properly initialized during boot, despite the monitor being detected.

vk092 · June 29, 2026, 10:18am

Hey @Namitjain07 ,
Are you getting the same error in TX1 port too ??

Your logs point towards, failure(timeout) of reading the EDID of the monitor, which can be a race-time condition.

Let me know about TX1 port and what kind of monitor you are using, so that I can further diagnose the issue.

Namitjain07 · June 30, 2026, 3:15am

tx1 works:
vicharak@vicharak:~$ xrandr
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 16384 x 16384
HDMI-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1920x1080 60.00*+ 50.00
1280x720 60.00 50.00
720x576 50.00
720x480 59.94
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 698mm x 393mm
3840x2160 60.00*+ 60.00 50.00 59.94 30.00 29.97
1920x1080 239.65 164.92 143.98 120.00 119.88 60.00 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.90
1280x720 120.00 119.88 60.00 50.00 59.94
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08

vk092 · July 2, 2026, 6:01am

Hey @Namitjain07 , I tried creating the same conditions which you described, in multiple boards, but I am not able to recreate the same issue.

Please share the pictures of your setup, which includes the connectors and cables you are using, closeups of board. And info about the display you are using.

Namitjain07 · July 2, 2026, 6:28am

One thing I noticed is that my monitor is 1920×1080 at 240 Hz, but since it has HDMI 2.1, it also accepts 4K 60 Hz as an input. I think the board might be trying to boot at 4K by default, then failing for some reason and falling back to something like 320×320 (I’m not sure of the exact issue).
My monitor is a Lenovo R27fc-30.
With TX1, the monitor is detected correctly as 1920×1080, although only at 60 Hz, so it works fine.
TX0 supports more display output modes, so I suspect the default output or display mode selection on TX0 might be causing the problem.

Namitjain07 · July 2, 2026, 6:30am

All the monitors in your video are 1080p with refresh rate less that 120hz probably so maybe u cant reproduce the issue

Namitjain07 · July 2, 2026, 7:03am

please increase file upload size limit

. 4mb is very less