Problems running capture_encode demo

Weilong Chen

Other Parts Discussed in Thread: PMP

I have problems when running capture_encode demo. It stops at "connect call for dei-display". Is it correct to connect YPrPb video output to daughter board J5~J7? Can the demo be run through even if the input video source is not correct? Anyone can help? Thanks!

root@dm816x-evm:/usr/share/ti/ti-omx# ./capture_encode_a8host_debug.xv5T -o samp

le.h264 -m 1080p -f 60 -b 1000000 -n 1000

output file: sample.h264

bit_rate: 1000000

frame_rate: 60

num_frames: 1000

mode: 1080p

Capture-Encode example

===============================

OMX_Init completed

UIAClient is ready to send a UIA configuration command

UIAClient received UIA_CONFIGURE_ACK

UIAClient is done sending requests

UIAClient is ready to send a UIA configuration command

UIAClient received UIA_CONFIGURE_ACK

UIAClient is done sending requests

openeing file

capture compoenent is created

control TVP compoenent is created

Buffer Size computed: 3110400

set input port params (width = 1920, height = 1080)enable capture output port

got eventEnable/Disable Event

dei compoenent is created

set input port params (width = 1920, height = 1080)

set output port params (width = 1920, height = 1080)set output port params (widt

h = 1920, height = 1080)set number of channelsset input resolutionset output res

olutionenable dei input port

got eventEnable/Disable Event

enable dei output port 0

got eventEnable/Disable Event

enable dei output port 1

got eventEnable/Disable Event

encoder compoenent is created

found handle 0x123008 for component OMX.TI.VPSSM3.VFDC

got display handle

found handle 0x126b10 for component OMX.TI.VPSSM3.CTRL.DC

Buffer Size computed: 4147200

set input port params (width = 1920, height = 1080)setting input and output memo

ry type to defaultenable input port

got eventEnable/Disable Event

connect call for capture-Dei

connect call for dei- encoder

connect call for dei-display

over 13 years ago

0 Sathish over 13 years ago

TI__Intellectual 1950 points

Hi Weilong Chen,

Please refer the below wiki for running the OMX tests:
http://processors.wiki.ti.com/index.php/OMX_EZSDK_Examples

Thanks!!

Regards
Sathish

0 Weilong Chen over 13 years ago in reply to Sathish

Intellectual 390 points

Hi Sathish

Thanks for your information. But I don't quite understand the following statement. How to disable SDK binaries auto-loading? What is the SDK
"init sequence" and how do I know whether it is disabled or not? I don't know where to execute the following commands like "prcm_config_app" etc.

Regards,

Weilong

For running the application following steps are required (These steps assume that all the binaries are stored in same folder). Please note, SDK would autoload the binaries as part of demonstration application, which should be disabled before following the procedure below. It assumes that EVM has been booted and user has logged in as root. If init sequence in SDK is not disabled, following steps are not required, and user can proceed with Matrix GUI disabling step.

•# /prcm_config_app s

• Insert syslink module
 # insmod syslink.ko


• Load the Firware using firmware_loader utility provided in SDK. 
( By default in the init scripts of Linux, firmaware might be getting loaded, so care needs to taken)

i. #  ./firmware_load 1 dm816x_hdvicp.xem3 start
ii.#  ./firmware_load 2 dm816x_hdvpss.xem3 start

• Insert HDMI controller / FB dev driver
i.  #  insmod vpss .ko vpss_slaveloader = 0xbfb0000
ii. #  insmod ti816xxxhdmi.ko

0 Sathish over 13 years ago in reply to Weilong Chen

TI__Intellectual 1950 points

Hi Weilong Chen,

By default the scripts present in etc/rc5.d/ will execute during the boot sequence.
You can check in the boot log. If you see any of these commands are not run then please re-run those commands.

Thanks!!

Regards
Sathish

0 Weilong Chen over 13 years ago in reply to Sathish

Intellectual 390 points

Hi Sathish

Thanks.

Based on the boot log, I think the commands are run.

