DM365 Failed to detect video standard

Thank you so much!!!

Now I can encode the incoming video stream with demo application. I've chosen PlayStation 3 as input source, since the video sources can be upscaled to various resolutions.

What I was misunderstanding (for future readers):

Ordinal DVD players will not upscale the video sources.
Some of them will, but perhaps, only for HDMI outputs.

I am at the point where my whole system is set up and everything builds, loads and runs but I do not get to see anything.

How do I change the demo to receive the following input video:

PAL-I which is 625 lines CCIR specification?

Thanks, Hijn

Make sure the bootargs are set up correctly.

Does anybody know where I can find detail on the boot arguments please?

Thanks

Hijn

You should set your bootargs per the Getting Started Guide: http://wiki.davincidsp.com/index.php/GSG:_DM365_DVEVM_Software_Setup

Once your system boots up, you have three standard demos (encode, decode, and encodedecode).  As you can guess the encode demo does capture, so let us focus on this one.  If you see inside the encode.txt file that accompanies the demo, it describes run time options you can pass to the demo application.  You should see that using option '-y 2' sets up the demo for PAL Display; PAL input should be connected to composite input connector, I believe the demo can autodetect if the composite input is NTSC or PAL and adjust accordingly. 

Thanks Juan, got the board running already but found that the demo software doesn't detect my camera but if I get it running with a video pattern generator and swap over live to the camera it continues running. Am busy going through the documentation guides per module but some leads to go look at specifically to understand the bootargs' origin, settings and destinations would help newbies to linux and video like me.

I hear you HiJin and can certainly understand the way information is scattered and the amount of information out there can be overwhelming some times.  We are always looking for customer feedback in the way we can improve our collateral.

BTW, u-boot is an open source bootloader very popular in Linux systems, but not limited to Linux.  As such most u-boot arguments are pretty standard and are defined by http://www.denx.de/wiki/U-Boot .  There is also a u-boot online community at http://www.uboot.com/ .   These are likely reasons you do not see a u-boot training doc from us, but I do agree that a short doc or wiki article with a quick explanation and links to resources would help point our customers in the right direction (in addition to just giving you u-boot setting in GSG).   The bootargs variable is a bit unique in that 50% is standardized and 50% is driver dependant and hece vendor dependant.  For example, we do much of the configuration for our video drivers via bootargs.  In these sort of cases, we document what bootarg arguments mean in the corresponding driver docs (e.g. V4L2 video capture driver User Guide,  Framebuffer display driver User Guide...); the driver docs are normally located under PSP_X_XX_XX_XX/docs directory under root DVSDK tree. at least until we get a wiki article in place.

Hi Juan,

previously I was confused with you referring to the PSP_X.... but a while back found out the the installation of the PSP was not part of the instructions in the GSG that was specifically for an Ubuntu linux host.  I have in the mean time installed it and managed to do most of my evaluation and recently figured out how YCbCr work to insert my bit-encoded data into pixel lines.

At this stage I need to resolve getting my application running but when deployed in the field I can not be certain that a source is connected from the start so I need to have it running irrespective of a source connected or not and the source might nog be 100% PAL compliant (we use B&W cameras mostly) as I mentioned in other posts.  I have searched extensively and tried various things on the v4l2 interface to get it running but am not successful.  Please help on this issue as I can not start encodedecode or fbdev_loopback or any of the other loopback type demo's to run whether they are using DMAI or the fbdev or v4l2 interfaces when my B&W camera is connected.

Thanks, Hijn.

I know all these acronyms can get  abit confusing, but PSP_X... directory is part of dvsdk_setuplinux_#_#_#_#.bin installation file, which is part of the GSG.

That said, I am a little concerned about the comment on your post "source might nog be 100% PAL compliant "; I am not too familiar with TVP5146 part (hence I was hoping someone else would jump in and answer your other posts), but I believe it needs to lock in a compliant PAL (or NTSC signal) before it can start transmitting BT.656 data to DM365.  Since I am not familiar with TVP5146, I am not sure how it would handle non-compliant signals.  From a DM365 perspective, it should not care if the data is B&W or not, it just needs to be told when data is at ready to be captured (via sync signals, embedded or not) and it should capture the data.