Jetson touchscreen

Hi all,

I am looking for a LCD screen to connect to the Jetson K1 Development Kit, but I do not know exactly which type of connectors or screen are supported. Do you know some of them? Any ideas?

Thank you in advance,
David

Seems like one of these touchscreens with an LVDS-HDMI converter would work, though it’s too bad they’re sold out: http://www.chalk-elec.com/?page_id=1280#!/~/category/id=3094861&inview=product14647633&offset=0&sort=priceAsc.

You’d probably have to power the display separately from the Jetson board, though.

Hi, I purchased on of the LCD bundles mentioned above (http://www.chalk-elec.com/?page_id=1280#!/15-6-HDMI-interface-LCD-with-capacitive-touchscreen/p/38127425/category=3094861) howerver, I am having problems with it. Once the LCD is connected and the Jetson powered, I can see the console messages however once the NVIDIA splash screen is displayed, nothing else is shown. Any ideas on what can cause this?

V/r

Derrick

Not an answer, but perhaps useful…kernel command line has an effect on console stage (U-boot is easiest to experiment with, as the options can be duplicated and edited in /boot/extlinux.conf as an alternate serial console boot prompt option). In particular, the “console” argument exists once for each console; for serial port it is:
console=ttyS0,115200n8

For the regular “video card provided graphics” the console is:
console=tty1

Related: “no_console_suspend=1”. “fbcon=map:1”. See:
https://www.kernel.org/doc/Documentation/fb/fbcon.txt

Once you see the nVidia splash, you’re loading X11. This means your X11 will require configuration for this device, and frame buffer console is gone. Settings which automate X11 setup require the DDC/EDID information, which is not provided on LVDS. HDMI does have a DDC line, but the adapter means that essentially DDC has been cut. X11 just does not know what is connected when it takes over from frame buffer console. You’ll have to figure out the X11 configuration for this device and manually update your X11 configuration, or else make custom hardware to provide DDC/EDID response…in which case you’d need to know the information anyway.

But…you’re probably in luck because it says this touchscreen works with Raspberry Pi…the X11 configuration is likely an exact copy (or nearly exact) of what you need.

Thanks for the reply. I am now stuck at configuring Xorg to include the EDID info from the adapter. Not being an Xorg guru, on my FreeBSD machines, I usually execute X -configure to get the necessary information for display. On Ubuntu, this does not work because they system boots and enters a GUI multiuser runlevel and attempting to probe the devices with “X -configure” results in a error stating that Xorg is already running. I know it is not and hardware issue now because when I killed process relating to Xorg and lightdm, I was able to see UBUNTU login however, I was not able to login due to the processes probably being killed. Based on the EDID information provided, do you have any suggestions on what else is necessary in the /etc/X11/xorg.conf file for this to work?

./edid-rw 3 | edid-decode
Extracted contents:
header: 00 ff ff ff ff ff ff 00
serial number: 06 af ec 10 00 00 00 00 00 16
version: 01 04
basic params: 90 22 13 78 02
chroma info: bb f5 94 55 54 90 27 23 50 54
established: 00 00 00
standard: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1: 12 1b 56 5a 50 00 19 30 28 20 36 00 58 c1 10 00 00 18
descriptor 2: 00 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 20
descriptor 3: 00 00 00 fe 00 41 55 4f 0a 20 20 20 20 20 20 20 20 20
descriptor 4: 00 00 00 fe 00 42 31 35 36 58 54 54 30 31 2e 30 20 0a
extensions: 00
checksum: 4a

Manufacturer: AUO Model 10ec Serial Number 0
Made week 0 of 2012
EDID version: 1.4
Digital display
6 bits per primary color channel
Digital interface is not defined
Maximum image size: 34 cm x 19 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
Detailed mode: Clock 69.300 MHz, 344 mm x 193 mm
1366 1406 1438 1456 hborder 0
768 771 777 793 vborder 0
-hsync -vsync
Manufacturer-specified data, tag 15
ASCII string: AUO
ASCII string: B156XTT01.0
Checksum: 0x4a
EDID block does NOT conform to EDID 1.3!
Missing name descriptor
Missing monitor ranges

See:
https://devtalk.nvidia.com/default/topic/761449/embedded-systems/jetson-tk1-unable-to-boot/post/4309235/#4309235

Automatic configuration fails either because LVDS does not provide EDID information (always true without additional hardware added on to make it work), or because the extra hardware added to provide EDID has a bug. It’s very very unlikely the given LVDS ever had any hardware to provide EDID…it simply has a cable adapter, which won’t work. You need to find the information in documentation somewhere and type it into X11 config files by hand.

The touch screen mentions it works with Raspberry Pi, and likely the Raspberry Pi config is exactly what you need…the work is probably already done for you, but you need to find this other config and adapt relevant parts of Jetson to it. If you can’t find someone else’s X11 config, you will need to find the manufacturer’s data sheet and extract the mode settings information.

Hi,
I have great news to report. The product works out of the box. It was the “apt-get upgrade: libglx.so Corruption” that cause the black screen.

@derrick313
Glad to know you got the touch screen working with Jetson. I am planning to buy a touch screen for the Jetson for TK1 but have a great confusion. Can you suggest me what kind of touch screens Jetson can support and how to configure them? I can see many options here: http://www.chalk-elec.com/?page_id=1280#!/~/category/id=3094861&inview=product14647633&offset=0&sort=priceAsc