Using DaVinci EMAC device

TFTP from server 192.168.0.29; our IP address is 192.168.0.5

Filename 'uImage-dm816x-evm.bin'.

Load address: 0x81000000

Loading: #################################################################

#################################################################

################

done

Bytes transferred = 2410792 (24c928 hex)

## Booting kernel from Legacy Image at 81000000 ...

Image Name: Arago/2.6.37-psp04.00.00.12/dm81

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 2410728 Bytes = 2.3 MiB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Linux version 2.6.37 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 20

09q1-203) ) #1 Thu Sep 8 11:27:49 IST 2011

CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f

CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: ti8168evm

bootconsole [earlycon0] enabled

reserved size = 52428800 at 0

FB: Reserving 52428800 bytes SDRAM for VRAM

Memory policy: ECC disabled, Data cache writeback

OMAP chip is TI8168 1.1

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 52224

Kernel command line: console=ttyO2,115200n8 noinitrd rw root=/dev/nfs nfsroot=19

2.168.0.29:/home/long/targetfs,nolock mem=256M earlyprintk rootdelay=3 notifyk.v

pssm3_sva=0xBF900000 ip=192.168.0.5:192.168.0.29:192.168.0.1:255.255.255.0:longt

iboard:eth0:off

PID hash table entries: 1024 (order: 0, 4096 bytes)

Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

Memory: 206MB = 206MB total

Memory: 203476k/203476k available, 58668k reserved, 0K highmem

Virtual kernel memory layout:

vector : 0xffff0000 - 0xffff1000 ( 4 kB)

fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

DMA : 0xffc00000 - 0xffe00000 ( 2 MB)

vmalloc : 0xd0800000 - 0xf8000000 ( 632 MB)

lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)

modules : 0xbf000000 - 0xc0000000 ( 16 MB)

.init : 0xc0008000 - 0xc0038000 ( 192 kB)

.text : 0xc0038000 - 0xc0492000 (4456 kB)

.data : 0xc0492000 - 0xc04d89c0 ( 283 kB)

SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

NR_IRQS:407

IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts

Total of 128 interrupts on 1 active controller

GPMC revision 6.0

Trying to install interrupt handler for IRQ400

Trying to install interrupt handler for IRQ401

Trying to install interrupt handler for IRQ402

Trying to install interrupt handler for IRQ403

Trying to install interrupt handler for IRQ404

Trying to install interrupt handler for IRQ405

Trying to install interrupt handler for IRQ406

Trying to install type control for IRQ407

Trying to set irq flags for IRQ407

OMAP clockevent source: GPTIMER1 at 27000000 Hz

Console: colour dummy device 80x30

Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)

pid_max: default: 32768 minimum: 301

Security Framework initialized

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

devtmpfs: initialized

omap_voltage_early_init: voltage driver support not added

regulator: core version 0.5

regulator: dummy:

NET: Registered protocol family 16

OMAP GPIO hardware version 0.1

omap_mux_init: Add partition: #1: core, flags: 0

_omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl

_omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda

NOR: Can't request GPMC CS

registered ti816x_vpss device

registered ti816x_gpio_vr device

registered TI816x on-chip HDMI device

registered ti816x_sr device

pm_dbg_init: only OMAP3 supported

Registered ti81xx_fb device

ti816x_pcie: Invoking PCI BIOS...

ti816x_pcie: Setting up Host Controller...

ti816x_pcie: Register base mapped @0xd0820000

ti816x_pcie: Starting PCI scan...

PCI: bus0: Fast back to back transfers enabled

bio: create slab <bio-0> at 0

regulator: VFB: 800 <--> 1025 mV at 1010 mV

vgaarb: loaded

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz

omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 kHz

Advanced Linux Sound Architecture Driver Version 1.0.23.

Switching to clocksource gp timer

musb-hdrc: version 6.0, host, debug=0

musb-hdrc musb-hdrc.0: dma type: dma-cppi41

registerd cppi-dma Intr @ IRQ 17

Cppi41 Init Done

