running demo codes encode and decode on a DM355

Aside from setting the jumper correctly, you also need to add the following to your u-boot bootargs variable

videostd=pal

To elaborate on Juan's post, the videostd is a special U-Boot variable, you should be able to see it change between being NTSC and PAL based on the position of the J1 jumper when you power on the board, U-Boot is written to read in the GPIO that you change with J1 and set videostd based on it (of course if you did not have the standard U-Boot somehow this would not work). This way if you use $(videostd) to reference it in your boot arguments you can tell the kernel what standard you want by just changing the jumper setting. Unfortunately the default boot arguments do not use this variable so you end up defaulting to NTSC and have to change your boot arguments like this, though section 4.3.6 of the DM355 DVEVM getting started guide discusses the use of the videostd variable.

So for the NTSC/PAL setting on a DM355 it goes:

1. J1 Jumper is configured
2. U-Boot reads GPIO at initialization 
3. U-Boot sets the videostd environment variable 
4. Your bootcmd variable in U-Boot references $(videostd) 
5. The bootcmd is passed into the booting kernel with the videostd flag 
6. The video drivers in the kernel take this flag and configure for NTSC or PAL based on it

Sorry guys but I dont understrand how to change from PAL to NTSC and vice versa?

Explain in more detail please.

Thanks.

Assuming you are using DVSDK 1.30.00.40 go into your U-Boot prompt and type in:

 EVM # setenv bootargs 'mem=116M console=ttyS0,115200n8 root=/dev/mtdblock3 rw rootfstype=yaffs2 ip=dhcp video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal'

You can adjust this for whatever boot method (NFS, TFTP, etc) you are going for, but adding in the davinci_enc_mngr.ch0_mode=pal should put the board into pal mode.

Like Bernie suggested, the jumper on the EVM just sets the videostd variable; however, you still need to feed this into bootargs (this is what really controls PAL vs NTSC).  As a matter of fact, you do not even have to use the videostd variable at all, you can simply type the 'pal' into the bootargs like Bernie did above.

Hi Bernie,

I've done what you suggested.

when I run printenv I get this result

videostd=pal 

Looks good but when I reboot I see the below line in the startup?

ch0 default output "COMPOSITE", mode "NTSC"          

Could it be that I am booting from the wrong place?

The value of videostd does not directly cause the board to go into PAL mode, it only matters if you reference it in your bootargs variable, so if you modify your bootargs as suggested above you should get into PAL, regardless of the value of videostd.