adafruit Display with Jetson tk1

Hey,

I received the adafruit display " https://www.adafruit.com/products/2260 " and it looks very nice.

when I try to power it on the LEDS are turning on at the side which indicates that it is on but when I connect the display with Jetson TK1 it does not show any thing…

does any one had an experiences with such thing?what might be the problem?

Thank you.

Typically you’d start debugging by installing packages read-edid and edid-decode. The following will provide information on how the display responds:

sudo get-edid | parse-edid
sudo get-edid | edid-decode

Posting the file /var/log/Xorg.0.log and describing cabling also helps.

should I enter there commands while the display is attached? and where to post the file “/var/log/Xorg.0.log”

Thank you very much

Yes, display would need to be attached. EDID information is read from the monitor’s response to a query. The idea is to find out what happens when the monitor is asked what it is. You might need to prefix with sudo.

the following result appeared

ubuntu@tegra-ubuntu:~$     sudo get-edid | parse-edid
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
    Identifier "MS82P"
    ModelName "MS82P"
    VendorName "XXX"
    # Monitor Manufactured week 18 of 2013
    # EDID version 1.3
    # Digital Display
    DisplaySize 330 210
    Gamma 2.20
    Option "DPMS" "false"
    Horizsync 15-70
    VertRefresh 55-77
    # Maximum pixel clock is 150MHz

    #Extension block found. Parsing...
    Modeline     "Mode 17" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync 
    Modeline     "Mode 0" 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync 
    Modeline     "Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
    Modeline     "Mode 2" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
    Modeline     "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
    Modeline     "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
    Modeline     "Mode 5" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
    Modeline     "Mode 6" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
    Modeline     "Mode 7" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
    Modeline     "Mode 8" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
    Modeline     "Mode 9" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
    Modeline     "Mode 10" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
    Modeline     "Mode 11" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
    Modeline     "Mode 12" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
    Modeline     "Mode 13" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
    Modeline     "Mode 14" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
    Modeline     "Mode 15" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
    Modeline     "Mode 16" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
    Modeline     "Mode 18" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync 
    Modeline     "Mode 19" 74.25 1920 2448 2492 2640 540 542 547 562 +hsync +vsync interlace
    Modeline     "Mode 20" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync 
    Option "PreferredMode" "Mode 17"
EndSection
ubuntu@tegra-ubuntu:~$     sudo get-edid | edid-decode
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   63 18 1a 00 01 00 00 00 12 17
version:         01 03
basic params:    80 21 15 78 0a
chroma info:     43 d5 98 57 52 8c 27 21 50 54
established:     af ce 00
standard:        01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    66 21 50 b0 51 00 1b 30 40 70 36 00 00 00 00 00 00 1e
descriptor 2:    00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 1e
descriptor 3:    00 00 00 fd 00 37 4d 0f 46 0f 00 0a 20 20 20 20 20 20
descriptor 4:    00 00 00 fc 00 4d 53 38 32 50 0a 20 20 20 20 20 20 20
extensions:      01
checksum:        68

Manufacturer: XXX Model 1a Serial Number 1
Made week 18 of 2013
EDID version: 1.3
Digital display
Maximum image size: 33 cm x 21 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
  720x400@70Hz
  640x480@60Hz
  640x480@72Hz
  640x480@75Hz
  800x600@56Hz
  800x600@60Hz
  800x600@72Hz
  800x600@75Hz
  1024x768@60Hz
  1024x768@70Hz
  1024x768@75Hz
Standard timings supported:
Detailed mode: Clock 85.500 MHz, 0 mm x 0 mm
               1360 1424 1536 1792 hborder 0
                768  771  777  795 vborder 0
               +hsync +vsync
Dummy block
Monitor ranges: 55-77HZ vertical, 15-70kHz horizontal, max dotclock 150MHz
Monitor name: MS82P
       Has 1 extension blocks
Checksum: 0x68