musb-hdrc: kernel must blacklist external hubs

musb-hdrc musb-hdrc.0: MUSB HDRC host driver

musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1

usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb1: Product: MUSB HDRC host driver

usb usb1: Manufacturer: Linux 2.6.37 musb-hcd

usb usb1: SerialNumber: musb-hdrc.0

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

musb-hdrc musb-hdrc.0: USB Host mode controller at d080c000 using DMA, IRQ 18

musb-hdrc musb-hdrc.1: dma type: dma-cppi41

musb-hdrc: kernel must blacklist external hubs

musb-hdrc musb-hdrc.1: MUSB HDRC host driver

musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2

usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb2: Product: MUSB HDRC host driver

usb usb2: Manufacturer: Linux 2.6.37 musb-hcd

usb usb2: SerialNumber: musb-hdrc.1

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

musb-hdrc musb-hdrc.1: USB Host mode controller at d081e800 using DMA, IRQ 19

NET: Registered protocol family 2

IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

TCP established hash table entries: 8192 (order: 4, 65536 bytes)

TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

TCP: Hash tables configured (established 8192 bind 8192)

TCP reno registered

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

NetWinder Floating Point Emulator V0.97 (double precision)

PMU: registered new PMU device of type 0

omap-iommu omap-iommu.0: ducati registered

omap-iommu omap-iommu.1: sys registered

msgmni has been set to 397

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0

omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1

omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2

console [ttyO2] enabled, bootconsole disabled

brd: module loaded

loop: module loaded

ahci ahci.0: forcing PORTS_IMPL to 0x3

ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode

ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc

scsi0 : ahci_platform

scsi1 : ahci_platform

ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16

ata2: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x180 irq 16

m25p80 spi1.0: w25x32 (4096 Kbytes)

Creating 4 MTD partitions on "spi_flash":

0x000000000000-0x000000040000 : "U-Boot"

0x000000040000-0x000000042000 : "U-Boot Env"

0x000000042000-0x0000002c2000 : "Kernel"

0x0000002c2000-0x000000400000 : "File System"

omap2-nand driver initializing

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )

Creating 5 MTD partitions on "omap2-nand.0":

0x000000000000-0x000000260000 : "U-Boot"

0x000000260000-0x000000280000 : "U-Boot Env"

0x000000280000-0x0000006c0000 : "Kernel"

0x0000006c0000-0x00000cee0000 : "File System"

0x00000cee0000-0x000010000000 : "Reserved"

davinci_mdio davinci_mdio.0: davinci mdio revision 1.6

davinci_mdio davinci_mdio.0: detected phy mask fffffffd

davinci_mdio.0: probed

davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown

usbcore: registered new interface driver cdc_ether

usbcore: registered new interface driver dm9601

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

mice: PS/2 mouse device common for all mice

i2c /dev entries driver

Linux video capture interface: v2.00

usbcore: registered new interface driver uvcvideo

USB Video Class driver (v1.0.0)

OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

notify_init : notify drivercreated for remote proc id 2 at physical Address 0x

bf900000

usbcore: registered new interface driver snd-usb-audio

asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok

ALSA device list:

#0: TI81XX EVM

TCP cubic registered

NET: Registered protocol family 17

VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3

omap_voltage_late_init: Voltage driver support not added

smartreflex smartreflex: Driver initialized

ata2: SATA link down (SStatus 0 SControl 300)

ata1: SATA link down (SStatus 0 SControl 300)

usb 2-1: new low speed USB device using musb-hdrc and address 2

usb 2-1: New USB device found, idVendor=062a, idProduct=0003

usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

usb 2-1: Product: Optical Mouse

usb 2-1: Manufacturer: MosArt

input: MosArt Optical Mouse as /devices/platform/musb-ti81xx.1/musb-hdrc.1/usb2/

2-1/2-1:1.0/input/input0

generic-usb 0003:062A:0003.0001: input: USB HID v1.10 Mouse [MosArt Optical Mous

e] on usb-musb-hdrc.1-1/input0

