saLoopBack not displaying

Hi,

Was it working in earlier release. Can you please get us the detailed steps you are executing for this to work. Like what firmware you are loading etc.

Regards,

Hardik Shah

I only spent two days with the EZSDK v5.03 release prior to the v5.04 becoming available, and decided to move to v5.04 because I'm running Ubuntu 11.10 native and little with v.503 was working. saLoopBack was attempted once or twice with v5.03 but it was not working.

The initial setup consisted of running set-up.sh and updating Uboot on the 8168EVM when I started using v5.04. I built the sa* examples from ${EZSDK}/example-applications/linux-driver-examples-psp04.04.00.01/video. They built without error.

The step used are only those defined in the documentation for running from an SD card. On the SD, I copied /usr/share/ti/ti-media-controller-utils/load-hd-v4l2-firmware.sh to /etc/init.d/load-hd-firmware.sh. There was an issues with control of the I2C and I had to augment the "firmware_loader" lines to include "-i2c 0", see below. Other than that, the file is as supplied. The versions of firmware that it loads are the ones supplied with the v5.04.00.11 release. 

Except from load-hd-v4l2-firmware.sh:

start)
echo "Loading HDVICP2 Firmware"
prcm_config_app s
modprobe syslink
until [[ -e /dev/syslinkipc_ProcMgr && -e /dev/syslinkipc_ClientNotifyMgr ]]
do
sleep 0.5
done
firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm816x_hdvicp.xem3 start -i2c 0
echo "Loading HDVPSS (V4L2) Firmware "
firmware_loader $HDVPSS_ID /usr/share/ti/ti-media-controller-utils/dm816x_hdvpss_v4l2.xem3 start -i2c 0
modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080p-60,dvo2:1080p-60,hdcomp:1080p-60 i2c_mode=0
modprobe ti81xxfb vram=0:40M,1:1M,2:1M
modprobe ti81xxvo
modprobe tvp7002
modprobeset -depth 32 -rgba 8/16,8/8,8/0,0/0
modprobe ti81xxhdmi
;;

To run, I execute "/etc/init.d/matrix-gui-e stop" and "/etc/init.d/pvr-init stop". Followed by "./saLoopBack". Stopping the PVR disables the VPSS graphics0 buffer.

The hardware configuration has the serial port connected to my laptop (working), Ethernet network connected (working), monitor connected to EVM P6 (working), RGB connected to EVM J5-J7 and Daughter I/O J5-J7 (working for gstreamer demo), and DVD source connected to Daughter I/O P3 HDMI input. The DVD has been confirmed for output by connecting directly to the monitor. The EVM is rev G and the Daughter I/O is rev C.

Other than the small mod to load-hd-v4l2-firmware.sh, I enable the additional debug messages in the code and the system conforms to the directions. I have tried some of the suggestions in the forums regarding mods to the saLoopBack and saLoopBackFbdev code but those appear to be negated by the v5.04 release. 

I've been unable to find any document for the Daughter I/O that is equivalent to the 'evm816x_TechRef_RevG.pdf'. And I'm uncertain how the Daughter I/O interfaces can be utilized to try alternative tests.

Wait, I thought the HDMI input connector couldn't be used with an HDMI source because the decoder was only for DVI?

Tony

HDMI is DVI + PCM (uncompressed) or IEC61937-compliant (compressed) digital audio. And HDMI support of audio is optional.

IOW, it should work either way.

I thought the limiting issue was the SiI1161 , I didn't think it could figure out the inband audio component to the degree that it could ignore it. I am aware of the electrical compliance.

You already made the modification to the driver to switch the multiplexer to the SiI1161 chip? It isn't on by default , at least it wasn't prior to the 5.04 version of EZSDK.

Tony M.

A Marchini

I thought the limiting issue was the SiI1161 , I didn't think it could figure out the inband audio component to the degree that it could ignore it. I am aware of the electrical compliance.

You already made the modification to the driver to switch the multiplexer to the SiI1161 chip? It isn't on by default , at least it wasn't prior to the 5.04 version of EZSDK.

Tony M.

All modifications have already been explained in my previous posts. The instructions don't identify anything regarding changing the driver. Which driver needs to change and what needs to change?

I've seen posts stating that the saLoopBack example is working so I don't think there is a limitation in the SiI1161.

Here is a note I received in another thread. Anyone I have seen using this program, including myself, was using the component video. You may have issues with HDCP I imagine from your player.

Hi,

I am not sure what are you trying to do here. But if you are trying to setup PCF8575 for reception of input from DVI decoder instead of TVP7002 then you need to do following changes. You need to modify following function under arch/arm/mach-omap2/board-ti8168evm.c. Currently we are setting it for TVP7002 decoder. You just need to set it for DVI decoder. You need to set 1 on that VPS_VC_IO_EXP_SEL_VIN0_S1_MASK bits to select DVI instead of TVP7002.

"int vps_ti816x_select_video_decoder(int vid_decoder_id)"

Regards,

Hardik Shah

Hi,

I am not able to follow thread fully, But  what i got is that you want to capture through Sii1161. Is this correct. If this case,  than sii1161 driver is not supported and you need to refer to http://processors.wiki.ti.com/index.php/DM81xx_AM38xx_Adding_External_Decoders_to_V4L2_Capture_Driver on how to add new decoders support to V4L2 capture driver.

Regards,

Hardik Shah

OK, it's now capturing and displaying, but it's only in one-eighth of the screen. Shouldn't the playback be full screen?

For the record, the solution was that the saLoopBack application, as provided, captures from the component inputs of the 8168 EVM expansion I/O board (these are the RCA RGB connectors between the HDMI connectors.) In the Capture Driver User Guide, the "Read This First" with the sample programs said "Capture source must be connected to the component input..." and I interpreted that as the device doing the capturing, the 8168, as interpreted in "capture driver". It actually means "source to be captured". And since the quick start default configuration has the capture device and the expansion I/O connected via RGB, I assumed no change was needed.

HardikShah

I am not able to follow thread fully, But  what i got is that you want to capture through Sii1161. Is this correct. If this case,  than sii1161 driver is not supported and you need to refer to http://processors.wiki.ti.com/index.php/DM81xx_AM38xx_Adding_External_Decoders_to_V4L2_Capture_Driver on how to add new decoders support to V4L2 capture driver.

Regards, Hardik Shah 

Now that the capture is somewhat working, I will want to capture from the HDMI input as that is part of my evaluation of the 8168 chip. Although, I'm beginning to think that it  doesn't matter to the 8168 since there are interface chips performing a conversion of the input. It's disappointing that the EZSDK doesn't support all of the components of the evaluation platform (unless, of course, that you didn't mean "not supported" but meant "needs to be modified to include support", as inferred by Tony.) 

If there is an answer as to why the captured video is so small on the display, I'd like to hear it, otherwise I'm satisfied with information as supplied by Tony and I'm done with this thread.

John,

Did you ever get the DVI input working with standard HDMI input? I was curious if the input chip was capable of ignoring the embedded audio in a standard HDMI signal.

Tony

Tony, 

Sorry, I can't answer your question. I didn't try very hard to get that working. I switched to the RGB inputs to satisfy a couple of points of interest and then moved on. And I'm now on a different (paying) project. 

John

Ok, thanks for the reply at least.

Tony