CEA extension block
Extension version: 3
30 bytes of CEA data
  Video data block
    VIC 16 (native)
    VIC 05 
    VIC 04 
    VIC 03 
    VIC 07 
    VIC 02 
    VIC 06 
    VIC 01 
    VIC 31 
    VIC 20 
    VIC 19 
    VIC 18 
    VIC 22 
    VIC 17 
    VIC 21 
  Audio data block
  Vendor-specific data block, OUI 000c03 (HDMI)
    Source physical address 1.0.0.0
    Supports_AI
    DC_36bit
    DC_30bit
    DC_Y444
    Maximum TMDS clock: 225MHz
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 74.250 MHz, 0 mm x 0 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync
Detailed mode: Clock 27.000 MHz, 0 mm x 0 mm
                720  736  798  858 hborder 0
                480  489  495  525 vborder 0
               -hsync -vsync
Detailed mode: Clock 74.250 MHz, 0 mm x 0 mm
               1920 2448 2492 2640 hborder 0
                540  542  547  562 vborder 0
               +hsync +vsync interlaced
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
               1280 1720 1760 1980 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync
Detailed mode: Clock 27.000 MHz, 0 mm x 0 mm
                720  732  796  864 hborder 0
                576  581  586  625 vborder 0
               -hsync -vsync
Checksum: 0xe0

EDID block does not conform at all!
    Dummy block filled with garbage

I’v done this without connecting adafruit display. how to connect adafruit display while there is another monitor is already connected to control things and write the commands?

I am a beginner and I need some more details in order to make this work.

Thank you very much for your help…

Regards.

An interesting dilemma…most of the EDID software requires the screen to not only be present, but to also have a session connected to it. Here’s what I’d suggest…the EDID data will still be correct even if the screen is queried from a different computer where that screen functions. If you are able to run the EDID information (or xrandr) from another computer (such as an RPi), then that information should be useful and transferrable to the Jetson.

You could post the Xorg.0.log the same way as you did the EDID data in your previous post. You could either get that log via ssh while the non-working monitor is attached, or you could run the non-working monitor, and reboot with a working monitor, then attach /var/log/Xorg.0.log.old instead of Xorg.0.log (old is from the prior boot).

so I should get the EDID data of non-working display using another computer right? then how I am going to insert these EDID to my jetson? and for Xorg.0.log, I opened the system log on my Jetson, what should I do with it ?

sorry for such questions but unfortunately I am totally new to these stuffs.

The goal is to first compare what the display offers to what the video can support…you won’t have to add EDID data anywhere for that, other than to use it for comparison (post it here if you can). If you need to actually edit something, then remote ssh works, as well as serial console…in worst case, you can clone the partition, loopback mount it, edit the loopback mount, and then reflash using the edited clone image.

Probably the important thing here is to post the Xorg.0.log to the forum.

sorry for being late…
this is the X0rg.0.log file that I got while connecting the TV monitor (not the wanted display)