davinci_mdio davinci_mdio.0: resetting idled controller

net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)

IP-Config: Complete:

device=eth0, addr=192.168.0.5, mask=255.255.255.0, gw=192.168.0.1,

host=longtiboard, domain=, nis-domain=(none),

bootserver=192.168.0.29, rootserver=192.168.0.29, rootpath=

Waiting 3sec before mounting root device...

PHY: 0:01 - Link is Up - 1000/Full

VFS: Mounted root (nfs filesystem) on device 0:14.

devtmpfs: mounted

Freeing init memory: 192K

INIT: version 2.86 booting

Please wait: booting...

Error opening /dev/fb0: No such file or directory

Starting udev

udevd (76): /proc/76/oom_adj is deprecated, please use /proc/76/oom_score_adj in

stead.

udev: starting version 141

Root filesystem already rw, not remounting

Caching udev devnodes

Populating dev cachemv: cannot rename '/tmp/devices': No such file or directory

NET: Registered protocol family 10

ALSA: Restoring mixer settings...

NOT configuring network interfaces: / is an NFS mount

hwclock: can't open '/dev/misc/rtc': No such file or directory

Thu Sep 8 16:29:00 UTC 2011

hwclock: can't open '/dev/misc/rtc': No such file or directory

INIT: Entering runlevel: 5

Starting system message bus: dbus.

Loading HDVICP2 Firmware

DM816X prcm_config_app version: 2.0.0.1

Doing PRCM settings...

PRCM for IVHD0 is in Progress, Please wait.....

BW Phy Addr : 0x48180600 Data : 0x00000002

AW Phy Addr : 0x48180600 Data : 0x00000002

Phy Addr : 0x48180c04 Data : 0x00000037

BW Phy Addr : 0x48180620 Data : 0x00070000

AW Phy Addr : 0x48180620 Data : 0x00070002

BW Phy Addr : 0x48180624 Data : 0x00030000

AW Phy Addr : 0x48180624 Data : 0x00010002

Phy Addr : 0x48180600 Data : 0x00000102

BW Phy Addr : 0x48180c10 Data : 0x00000007

AW Phy Addr : 0x48180c10 Data : 0x00000003

Phy Addr : 0x48180c14 Data : 0x00000004

BW Phy Addr : 0x58088000 Data : 0xbbbe61cc

AW Phy Addr : 0x58088000 Data : 0xeafffffe

BW Phy Addr : 0x58098000 Data : 0xb6ae1282

AW Phy Addr : 0x58098000 Data : 0xeafffffe

BW Phy Addr : 0x48180c10 Data : 0x00000003

AW Phy Addr : 0x48180c10 Data : 0x00000000

Phy Addr : 0x48180c14 Data : 0x00000007

PRCM for IVHD0 is Done Successfully

PRCM for IVHD1 is in Progress, Please wait.....

BW Phy Addr : 0x48180700 Data : 0x00000002

AW Phy Addr : 0x48180700 Data : 0x00000002

Phy Addr : 0x48180d04 Data : 0x00000037

BW Phy Addr : 0x48180720 Data : 0x00070000

AW Phy Addr : 0x48180720 Data : 0x00050002

BW Phy Addr : 0x48180724 Data : 0x00030000

AW Phy Addr : 0x48180724 Data : 0x00010002

Phy Addr : 0x48180700 Data : 0x00000102

BW Phy Addr : 0x48180d10 Data : 0x00000007

AW Phy Addr : 0x48180d10 Data : 0x00000003

Phy Addr : 0x48180d14 Data : 0x00000004

BW Phy Addr : 0x5a088000 Data : 0x01b951ec

AW Phy Addr : 0x5a088000 Data : 0xeafffffe

BW Phy Addr : 0x5a098000 Data : 0xb827683f

AW Phy Addr : 0x5a098000 Data : 0xeafffffe

BW Phy Addr : 0x48180d10 Data : 0x00000003

AW Phy Addr : 0x48180d10 Data : 0x00000000

