Hi Jason,

for the GPIO pinout, the best starting point right now would be the description 
in the MPM code:
https://github.com/EttusResearch/uhd/blob/master/mpm/python/usrp_mpm/periph_manager/x4xx_periphs.py
Essentially, we've connected the 12 I/O lines that the regular HDMI pinout also 
defines as signals.
I/O voltages can be set per connector as well (1.8V/2.5V/3.3V).
One thing to keep in mind for the pinout: I/O direction setting is slow, so a 
fast protocol needs to have fixed I/O directions per pin.
If you're interested in using the HDMI voltage supply output, we've hooked up 
3.3V, ~500mA to the power pin of HDMI.

In terms of SW support for UHD to use the GPIOs, we're working on getting the 
support in - no firm timelines yet unfortunately.

Another option for peripheral circuit boards may be to use the USB-C connection 
in the back - depends on your application requirements of course.

Hope this helps
Jan


From: jason pro <[email protected]>
Sent: Sonntag, 10. Oktober 2021 19:27
To: [email protected]
Subject: [EXTERNAL] [USRP-users] pin definitions of the two HDMI interfaces of 
x410

Hi dear Engineers of Ettus Research,

We plan to design a peripheral circuit board controlled by GPIO of x410. Now I 
would like to know the pin definitions of the two HDMI interfaces of x410. 
could you share relevant information?

Best regards,
Jason
National Instruments Dresden GmbH; Gesch?ftsf?hrer (Managing Director): Kevin 
Schultz; Sitz (Registered Office): Dresden; HRB (Commercial Register No.): 
22081; Registergericht (Registration Court): Dresden

This email and any attachments are intended only for the person to whom this 
email is addressed and may contain confidential and/or privileged information. 
If you received this email in error, please do not disclose the contents to 
anyone, but notify the sender by return email and delete this email (and any 
attachments) from your system.
_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to