[    13.573] 
X.Org X Server 1.15.1
Release Date: 2014-04-13
[    13.573] X Protocol Version 11, Revision 0
[    13.573] Build Operating System: Linux 3.2.0-60-highbank armv7l Ubuntu
[    13.573] Current Operating System: Linux tegra-ubuntu 3.10.40-gdacac96 #1 SMP PREEMPT Thu Jun 25 15:25:11 PDT 2015 armv7l
[    13.573] Kernel command line: console=ttyS0,115200n8 console=tty1 no_console_suspend=1 lp0_vec=2064@0xf46ff000 mem=2015M@2048M memtype=255 ddr_die=2048M@2048M section=256M pmuboard=0x0177:0x0000:0x02:0x43:0x00 tsec=32M@3913M otf_key=c75e5bb91eb3bd947560357b64422f85 usbcore.old_scheme_first=1 core_edp_mv=1150 core_edp_ma=4000 tegraid=40.1.1.0.0 debug_uartport=lsport,3 power_supply=Adapter audio_codec=rt5640 modem_id=0 android.kerneltype=normal fbcon=map:1 commchip_id=0 usb_port_owner_info=2 lane_owner_info=6 emc_max_dvfs=0 touch_id=0@0 board_info=0x0177:0x0000:0x02:0x43:0x00 root=/dev/mmcblk0p1 rw rootwait tegraboot=sdmmc gpt
[    13.574] Build Date: 30 July 2014  12:24:34AM
[    13.574] xorg-server 2:1.15.1-0ubuntu2.1 (For technical support please see http://www.ubuntu.com/support) 
[    13.574] Current version of pixman: 0.30.2
[    13.574] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    13.574] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    13.575] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan  1 04:00:23 2000
[    13.583] (==) Using config file: "/etc/X11/xorg.conf"
[    13.583] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    13.588] (==) No Layout section.  Using the first Screen section.
[    13.588] (==) No screen section available. Using defaults.
[    13.588] (**) |-->Screen "Default Screen Section" (0)
[    13.588] (**) |   |-->Monitor "<default monitor>"
[    13.588] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[    13.588] (**) |   |-->Device "Tegra0"
[    13.588] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    13.589] (==) Automatically adding devices
[    13.589] (==) Automatically enabling devices
[    13.589] (==) Automatically adding GPU devices
[    13.593] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    13.593] 	Entry deleted from font path.
[    13.593] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    13.593] 	Entry deleted from font path.
[    13.593] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    13.593] 	Entry deleted from font path.
[    13.594] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    13.594] 	Entry deleted from font path.
[    13.595] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    13.595] 	Entry deleted from font path.
[    13.595] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	built-ins
[    13.595] (==) ModulePath set to "/usr/lib/arm-linux-gnueabihf/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[    13.595] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    13.595] (II) Loader magic: 0xb6f9ef10
[    13.595] (II) Module ABI versions:
[    13.595] 	X.Org ANSI C Emulation: 0.4
[    13.595] 	X.Org Video Driver: 15.0
[    13.595] 	X.Org XInput driver : 20.0
[    13.595] 	X.Org Server Extension : 8.0
[    13.596] Initializing built-in extension Generic Event Extension
[    13.596] Initializing built-in extension SHAPE
[    13.596] Initializing built-in extension MIT-SHM
[    13.596] Initializing built-in extension XInputExtension
[    13.596] Initializing built-in extension XTEST
[    13.596] Initializing built-in extension BIG-REQUESTS
[    13.596] Initializing built-in extension SYNC
[    13.597] Initializing built-in extension XKEYBOARD
[    13.597] Initializing built-in extension XC-MISC
[    13.597] Initializing built-in extension SECURITY
[    13.597] Initializing built-in extension XINERAMA
[    13.597] Initializing built-in extension XFIXES
[    13.597] Initializing built-in extension RENDER
[    13.597] Initializing built-in extension RANDR
[    13.597] Initializing built-in extension COMPOSITE
[    13.597] Initializing built-in extension DAMAGE
[    13.597] Initializing built-in extension MIT-SCREEN-SAVER
[    13.597] Initializing built-in extension DOUBLE-BUFFER
[    13.597] Initializing built-in extension RECORD
[    13.597] Initializing built-in extension DPMS
[    13.597] Initializing built-in extension Present
[    13.597] Initializing built-in extension DRI3
[    13.597] Initializing built-in extension X-Resource
[    13.597] Initializing built-in extension XVideo
[    13.597] Initializing built-in extension XVideo-MotionCompensation
[    13.597] Initializing built-in extension SELinux
[    13.597] Initializing built-in extension XFree86-VidModeExtension
[    13.597] Initializing built-in extension XFree86-DGA
[    13.597] Initializing built-in extension XFree86-DRI
[    13.597] Initializing built-in extension DRI2
[    13.597] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
[    13.597] (II) "glx" will be loaded by default.
[    13.597] (WW) "xmir" is not to be loaded by default. Skipping.
[    13.597] (II) LoadModule: "extmod"
[    13.598] (II) Module "extmod" already built-in
[    13.598] (II) LoadModule: "glx"
[    13.610] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    13.873] (II) Module glx: vendor="NVIDIA Corporation"
[    13.873] 	compiled for 4.0.2, module version = 1.0.0
[    13.873] 	Module class: X.Org Server Extension
[    13.873] (II) NVIDIA GLX Module  21.4  Release Build  (integ_stage_rel)  (buildbrain@mobile-u64-286)  Thu Jun 25 15:24:45 PDT 2015
[    13.873] Loading extension GLX
[    13.873] (II) LoadModule: "nvidia"
[    13.874] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    13.907] (II) Module nvidia: vendor="NVIDIA Corporation"
[    13.907] 	compiled for 4.0.2, module version = 1.0.0
[    13.907] 	Module class: X.Org Video Driver
[    13.928] (II) NVIDIA dlloader X Driver  21.4  Release Build  (integ_stage_rel)  (buildbrain@mobile-u64-286)  Thu Jun 25 15:26:03 PDT 2015
[    13.928] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    13.928] (++) using VT number 7

