I am
I am booting tdx-reference-multimedia-image on my Verdin board and trying to see the output on HDMI. Currently I don’t see anything on the display. I had an older image flashed and the display worked fine. So I know for sure the display does work.
I have ordered some debug cables for UART so I don’t have access to the console.
I was wondering if there was a way to enable SSH over RNDIS USB-C port.
When I connect the board to my host, I see automatically the RNDIS interface with an IP address assigned to it.
When I do SSH to this IP, I get connection refused.
Hence, is there any configuration changes I can make while building the image to enable SSH access over RNDIS?
Also, are there any instructions to configure HDMI output explicitly?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
To enable SSH access over the RNDIS USB-C port on your Verdin board, you can make some configuration changes while building the image. Since you are using the tdx-reference-multimedia-image, SSH should be available, but it might not be enabled by default for the RNDIS interface. Here are some steps you can take:
Enable SSH for RNDIS:
Ensure that the SSH service is enabled and configured to start on boot. You can do this by checking the systemd service configuration for SSH. If you have access to the image build configuration, make sure that the SSH service is included and enabled.
Check SSH Configuration:
Verify the SSH daemon configuration file (/etc/ssh/sshd_config) to ensure that it allows connections from the RNDIS interface. You might need to adjust the ListenAddress directive to include the IP address assigned to the RNDIS interface.
Firewall and Security Settings:
Ensure that there are no firewall rules or security settings blocking SSH connections on the RNDIS interface.
Regarding configuring HDMI output explicitly, since you mentioned that the display worked with an older image, it might be a configuration issue with the new image. Here are some general steps:
Check HDMI Configuration:
If you have access to the image build configuration, ensure that the HDMI output is enabled and correctly configured. This might involve setting the correct display resolution and refresh rate.
Kernel and Device Tree:
Verify that the kernel and device tree used in the new image support HDMI output for your specific Verdin board and carrier board setup.
Logs and Debugging:
Once you have access to the UART console, check the boot logs for any errors or messages related to HDMI initialization.
If you need to make these changes while building the image, you might need to modify the Yocto build configuration files to include the necessary packages and settings for SSH and HDMI support.
Please, also check if these links can help you solve your problem:
I have a custom hardware, which has two USB ports and 2 debug UARTS connectors on it.
I have one port, which I used for flashing and there is a CDC NCM network interface coming on it when the device boots. Other USB is more or less dead. Nothing happens when I connect it to host.
