help, 1080i30 error on evm816x ezsdk-5.05

wang wang1

i've test the 1080p and 720p on normal. sdk is ezsdk-5.05

now is analog input 1080i60 YPbPr, after login in linux shell:
(1)run /usr/share/ti/ti-media-controller-utils/load-hd-firmware.sh
(2)run command: ./capture_encode_a8host_debug.xv5T -o /home/root/sample_capture.h264 -m 1080i -f 30 -b 100000000 -n 10000000 -d 0

the console display an error:

output file: /home/root/sample_capture.h264
bit_rate: 100000000
frame_rate: 30
num_frames: 10000000
mode: 1080i
display_id: 0
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: 2073600
11111set input port params (width = 1920, height = 1080) applying skip mask
enable capture output port
got eventEnable/Disable Event
dei compoenent is created
22222set input port params (width = 1920, height = 1080)
set output port params (width = 1920, height = 1080)set output port params (width = 1920, height = 1080)set number of channelsset input resolutionset output
resolutionenable 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 0x12f4f8 for component OMX.TI.VPSSM3.VFDC
got display handle
found handle 0x133500 for component OMX.TI.VPSSM3.CTRL.DC
Buffer Size computed: 4147200
33333set input port params (width = 1920, height = 1080)setting input and output memory type to defaultenable input port
got eventEnable/Disable Event
connect call for capture-Dei
connect call for dei- encoder
connect call for dei-display
got eventState changed to: OMX_StateIdle
Capture outport buffers allocated
got eventState changed to: OMX_StateIdle
Capture is in IDLE state
got event*** unrecoverable error: OMX_ErrorInsufficientResources (0x80001000)
Press a key to proceed
Dei input port use buffer done
DEI outport buffers allocated

(3)i've track the source, it's crush at source:

eError =
OMX_SendCommand (pAppData->pDeiHandle, OMX_CommandStateSet,
OMX_StateIdle, NULL);
if (eError != OMX_ErrorNone)
{
printf ("Error in SendCommand()-OMX_StateIdle State set : %s \n",
IL_ClientErrorToStr (eError));
goto EXIT;
}

the function IL_ClientCbEventHandler() catch the error.

(4)loggerSMDump.out 0x9E400000 0x100000 all
result:

......
N:VPSS P:2 #:00792 T:0000000098414d87 M:xdc.runtime.Main S: OMX_VFCC_DriverCreate - DONE !!!
N:VPSS P:2 #:00793 T:000000009841e42d M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Entering<OMX_BASE_CB_ReturnEventNotify> @line<100>
N:VPSS P:2 #:00794 T:000000009842605f M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> @<OMX_BASE_CB_ReturnEventNotify> @line<115> msg<Notify client for state
transition>
N:VPSS P:2 #:00795 T:000000009842fecf M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<OMX_BASE_CB_ReturnEventNotify> @line<224> with error<0:ErrorNone>
N:VPSS P:2 #:00796 T:0000000098438445 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<_OMX_BASE_HandleStateTransition> @line<483> with error<0:ErrorNone>
N:VPSS P:2 #:00797 T:0000000098440b60 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<OMX_BASE_PROCESS_CmdEvent> @line<784> with error<0:ErrorNone>
N:VPSS P:2 #:00798 T:0000000098448c2f M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<OMX_BASE_CmdEventHandler> @line<466> with error<0:ErrorNone>
N:VPSS P:2 #:00799 T:0000000098451e93 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Entering<OMX_BASE_CmdCompleteEventHandler> @line<483>
N:VPSS P:2 #:00800 T:0000000098459669 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Entering<OMX_BASE_PROCESS_CmdCompleteEvent> @line<809>
N:VPSS P:2 #:00801 T:0000000098460f4d M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> @<OMX_BASE_PROCESS_CmdCompleteEvent> @line<821> msg<Processing
OMX_CommandStateSet>
N:VPSS P:2 #:00802 T:0000000098469747 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Entering<_OMX_BASE_HandleStateTransitionComplete> @line<506>
N:VPSS P:2 #:00803 T:000000009847156d M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> @<_OMX_BASE_HandleStateTransitionComplete> @line<535> msg<Loaded to Idle
Transition>
N:VPSS P:2 #:00804 T:000000009847aa4b M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Entering<OMX_BASE_RestoreDioGroupInfo> @line<1398>
N:VPSS P:2 #:00805 T:0000000098482849 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<OMX_BASE_RestoreDioGroupInfo> @line<1453> with error<0:ErrorNone>
N:VPSS P:2 #:00806 T:000000009848b4d3 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<_OMX_BASE_HandleStateTransitionComplete> @line<704> with
error<0:ErrorNone>
N:VPSS P:2 #:00807 T:0000000098495bd7 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Entering<_OMX_BASE_EventNotifyToClient> @line<881>
N:VPSS P:2 #:00808 T:00000000984ca8b9 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<_OMX_BASE_EventNotifyToClient> @line<1172> with error<0:ErrorNone>
N:VPSS P:2 #:00809 T:00000000984d3f67 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<OMX_BASE_PROCESS_CmdCompleteEvent> @line<930> with error<0:ErrorNone>
N:VPSS P:2 #:00810 T:00000000984dc4ff M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<OMX_BASE_CmdCompleteEventHandler> @line<496> with error<0:ErrorNone>
N:VPSS P:2 #:00811 T:00000000984e4ebb M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Entering<OMX_BASE_CmdEventHandler> @line<434>
N:VPSS P:2 #:00812 T:00000000984ed123 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFCC> Leaving<OMX_BASE_CmdEventHandler> @line<466> with error<0:ErrorNone>
N:VPSS P:2 #:00813 T:00000000bdff177d M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Entering<OMX_BASE_SendCommand> @line<499>
N:VPSS P:2 #:00814 T:00000000be000367 M:xdc.runtime.Main S:OMX_BASE_SendCommand:OMX_CommandStateSet, nParam1: 2
N:VPSS P:2 #:00815 T:00000000be00b0b5 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Leaving<OMX_BASE_SendCommand> @line<669> with error<0:ErrorNone>
N:VPSS P:2 #:00816 T:00000000be01e10d M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Entering<OMX_BASE_CmdEventHandler> @line<434>
N:VPSS P:2 #:00817 T:00000000be02864b M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Entering<OMX_BASE_PROCESS_CmdEvent> @line<526>
N:VPSS P:2 #:00818 T:00000000be02ffdf M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> @<OMX_BASE_PROCESS_CmdEvent> @line<538> msg<Processing
OMX_CommandStateSet>
N:VPSS P:2 #:00819 T:00000000be038eb5 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Entering<_OMX_BASE_HandleStateTransition> @line<316>
N:VPSS P:2 #:00820 T:00000000be043499 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> @<_OMX_BASE_HandleStateTransition> @line<339> msg<Loaded to Idle
Transition>
N:VPSS P:2 #:00821 T:00000000be0e7249 M:xdc.runtime.Main S: OMX Error in _OMX_VFPCDeiDualOutCreate :: line 1159
N:VPSS P:2 #:00822 T:00000000be0ef44f M:xdc.runtime.Main S: OMX Error in OMX_TI_VFPC_CommandNotify :: line 1273
N:VPSS P:2 #:00823 T:00000000be0f584b M:xdc.runtime.Main S: OMX Error in _OMX_BASE_HandleStateTransition :: line 344
N:VPSS P:2 #:00824 T:00000000be0fc78d M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Leaving<_OMX_BASE_HandleStateTransition> @line<483> with error<-
2147479552:ErrorInsufficientResources>
N:VPSS P:2 #:00825 T:00000000be135851 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Leaving<OMX_BASE_PROCESS_CmdEvent> @line<784> with error<-
2147479552:ErrorInsufficientResources>
N:VPSS P:2 #:00826 T:00000000be140b93 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Leaving<OMX_BASE_CmdEventHandler> @line<466> with error<-
2147479552:ErrorInsufficientResources>
N:VPSS P:2 #:00827 T:00000000be14b439 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Entering<OMX_BASE_CmdEventHandler> @line<434>
N:VPSS P:2 #:00828 T:00000000be153e7f M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Leaving<OMX_BASE_CmdEventHandler> @line<466> with error<0:ErrorNone>
N:VPSS P:2 #:00829 T:00000000c4c36603 M:xdc.runtime.Main S:Entered Function :omxrpc_skel_usebuffer
N:VPSS P:2 #:00830 T:00000000c4c50635 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Entering<OMX_BASE_DIO_Init> @line<120>
N:VPSS P:2 #:00831 T:00000000c4c586c1 M:xdc.runtime.Main S:Entered: OMX_BASE_DIO_Init (0x9f242010, 0, OMX.DIO.NONTUNNEL, 0x9f2419ac)
N:VPSS P:2 #:00832 T:00000000c4c6591d M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Leaving<OMX_BASE_DIO_Init> @line<172> with error<0:ErrorNone>
N:VPSS P:2 #:00833 T:00000000c4c6e4b5 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Entering<OMX_BASE_DIO_Open> @line<252>
N:VPSS P:2 #:00834 T:00000000c4ca60e7 M:xdc.runtime.Main S:Module<OMX.TI.VPSSM3.VFPC.DEIMDUALOUT> Leaving<OMX_BASE_DIO_Open> @line<258> with error<0:ErrorNone>
N:VPSS P:2 #:00835 T:00000000c4cd0e55 M:xdc.runtime.Main S:Entered Function :omxrpc_skel_usebuffer
N:VPSS P:2 #:00836 T:00000000c4d04477 M:xdc.runtime.Main S:Entered Function :omxrpc_skel_usebuffer