[    13.932] (WW) Falling back to old probe method for NVIDIA
[    13.932] (II) Loading sub module "fb"
[    13.932] (II) LoadModule: "fb"
[    13.933] (II) Loading /usr/lib/xorg/modules/libfb.so
[    13.935] (II) Module fb: vendor="X.Org Foundation"
[    13.935] 	compiled for 1.15.1, module version = 1.0.0
[    13.936] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    13.936] (WW) Unresolved symbol: fbGetGCPrivateKey
[    13.936] (II) Loading sub module "wfb"
[    13.936] (II) LoadModule: "wfb"
[    13.936] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    13.939] (II) Module wfb: vendor="X.Org Foundation"
[    13.939] 	compiled for 1.15.1, module version = 1.0.0
[    13.939] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    13.939] (II) Loading sub module "ramdac"
[    13.939] (II) LoadModule: "ramdac"
[    13.939] (II) Module "ramdac" already built-in
[    13.939] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    13.939] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    13.939] (==) NVIDIA(0): RGB weight 888
[    13.939] (==) NVIDIA(0): Default visual is TrueColor
[    13.939] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    13.940] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration" "true"
[    13.940] (**) NVIDIA(0): Enabling 2D acceleration
[    14.134] (II) NVIDIA(0): NVIDIA GPU GK20A/NullRM (GK20A) at SoC (GPU-0)
[    14.134] (--) NVIDIA(0): Memory: 1937408 kBytes
[    14.134] (--) NVIDIA(0): VideoBIOS: 
[    14.134] (--) NVIDIA(0): Valid display device(s) on GK20A/NullRM at SoC
[    14.134] (--) NVIDIA(0):     DFP-0 (connected)
[    14.134] (--) NVIDIA(0):     DFP-1 (connected)
[    14.134] (--) NVIDIA(0): DFP-0: External TMDS
[    14.134] (--) NVIDIA(0): DFP-1: External TMDS
[    14.134] (**) NVIDIA(0): Option "Ignore"
[    14.134] (**) NVIDIA(0): Ignoring display device DFP-0
[    14.134] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    14.134] (**) NVIDIA(0):     device DFP-1 (Using EDID frequencies has been enabled on
[    14.134] (**) NVIDIA(0):     all display devices.)
[    14.135] (==) NVIDIA(0): 
[    14.135] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    14.135] (==) NVIDIA(0):     will be used as the requested mode.
[    14.135] (==) NVIDIA(0): 
[    14.135] (II) NVIDIA(0): Validated MetaModes:
[    14.135] (II) NVIDIA(0):     "DFP-1:nvidia-auto-select"
[    14.135] (II) NVIDIA(0): Virtual screen size determined to be 1360 x 768
[    14.136] (WW) NVIDIA(0): Unable to support custom viewPortOut 1360 x 765 +0 +1
[    14.137] (WW) NVIDIA(0): Unable to get display device DFP-1's EDID; cannot compute DPI
[    14.137] (WW) NVIDIA(0):     from DFP-1's EDID.
[    14.137] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
[    14.137] (--) Depth 24 pixmap format is 32 bpp
[    14.138] (WW) NVIDIA(GPU-0): Failed to enter interactive mode. 
[    14.150] (EE) NVIDIA(0): Failed to allocate NVIDIA Error Handler
[    14.151] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    14.151] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    14.151] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    14.151] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    14.151] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    14.151] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    14.151] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    14.151] (II) NVIDIA(0):     Config Options in the README.
[    14.151] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[    14.240] Loading extension NV-GLX
[    14.248] (==) NVIDIA(0): Disabling shared memory pixmaps
[    14.248] (==) NVIDIA(0): Backing store enabled
[    14.248] (==) NVIDIA(0): Silken mouse enabled
[    14.260] (==) NVIDIA(0): DPMS enabled
[    14.260] Loading extension NV-CONTROL
[    14.267] (EE) NVIDIA(0): Failed to allocate NVIDIA Damage Manager
[    14.267] Loading extension XINERAMA
[    14.267] (II) Loading sub module "dri2"
[    14.267] (II) LoadModule: "dri2"
[    14.267] (II) Module "dri2" already built-in
[    14.267] (II) NVIDIA(0): [DRI2] Setup complete
[    14.267] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    14.267] (--) RandR disabled
[    14.285] (II) SELinux: Disabled on system
[    14.288] (II) Initializing extension GLX
[    14.352] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[    14.360] (II) config/udev: Adding input device gpio-keys.4 (/dev/input/event1)
[    14.360] (**) gpio-keys.4: Applying InputClass "evdev keyboard catchall"
[    14.360] (II) LoadModule: "evdev"
[    14.360] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    14.370] (II) Module evdev: vendor="X.Org Foundation"
[    14.370] 	compiled for 1.15.0, module version = 2.8.2
[    14.370] 	Module class: X.Org XInput Driver
[    14.370] 	ABI class: X.Org XInput driver, version 20.0
[    14.370] (II) Using input driver 'evdev' for 'gpio-keys.4'
[    14.370] (**) gpio-keys.4: always reports core events
[    14.370] (**) evdev: gpio-keys.4: Device: "/dev/input/event1"
[    14.370] (--) evdev: gpio-keys.4: Vendor 0x1 Product 0x1
[    14.370] (--) evdev: gpio-keys.4: Found keys
[    14.370] (II) evdev: gpio-keys.4: Configuring as keyboard
[    14.371] (**) Option "config_info" "udev:/sys/devices/platform/gpio-keys.4/input/input1/event1"
[    14.371] (II) XINPUT: Adding extended input device "gpio-keys.4" (type: KEYBOARD, id 6)
[    14.371] (**) Option "xkb_rules" "evdev"
[    14.371] (**) Option "xkb_model" "pc105"
[    14.371] (**) Option "xkb_layout" "us"
[    14.373] (II) config/udev: Adding input device tegra-rt5639 Headphone Jack (/dev/input/event0)
[    14.373] (II) No input driver specified, ignoring this device.
[    14.373] (II) This device may have been added with another device file.
[    23.600] (II) config/udev: Adding input device Lite-On Technology Corp. USB Multimedia Keyboard (/dev/input/event2)
[    23.600] (**) Lite-On Technology Corp. USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[    23.600] (II) Using input driver 'evdev' for 'Lite-On Technology Corp. USB Multimedia Keyboard'
[    23.600] (**) Lite-On Technology Corp. USB Multimedia Keyboard: always reports core events
[    23.600] (**) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Device: "/dev/input/event2"
[    23.600] (--) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Vendor 0x4ca Product 0x2f
[    23.600] (--) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Found keys
[    23.600] (II) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Configuring as keyboard
[    23.600] (**) Option "config_info" "udev:/sys/devices/platform/tegra-xhci/usb1/1-3/1-3.1/1-3.1.4/1-3.1.4:1.0/input/input2/event2"
[    23.600] (II) XINPUT: Adding extended input device "Lite-On Technology Corp. USB Multimedia Keyboard" (type: KEYBOARD, id 7)
[    23.600] (**) Option "xkb_rules" "evdev"
[    23.600] (**) Option "xkb_model" "pc105"
[    23.601] (**) Option "xkb_layout" "us"
[    23.602] (II) config/udev: Adding input device Lite-On Technology Corp. USB Multimedia Keyboard (/dev/input/event3)
[    23.602] (**) Lite-On Technology Corp. USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[    23.602] (II) Using input driver 'evdev' for 'Lite-On Technology Corp. USB Multimedia Keyboard'
[    23.602] (**) Lite-On Technology Corp. USB Multimedia Keyboard: always reports core events
[    23.602] (**) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Device: "/dev/input/event3"
[    23.602] (--) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Vendor 0x4ca Product 0x2f
[    23.602] (--) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Found 20 mouse buttons
[    23.602] (--) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Found keys
[    23.602] (II) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Forcing relative x/y axes to exist.
[    23.602] (II) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Configuring as mouse
[    23.602] (II) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: Configuring as keyboard
[    23.602] (**) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: YAxisMapping: buttons 4 and 5
[    23.602] (**) evdev: Lite-On Technology Corp. USB Multimedia Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    23.602] (**) Option "config_info" "udev:/sys/devices/platform/tegra-xhci/usb1/1-3/1-3.1/1-3.1.4/1-3.1.4:1.1/input/input3/event3"
[    23.602] (II) XINPUT: Adding extended input device "Lite-On Technology Corp. USB Multimedia Keyboard" (type: KEYBOARD, id 8)
[    23.602] (**) Option "xkb_rules" "evdev"
[    23.602] (**) Option "xkb_model" "pc105"
[    23.602] (**) Option "xkb_layout" "us"
[    24.597] (II) config/udev: Adding input device USB Optical Mouse (/dev/input/event4)
[    24.597] (**) USB Optical Mouse: Applying InputClass "evdev pointer catchall"
[    24.597] (II) Using input driver 'evdev' for 'USB Optical Mouse'
[    24.597] (**) USB Optical Mouse: always reports core events
[    24.597] (**) evdev: USB Optical Mouse: Device: "/dev/input/event4"
[    24.597] (--) evdev: USB Optical Mouse: Vendor 0x461 Product 0x4d81
[    24.597] (--) evdev: USB Optical Mouse: Found 3 mouse buttons
[    24.597] (--) evdev: USB Optical Mouse: Found scroll wheel(s)
[    24.597] (--) evdev: USB Optical Mouse: Found relative axes
[    24.597] (--) evdev: USB Optical Mouse: Found x and y relative axes
[    24.597] (II) evdev: USB Optical Mouse: Configuring as mouse
[    24.597] (II) evdev: USB Optical Mouse: Adding scrollwheel support
[    24.597] (**) evdev: USB Optical Mouse: YAxisMapping: buttons 4 and 5
[    24.597] (**) evdev: USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    24.597] (**) Option "config_info" "udev:/sys/devices/platform/tegra-xhci/usb1/1-3/1-3.1/1-3.1.3/1-3.1.3:1.0/input/input4/event4"
[    24.597] (II) XINPUT: Adding extended input device "USB Optical Mouse" (type: MOUSE, id 9)
[    24.597] (II) evdev: USB Optical Mouse: initialized for relative axes.
[    24.598] (**) USB Optical Mouse: (accel) keeping acceleration scheme 1
[    24.598] (**) USB Optical Mouse: (accel) acceleration profile 0
[    24.598] (**) USB Optical Mouse: (accel) acceleration factor: 2.000
[    24.598] (**) USB Optical Mouse: (accel) acceleration threshold: 4
[    30.564] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[    30.597] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[    32.282] (II) XKB: reuse xkmfile /var/lib/xkb/server-34CEB476A3CB596DA76FD7010A029F76732EF824.xkm
[    57.388] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[   101.843] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[   101.843] (**) NVIDIA(0):     device DFP-1 (Using EDID frequencies has been enabled on
[   101.844] (**) NVIDIA(0):     all display devices.)
[   101.993] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[   102.041] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1360x768 +0+0 {ViewPortIn=1360x768, ViewPortOut=1360x768+0+0}"
[  1283.019] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1360x768 +0+0 {ViewPortIn=1360x768, ViewPortOut=1360x768+0+0}"
[  1313.328] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[  1313.328] (**) NVIDIA(0):     device DFP-1 (Using EDID frequencies has been enabled on
[  1313.329] (**) NVIDIA(0):     all display devices.)
[  1313.367] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1360x768 +0+0 {ViewPortIn=1360x768, ViewPortOut=1360x768+0+0}"
[  1313.478] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1360x768 +0+0 {ViewPortIn=1360x768, ViewPortOut=1360x768+0+0}"

