This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/EVMK2G: Booting hangs with HDMI monitor connected

Part Number: EVMK2G

Tool/software: Linux

Hi,

Booting with HDMI monitor connected hangs the boot process. This is independent on the state of the SW13 and SW14 switches (either both on or both off). I include below the boot log. I have LCD panel installed (in case it matters).

I am using the latest k2g-evm-linux-05.02.00.10.img.

On software-dl.ti.com/.../Foundational_Components_Graphics.html I have found that modetest can be used to test the display driver.

WhenI boot without HDMI monitor connected and execute modetest I obtain:

id      encoder status          name            size (mm)       modes   encoders
35      0       disconnected    HDMI-A-1        0x0             0       34
  props:
        1 EDID:
                flags: immutable blob
                blobs:

                value:
        2 DPMS:
                flags: enum
                enums: On=0 Standby=1 Suspend=2 Off=3
                value: 0
        5 link-status:
                flags: enum
                enums: Good=0 Bad=1
                value: 0

Then I connect HDMI monitor and run modetest again:

id      encoder status          name            size (mm)       modes   encoders
35      0       connected       HDMI-A-1        530x300         8       34
  modes:
        name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
  1280x720 60 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  1280x720 60 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver
  1280x720 50 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  1024x768 70 1024 1048 1184 1328 768 771 777 806 75000 flags: nhsync, nvsync; type: driver
  1024x768 60 1024 1048 1184 1344 768 771 777 806 65000 flags: nhsync, nvsync; type: driver
  832x624 75 832 864 928 1152 624 625 628 667 57284 flags: nhsync, nvsync; type: driver
  800x600 75 800 816 896 1056 600 601 604 625 49500 flags: phsync, pvsync; type: driver
  800x600 72 800 856 976 1040 600 637 643 666 50000 flags: phsync, pvsync; type: driver
  props:
        1 EDID:
                flags: immutable blob
                blobs:

                value:
                        00ffffffffffff004c2d920d31515a5a
                        181b010380351e782a9ff5a555509e26
                        105054bfef80714f81c0810081809500
                        a9c0b3000101023a801871382d40582c
                        4500132b2100001e011d007251d01e20
                        6e285500132b2100001e000000fd0032
                        4b1e5111000a202020202020000000fc
                        00533234443333300a202020202001cd
                        020311b14690041f13031265030c0010
                        00011d00bc52d01e20b8285540132b21
                        00001e8c0ad090204031200c40550013
                        2b210000188c0ad08a20e02d10103e96
                        00132b21000018000000000000000000
                        00000000000000000000000000000000
                        00000000000000000000000000000000
                        00000000000000000000000000000021
        2 DPMS:
                flags: enum
                enums: On=0 Standby=1 Suspend=2 Off=3
                value: 0
        5 link-status:
                flags: enum
                enums: Good=0 Bad=1
                value: 0

Then I run modetest again and the system hangs.

The courious thing is that I obtain the same results independently on the state of the SW13 and SW14 switches (that theoretically choose between onboard LCD and HDMI)

Thank you and best regards

Adam

---- boot log ---


U-Boot 2018.01-g313dcd69c2 (Dec 16 2018 - 07:15:30 +0000)

CPU: 66AK2Gx-60 SR1.0
Model: Texas Instruments K2G General Purpose EVM
DRAM:
Clear entire DDR3 memory to enable ECC
2 GiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Net:   eth0: netcp@4000000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** Unable to read file boot.scr **
** Unable to read file uEnv.txt **
32832 bytes read in 13 ms (2.4 MiB/s)
K2_BM_15.07-53-ge1f885a SoC:k2g built:05:44:19, Dec 16 2018

## installed monitor @ 0xc0f7000, freq [24000000], status 202338304
33620 bytes read in 19 ms (1.7 MiB/s)
0 - Name:'pmmc@2900000' type:'internal memory mapped' supports: load start
Load Remote Processor 0 with data@addr=0x82000000 33620 bytes: Success!
3916288 bytes read in 204 ms (18.3 MiB/s)
34793 bytes read in 18 ms (1.8 MiB/s)
29386 bytes read in 11 ms (2.5 MiB/s)
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Ramdisk to 8fff7000, end 8ffff7e9 ... OK
   Loading Device Tree to 8ffec000, end 8fff62c9 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.79-gbde58ab01e (oe-user@oe-host) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #1 SMP PREEMPT Thu Dec 20 03:57:44 UTC 2018
