Part Number: AM5728
Other Parts Discussed in Thread: AM5718
Tool/software: Linux
Hi,
We are using ti-processor-sdk-linux-am57xx-evm-04.02.00.09 release to develop our custom board.
While using example command of gstreamer:
target # gst-launch-1.0 -e v4l2src device=/dev/video1 num-buffers=1000 io-mode=4 ! 'video/x-raw, \
format=(string)YUY2, width=(int)1280, height=(int)720, framerate=(fraction)30/1' ! vpe num-input-buffers=8 ! \ queue ! ducatimpeg4enc bitrate=4000 ! queue ! mpeg4videoparse ! qtmux ! filesink location=x.mp4
We got error message as below:
root@am57xx-evm:~# ls /dev/video*
/dev/video0 /dev/video1 /dev/video10 /dev/video11
root@am57xx-evm:~# gst-launch-1.0 -e v4l2src device=/dev/video1 num-buffers=1000
io-mode=4 ! 'video/x-raw, format=(string)YUY2, width=(int)1280, height=(int)720
, framerate=(fraction)30/1' ! vpe num-input-buffers=8 ! queue ! ducatimpeg4enc b
itrate=4000 ! queue ! mpeg4videoparse ! qtmux ! filesink location=x.mp4
Setting pipeline to PAUSED ...
MmRpc_create: Error: open failed, name=/dev/rpmsg-dce
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstDucatiMPEG4Enc:ducatimpeg4enc0: Co
uld not initialize supporting library.
Additional debug info:
../../../../gst-plugins-base-1.8.3/gst-libs/gst/video/gstvideoencoder.c(1541): g
st_video_encoder_change_state (): /GstPipeline:pipeline0/GstDucatiMPEG4Enc:ducat
impeg4enc0:
Failed to start encoder
../git/libdce.c:416: dce_ipc_init ERROR: Failed eError == DCE_EOK error va
l -4../git/libdce.c:479: Engine_open ERROR: Failed dce_ipc_init(coreIdx) == D
CE_EOK error val -4Setting pipeline to NULL ...
Freeing pipeline ...
root@am57xx-evm:~#
By searching on E2E, we found that the IPU2 is not enabled in out dts file (thread). After enable the IPU2, we still got same error message while using gstreamer.
And got「omap_hwmod: ipu2: failed to hardreset」 while entering Kernel. We searched on E2E and found the thread has report the same issue.
We also try to apply our customized dtb & zImage with TI released MLO & u-boot.img run on the EVM board and it works fine.
But it cannot work while apply our customized dtb & zImage & MLO & u-boot.img on our customized board.
We wondered is there anything required to prevent hardreset fail?
Or is it possible caused by PinMUX conflict (timer3/timer4/timer9)? Or is it caused by hardware boot-up sequence?
Below is my current dts file.
Regards,
Collin