Phy Addr : 0x48180d14 Data : 0x00000007

PRCM for IVHD1 is Done Successfully

PRCM for IVHD2 is in Progress, Please wait.....

BW Phy Addr : 0x48180800 Data : 0x00000002

AW Phy Addr : 0x48180800 Data : 0x00000002

Phy Addr : 0x48180e04 Data : 0x00000037

BW Phy Addr : 0x48180820 Data : 0x00070000

AW Phy Addr : 0x48180820 Data : 0x00050002

BW Phy Addr : 0x48180824 Data : 0x00030000

AW Phy Addr : 0x48180824 Data : 0x00010002

Phy Addr : 0x48180800 Data : 0x00000102

BW Phy Addr : 0x48180e10 Data : 0x00000007

AW Phy Addr : 0x48180e10 Data : 0x00000003

Phy Addr : 0x48180e14 Data : 0x00000004

BW Phy Addr : 0x53088000 Data : 0x4b78efaa

AW Phy Addr : 0x53088000 Data : 0xeafffffe

BW Phy Addr : 0x53098000 Data : 0xf60e1824

AW Phy Addr : 0x53098000 Data : 0xeafffffe

BW Phy Addr : 0x48180e10 Data : 0x00000003

AW Phy Addr : 0x48180e10 Data : 0x00000000

Phy Addr : 0x48180e14 Data : 0x00000007

PRCM for IVHD2 is Done Successfully

PRCM Initialization completed

SysLink version : 2.00.02.80

SysLink module created on Date:Sep 8 2011 Time:12:18:39

FIRMWARE: Memory map bin file not passed

Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Loca

tion of Mem map bin file]

FIRMWARE: Default memory configuration is used

MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1

FIRMWARE: Memory Configuration status : In Progress

FIRMWARE: 1 start Successful

Starting telnet daemon.

Loading HDVPSS Firmware

FIRMWARE: Memory map bin file not passed

Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Loca

tion of Mem map bin file]

FIRMWARE: Default memory configuration is used

MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1

FIRMWARE: Memory Configuration status : In Progress

FIRMWARE: 2 start Successful

omap_i2c omap_i2c.2: controller timed out

VPSS_DCTRL: setup 7375 filter failed

omap_i2c omap_i2c.2: controller timed out

VPSS_DCTRL: setup 7360 filter failed.

cat: write error: No space left on device

HDMI W1 rev 2.0

Starting syslogd/klogd: done

Starting thttpd.

Starting PVR

/dev/mem opened.

Memory mapped at address 0x40234000.

Read at address 0x48180F04 (0x40234f04): 0x00000001

Write at address 0x48180F04 (0x40234f04): 0x00000000, readback 0x00000000

/dev/mem opened.

Memory mapped at address 0x400f0000.

Read at address 0x48180900 (0x400f0900): 0x00000102

Write at address 0x48180900 (0x400f0900): 0x00000002, readback 0x00000002

/dev/mem opened.

Memory mapped at address 0x4029f000.

Read at address 0x48180920 (0x4029f920): 0x00040002

Write at address 0x48180920 (0x4029f920): 0x00000002, readback 0x00000002

Starting Matrix GUI application.

_____ _____ _ _

| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_

| | _| .'| . | . | | __| _| . | | | -_| _| _|

|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|

|___| |___|

Arago Project http://arago-project.org dm816x-evm ttyO2

Arago 2011.05 dm816x-evm ttyO2

0 peter lin over 13 years ago

Prodigy 180 points

I have the exact same problem, did you figure it out? Thank you for sharing. after that, it show:

got event *** unrecoverable error: OMX_Errorundefined(0x80001001)

press any key to proceed.

then it hangs.....

0 Jon S. over 13 years ago in reply to peter lin

Expert 1240 points

I've been running into this same exact problem (but on a DM8148EVM). I'm bringing in 720p video from a DVD player.

It appears that the HDMI display output *must* be configured for 1080p to run this demo -- I have not seen 720p work (fails with the "undefined" error you described), despite following the directions in the demo's help text and on the wiki.