The output under the TV won’t help much, although it does demonstrate something. These lines for example apply to the connected port DFP-1:

... NVIDIA(0): Validated MetaModes:
... NVIDIA(0):     "DFP-1:nvidia-auto-select"
... NVIDIA(0): Virtual screen size determined to be 1360 x 768
... NVIDIA(0): Unable to support custom viewPortOut 1360 x 765 +0 +1
... NVIDIA(0): Unable to get display device DFP-1's EDID; cannot compute DPI
... NVIDIA(0):     from DFP-1's EDID.
... NVIDIA(0): DPI set to (75, 75); computed from built-in default

This shows the TV did not provide EDID information (at least not in a format the parsing software understood…there is different parsing software in different locations which may be more or less successful than the other software). This could be because of the TV or because of the cable. As a result, defaults are used, which are resolution 1360x768. If your TV works, it’s because it happens to support that default.

I was looking more at remote ssh connection to get the information, and it looks like get-edid and xrandr identify the monitor and so there should be no issue or confusion when doing a remote login to check values. Are you able to run commands via ssh when only the non-functional RPi display is attached? It would be helpful to see output (via ssh login) from:

sudo xrandr
sudo get-edid | edid-decode
sudo get-edid | parse-edid

On a side note, if your television connects to another computer and shows the part indicating no EDID response, then the odds go up that the cable is an issue (but not guaranteed). Should the television give EDID information on another computer, then it tends to validate the cable works (leaving software parsing the suspect). In any case, it gets difficult to move forward without knowing how the RPi display EDID behaves when connected to the Jetson.