(5)i've no change of the capture_encode source. wha't the error?

thanks.

over 12 years ago

0 Margarita Gashova over 12 years ago

TI__Guru* 80190 points

Hello,

In EZSDK 5.05:

-interlace capture (1080i60) is supported in capture_encode example;

-For 1080i60, DEI has been activated to do de-interlacing in capture_encode
example.

Could you try:

./capture_encode_a8host_debug.xv5T -o sample.h264 -m 1080i -f 60 -b 1000000 -n 1000 –d 0

More info for capture_encode example: http://processors.wiki.ti.com/index.php/OMX_EZSDK_Examples#Capture_Encode

Best regards,

Margarita

0 wang wang1 over 12 years ago in reply to Margarita Gashova

Intellectual 610 points

hi, Margarita.thanks for you reply.

i test the ./capture_encode_a8host_debug.xv5T -o sample.h264 -m 1080i -f 60 -b 1000000 -n 1000 –d 0

but it's the same error. sdk is 'ti-ezsdk_dm816x-evm_5_05_01_04'

the 1080p and 720p works normally, only 1080i error.

is there some hint in 'loggerSMDump.out' output?

0 Vimal Jain over 12 years ago in reply to wang wang1

TI__Expert 6535 points

Hi,

For 1080i we are using 422 format, and pitch would be 2xwidth. On PG1.0 DM8168, this pitch is not supported for > 1920, so you would see the error. PG2.0 supports this.

Regards

Vimal

0 wang wang1 over 12 years ago in reply to Vimal Jain

Intellectual 610 points

hi, vimal.

thanks for your reply.

my dm8168 evm version is revC,

root@dm816x-evm:~# dmesg| grep 8168
Machine: ti8168evm
OMAP chip is TI8168 1.1
root@dm816x-evm:~#

does it's PG1.1? and not support 1080i?

best wish.

0 David Hill100919 over 12 years ago in reply to wang wang1

Intellectual 310 points

Hi, Wang. I got the same ERROR like you. My EVM version is TI 8168 PG 1.1 too. Have you solved the problems?

Jiaxin.

0 Swaroop Chanda over 12 years ago in reply to David Hill100919

Prodigy 10 points

Is any one able to evaluate DEI and 3D noise filters on this EVM?

Processors

Processors forum

help, 1080i30 error on evm816x ezsdk-5.05