Try the following:

# Verify display is configured for 1080p. You can use /usr/share/ti/ti-multimedia-control-utils/change_resolution.sh to change this for you if needed (or just echo the setting to the sysfs node)

root@dm814x-evm:~# cat /sys/devices/platform/vpss/display0/mode
1080p-60

# Run the demo, configured for 720p capture and display. Your 720p video will be in the top-left of the display (running @ 1080p)

/usr/share/ti/ti-omx/capture_encode_a8host_debug.xv5T -o sample.h264 -m 720p -f 60 -b 1000000 -d 0 -n 1000

I haven't yet discovered why the capture_encode demo errors out when running the HDMI display @720p. As far as it hanging, I've been told that failing to make OMX_FreeHandle() calls for every accompanying OMX_GetHandle() call can result in a zombied process, which you're seeing. I still have more digging to do, but am guessing that the error handling logic might not clean up everything the application has allocated...

EDIT: So I've been able to reproduce and solve this as follows:

(1) Start with the default rootfs provided with EZSDK 5.03.01.15. Capture Encode demo works fine here (for 720p input, it's pinned to the top-left of the display)

(2) Run the change_display.sh script to switch to the HDMI. After a reboot, the Capture Encode demo continues to work fine here (same result as (1)).

(3) Run the change_resolution.sh script to switch to 720p and reboot. Here is where I start seeing the failure.

(4) Run the change_resolution.sh script to switch back to 1080p and reboot again. The problem persists, despite trying to return to the state in (2).

It looks like the difference between steps (2) and (4) is a line in /etc/init.d/load-hd-firmware.sh that's modified by the script -- I believe "i2c_mode=1" must be in the vpss module insertion args for the OMX TVP (on the M3) component to setup up the TVP decoder. If I remember correctly, i2c_mode=0 is needed/used when the A8 will be controlling the TVP.

In short, it seems to me that if you use the change_resolution.sh script provided with EZSDK 5.03.01.15, the aforementioned change is also needed. Can someone double-check me on this?

Patch:

Fullscreen 0842.change_resolution.sh.patch.txt Download

--- ./change_resolution.orig.sh	2012-03-13 16:47:26.246998737 -0400
+++ ./change_resolution.sh	2012-03-13 16:44:12.707559349 -0400
@@ -11,19 +11,19 @@
 case $1 in
 	720p60 )
 		echo "==== Changing Resolution to 720p60 ===="
-		sed -i -e "s/modprobe vpss.*/modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:720p-60 debug=1/g" \
+		sed -i -e "s/modprobe vpss.*/modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:720p-60 i2c_mode=1 debug=1/g" \
 		       $SCRIPT;;
 	1080i60 )
 		echo "==== Changing Resolution to 1080i60 ===="
-		sed -i -e "s/modprobe vpss.*/modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080i-60 debug=1/g" \
+		sed -i -e "s/modprobe vpss.*/modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080i-60 i2c_mode=1 debug=1/g" \
 		       $SCRIPT;;
 	1080p30 )
 		echo "==== Changing Resolution to 1080p30 ===="
-		sed -i -e "s/modprobe vpss.*/modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080p-30 debug=1/g" \
+		sed -i -e "s/modprobe vpss.*/modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080p-30 i2c_mode=1 debug=1/g" \
 		       $SCRIPT;;
 	1080p60 )
 		echo "==== Changing Resolution to 1080p60 ===="
-		sed -i -e "s/modprobe vpss.*/modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080p-60 debug=1/g" \
+		sed -i -e "s/modprobe vpss.*/modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080p-60 i2c_mode=1 debug=1/g" \
 		       $SCRIPT;;
 	* )
 		echo "Error: Unsupported Resolution"

- Jon

0 Sobolevsky Vladik over 13 years ago in reply to Jon S.

Prodigy 240 points

Hi,

Is there any definite solution for this ? I have same problem here.

Thank You,

Vladik

Processors

Processors forum

Problems running capture_encode demo