I do have that display in use.
Make sure you also have the micro USB connected, this is needed for the backlight supply.
Also, I needed to patch the pll frequency table to add the required clock for the display, see attached patch.

--- a/arch/arm/mach-tegra/tegra12_clocks.c
+++ b/arch/arm/mach-tegra/tegra12_clocks.c
@@ -6954,6 +6954,7 @@ static struct clk_pll_freq_table tegra_plld2_freq_table[] = {
 	{ 12000000, 297000000,  99, 1, 4,  1}, /*1080p @ 60Hz*/
 	{ 12000000, 148500000,  99, 1, 8,  1}, /* 720p @ 60Hz*/
 	{ 12000000,  54000000,  54, 1, 6,  1}, /* 480p @ 60Hz*/
+	{ 12000000,  96000000,  48, 1, 6,  1}, /* 800x480 Adafruit */
 	{ 13000000, 594000000,  91, 1, 2},	/* actual: 591.5 MHz */
 	{ 16800000, 594000000,  71, 1, 2},	/* actual: 596.4 MHz */
 	{ 19200000, 594000000,  62, 1, 2},	/* actual: 595.2 MHz */

I have used ssh to get the EDID for the adafruit display and got the following :

ubuntu@tegra-ubuntu:~$ sudo get-edid | parse-edid
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
Bus 3 doesn't really have an EDID...
Couldn't find an accessible EDID on this computer.
I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.
Partial Read... Try again
ubuntu@tegra-ubuntu:~$ sudo get-edid | edid-decode
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
Bus 3 doesn't really have an EDID...
Couldn't find an accessible EDID on this computer.

I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.
Extracted contents:
header:          00 00 00 00 00 00 00 00
serial number:   00 00 00 00 00 00 00 00 00 00
version:         00 00
basic params:    00 00 00 00 00
chroma info:     00 00 00 00 00 00 00 00 00 00
established:     00 00 00
standard:        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 1:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 2:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 3:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 4:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
extensions:      00
checksum:        00

No header found
Manufacturer: @@@ Model 0 Serial Number 0
EDID version: 0.0
Analog display, Input voltage level: 0.7/0.3 V
Sync: 
Image size is variable
Gamma: 1.00
Monochrome or grayscale display
Established timings supported:
Standard timings supported:
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Checksum: 0x0
EDID block does not conform at all!
	Bad year of manufacture
	Manufacturer name field contains garbage

why there is no EDID information on bus 3?

and regarding the xorg.0.log file, while opening it from the ssh i got this

ubuntu@tegra-ubuntu:/var/log$ ./Xorg.0.log
-bash: ./Xorg.0.log: Permission denied

and I tried also the second method but there is no application that can open the Xorg.0.log.old …

and do I have to patch my own kernel to turn on my display?

To read the log files you will need to prefix your commands with “sudo”…many logs require root privilege. E.G., “cat /var/log/Xorg.0.log”.

In the failed EDID read it looks like your adafruit display breaks some rules and is not readable by the software (formatting and content of the data probably should get an update from adafruit). You’ll see in the messages of failing to read this that there is an email address which you can send results to, along with specification of which display you’re using, and he can perhaps update the software reading EDID and work around the problem (in the past a response to email of required change has been remarkably fast).

Being able to read EDID is the first half of the issue…the second half may be where @mandre gave kernel clock timing update information (this would require adding that one line to your kernel source, followed by compile and install). The summary is that if EDID cannot determine what the mode of the display is, then you have to get lucky and have it work at the clock chosen by default; if EDID is readable, then the valid modes have to include something valid in the kernel. What’s best is if EDID is readable and the “best” mode of the display is also in the valid clock settings (which looks like the 800x480 given by @mandre).

while searching I found a way to edit the EDID as shown here but it doesn’t work with me…
https://learn.adafruit.com/adafruit-tfp401-hdmi-slash-dvi-decoder-to-40-pin-ttl-display/editing-the-edid

the same page suggested that changing the resolution may solve the problem and I found this topic here,
https://devtalk.nvidia.com/default/topic/795733/jetson-tk1-how-can-i-force-a-display-resolution-setting-/?offset=1

can this help me to solve the problem? and how to force my jetson to follow certain resolution?
the main issue here is, how I can get the edid if there is no edid while typing the command “get-edid | parse-edid” ?

The xorg.conf file used to look like the current version plus the append of the “Monitor” section of “get-edid | parse-edid”. You can put sections such as “Monitor” in your xorg.conf and that should be used (EDID silently does the equivalent of putting “Monitor” in xorg.conf). If you know what data should fit there, then you don’t actually need EDID anymore. Here is an example “get-edid | parse-edid” output excerpt from an older monitor on a JTK1 which could be used for illustration:

Section "Monitor"
        Identifier "VX2235wm"
        ModelName "VX2235wm"
        VendorName "VSC"
        # Monitor Manufactured week 28 of 2007
        # EDID version 1.3
        # Digital Display
        DisplaySize 470 300
        Gamma 2.20
        Option "DPMS" "true"
        Horizsync 30-82
        VertRefresh 50-75
        # Maximum pixel clock is 150MHz
        #Not giving standard mode: 1680x1050, 60Hz
        #Not giving standard mode: 1600x1200, 60Hz
        #Not giving standard mode: 1440x900, 60Hz
        #Not giving standard mode: 1400x1050, 60Hz
        #Not giving standard mode: 1280x1024, 60Hz
        #Not giving standard mode: 1280x960, 60Hz
        #Not giving standard mode: 1152x864, 75Hz
        #Not giving standard mode: 640x400, 70Hz
        Modeline        "Mode 0" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync 
EndSection

Notice that comments start with “#”, and that some of the lines are not actually mandatory…here’s a subset of lines which I believe would be a minimum to put in xorg.conf for the “Monitor” section:

Section "Monitor"
        Identifier "VX2235wm"
        Option "DPMS" "true"
        Horizsync 30-82
        VertRefresh 50-75
        Modeline        "Mode 0" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync 
EndSection

Of those, you can probably find vertical and horizontal ranges and edit to match your monitor. Identifier is not important, but probably choose something like “Adafruit”. The key to getting the display to be as you want is the “Modeline”. There are programs out there to help compute a modeline based on other information, as well as documentation…it’s complicated and I don’t know the answer offhand. You’ll have to research that and the information the calculations want.

The xrandr command can be used to test prior to edit if you want. See “man xrandr”. Basically earlier EDID commands are used to directly query and display information in general for the display…making changes from this means editing xorg.conf and restarting X11. xrandr is tied to currently running display and can edit display parameters without restarting X11…but changes would go away upon reboot.

Note about xorg.conf: The file is arranged in "Section " blocks. One block can refer to another block. The “Monitor” section can have as many copies as you want for different monitors, e.g., having 2 or 3 monitors on a large desktop graphics card. The “Device” is about the graphics card. I don’t remember enough of this anymore, but there should be another section (I think “Screen”) which ties together what you will see on a given monitor by naming the identifier of a “Monitor” section and a “Device” section. It gets complicated, there are good reasons for doing away with manual configuration.

Big note: If you edited the EDID data EEPROM you can no longer use that information to get the format added to valid EDID parsing. The email address that was in the original message is VERY useful, as the data from a slightly broken format could be added to the next update from the maintainer. Be very careful about choosing between editing an EEPROM and instead sending the data to the email address.