[    0.000000] CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), cr=30c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] OF: fdt: Machine model: Texas Instruments K2G General Purpose EVM
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Switching physical address space to 0x800000000
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x000000081f800000, size 8 MiB
[    0.000000] OF: reserved mem: initialized node dsp-common-memory@81f800000, compatible id shared-dma-pool
[    0.000000] cma: Reserved 48 MiB at 0x000000087cc00000
[    0.000000] percpu: Embedded 15 pages/cpu @eedce000 s31308 r8192 d21940 u61440
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 491840
[    0.000000] Kernel command line: console=ttyS0,115200n8 video=HDMI-A-1:1024x768 root=PARTUUID=7408e099-02 rw rootfstype=ext4 rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1883588K/1974272K available (8192K kernel code, 289K rwdata, 2544K rodata, 2048K init, 280K bss, 33340K reserved, 57344K cma-reserved, 1261568K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0a00000   (10208 kB)
[    0.000000]       .init : 0xc0e00000 - 0xc1000000   (2048 kB)
[    0.000000]       .data : 0xc1000000 - 0xc1048678   ( 290 kB)
[    0.000000]        .bss : 0xc104a000 - 0xc1090320   ( 281 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1.
[    0.000000]  Tasks RCU enabled.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000007] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.000027] Switching to timer-based delay loop, resolution 41ns
[    0.000219] keystone_timer_init: failed to get clock
[    0.000247] Failed to initialize '/soc/timer@2210000': -517
[    0.000645] Console: colour dummy device 80x30
[    0.000696] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000)
[    0.000722] pid_max: default: 32768 minimum: 301
[    0.000897] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000919] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001791] CPU: Testing write buffer coherency: ok
[    0.001846] CPU0: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.002169] /cpus/cpu@0 missing clock-frequency property
[    0.002191] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.040006] Setting up static identity map for 0x80200000 - 0x80200138
[    0.060016] Hierarchical SRCU implementation.
[    0.080323] EFI services will not be available.
[    0.100110] smp: Bringing up secondary CPUs ...
[    0.100128] smp: Brought up 1 node, 1 CPU
[    0.100144] SMP: Total of 1 processors activated (48.00 BogoMIPS).
[    0.100158] CPU: All CPU(s) started in HYP mode.
[    0.100169] CPU: Virtualization extensions available.
[    0.100993] devtmpfs: initialized
[    0.110393] random: get_random_u32 called from bucket_table_alloc+0x104/0x22c with crng_init=0
[    0.120343] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.120689] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.120717] futex hash table entries: 256 (order: 2, 16384 bytes)
[    0.122731] pinctrl core: initialized pinctrl subsystem
[    0.123486] DMI not present or invalid.
[    0.123894] NET: Registered protocol family 16
[    0.131650] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.132949] cpuidle: using governor ladder
[    0.133004] cpuidle: using governor menu
[    0.133551] No ATAGs?
[    0.133618] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.133638] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.141419] davinci_gpio 2603000.gpio: Error -517 getting gpio clock
[    0.143191] davinci_gpio 260a000.gpio: Error -517 getting gpio clock
[    0.196924] i2c_davinci 2530000.i2c: could not find pctldev for node /soc/pinmux@02621000/pinmux_i2c0_pins, deferring probe
[    0.196994] i2c_davinci 2530400.i2c: could not find pctldev for node /soc/pinmux@02621000/pinmux_i2c1_pins, deferring probe
[    0.197304] media: Linux media interface: v0.10
[    0.197370] Linux video capture interface: v2.00
[    0.197500] pps_core: LinuxPPS API ver. 1 registered
[    0.197515] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.197545] PTP clock support registered
[    0.197574] EDAC MC: Ver: 3.0.0
[    0.198092] dmi: Firmware registration failed.
[    0.198305] Advanced Linux Sound Architecture Driver Initialized.
[    0.200771] clocksource: Switched to clocksource arch_sys_counter
[    0.212235] NET: Registered protocol family 2
[    0.213057] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.213164] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.213374] TCP: Hash tables configured (established 8192 bind 8192)
[    0.213492] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.213547] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.213762] NET: Registered protocol family 1
[    0.250927] RPC: Registered named UNIX socket transport module.
[    0.250947] RPC: Registered udp transport module.
[    0.250962] RPC: Registered tcp transport module.
[    0.250975] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.251297] Trying to unpack rootfs image as initramfs...
[    0.255250] Freeing initrd memory: 36K
[    0.255646] hw perfevents: no interrupt-affinity property for /pmu, guessing.
[    0.255897] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
[    0.257140] platform alarmtimer: set dma_pfn_offset00780000
[    0.258266] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    0.265634] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.281347] NFS: Registering the id_resolver key type
[    0.281393] Key type id_resolver registered
[    0.281410] Key type id_legacy registered
[    0.281475] ntfs: driver 2.1.32 [Flags: R/O].
[    0.284408] bounce: pool size: 64 pages
[    0.284491] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    0.284512] io scheduler noop registered
[    0.284527] io scheduler deadline registered
[    0.284704] io scheduler cfq registered (default)
[    0.284722] io scheduler mq-deadline registered
[    0.284736] io scheduler kyber registered
[    0.285206] keystone_irq soc:keystone_irq@026202a0: irqchip registered, nr_irqs 28
[    0.287077] pinctrl-single 2621000.pinmux: please update dts to use #pinctrl-cells = <1>
[    0.287691] pinctrl-single 2621000.pinmux: 260 pins at pa f0854000 size 1040
[    0.385154] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
[    0.385281] platform serial8250: set dma_pfn_offset00780000
[    0.393764] connector-hdmi connector: failed to find video source
[    0.409664] brd: module loaded
[    0.419266] loop: module loaded
[    0.424098] platform Fixed MDIO bus.0: set dma_pfn_offset00780000
[    0.424437] libphy: Fixed MDIO Bus: probed
[    0.427450] i2c /dev entries driver
[    0.428257] IR NEC protocol handler initialized
[    0.428274] IR RC5(x/sz) protocol handler initialized
[    0.428288] IR RC6 protocol handler initialized
[    0.428301] IR JVC protocol handler initialized
[    0.428313] IR Sony protocol handler initialized
[    0.428325] IR SANYO protocol handler initialized
[    0.428339] IR Sharp protocol handler initialized
[    0.428351] IR MCE Keyboard/mouse protocol handler initialized
[    0.428363] IR XMP protocol handler initialized
[    0.430724] sdhci: Secure Digital Host Controller Interface driver
[    0.430737] sdhci: Copyright(c) Pierre Ossman
[    0.431464] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.433472] ledtrig-cpu: registered to indicate activity on CPUs
[    0.436472] platform snd-soc-dummy: set dma_pfn_offset00780000
[    0.438679] NET: Registered protocol family 10
[    0.451285] Segment Routing with IPv6
[    0.451400] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    0.452196] NET: Registered protocol family 17
[    0.452506] Key type dns_resolver registered
[    0.452745] Registering SWP/SWPB emulation handler
[    0.455734] davinci_gpio 2603000.gpio: Error -517 getting gpio clock
[    0.457259] davinci_gpio 260a000.gpio: Error -517 getting gpio clock
[    0.465773] connector-hdmi connector: failed to find video source
[    0.470692] ti-sci 2921c00.pmmc: ABI: 2.4 (firmware rev 0x0011 '0.1.1-50-g129ef (Eagle)')
[    0.484542] random: fast init done
[    0.544359] ti-sci-clk 2921c00.pmmc:clocks: get-parent failed for dev=76, clk=11, ret=-19
[    0.544553] ti-sci-clk 2921c00.pmmc:clocks: get-parent failed for dev=76, clk=11, ret=-19
[    0.544917] ti-sci-clk 2921c00.pmmc:clocks: get-parent failed for dev=76, clk=11, ret=-19
[    0.554496] keystone timer clock @100000000 Hz
[    0.574224] edma 2700000.edma: TI EDMA DMA engine driver
[    0.574994] edma 2728000.edma: memcpy is disabled
[    0.580538] edma 2728000.edma: TI EDMA DMA engine driver
[    0.583708] sii9022 1-003b: failed to find video source
[    0.585078] ti,keystone-serdes 2320000.phy: init fw ks2_pcie_serdes.bin: version 3.3.0.2c
[    0.587224] OF: PCI: host bridge /soc/pcie@21800000 ranges:
[    0.587250] OF: PCI:   No bus range found for /soc/pcie@21800000, using [bus 00-ff]
[    0.587297] OF: PCI:    IO 0x23250000..0x23253fff -> 0x00000000
[    0.587338] OF: PCI:   MEM 0x70000000..0x7fffffff -> 0x70000000
[    1.588969] keystone-pcie 21800000.pcie: phy link never came up
[    1.589202] keystone-pcie 21800000.pcie: PCI host bridge to bus 0000:00
[    1.589226] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.589245] pci_bus 0000:00: root bus resource [io  0x0000-0x3fff]
[    1.589263] pci_bus 0000:00: root bus resource [mem 0x70000000-0x7fffffff]
[    1.589709] PCI: bus0: Fast back to back transfers disabled
[    1.589857] PCI: bus1: Fast back to back transfers enabled
[    1.589910] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    1.590210] pcieport 0000:00:00.0: limiting MRRS to 256
[    1.590539] pcieport 0000:00:00.0: Signaling PME with IRQ 320
[    1.590856] pcieport 0000:00:00.0: AER enabled with IRQ 320
[    1.591496] keystone-navigator-qmss soc:qmss@4020000: qmgr start queue 0, number of queues 128
[    1.591686] keystone-navigator-qmss soc:qmss@4020000: added qmgr start queue 0, num of queues 128, reg_peek f0e77000, reg_status   (null), reg_config f0e79000, reg_region f0e7b000, reg_push f0e7d000, reg_pop f0e7d000
[    1.593299] keystone-navigator-dma soc:knav_dmas@0: DMA dma_gbe registered 53 logical channels, flows 32, tx chans: 21, rx chans: 32
[    1.595029] console [ttyS0] disabled
[    1.595091] 2530c00.serial: ttyS0 at MMIO 0x2530c00 (irq = 23, base_baud = 12000000) is a TI DA8xx/66AK2x
[    2.687505] console [ttyS0] enabled
[    2.693097] 2531400.serial: ttyS2 at MMIO 0x2531400 (irq = 24, base_baud = 12000000) is a TI DA8xx/66AK2x
[    2.703883] omap_dss6 2540000.dss: bound 2550000.dispc (ops dispc6_component_ops)
[    2.711541] platform omapdrm.0: set dma_pfn_offset00780000
[    2.717766] connector-hdmi connector: failed to find video source
[    2.725745] cadence-qspi 2940000.qspi: non-uniform erase sector maps are not supported yet.
[    2.734163] cadence-qspi 2940000.qspi: s25fl512s (65536 Kbytes)
[    2.740168] 6 ofpart partitions found on MTD device 2940000.qspi.0
[    2.746372] Creating 6 MTD partitions on "2940000.qspi.0":
[    2.751880] 0x000000000000-0x000000100000 : "QSPI.u-boot-spl-os"
[    2.759135] 0x000000100000-0x000000140000 : "QSPI.u-boot-env"
[    2.766011] 0x000000140000-0x000000180000 : "QSPI.skern"
[    2.772440] 0x000000180000-0x0000001c0000 : "QSPI.pmmc-firmware"
[    2.779495] 0x0000001c0000-0x0000009c0000 : "QSPI.kernel"
[    2.786004] 0x0000009c0000-0x000004000000 : "QSPI.file-system"
[    2.794216] spi_davinci 21805400.spi: DMA is not supported (-19)
[    2.800715] spi_davinci 21805400.spi: Controller at 0xf0e99400
[    2.807764] spi_davinci 21805800.spi: DMA is not supported (-19)
[    2.815666] m25p80 spi1.0: n25q128a13 (16384 Kbytes)
[    2.820672] 2 ofpart partitions found on MTD device spi1.0
[    2.826210] Creating 2 MTD partitions on "spi1.0":
[    2.831032] 0x000000000000-0x000000100000 : "u-boot-spl"
[    2.837597] 0x000000100000-0x000001000000 : "misc"
[    2.843577] spi_davinci 21805800.spi: Controller at 0xf0e9b800
[    2.850541] spi_davinci 21805c00.spi: DMA is not supported (-19)
[    2.857069] spi_davinci 21805c00.spi: Controller at 0xf0e9dc00
[    2.863998] spi_davinci 21806000.spi: DMA is not supported (-19)
[    2.870453] spi_davinci 21806000.spi: Controller at 0xf0e9f000
[    2.930815] davinci_mdio 4200f00.mdio: davinci mdio revision 1.7, bus freq 2500000
[    2.938381] libphy: 4200f00.mdio: probed
[    2.943428] davinci_mdio 4200f00.mdio: phy[0]: device 4200f00.mdio:00, driver Micrel KSZ9031 Gigabit PHY
[    2.953899] netcp-1.0 2620110.netcp: ALE enabled
[    2.958722] netcp-1.0 2620110.netcp: initialized cpsw ale version 1.4
[    2.965263] netcp-1.0 2620110.netcp: ALE Table size 64
[    2.970510] netcp-1.0 2620110.netcp: cpts: overflow check period 500 (jiffies)
[    2.977830] netcp-1.0 2620110.netcp: CPTS: ref_clk_freq:250000000 calc_mult:2147483648 calc_shift:29 error:0 nsec/sec
[    2.989528] netcp-1.0 2620110.netcp: module(netcp-xgbe) not used for device
[    2.997519] sdhci-omap 23000000.mmc: Got CD GPIO
[    3.061043] mmc0: SDHCI controller on 23000000.mmc [23000000.mmc] using ADMA
[    3.119073] mmc0: host does not support reading read-only switch, assuming write-enable
[    3.129997] mmc0: new high speed SDHC card at address 0007
[    3.136017] mmcblk0: mmc0:0007 SD32G 29.0 GiB
[    3.140871] mmc1: SDHCI controller on 23100000.mmc [23100000.mmc] using ADMA
[    3.151413]  mmcblk0: p1 p2
[    3.157523] sii9022 1-003b: SiI902xA HDMI device b0, rev 2, tpi 3
[    3.167218] omapdrm omapdrm.0: DMM not available, disable DMM support
[    3.177481] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.184187] [drm] No driver support for vblank timestamp query.

  • Hi,

    Did you modify the dts file (or did you use the prebuilt binaries from linux SDK)? If yes, could you share it?

    Best Regards,
    Yordan
  • Hi,

    No, I didn't. I just wrote the latest image to an SD card under Windows and booted from it.

    Best regards

    Adam
  • Hi,

    Sorry for the delay. Let me test this on my side and I will clarify.

    Best Regards,
    Yordan
  • Yordan,

    we have bought a second K2G EVM and I have thought we could try it without anything else connected (just power and USB UART, no onboard LCD screen, I even used physically the same SD card). But there is a new problem with that seconf board. Now on th Linux UART I get just a single character "▒". I just swapped the two boards, the Putty configuration is the same 115200/8/1, no parity, Flow control XON/XOFF (except, of course, the second EVM appears at different COM). I suspect the second EVM uses different Linux UART configuration. Which is that? How one can know it?

    On the second EVM I connect to the BMC COM (with the same config on the PC as for the Linux COM) and I can see BMC boot displayed with no problem.

    Thanks,

    Adam

  • Hi Adam,

    Regarding the HDMI problem, I managed to get my hands on an hdmi display and test on my side. I am seeing the same problem, kernel hangs at:
    [ 3.163468] sii9022 1-003b: SiI902xA HDMI device b0, rev 2, tpi 3
    [ 3.172120] omapdrm omapdrm.0: DMM not available, disable DMM support
    [ 3.182404] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    [ 3.189013] [drm] No driver support for vblank timestamp query.

    When booting with hdmi connected. I've looped the design team to help on this.

    Regarding the second board uart configurations should be the same. Can you try configuring SW1 (as described in the EVM TRM:
    www.ti.com/.../sprui65a.pdf) and try the other UART connector on the board?

    Best Regards,
    Yordan
  • Hi,

    I noticed that in tisdk_k2g-evm_defconfig CONFIG_DRM_SII902X is NOT set. Could you try adding:
    CONFIG_DRM_SII902X=y

    And rebuilding the kernel?


    Best Regards,
    Yordan
  • Hi Yordan,

    thank you very much for your answer.

    Regarding rebuilding the kernel - did it work for you? If so, could you post the rebuilt kernel so that I can replace it on the SD card?

    Regarding the second EVM - I understand you mean the SW12 to output the through the DB connector. Didn't think of that! I will check it.

    Best regards,

    Adam

  • Hi, Adam,

    Before you run the modetest the 2nd time, could you check if modetest process is still running? If it is, kill it before running the 2nd time. I checked our system test logs in which we ran multiple times without issues though they are in different mode:

    modetest
    modetest -t -v -d -s 35@40:1280x720-60@AR24
    modetest -t -v -d -s 35@40:1024x576-60@AR24
    modetest -t -v -d -s 35@40:832x624-75@AR24
    modetest -t -v -d -s 35@40:800x600-75@AR24
    modetest -t -v -d -s 35@40:800x600-72@AR24

    In the script, there is a killall -9 modetest 2>&1 after each modetest. Could you also try to run the same test we did?

    Rex
  • Hi Adam,

    Please test Rex's suggestion on your side. The CONFIG_DRM_SII902X=y does not work well.

    Best Regards,
    Yordan
  • Hi, Adam,

    Does it work for you? If it works, please click "Resolved". I'll close this one for now, but you can always reply to this thread to re-open it. If you have new issue, please submit a new e2e thread. Thanks.

    Rex
  • Hi Yordan,

    I tried UART on the second EVM. I get the same result when using UART as when using USB COM. This means that there is this strange character coming on the USB COM (yes, on USB COM) also when the position of SW12 is to direct the output through the UART, and there is nothing coming out of UART, which means the strange character appears always on USB COM independently on the position of the SW12 switch. I did the same test with the first EVM and everything works fine. Is there anything I should try before claiming the EVM replacement? Thank you.

    Regards,

    Adam

  • Hi Rex,

    I had to use a different HDMI monitor (I'll call it monitor 2) than before and the behaviour was also different. Monitor 2 is Philips 223V5 and monitor 3 is HP Z24nf G2.

    Accidentally I connected the monitor 2 before logging in and I saw this (this did not happen with monitor 1):

    root@k2g-evm:~# [ 46.320807] i2c_davinci 2530400.i2c: controller timed out
    [ 47.360801] i2c_davinci 2530400.i2c: controller timed out
    ...
    [ 55.680803] i2c_davinci 2530400.i2c: controller timed out
    [ 55.686220] sii9022 1-003b: error releasing DDC Bus Access

    I logged in, executed modetest and the EVM hanged.

    I rebooted with the monitor 2 connected and this information appeared before boot hanged:

    [ 4.240818] i2c_davinci 2530400.i2c: controller timed out
    ...
    [ 13.600803] i2c_davinci 2530400.i2c: controller timed out
    [ 13.606204] sii9022 1-003b: error releasing DDC Bus Access

    Rebooted it again and this time saw this:

    [ 3.157553] sii9022 1-003b: SiI902xA HDMI device b0, rev 2, tpi 3
    [ 3.167243] omapdrm omapdrm.0: DMM not available, disable DMM support
    [ 3.177508] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    [ 3.184216] [drm] No driver support for vblank timestamp query.

    I thought this might be an issue with the monitor 2 going to sleep during boot. I got antoher monitor (monitor 3) in which I could switch of the auto sleep and this time the EVM got through all the boot process.

    Executing modetest produces:

    root@k2g-evm:~# modetest
    trying to open device 'i915'...failed
    trying to open device 'amdgpu'...failed
    trying to open device 'radeon'...failed
    trying to open device 'nouveau'...failed
    trying to open device 'vmwgfx'...failed
    trying to open device 'omapdrm'...done
    Encoders:
    id crtc type possible crtcs possible clones
    34 0 TMDS 0x00000001 0x00000000

    Connectors:
    id encoder status name size (mm) modes encoders
    35 0 disconnected HDMI-A-1 0x0 0 34
    props:
    1 EDID:
    flags: immutable blob
    blobs:

    value:
    2 DPMS:
    flags: enum
    enums: On=0 Standby=1 Suspend=2 Off=3
    value: 0
    5 link-status:
    flags: enum
    enums: Good=0 Bad=1
    value: 0

    CRTCs:
    id fb pos size
    40 0 (0,0) (0x0)
    0 0 0 0 0 0 0 0 0 0 flags: ; type:
    props:
    23 CTM:
    flags: blob
    blobs:

    value:
    24 GAMMA_LUT:
    flags: blob
    blobs:

    value:
    25 GAMMA_LUT_SIZE:
    flags: immutable range
    values: 0 4294967295
    value: 256
    30 background:
    flags: range
    values: 0 16777215
    value: 0
    31 trans-key-mode:
    flags: enum
    enums: disable=0 gfx-dst=1 vid-src=2
    value: 0
    32 trans-key:
    flags: range
    values: 0 16777215
    value: 0
    33 alpha_blender:
    flags: range
    values: 0 1
    value: 0
    27 zorder:
    flags: range
    values: 0 0
    value: 0

    Planes:
    id crtc fb CRTC x,y x,y gamma size possible crtcs
    36 0 0 0,0 0,0 0 0x00000001
    formats: XR24 AR24 RX24 RA24 YUYV UYVY NV12
    props:
    6 type:
    flags: immutable enum
    enums: Overlay=0 Primary=1 Cursor=2
    value: 1
    27 zorder:
    flags: range
    values: 0 0
    value: 0
    37 zpos:
    flags: range
    values: 0 0
    value: 0
    28 global_alpha:
    flags: range
    values: 0 255
    value: 255
    29 pre_mult_alpha:
    flags: range
    values: 0 1
    value: 0

    Frame buffers:
    id size pitch

    I tried to kill modetest but there was no modetest process running:

    root@k2g-evm:~# killall -9 modetest 2>&1
    killall: modetest: no process killed

    Then I tried all modetest options you listed with monitor 3 but I get the same message (except for the resolution) in all cases:

    root@k2g-evm:~# modetest -t -v -d -s 35@40:1280x720-60@AR24
    trying to open device 'i915'...failed
    trying to open device 'amdgpu'...failed
    trying to open device 'radeon'...failed
    trying to open device 'nouveau'...failed
    trying to open device 'vmwgfx'...failed
    trying to open device 'omapdrm'...done
    failed to find mode "1280x720" for connector 35
    failed to create dumb buffer: Invalid argument
    failed to create dumb buffer: Invalid argument

    I rebooted the board with the monitor 3 connected to see if the EVM boots consistently with monitor 3, but no, it does not. I tried two times more and the boot hanged in both with these as the last messages:

    [ 3.157548] sii9022 1-003b: SiI902xA HDMI device b0, rev 2, tpi 3
    [ 3.167235] omapdrm omapdrm.0: DMM not available, disable DMM support
    [ 3.177505] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    [ 3.184217] [drm] No driver support for vblank timestamp query.

    So I rebooted the EVM and connected monitor 3 after logging in.

    Executing modetest works. Then executing modetest -t -v -d -s 35@40:1280x720-60@AR24 hanged. There was no modetest process running in between.

    So I disconnected monitor 3, rebooted the EVM again and connected monitor 3 after logging in, and executed modetest -t -v -d -s 35@40:1280x720-60@AR24 directly:

    root@k2g-evm:~# modetest -t -v -d -s 35@40:1280x720-60@AR24
    trying to open device 'i915'...failed
    trying to open device 'amdgpu'...failed
    trying to open device 'radeon'...failed
    trying to open device 'nouveau'...failed
    trying to open device 'vmwgfx'...failed
    trying to open device 'omapdrm'...done
    failed to find mode "1280x720" for connector 35
    failed to create dumb buffer: Invalid argument
    failed to create dumb buffer: Invalid argument

    then EVM hangs.

    I do not understand this random behaviour.

    Monitor 3 just shows "no input signal" message all the time.

    Best regards,

    Adam

  • Hi Adam,

    For the Uart problem. You run the prebuilt images from Processor SDK Linux (v05.02), right? Can you verify that the SD card is correctly created (i.e. try to boot the same sd card with the same images on the other board)? Also try different sd card on the problematic board, it might be a problem with the sd card not being compatible (very very rare case, but it I've seen it with other TI SoCs).

    Best Regards,
    Yordan
  • Hi Adam,

    As for the following behaviour:
    root@k2g-evm:~# modetest -t -v -d -s 35@40:1280x720-60@AR24
    trying to open device 'i915'...failed
    trying to open device 'amdgpu'...failed
    trying to open device 'radeon'...failed
    trying to open device 'nouveau'...failed
    trying to open device 'vmwgfx'...failed
    trying to open device 'omapdrm'...done
    failed to find mode "1280x720" for connector 35
    failed to create dumb buffer: Invalid argument
    failed to create dumb buffer: Invalid argument

    It is because your board cannot detect that HDMI is connected, see the log from first execution of modetest:
    35 0 disconnected HDMI-A-1 0x0 0 34

    I will escalate this to the team.

    Best Regards,
    Yordan
  • Hi, Adam,

    Sorry for the confusion. Internal investigation shows that the TI Linux CoreSDK works fine, but the Processor Linux SDK 5.2 has the issue.
    The previous release PLSDK 5.1 works fine. Could you try 5.1 while we investigate what was introduced into 5.2 to cause the issue.

    Thanks!

    Rex
  • Hi Rex,

    Thanks a lot for your message. Do you mean by version 5.1 that we should use PROCESSOR-SDK-LINUX-K2G  05_01_00_11?

    Best regards,

    Adam

  • Hi Yordan,

    for the UART problem: yes, we have used the prebuilt images from Processor SDK Linux (v05.02). We have tried what you said: we have used two different SD cards from different manufacturers. We have also tried the SD cards that come with the EVM. The same result in the three cases: EVM 1 works fine, EVM 2 produces only the single strange character. We have also tried \processor_sdk_rtos_k2g_5_02_00_10\prebuilt-sdcards\evmK2G\sd_card_img which blinks the LED in the EVM 1 and does nothing in EVM 2.

    Thank you and best regards,

    Adam
  • Hi Yordan,

    I am not clear if there is something I am doing wrong or this is a software problem the team will help to solve.

    Thank you and best regards,

    Adam
  • Hi Adam,

    Yes, Processor SDK 05.01 has been tested internally, as Rex said and HDMI works with it. So revert back to Processor SDK Linux v05.01:
    software-dl.ti.com/.../index_FDS.html

    Best Regards,
    Yordan
  • HI, Adam,

    It's not something you did wrong. TI will address this issue in 6.0 release. It works for Kernel Core release internally which was used by PLSDK 5.2, but issue occurs in Linux SDK release. We suspect the issue may be related to kernel Kconfig differences because there wasn't any patch applied for HDMI in PLSDK. But when packaging the PLSDK, PLSDK has its own Kconfig and also different between 5.1 and 5.2 releases.. If you like, you can try to revert back to 5.1 Kconfig to see if it solves the issue.

    Rex

  • Hi Rex,

    I confirm the HDMI display works with PLSDK 5.01, the terminal window is being shown and I was able to log in using a keyboard attached to the EVM. Thank you.

    Best regards,

    Adam