How to display video captured by OS08A20 camera via HDMI?

Technical Support
16

Weston Container Startup Issue on Verdin iMX95

The Weston container is failing to start. Let’s troubleshoot this step by step.

Step 1: Check Container Logs

First, check the logs to see why the container failed to start:

docker logs weston

(1)

Step 2: Use Correct Container Image

For the Verdin iMX95, you should use the correct Weston container. Based on the documentation, the proper command for iMX95 is(2):

docker container run -d --name=weston --net=host \
    --cap-add CAP_SYS_TTY_CONFIG \
    -v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/ \
    --device-cgroup-rule="c 4:* rmw" --device-cgroup-rule="c 253:* rmw" \
    --device-cgroup-rule="c 13:* rmw" --device-cgroup-rule="c 226:* rmw" \
    --device-cgroup-rule="c 10:223 rmw" --device-cgroup-rule="c 199:0 rmw" \
    --device-cgroup-rule="c 10:* rmw" \
    torizon/weston-imx95:4 \
    --developer

(2)

Step 3: Remove Failed Container

Before trying again, remove the failed container:

docker rm weston

Step 4: Check Video Devices from Host

You can check available video devices directly from the host system without needing the container running:

ls /dev/video*

(3)

Step 5: Alternative Container Approach

If the iMX95-specific container continues to fail, you might need to try a different approach. Based on community discussions, there have been issues with Weston containers on newer modules(4).

Step 6: Device-Specific Considerations

For the iMX95, ensure that:

  1. Device Tree Overlays are properly configured for your display output(5)
  2. Hardware Access Rules are correctly set for the specific hardware(1)
  3. Display Interface is properly initialized (DSI to HDMI adapter)(5)

Troubleshooting Tips

The device cgroup rules in your command need to be properly formatted. Make sure you’re using the exact syntax from the documentation(1):

  • Use --device-cgroup-rule="c 4:* rmw" (with equals sign and quotes)
  • Ensure all backslashes for line continuation are properly placed
  • Check that the container image torizon/weston-imx95:4 is available and correct

Hardware Access Requirements

The Weston container needs specific hardware access(3):

  • /dev - Access to devices attached to the system
  • /tmp - Interaction with Weston (GUI)
  • /run/udev/ - Access to udev for hardware detection

Once you get the container logs, we can better diagnose the specific issue preventing the Weston container from starting.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.