Re: Requesting for help:
Hi, As per the log : js: "/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/xdc.tci", line 270: exception from uncaught _javascript_ throw: Error: xdc.loadPackage: can't find package 'ti.sdo.fc.dskt2' along the path Locating "ti/so/fc/dskt2", I found it to be part of framework components, can you please add the path of "framework_components_X_XX_XX" in your configuration file and try to build it. Thanks & Regards, Deepika Makhija chandrashekar reddy wrote: Hi All, I am trying to build ov analytics server upon dm6446.I am getting fallowing issue.. # configuring ovanalytics.x64P from package/cfg/ovanalytics_x64P.cfg ... /home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/xs -Dxdc.path="/home/dm6446/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/dm6446/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages;/home/dm6446/dvsdk_1_30_01_41/codec_engine_2_00_01/examples;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages/ti/bios/include;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages/ti;/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/packages;../.." -Dxdc.root=/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02 -Dxdc.hostOS=Linux -Dconfig.importPath=".;/home/dm6446/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/dm6446/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages;/home/dm6446/dvsdk_1_30_01_41/codec_engine_2_00_01/examples;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages/ti/bios/include;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages/ti;/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/packages;../..;/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02;/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/etc ;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages/ti/bios/include;../../analytics/ovanalytics" -Dxdc.bld.targets="" -DTOOLS= -Dxdc.traceEnable= xdc.cfg ovanalytics.x64P package/cfg/ovanalytics_x64P.cfg package/cfg/ovanalytics_x64P '/home/dm6446/dvsdk_1_30_01_41/codec_engine_2_00_01/packages;/home/dm6446/dvsdk_1_30_01_41/codec_engine_2_00_01/cetools/packages;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages;/home/dm6446/dvsdk_1_30_01_41/codec_engine_2_00_01/examples;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages/ti/bios/include;/home/dm6446/dvsdk_1_30_01_41/bios_5_31_08/packages/ti;/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/packages;/home/dm6446/chandra/OV_5.0.1/OnBoard_SDK/Davinci/CCS3.2_DVEVM6446/servers/ovanalytics/./../..;'; try redefining the package path (XDCPATH). "/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/xdc.tci", line 450 "/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/Main.xs", line 1326 "./ovanalytics.cfg", line 46 "/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/include/utils.tci", line 588 "/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/include/utils.tci", line 506 "./package/cfg/ovanalytics_x64P.cfg", line 645 "./package/cfg/ovanalytics_x64P.cfg", line 606 "/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/Main.xs", line 182 "/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/cfg/Main.xs", line 151 "/home/dm6446/dvsdk_1_30_01_41/xdc_3_00_02/packages/xdc/xs.js", line 144 gmake[1]: *** [package/cfg/ovanalytics_x64Pcfg_c.c] Error 1 gmake[1]: *** Deleting file `package/cfg/ovanalytics_x64Pcfg_c.c' gmake[1]: *** [package/cfg/ovanalytics_x64Pcfg_c.c] Deleting file `package/cfg/ovanalytics_x64Pcfg.cmd' gmake[1]: *** [package/cfg/ovanalytics_x64Pcfg_c.c] Deleting file `package/cfg/ovanalytics_x64Pcfg.s62' gmake: *** [/home/dm6446/chandra/OV_5.0.1/OnBoard_SDK/Davinci/CCS3.2_DVEVM6446/servers/ovanalytics,.executables] Error 2 make: *** [all] Error 2 Thanks for kind help. Regards, Chandra Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this messa
Re: compile help
Hi, Try to follow below steps: make clean make distclean make davinci_all_defconfig (Instead this i was suggest use config specific to your board which u can find in arch/arm/configs/ ) make menuconfig: To select eabi and debugging options make uImage Please follow above steps and try with them. One more thing, whenever you perform make distclean, your default configuration file will be removed, so "make defconfig" (specific to board) is mandatory or else you would have you select each option manually with help of "menuconfig". Regards, Deepika rohan tabish wrote: i AM USING DM6446 we have made our own custom board.I am using the cross compiler and the steps i follow are make distclean make menuconfig in the menuconfig i selected eabi and the debuging option and other modules. and then make uImage After compilation i get uImage and then load this uImage in my board and got the debug error msgs printed. berfore that instead of the meunconfig i used make davinci_all_defconfig but at that no msgs were printed because in the default it does not enable the kernel debugging option. With Regard's Rohan --- On Thu, 20/8/09, deepika.makh...@einfochips.com wrote: From: deepika.makh...@einfochips.com Subject: Re: compile help To: "rohan tabish" Cc: davinci-linux-open-source@linux.davincidsp.com Date: Thursday, 20 August, 2009, 10:29 PM Hi, I haven't seen such error before, but as the log suggest try to verify your kernel config parameters. Can you tell us on which board you are loading the kernel and the steps to build your kernel. Along with that do keep "davinci-linux-open-source@linux.davincidsp.com" in loop so that people can help you. Regards, Deepika > Hi deepika,I got some kernel msgs by enabling the debuging option the log looks like > > Booting kernel from Legacy Image at 8070 ... > > > > Image Name: Linux-2.6.31-rc5-davinci1 > > Created: 2009-08-16 13:56:56 UTC > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 1478408 Bytes = 1.4 MB > > Load Address: 80008000 > > Entry Point: 80008000 > > Verifying Checksum ... OK > > Loading Kernel Image ... OK > > > > Starting kernel ... > > > > Uncompressing > Linux > done, booting the kernel. > > > > > Error: unrecognized/unsupported machine ID (r1 = > 0x04e7). > > > > Available machine support: > > > > ID (hex) NAME > > 0385 DaVinci > DM644x EVM > > 0679 Lyrtech > SFFSDR > > 0565 DaVinci > DM355 EVM > > 085a DaVinci > DM355 leopard > > 0564 DaVinci > DM646x EVM > > 0793 DaVinci > DM365 EVM > > > > Please check your kernel config and/or bootloader. > > I am going to check now kernel config.And set the machine number can you tell me what > change i need to do in the source code. > --- On Wed, 19/8/09, Deepika Makhija <deepika.makh...@einfochips.com> wrote: > > From: Deepika Makhija <deepika.makh...@einfochips.com> > Subject: Re: compile help > To: "rohan tabish" <rohan_ja...@yahoo.co.uk> > Cc: "davinci-linux-open-source@linux.davincidsp.com" > <davinci-linux-open-source@linux.davincidsp.com> > Date: Wednesday, 19 August, 2009, 4:00 PM > > > > > > Hi Rohan, > > > > Does the uImage halt at the same location or you are getting some > kernel prints? Other than this, please refer to below suggestion from > Vijay Soni. > > I f possible mail your complete boot up -log including boot parameters. > > > > Regards, > > Deepika > > > Original Message > > > > Subject: > Re: compile help > > > Date: > Wed, 19 Aug 2009 02:39:20 -0700 (PDT) > > > From: > Vijay Soni <vij_s...@yahoo.com> > > > To: > Deepika Makhija <deepika.makh...@einfochips.com> > > > > > > Hi Deepika, > > I had the same problem though it was on my custom board based on DM355 but I had to add > printascii patch in printk.c file in addition to what you have suggested. Just for your > info. > > Vijay Soni > > > > rohan tabish wrote: > > > > > Thanks atleast someone has replied i have enabled the > debugging tool.and compiled the source code.when i load the uImage it > again gets halt.can u tell what is the probelm.any link or
Re: compile help
Hi, I haven't seen such error before, but as the log suggest try to verify your kernel config parameters. Can you tell us on which board you are loading the kernel and the steps to build your kernel. Along with that do keep "davinci-linux-open-source@linux.davincidsp.com" in loop so that people can help you. Regards, Deepika > Hi deepika,I got some kernel msgs by enabling the debuging option the log > looks like > > Booting kernel from Legacy Image at 8070 ... > > > > Image Name: Linux-2.6.31-rc5-davinci1 > > Created: 2009-08-16 13:56:56 UTC > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 1478408 Bytes = 1.4 MB > > Load Address: 80008000 > > Entry Point: 80008000 > > Verifying Checksum ... OK > > Loading Kernel Image ... OK > > > > Starting kernel ... > > > > Uncompressing > Linux > done, booting the kernel. > > > > > Error: unrecognized/unsupported machine ID (r1 = > 0x04e7). > > > > Available machine support: > > > > ID (hex) NAME > > 0385 DaVinci > DM644x EVM > > 0679 Lyrtech > SFFSDR > > 0565 DaVinci > DM355 EVM > > 085a DaVinci > DM355 leopard > > 0564 DaVinci > DM646x EVM > > 0793 DaVinci > DM365 EVM > > > > Please check your kernel config and/or bootloader. > > I am going to check now kernel config.And set the machine number can you tell > me what > change i need to do in the source code. > --- On Wed, 19/8/09, Deepika Makhija wrote: > > From: Deepika Makhija > Subject: Re: compile help > To: "rohan tabish" > Cc: "davinci-linux-open-source@linux.davincidsp.com" > > Date: Wednesday, 19 August, 2009, 4:00 PM > > > > > > Hi Rohan, > > > > Does the uImage halt at the same location or you are getting some > kernel prints? Other than this, please refer to below suggestion from > Vijay Soni. > > I f possible mail your complete boot up -log including boot parameters. > > > > Regards, > > Deepika > > > Original Message > > > > Subject: > Re: compile help > > > Date: > Wed, 19 Aug 2009 02:39:20 -0700 (PDT) > > > From: > Vijay Soni > > > To: > Deepika Makhija > > > > > > Hi Deepika, > > I had the same problem though it was on my custom board based on DM355 but I > had to add > printascii patch in printk.c file in addition to what you have suggested. > Just for your > info. > > Vijay Soni > > > > rohan tabish wrote: > > > > > Thanks atleast someone has replied i have enabled the > debugging tool.and compiled the source code.when i load the uImage it > again gets halt.can u tell what is the probelm.any link or help. > > > > > > Regard's > > Rohan Tabish > > > > --- On Wed, 19/8/09, Deepika Makhija > wrote: > > > > From: Deepika Makhija > > Subject: Re: compile help > > To: "rohan tabish" > > Cc: davinci-linux-open-source@linux.davincidsp.com > > Date: Wednesday, 19 August, 2009, 12:32 PM > > > > Hi, > > > > Re-build the kernel with debugging enabled, debug log will help you to > solve the problem. For this follow below steps: > > > cd > Enable debugging options as indicate below with help > of > "make > menuconfig" command. > > > > Kernel hacking ---> > > [*] Kernel debugging > > [*] Kernel low-level debugging functions > > > > Build the kernel > > make uImage > > > Boot the board with this new build kernel, console log will point out > the problem. > > > > Regards, > > Deepika > > > > rohan tabish wrote: > > > > > Hey guys i have downloaded the latest source code from > git for Davinci Kernel.When i load the kernel in the board it gets halt. > > > > Booting kernel from Legacy Image at 8070 ... > > > > Image Name: Linux-2.6.31-rc5-davinci1 > > Created: 2009-08-16 13:56:56 UTC > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 1478408 Bytes = 1.4 MB > > Load Address: 80008000
Re: compile help
Hi Rohan, Does the uImage halt at the same location or you are getting some kernel prints? Other than this, please refer to below suggestion from Vijay Soni. I f possible mail your complete boot up -log including boot parameters. Regards, Deepika Original Message Subject: Re: compile help Date: Wed, 19 Aug 2009 02:39:20 -0700 (PDT) From: Vijay Soni To: Deepika Makhija Hi Deepika, I had the same problem though it was on my custom board based on DM355 but I had to add printascii patch in printk.c file in addition to what you have suggested. Just for your info. Vijay Soni rohan tabish wrote: Thanks atleast someone has replied i have enabled the debugging tool.and compiled the source code.when i load the uImage it again gets halt.can u tell what is the probelm.any link or help. Regard's Rohan Tabish --- On Wed, 19/8/09, Deepika Makhija wrote: From: Deepika Makhija Subject: Re: compile help To: "rohan tabish" Cc: davinci-linux-open-source@linux.davincidsp.com Date: Wednesday, 19 August, 2009, 12:32 PM Hi, Re-build the kernel with debugging enabled, debug log will help you to solve the problem. For this follow below steps: cd Enable debugging options as indicate below with help of "make menuconfig" command. Kernel hacking ---> [*] Kernel debugging [*] Kernel low-level debugging functions Build the kernel make uImage Boot the board with this new build kernel, console log will point out the problem. Regards, Deepika rohan tabish wrote: Hey guys i have downloaded the latest source code from git for Davinci Kernel.When i load the kernel in the board it gets halt. Booting kernel from Legacy Image at 8070 ... Image Name: Linux-2.6.31-rc5-davinci1 Created: 2009-08-16 13:56:56 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1478408 Bytes = 1.4 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Uncompressing Linux done, booting the kernel. after that. I have checked the version of the kernel in the linux on which i am compiling the source code.The version is 2.6.23.17 -88.fc7.It is found by command "uname -r".Is this the cause for that.if so plz tell me how to update the kernel. I have found in some forums 2 set the bootargs. My bootargs are correct. they are: bootargs=mem=56M console=ttyS0,115200n8 root=/dev/hda1 rw noinitrd ip=dhcp Can any1 tell me whats going wrong. Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
Re: compile help
Hi, Re-build the kernel with debugging enabled, debug log will help you to solve the problem. For this follow below steps: cd Enable debugging options as indicate below with help of "make menuconfig" command. Kernel hacking ---> [*] Kernel debugging [*] Kernel low-level debugging functions Build the kernel make uImage Boot the board with this new build kernel, console log will point out the problem. Regards, Deepika rohan tabish wrote: Hey guys i have downloaded the latest source code from git for Davinci Kernel.When i load the kernel in the board it gets halt. Booting kernel from Legacy Image at 8070 ... Image Name: Linux-2.6.31-rc5-davinci1 Created: 2009-08-16 13:56:56 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1478408 Bytes = 1.4 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Uncompressing Linux done, booting the kernel. after that. I have checked the version of the kernel in the linux on which i am compiling the source code.The version is 2.6.23.17 -88.fc7.It is found by command "uname -r".Is this the cause for that.if so plz tell me how to update the kernel. I have found in some forums 2 set the bootargs. My bootargs are correct. they are: bootargs=mem=56M console=ttyS0,115200n8 root=/dev/hda1 rw noinitrd ip=dhcp Can any1 tell me whats going wrong. Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: saDisplay + DM6467 showing black an white image in SD Display
Hi Vinayagam, I suppose that your customized MPEG-4 Decoder is xDAIS-xDM complaint, if yes than TI's application will run without any changes. I don't know much about codec interface for customized Codec's, however you can take reference of few doc's on net. http://wiki.davincidsp.com/index.php/TopTenCodecPackageCheckList#3._VISA_XDM_API_usage XDAIS Rules & Guidelines : SPRU352 XDAIS API Reference : SPRU360 Regards, Deepika Vinayagam Mariappan wrote: Hi, I have checked with H264 Stream with D1 resolution using TI DM6467 Demo Application. Its working. But It doest work with our customized MPEG-4 Decoder. I am doubting only my codec interface Do you have simple codec interface using VIDEC2 using two output buffer? Please do help me to fix this issueThis is first time I am doing all this kind of interface so confusing me. Regards, Vinayagam M On Mon, Aug 10, 2009 at 4:02 PM, Deepika Makhija <deepika.makh...@einfochips.com> wrote: Hi Vinayagam, H264 sample streams are available on TI Extranet: https://www-a.ti.com/extranet/cm/product/dvevmsw/dspswext/general/dm355_dvevm.shtml Consider TI's decode application, file "dvsdk_demos_1_40_00_18/dm6467/decode/video.c" is used to set the decoder parameters, where Vdec2_Params_DEFAULT and Vdec2_DynamicParams_DEFAULT are used to set the default decoder parameters, whose value is mentioned in dmai module, you have to modify height/width of these as per your resolution. Same would be the case with "dvsdk_demos_1_40_00_18/dm6467/decode/display.c" where default display parameters are set with Display_Attrs_DM6467_VID_DEFAULT. Regards, Deepika Vinayagam Mariappan wrote: Hi, I have only H264 TI Codec Lib but I do not find H264 Stream for D1. Do you have any sample file? Please send me if you have one... Its confusing me to Integrate with our customized codec... As I know, I have to do minimal changes to get our customized codec to work with our TI Demo Application. Could you please me specific things to see? Do you have any idea which specific enum directly look into it...? Regards, Vinayagam M On Mon, Aug 3, 2009 at 1:40 PM, Deepika Makhija <deepika.makh...@einfochips.com> wrote: Hi, Nice to hear that your saDisplay is working now. "we are not getting video.But I get video data till App." Can you please describe in detail, up till which module you are getting correct output. I would suggest instead of integrating your decoder, first try to modify the application to work at D1 resolution with TI codecs, which are capable of decoding D1 resolution also, for that you would have to change few enums in the application. Once that path is clear than integrate your decoder. Regards, Deepika Vinayagam Mariappan wrote: Hi Deepika, I just made the saDisplay to work properly. Now I have to change the Decoder Application to work with our customized decoder which always give video out with D1 resolution... The TI Demo Application is for HD Display and I change that to work for SD Display. When I integrate our customized decoder with demo application, we are not getting video.But I get video data till App. Where will be the problem... Regards, Vinayagam M -- _ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _ -- Regards, Vinayagam M VeNMSOL Technologies, #7A, First Cross Street, Ganapathy Colony, Ekkaduthangal, Chennai - 600 032,India. Tel:+91-44-4353 0168;Mobile:+91-9445-019919 URL: www.venmsol.com "We make a living by what we get, we make a life by what we give...- Unknown "
Re: saDisplay + DM6467 showing black an white image in SD Display
Hi Vinayagam,
H264 sample streams are available on TI Extranet:
https://www-a.ti.com/extranet/cm/product/dvevmsw/dspswext/general/dm355_dvevm.shtml
Consider TI's decode application, file
"dvsdk_demos_1_40_00_18/dm6467/decode/video.c" is used to set the
decoder parameters, where Vdec2_Params_DEFAULT and
Vdec2_DynamicParams_DEFAULT are used to set the default decoder
parameters, whose value is mentioned in dmai module, you have to
modify height/width of these as per your resolution. Same would be the
case with "dvsdk_demos_1_40_00_18/dm6467/decode/display.c" where
default display parameters are set with
Display_Attrs_DM6467_VID_DEFAULT.
Regards,
Deepika
Vinayagam Mariappan wrote:
Hi,
I have only H264 TI Codec Lib but I do not find H264 Stream for D1.
Do you have any sample file?
Please send me if you have one...
Its confusing me to Integrate with our customized codec... As I know,
I have to do minimal changes to get our customized codec to work with
our TI Demo Application.
Could you please me specific things to see?
Do you have any idea which specific enum directly look into it...?
Regards,
Vinayagam M
On Mon, Aug 3, 2009 at 1:40 PM, Deepika
Makhija <deepika.makh...@einfochips.com>
wrote:
Hi,
Nice to hear that your saDisplay is working now.
"we are not getting video.But I get video data till App." Can you
please describe in detail, up till which module you are getting correct
output.
I would suggest instead of integrating your decoder, first try to
modify the application to work at D1 resolution with TI codecs, which
are capable of decoding D1 resolution also, for that you would have to
change few enums in the application. Once that path is clear than
integrate your decoder.
Regards,
Deepika
Vinayagam Mariappan wrote:
Hi
Deepika,
I just made the saDisplay to work properly.
Now I have to change the Decoder Application to work with our
customized decoder which always give video out with D1 resolution...
The TI Demo Application is for HD Display and I change that to work
for SD Display. When I integrate our customized decoder with demo
application, we are not getting video.But I get video data till App.
Where will be the problem...
Regards,
Vinayagam M
--
_
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
_
--
Regards,
Vinayagam M
VeNMSOL Technologies,
#7A, First Cross Street, Ganapathy Colony,
Ekkaduthangal, Chennai - 600 032,India.
Tel:+91-44-4353 0168;Mobile:+91-9445-019919
URL: www.venmsol.com
"We make a living by what we get, we make a life by what we give...-
Unknown "
Email Scanned for
Virus & Dangerous Content by : www.CleanMailGateway.com
--
Thanks & Regards,
Deepika Makhija
eInfochips Ltd.
Tel. No. +91-79-26563705 Ext. 218
www.einfochips.com
--
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
___
Davinci-linux-open-source mailing list
Davinci-linux-open-sour
Re: saDisplay + DM6467 showing black an white image in SD Display
Hi, Display won't work with YUV 422 Planar sorry it was my mistake. Your input is 4:2:0 semi planar to VDCE, and output of VDCE will be 4:2:2 semi planar which will be given to display driver and hence display would be working, as display accepts 4:2:2 semi planar input. Regards, Deepika Vinayagam Mariappan wrote: Hi Deepika, I just made the saDisplay to work. Its always better to follow some principle like, >> Give YUV420 semi planar data to convert YUV422 data other wise you will get wrong conversion file because when we use Ccv it always copy the data with image width size >> Display always works with YUV422 Planar Anyway thanks for your detailed description that made me analyse it properly. Regards, Vinayagam M On Sun, Aug 2, 2009 at 3:04 AM, Jadav, Brijesh R <brijes...@ti.com> wrote: Hi Deepika, As per the specs, VPIF cannot display planar YUV422 data. It says it takes Luma and Chroma data for top and bottom field for interlaced image and Luma and Chroma data for the Progressive image. Also there is no separate register even to specify buffer pointer for cb and cr data. This is also true for the VDCE. Can you please tell me where it says VPIF can display planar YUV422 images? Thanks, Brijesh Jadav From: davinci-linux-open-source-boun...@linux.davincidsp.com [davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Deepika Makhija [deepika.makh...@einfochips.com] Sent: Saturday, August 01, 2009 12:01 AM To: Vinayagam Mariappan Cc: Davinci-linux-open-source@linux.davincidsp.com Subject: Re: saDisplay + DM6467 showing black an white image in SD Display Hi, DM6467 encode/decode supports 4:2:0 YUV semi planar mode only Capture driver supports 4:2:2 YUV semi planar and display supports 4:2:2 semi planar and planar. VDCE module performs conversion irrespective of planar/semi planar mode, it does resize and CCV conversion Assume you perform CCV conversion of 4:2:2 to 4:2:0 than * If input is 4:2:2 semi planar than output will be 4:2:0 semi planar * If input is 4:2:2 planar than output will be 4:2:0 planar Capture and display drivers allocate buffer for 1920x1080 resolution during initialization. Two buffers are located, one for luma and other for chroma. So, Chroma will be at the offset of 1920*1080 irrespective of the capture resolution. Same is true for the display driver. But this is the case only for MMAP buffers as MMAP buffers are allocated by the driver. Luma and chroma can be arranged together with the ioctl S_FMT. In that case chroma data will be at the offset of "width*height", where width/height corresponds to the resolution selected. One more thing, in case of MMAP buffers, if S_FMT is performed than Luma and chroma will be aligned together and buffer length would be still 1920*1080*2 as those buffers are allocated during initialization. VDCE expects chroma at the offset of "buffer length /2", in that case also only Y data will appear, as actual chroma data would be at 720*480 offset for NTSC. Hope this helps you to debug your problem Regards, Deepika Vinayagam Mariappan wrote: Hi, Its confusing me.. Let me give your data In my system, I just decode MPEG-4 Data and get YUV420 on D1 resolution.. Now What I am doing is Just get one Frame of YUV420 data from decoder (YUV420 => [YY][UU...][V] then convert that YUV420 to YUV422 using saCCV420_422 and then I use the converted YUV422 to display unit using saDisplay. I get Luma data properly out on screen but never get Chroma. Actually I use Decoder Demo Application which made for HD. I have able to display the HD Decoded data comes with demo and display it on SD unit. But when I use my customized decoded on D1 resolution I am not getting anything on screen. So I want to debug the issue using saDisplay then update it on applicayion. I hope you got me in a right way... Looking forward to fix this issue. Regards, Vinayagam M On Sat, Aug 1, 2009 at 3:12 AM, Jadav, Brijesh R <brijes...@ti.combrijes...@ti.com>> wrote: Hello Murali, DM6467 supports NV16 video format, where image is stored in two buffers. First buffer contains luma data and second buffer contains cb and cr interleaved data. It does not support completele YUV422 interleaved data. You are right, chroma buffer pointer could also be an problem. Display driver always expects chroma data at the half of the buffer size. Thanks, Brijesh Jadav From: Karicheri, Muralidharan Sent: Friday, July 31, 2009 10:34 AM To: Jadav, Brijesh R; Vinayagam Mariappan Cc: Davinci-linux-open-source@linux.davincidsp.comDavinci-linux-open-source@linux.davincidsp.com> Subject: RE: saDisplay + DM64
Re: saDisplay + DM6467 showing black an white image in SD Display
Hi, Nice to hear that your saDisplay is working now. "we are not getting video.But I get video data till App." Can you please describe in detail, up till which module you are getting correct output. I would suggest instead of integrating your decoder, first try to modify the application to work at D1 resolution with TI codecs, which are capable of decoding D1 resolution also, for that you would have to change few enums in the application. Once that path is clear than integrate your decoder. Regards, Deepika Vinayagam Mariappan wrote: Hi Deepika, I just made the saDisplay to work properly. Now I have to change the Decoder Application to work with our customized decoder which always give video out with D1 resolution... The TI Demo Application is for HD Display and I change that to work for SD Display. When I integrate our customized decoder with demo application, we are not getting video.But I get video data till App. Where will be the problem... Regards, Vinayagam M -- _ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: saDisplay + DM6467 showing black an white image in SD Display
lay it. Where do I making mistake? Regards, Vinayagam M On Fri, Jul 31, 2009 at 9:31 PM, Jadav, Brijesh R <brijes...@ti.combrijes...@ti.com>> wrote: Hi, What is the format of your YUV422 file? DM6467 supports only YUV422 Semi-Planar format. Thanks, Brijesh Jadav From: Vinayagam Mariappan [mailto:vinayagamenm...@gmail.comvinayagamenm...@gmail.com>] Sent: Friday, July 31, 2009 5:57 PM To: Jadav, Brijesh R Cc: Davinci-linux-open-source@linux.davincidsp.comDavinci-linux-open-source@linux.davincidsp.com> Subject: Re: saDisplay + DM6467 showing black an white image in SD Display Hi, Yes, I know... But I have modified to play with YUV422 sample. I get only Luma not chroma I am just fulling the buffer with YUV422 Data. Regards, Vinayagam M On Fri, Jul 31, 2009 at 9:19 PM, Jadav, Brijesh R <brijes...@ti.combrijes...@ti.com>> wrote: Hi, As far as I remember, this application does not work the sample image. Application actually generates color bar and displays it. Thanks, Brijesh Jadav From: davinci-linux-open-source-boun...@linux.davincidsp.comdavinci-linux-open-source-boun...@linux.davincidsp.com> [mailto:davinci-linux-open-source-boun...@linux.davincidsp.comdavinci-linux-open-source-boun...@linux.davincidsp.com>] On Behalf Of kirthika varadarajan Sent: Friday, July 31, 2009 3:28 PM To: Davinci-linux-open-source@linux.davincidsp.comDavinci-linux-open-source@linux.davincidsp.com> Subject: saDisplay + DM6467 showing black an white image in SD Display We tried displaying yuv4::2:2(740x480) image in SD display using saDisplay(application sample ibn PSP), But we are getting black and white image even if we input color image. We tried the sample file given in PSP. But black. we are curious to know how to get the color SD display. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.comDavinci-linux-open-source@linux.davincidsp.com> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- Regards, Vinayagam M VeNMSOL Technologies, #7A, First Cross Street, Ganapathy Colony, Ekkaduthangal, Chennai - 600 032,India. Tel:+91-44-4353 0168;Mobile:+91-9445-019919 URL: www.venmsol.com<http://www.venmsol.com> "We make a living by what we get, we make a life by what we give...- Unknown " -- Regards, Vinayagam M VeNMSOL Technologies, #7A, First Cross Street, Ganapathy Colony, Ekkaduthangal, Chennai - 600 032,India. Tel:+91-44-4353 0168;Mobile:+91-9445-019919 URL: www.venmsol.com<http://www.venmsol.com> "We make a living by what we get, we make a life by what we give...- Unknown " -- Regards, Vinayagam M VeNMSOL Technologies, #7A, First Cross Street, Ganapathy Colony, Ekkaduthangal, Chennai - 600 032,India. Tel:+91-44-4353 0168;Mobile:+91-9445-019919 URL: www.venmsol.com "We make a living by what we get, we make a life by what we give...- Unknown " Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- Thanks & Regards, Deepika Makhija eInfochips Ltd. Tel. No. +91-79-26563705 Ext. 218 www.einfochips.com -- Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: No interrupts on VDINT0
Hi All,
VPFE datasheet (spruf71.pdf) section 5.4.3.1 indicates that "VDINT0 and
VDINT1 will occur after receiving the
number of horizontal lines (HD pulse signals) set in the VDINT.VDINT0
and VDINT.VDINT1 register fields,
respectively" while when I looked at the CCDC and vpfe driver code, I
found:
vert_start = image_win->top;
if (frm_fmt == CCDC_FRMFMT_INTERLACED) {
vert_nr_lines = (image_win->height >> 1) - 1;
vert_start >>= 1;
/* configure VDINT0 and VDINT1 */
regw(vert_start, VDINT0);
} else {
vert_nr_lines = image_win->height - 1;
/* configure VDINT0 and VDINT1 */
mid_img = vert_start + (image_win->height / 2);
regw(vert_start, VDINT0);
regw(mid_img, VDINT1);
}
image_win top, is zero in my case, so it leads to 0x0 in VDINT0. Am I
doing something wrong over here?
Thanks,
Deepika
Karicheri, Muralidharan wrote:
SYNCEN should be 3 for capture to start
Murali
Karicheri
Software
Design Engineer
Texas
Instruments Inc.
Germantown, MD 20874
Phone :
301-515-3736
email:
m-kariche...@ti.com
From:
davinci-linux-open-source-boun...@linux.davincidsp.com
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of omkar savagaonkar
Sent: Wednesday, July
08, 2009
6:37 AM
To: davinci-linux-open-source@linux.davincidsp.com;
Deepika Makhija
Subject: Re: No
interrupts on
VDINT0
First check out whether your system is
getting the interrupt and driver is unable to handle.
U can do this by cat /proc/interrupts and cat /proc/stat.
--- On Wed, 8/7/09, Deepika
Makhija
wrote:
From: Deepika Makhija
Subject: No interrupts on VDINT0
To: davinci-linux-open-source@linux.davincidsp.com
Date: Wednesday, 8 July, 2009, 3:21 PM
Hi All,
I am working on customized board based on DM355 SoC, in which I have to
capture 16bit YCbCr data in 1024x768 and 1920x1080 resolution. I have
modified CCDC driver (davinci_vpfe.c/ cccdc_dm355..c files) for the
same, but unable to get interrupts. I have configured PINMUX0 setting
to 0x7F55 and HD/VD sync signal will be external, so configured as
input. PCLK is 74.18MHz (I won't be using H3A module).CAM_WEN_FIELD
signal will be used to indicate even/odd field.
Below is the register dump of CCDC:
Reading
0x0 to SYNCEN...
Reading
0x9080 to MODESET
Reading
0x0 to HDWIDTH...
Reading
0x0 to VDWIDTH...
Reading
0x0 to PPLN...
Reading
0x0 to LPFR...
Reading
0x0 to SPH...
Reading 0xeff to NPH...
Reading
0x0 to SLV0...
Reading
0x0 to SLV1...
Reading 0x21b to NLV...
Reading 0x to CULH...
Reading 0xff to CULV...
Reading
0x78 to HSIZE...
Reading
0x249 to SDOFST...
Reading
0x0 to STADRH...
Reading
0x0 to STADRL...
Reading
0x0 to CLAMP...
Reading
0x0 to DCSUB...
Reading
0x0 to COLPTN...
Reading
0x0 to BLKCMP0...
Reading
0x0 to BLKCMP1...
Reading
0x0 to MEDFILT...
Reading
0x80 to RYEGAIN...
Reading
0x80 to GRCYGAIN...
Reading
0x80 to GBGGAIN...
Reading
0x80 to BMGGAIN...
Reading
0x0 to OFFSET...
Reading 0xfff to OUTCLIP...
Reading
0x0 to VDINT0...
Reading
0x0 to VDINT1...
Reading
0x0 to RSV0...
Reading
0x0 to GAMMAWD...
Reading
0x0 to REC656IF
Reading
0x8840 to CCDCFG...
Reading
0x0 to FMTCFG...
Reading
0x0 to FMTPLEN...
Reading
0x0 to FMTSPH...
Reading
0x0 to FMTLNH...
Reading
0x0 to FMTSLV...
Reading
0x0 to FMTLNV...
Reading
0x0 to FMTRLEN...
Reading
0x0 to FMTHCNT...
Reading
0x0 to FMT_ADDR_PTR_B...
Reading
0x0 to FMTPGM_VF0...
Reading
0x0 to FMTPGM_VF1...
Reading
0x0 to FMTPGM_AP0...
Reading
0x0 to FMTPGM_AP1...
Reading
0x0 to FMTPGM_AP2...
Reading
0x0 to FMTPGM_AP3...
Reading
0x0 to FMTPGM_AP4...
Reading
0x0 to FMTPGM_AP5...
Reading
0x0 to FMTPGM_AP6...
Reading
0x0 to FMTPGM_AP7...
Reading
0x0 to LSCCFG1...
Reading
0x0 to LSCCFG2...
Reading
0x0 to LSCH0...
Reading
0x0 to LSCV0...
Reading
0x0 to LSCKH...
Reading
0x0 to LSCKV...
Reading
0x0 to LS
Re: No interrupts on VDINT0
I have verified Syncen in my code, Syncen value is set to 0x3 in STREAMON ioctl and reset again to 0x0 in STREAMOFF icotl. Register log was taken at the end of ccdc_config_ycbcr() function, and SYNCEN was updated later, so currently value of SYNCEN is 0x3, but still no interrupts :(. Thanks, Deepika Karicheri, Muralidharan wrote: SYNCEN should be 3 for capture to start Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 Phone : 301-515-3736 email: m-kariche...@ti.com From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of omkar savagaonkar Sent: Wednesday, July 08, 2009 6:37 AM To: davinci-linux-open-source@linux.davincidsp.com; Deepika Makhija Subject: Re: No interrupts on VDINT0 First check out whether your system is getting the interrupt and driver is unable to handle. U can do this by cat /proc/interrupts and cat /proc/stat. --- On Wed, 8/7/09, Deepika Makhija wrote: From: Deepika Makhija Subject: No interrupts on VDINT0 To: davinci-linux-open-source@linux.davincidsp.com Date: Wednesday, 8 July, 2009, 3:21 PM Hi All, I am working on customized board based on DM355 SoC, in which I have to capture 16bit YCbCr data in 1024x768 and 1920x1080 resolution. I have modified CCDC driver (davinci_vpfe.c/ cccdc_dm355..c files) for the same, but unable to get interrupts. I have configured PINMUX0 setting to 0x7F55 and HD/VD sync signal will be external, so configured as input. PCLK is 74.18MHz (I won't be using H3A module).CAM_WEN_FIELD signal will be used to indicate even/odd field. Below is the register dump of CCDC: Reading 0x0 to SYNCEN... Reading 0x9080 to MODESET Reading 0x0 to HDWIDTH... Reading 0x0 to VDWIDTH... Reading 0x0 to PPLN... Reading 0x0 to LPFR... Reading 0x0 to SPH... Reading 0xeff to NPH... Reading 0x0 to SLV0... Reading 0x0 to SLV1... Reading 0x21b to NLV... Reading 0x to CULH... Reading 0xff to CULV... Reading 0x78 to HSIZE... Reading 0x249 to SDOFST... Reading 0x0 to STADRH... Reading 0x0 to STADRL... Reading 0x0 to CLAMP... Reading 0x0 to DCSUB... Reading 0x0 to COLPTN... Reading 0x0 to BLKCMP0... Reading 0x0 to BLKCMP1... Reading 0x0 to MEDFILT... Reading 0x80 to RYEGAIN... Reading 0x80 to GRCYGAIN... Reading 0x80 to GBGGAIN... Reading 0x80 to BMGGAIN... Reading 0x0 to OFFSET... Reading 0xfff to OUTCLIP... Reading 0x0 to VDINT0... Reading 0x0 to VDINT1... Reading 0x0 to RSV0... Reading 0x0 to GAMMAWD... Reading 0x0 to REC656IF Reading 0x8840 to CCDCFG... Reading 0x0 to FMTCFG... Reading 0x0 to FMTPLEN... Reading 0x0 to FMTSPH... Reading 0x0 to FMTLNH... Reading 0x0 to FMTSLV... Reading 0x0 to FMTLNV... Reading 0x0 to FMTRLEN... Reading 0x0 to FMTHCNT... Reading 0x0 to FMT_ADDR_PTR_B... Reading 0x0 to FMTPGM_VF0... Reading 0x0 to FMTPGM_VF1... Reading 0x0 to FMTPGM_AP0... Reading 0x0 to FMTPGM_AP1... Reading 0x0 to FMTPGM_AP2... Reading 0x0 to FMTPGM_AP3... Reading 0x0 to FMTPGM_AP4... Reading 0x0 to FMTPGM_AP5... Reading 0x0 to FMTPGM_AP6... Reading 0x0 to FMTPGM_AP7... Reading 0x0 to LSCCFG1... Reading 0x0 to LSCCFG2... Reading 0x0 to LSCH0... Reading 0x0 to LSCV0... Reading 0x0 to LSCKH... Reading 0x0 to LSCKV... Reading 0x0 to LSCMEMCTL... Reading 0x0 to LSCMEMD... Reading 0x0 to LSCMEMQ... Reading 0x0 to DFCCTL... Reading 0x0 to DFCVSAT... Reading 0x0 to DFCMEMCTL... Reading 0x0 to DFCMEM0... Reading 0x0 to DFCMEM1... Reading 0x0 to DFCMEM2... Reading 0x0 to DFCMEM3... Reading 0x0 to DFCMEM4 Reading 0x0 to CSCCTL... Reading 0x0 to CSCM0... Reading 0x0 to CSCM1... Reading 0
No interrupts on VDINT0
Hi All, I am working on customized board based on DM355 SoC, in which I have to capture 16bit YCbCr data in 1024x768 and 1920x1080 resolution. I have modified CCDC driver (davinci_vpfe.c/ cccdc_dm355.c files) for the same, but unable to get interrupts. I have configured PINMUX0 setting to 0x7F55 and HD/VD sync signal will be external, so configured as input. PCLK is 74.18MHz (I won't be using H3A module).CAM_WEN_FIELD signal will be used to indicate even/odd field. Below is the register dump of CCDC: Reading 0x0 to SYNCEN... Reading 0x9080 to MODESET... Reading 0x0 to HDWIDTH... Reading 0x0 to VDWIDTH... Reading 0x0 to PPLN... Reading 0x0 to LPFR... Reading 0x0 to SPH... Reading 0xeff to NPH... Reading 0x0 to SLV0... Reading 0x0 to SLV1... Reading 0x21b to NLV... Reading 0x to CULH... Reading 0xff to CULV... Reading 0x78 to HSIZE... Reading 0x249 to SDOFST... Reading 0x0 to STADRH... Reading 0x0 to STADRL... Reading 0x0 to CLAMP... Reading 0x0 to DCSUB... Reading 0x0 to COLPTN... Reading 0x0 to BLKCMP0... Reading 0x0 to BLKCMP1... Reading 0x0 to MEDFILT... Reading 0x80 to RYEGAIN... Reading 0x80 to GRCYGAIN... Reading 0x80 to GBGGAIN... Reading 0x80 to BMGGAIN... Reading 0x0 to OFFSET... Reading 0xfff to OUTCLIP... Reading 0x0 to VDINT0... Reading 0x0 to VDINT1... Reading 0x0 to RSV0... Reading 0x0 to GAMMAWD... Reading 0x0 to REC656IF... Reading 0x8840 to CCDCFG... Reading 0x0 to FMTCFG... Reading 0x0 to FMTPLEN... Reading 0x0 to FMTSPH... Reading 0x0 to FMTLNH... Reading 0x0 to FMTSLV... Reading 0x0 to FMTLNV... Reading 0x0 to FMTRLEN... Reading 0x0 to FMTHCNT... Reading 0x0 to FMT_ADDR_PTR_B... Reading 0x0 to FMTPGM_VF0... Reading 0x0 to FMTPGM_VF1... Reading 0x0 to FMTPGM_AP0... Reading 0x0 to FMTPGM_AP1... Reading 0x0 to FMTPGM_AP2... Reading 0x0 to FMTPGM_AP3... Reading 0x0 to FMTPGM_AP4... Reading 0x0 to FMTPGM_AP5... Reading 0x0 to FMTPGM_AP6... Reading 0x0 to FMTPGM_AP7... Reading 0x0 to LSCCFG1... Reading 0x0 to LSCCFG2... Reading 0x0 to LSCH0... Reading 0x0 to LSCV0... Reading 0x0 to LSCKH... Reading 0x0 to LSCKV... Reading 0x0 to LSCMEMCTL... Reading 0x0 to LSCMEMD... Reading 0x0 to LSCMEMQ... Reading 0x0 to DFCCTL... Reading 0x0 to DFCVSAT... Reading 0x0 to DFCMEMCTL... Reading 0x0 to DFCMEM0... Reading 0x0 to DFCMEM1... Reading 0x0 to DFCMEM2... Reading 0x0 to DFCMEM3... Reading 0x0 to DFCMEM4... Reading 0x0 to CSCCTL... Reading 0x0 to CSCM0... Reading 0x0 to CSCM1... Reading 0x0 to CSCM2... Reading 0x0 to CSCM3... Reading 0x0 to CSCM4... Reading 0x0 to CSCM5... Reading 0x0 to CSCM6... Reading 0x0 to CSCM7... Reading 0x0 to DATAOFST... I don't know why I am unable to receive interrupts, i have probed the CAM_HD/CAM_VD/CAM_ WEN_FIELD/PCLK signals and everything seems correct over there. Am I missing anything or is there something wrong in understanding/implementation?? Any kind of help will be appreciated. Thanks & Regards, Deepika -- _ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: u boot and framebuffer interface
Thanks for help.
Now I am able to display logo, after enabling Framebuffer Console
support in kernel config.
Device Drivers -> Graphics Support -> Console display driver support
---> <*> Framebuffer Console support
Background for the logo is blue by default, I am successfully able to
replace logo, but failed to change the background color.
Can you please help me on that.
Regards,
Deepika
Deepak Mundra wrote:
Hi Seems like your driver configuration is not proper, may be your
offset.. are images coming properly on display ??? .. And please from
next time mail in mailing list .. it will help other people also
Regards
deepak
On 4/10/09, *Deepika Makhija* <mailto:deepika.makh...@einfochips.com>> wrote:
Hello,
Response is inline to previous help.
Deepak Mundra wrote:
hi,
On 4/10/09, *Deepika Makhija* mailto:deepika.makh...@einfochips.com>> wrote:
Hi,
Mine is VGA 1024x768 output to touchscreen LCD.
I didn't knew that Davinci Kernel, displays logo during boot,
some random display patterns (Vertical lines of different
colors) are observed on LCD during kernel boot up
did you mean by color baar pattern ?
Deepika :
No Not the color bar pattern. While u-boot is loaded some random
lines are observed, every time different :(
then in driver/video/davincifb.c check if
dispc_reg_out(VENC_VDPRO, 0x100); is enabled .. this value is set
to generate colorbar pattern .. if this is line is ther just
comment. and try to boot
or second thing could be to make sure logo display is enabled in
kernel
# make menuconfig
Device drivers -> Graphics support -> Logo configuration ->bootup
logo and select 224 pattern.
Deepika :
Default Kernel Configuration enables all three options i.e
[*] Standard black and white Linux logo
[*] Standard 16-color Linux logo
[* ] Standard 224-color Linux logo
I tried which each of them one by one, but no LOGO appeared, only
black(blank) screen.
process (after FB is initialized). Can u help me in that, i
mean guide if i m missing something in that case
Thanks,
Deepika
Deepak Mundra wrote:
And davinci kernel already has logo display
during boot up ryt, so you can replace that logo with your
logo .. this will make logo to be displayed immediately
after frame buffer is initialized in kernel and before
filesystem is loaded..
On 4/10/09, *Deepak Mundra* mailto:deepa...@allaboutif.com>> wrote:
Hi,
Just to confirm .. are you using VGA output or
composit .. coz a s i mentioned earlier for me it is
taking time in ths8200 chip initialization code.. coz it
uses i2c writes almost in 20+ adress which was taking
time .. and i felt like it is coz of i2c driver used in
uboot 1.2.0 .. So my suggetion is that in case if you
are not using ths8200 chip you can go ahead with that ..
and i feel that in latest uboot it should work fine..
you can go throgh following link for davincifb support
in uboot 1.3.x+ ..i had to do little work to pul it down
to 1.2.0 ..
http://github.com/neuros/u-boot/commit/689195c1865b79f745bcf145a809464dec2f391f
Thanks & Regards
Deepak.
On 4/10/09, *Deepika Makhija*
mailto:deepika.makh...@einfochips.com>> wrote:
Hello Deepak,
Thanks for your inputs. Actually I wanted to display
a logo, till the system boots up. I am working on
DM355 based product, in which it few sec's to
initialize the everything
(ubl,U-boot,kernel,filesystem), so i thought to
display something till the board is up, but if this
adds 3/4 sec delay in boot up process than it is of
no use for me. I guess, I have to think of some
other option like initialize video interface earlier
in kernel and display LOGO from the kernel, because
loading filesystem from NAND eats up much of the
booting time.
Thanks for your help
Regards,
Deepika
Deepak Mundra wrote:
Hello Deepika,
I am working with dm6446 .. and we r using vga
output .. actulauly i was able to enable
framebuffer support in uboot and display colorbaar
pattern and also diffrent colors.. but couldnt draw
any images.. actualy i found that when initializing
framebuffer THS8200 is taking time almost 3-4
seconds(may b coz of
Re: Davinci-linux-open-source Digest, Vol 40, Issue 48
Hi All, I am working on DaVinci Processor, and had a query*:* Is it possible to display any image/Logo on frame buffer at u-boot level, I mean display something before the kernel and filesystem is up and working? If yes, than how can I do that? Any suggestions/help will be appreciated. Regards, Deepika ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
DM355 IPIPE: Image corruption in resizing
Hi All,
I am working on DM355 IPIPE module, and facing some issues in that.
I am performing resizing operation with IPIPE, in my case multiple
frames are resized and in few resized images corruption is observed.
Debugging this corruption I observed that the corruption occurs while
threading, in sequential code there was no corruption.
Even if other thread is not related to the resize operation thread i.e.
for example my other thread contains only this code:
while(1) { usleep(1); }, even than corruption is observed.
Has anyone faced this kind of issue??
Any kind of help will be appreciated.
Thanks in advance,
Deepika
--
_
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
__
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: DM355 IPIPE: Image corruption in resizing
Deepika Makhija wrote: Hi All, I am facing image corruption problem while resizing 960*1080 image into different resolution like 256*384, 256*192, 192*288, 512*384 Input is 1920*1080 image jpeg image which is decoded and than resized to 512*384 resolution. DM355 ipipe can only process 1344 per line once so I split the image into two parts each of 960*1080. Resize operation is performed on each part and those buffers are combined. Below is snapshot of input and output image. Image corruption behavior is not at all certain. This corruption occurs while processing n number of images in loop. Below is my ipipe module configurations. int i_width = 960; int i_height = 1080; int o_width = 256; int _height = 384; ipipeParamStruct.ipipeif_param.source = SDRAM_YUV; ipipeParamStruct.ipipeif_param.hnum = i_width; ipipeParamStruct.ipipeif_param.vnum = i_height; ipipeParamStruct.ipipeif_param.glob_hor_size = i_width + 8; ipipeParamStruct.ipipeif_param.glob_ver_size = i_height + 10; ipipeParamStruct.ipipeif_param.adofs = ((i_width * 2 + 31) & (~31)); ipipeParamStruct.ipipeif_param.rsz = 16; ipipeParamStruct.ipipeif_param.clk_div = DIVIDE_SIXTH; ipipeParamStruct.ipipe_dpaths_fmt = data_fmt; ipipeParamStruct.ipipe_vst = 0; ipipeParamStruct.ipipe_hst = 0; ipipeParamStruct.ipipe_vsz = i_height - 1; ipipeParamStruct.ipipe_hsz = i_width - 1; ipipeParamStruct.rsz_rsc_param[0].rsz_h_dif = (i_width * 256 / o_width); ipipeParamStruct.rsz_rsc_param[0].rsz_v_dif = ((i_height) * 256 / o_height); ipipeParamStruct.rsz_rsc_param[0].rsz_o_hsz = o_width - 1; ipipeParamStruct.rsz_rsc_param[0].rsz_o_vsz = o_height - 1; ipipeParamStruct.ext_mem_param[0].rsz_sdr_oft = ((o_width * 2 + 31) & (~31)); ipipeParamStruct.ext_mem_param[0].rsz_sdr_ptr_e = o_height; ipipeParamStruct.rsz_en[0] = ENABLE; ipipeParamStruct.rsz_en[1] = DISABLE; ipipeParamStruct.prefilter.pre_en = DISABLE; ipipeParamStruct.false_color_suppresion.fcs_en = DISABLE; ipipeParamStruct.edge_enhancer.yee_emf = DISABLE; ipipeParamStruct.rgb2yuv.yuv_adj_ctr = 0x20; ipipeParamStruct.wb.wb2_dgn = 0x200; ipipeParamStruct.wb.wb2_wg_r = 0x110; ipipeParamStruct.wb.wb2_wg_gr = 0xf0; ipipeParamStruct.wb.wb2_wg_gb = 0xf0; ipipeParamStruct.wb.wb2_wg_b = 0x130; According to my observation, there is some problem of HSYNC and VSYNC i.e glob_hor_size and glob_ver_size still I am not sure of it and even don't know what should be value of glob_hor_size and glob_ver_size in my case. Any kind of help will be appreciated. Thanks & Regards, Deepika ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
YCbCr422 format, 16-bit with discrete H and VSYNC signals Capture via VPFE interface
Hi All, I am working on vpfe interface of v4l2 on DM355. According to vpfe user guide it supports YCbCr422 format, 16-bit with discrete H and VSYNC signals, but looking at vpfe driver I didn't found support for it (correct me if I am wrong). Can anyone suggest me what kind of changes are needed to capture 16 bit data with discrete H and Vsync ??? Mine is the customized board with DM355 Soc over it. Kernel version is DaVinciLSP_01_30_00_082.tar.gz (2.6.10). Any kind of help will be appreciated. Thanks, Deepika -- _ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. __ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
UART1/2 on DM6467
Hi All,
Finally we got UART1 / UART2 working on DM6467 :)
Step#1
Make menuconfig and put no of uart to 3
( Device Drivers
->Character Devices
->Serial Drivers
->Maximum number of non-legacy 8250/16550 serial ports
Set this to 3 )
Step#2
To enable UART2 and UART1
Disable Consumer IR and TSIF module from Menuconfig
( Device Drivers
->Character Devices
-> DM646x Consumer IR Driver ( Remove it )
-> DM646x Transport Stream Interface Support ( Remove it )
Step#3
Add follow code snippest to your
/arch/arm/mach-davinci/board-dm6467.c file
( Modify board_init function with the following code )
static void board_init(void)
{
volatile int *ptr_pgmgt,*ptr_ier;
int del = 0;
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_LPSC_VLYNQ, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_HDVICP0, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_HDVICP1, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_SPI, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_TPCC, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_TPTC0, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_TPTC1, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_TPTC2, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_TPTC3, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_AEMIF, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_DM646X_LPSC_GPIO, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_LPSC_TIMER2, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_LPSC_UART1, 1);
board_setup_psc(DAVINCI_GPSC_ARMDOMAIN, DAVINCI_LPSC_UART2, 1);
#define PINMUX0REG __REG(PINMUX0)
#define PINMUX1REG __REG(PINMUX1)
#define VDD3P3V_PWDN __REG(0x01C40048)
VDD3P3V_PWDN = 0;
PINMUX0REG &= ~(0x1);
PINMUX0REG = 0x4;
PINMUX1REG = 0x15;
ptr_ier = (volatile int *)IO_ADDRESS(DAVINCI_UART1_BASE+0x4);
*ptr_ier = 0x0; //disable int
ptr_pgmgt = (volatile int *) IO_ADDRESS(DAVINCI_UART1_BASE+0x20);
*ptr_pgmgt = 0x00;
ptr_ier = (volatile int *)IO_ADDRESS(DM644X_UART2_BASE+0x4);
*ptr_ier = 0x0; //disable int
ptr_pgmgt = (volatile int *) IO_ADDRESS(DM644X_UART2_BASE+0x20);
*ptr_pgmgt = 0x00;
davinci_serial_init(&serial_device);
davinci_clk_init();
}
Step #4 Make uImage
Have your UART1 / UART2 working without flow control :)
Thanks,
Deepika
--
_
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
__
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Can we decode video clips in fast-forward mode?
Hi All, I am working on DM355 evm board. I am developing application using TI DVSDK framework. I am end application will be: .264 Clip > decode -> display But in this I want to provide facility of forward/rewind video clip as per user selection through GUI. Can anyone guide me on this??? I wanted to know is there any facility in MPEG4 decoder to forward/rewind input clip? Will I need any algorithm for that??? Any help will be appreciated. Thanks in advance. - Deepika -- _ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. __ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
What is purpose of targetFrameRate and refFrameRate in dynamic parameter of Video Encoder?
Hi All, I am working on DM355 evm board. As I am new to this environment I had few doubts in Video encode demo application. What is purpose of targetFrameRate and refFrameRate in dynamic parameters? I guess those are to indicate the codec the frame rate. But what is need for two different variables? Can anyone guide me on this? Thanks in advance Regards, Deepika -- _ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. __ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
[Fwd: Decode demo not working on dvsdk_1_30_00_40 for DM6446]
Hi All, I am working on DM6446 Davinci. For that I have installed "dvsdk_1_30_00_40". I have taken following fresh installation files (i.e. without recompiling anything)* *and tried to run the the deocode demo, but cmem insertion failed. * *uImage:* dvsdk_1_30_00_40/PSP_01_20_00_014/bin/dm6446/ uImage-dm6446 * *cmemk.ko: * dvsdk_1_30_00_40/cmem_2_00_01/packages/ti/sdo/linuxutils/cmem/src/module/ cmemk.ko * *dsplinkk.ko:* dvsdk_1_30_00_40/dsplink_140-05p1/packages/dsplink/gpp/export/BIN/Linux/Davinci/DEBUG/dsplink.ko * *loadmodules.sh:* dvsdk_1_30_00_40/demos/dm6446/loadmodules.sh Later on recompiling CMEM, i was able to insert it, but decode demo gave following error. *Unable to handle kernel paging request at virtual address 43016132 pgd = c0004000 [43016132] *pgd= Internal error: Oops: 1 [#1] Modules linked in: dsplinkk cmemk CPU: 0 PC is at IPS_unregister+0x20c/0x318 [dsplinkk]* and than kernel panic messages. Thanks in advance. Any help will be appreciated. Regards, Deepika -- _ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. __ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Decode demo not working on dvsdk_1_30_00_40 for DM6446
Hi All, I am working on DM6446 Davinci. For that I have installed "dvsdk_1_30_00_40". I have taken following fresh installation files (i.e. without recompiling anything)* *and tried to run the the deocode demo, but cmem insertion failed. * *uImage:* dvsdk_1_30_00_40/PSP_01_20_00_014/bin/dm6446/ uImage-dm6446 * *cmemk.ko: * dvsdk_1_30_00_40/cmem_2_00_01/packages/ti/sdo/linuxutils/cmem/src/module/ cmemk.ko * *dsplinkk.ko:* dvsdk_1_30_00_40/dsplink_140-05p1/packages/dsplink/gpp/export/BIN/Linux/Davinci/DEBUG/dsplink.ko * *loadmodules.sh:* dvsdk_1_30_00_40/demos/dm6446/loadmodules.sh Later on recompiling CMEM, i was able to insert it, but decode demo gave following error. *Unable to handle kernel paging request at virtual address 43016132 pgd = c0004000 [43016132] *pgd= Internal error: Oops: 1 [#1] Modules linked in: dsplinkk cmemk CPU: 0 PC is at IPS_unregister+0x20c/0x318 [dsplinkk]* Complete error log is attached. Thanks in advance. Any help will be appreciated. Regards, Deepika [EMAIL PROTECTED]:/home/WGV/decode# ./decoded -v davincieffect_pal.264 Decode Debug: PAL selected Decode demo started. Decode Debug: Codec Engine initialized Decode Debug: Logging initialized Decode Debug: Pause object opened Decode Debug: Init rendezvous opened for 3 threads Decode Debug: Cleanup rendezvous opened for 3 threads Decode Debug: Priming rendezvous opened for 2 threads Decode Debug: Display buffer 0 mapped to 0x42b45000 has physical address 0x8080 Decode Debug: Display buffer 1 mapped to 0x42c0f800 has physical address 0x808ca800 Decode Debug: Display buffer 2 mapped to 0x42cda000 has physical address 0x80995000 Decode Debug: Video display device initialized. Decode Debug: Display thread created Decode Debug: Video file successfully opened Decode Debug: Codec Engine opened in video thread Decode Debug: OSD successfully initialized Decode Debug: OSD transparency initialized Decode Debug: Video decoder created Decode Debug: Contiguous buffer allocated at physical address 0x87d0 Decode Debug: Contiguous buffer allocated at physical address 0x87c35000 Decode Debug: Contiguous buffer allocated at physical address 0x87b6a000 Decode Debug: Contiguous buffer allocated at physical address 0x87a9f000 Decode Debug: Codec Engine opened in control thread Decode Debug: MSP430 library initialized Decode Debug: User interface created Decode Debug: Entering control main loop. Decode Debug: Entering display main loop. Unable to handle kernel paging request at virtual address 43016132 pgd = c0004000 [43016132] *pgd= Internal error: Oops: 1 [#1] Modules linked in: dsplinkk cmemk CPU: 0 PC is at IPS_unregister+0x20c/0x318 [dsplinkk] LR is at 0x0 pc : []lr : [<>]Tainted: PF sp : c5659d44 ip : 43016132 fp : c5659d88 r10: c8d82600 r9 : r8 : c88e r7 : r6 : c88e r5 : bf02fac4 r4 : 8000 r3 : 0020 r2 : 0001 r1 : c047d840 r0 : 8000 Flags: Nzcv IRQs off FIQs on Mode SVC_32 Segment user Control: 5317F Table: 8564C000 DAC: 0015 Process decoded (pid: 1161, stack limit = 0xc56581a0) Stack: (0xc5659d44 to 0xc565a000) 9d40: 6013 c562bc60 c562bc60 bf01b968 bf02fecc 9d60: 8000 bf02fecc 8000 c888d000 c8dfee80 c5659dbc 9d80: c5659d8c bf01b628 bf010768 bf02fecc bf02fe30 8000 9da0: 0001 c5659f68 000b c5659dd8 c5659dc0 bf014164 bf01b5d4 9dc0: 0082 bf02f3a4 c5659dfc c5659ddc bf0061a4 bf0140e8 0003 9de0: c61c c51e7b20 c773e060 c5659e0c c5659e00 bf00620c bf0060a4 9e00: c5659e2c c5659e10 c008ad9c bf0061fc c5659e4c c773e060 0ffd 0008 9e20: c5659e4c c5659e30 c004d71c c008ad50 c773e060 c6c55080 c5630840 c6c550b0 9e40: c5659e6c c5659e50 c004df40 c004d69c c5659f68 c5659ee8 c5659e84 c5659e68 9e60: c5659e84 c5659e70 c004eb9c c004dcf0 c5658000 0009 c5659ebc c5659e88 9e80: c0058e24 c004eacc c5630a40 c5659fb0 c0063770 c5658000 c5659fb0 9ea0: c0036154 c0036154 c5659ee8 0095 c5659fac c5659ec0 c0039d58 c0058918 9ec0: c57e7a20 c564b700 fe00 c5659f04 c5630a40 c5659f04 c5659ee8 9ee0: c00a4a10 c012f4a8 0009 c5659f08 9f00: c008aa00 c00a49f4 0009 c049e000 c0036154 0095 9f20: c5659f84 c5659f30 c008aa8c c008a798 c5114dd8 c04793c0 3ff40e45 3ab8a378 9f40: c06e52b0 0101 0001 00038b8c 0001 c5659f84 c5659f68 9f60: c0099b4c c0072d5c fe00 fe00 c049e000 c5659fa4 c5659f88 9f80: c008ad04 0004dcc8 0001 0008 0005 c0036154 c5658000 0095 9fa0: c5659fb0 c0035a0c c0039cfc fe00 01b6 9fc0: 0004dcc8 0001 0008 0004dcc8 00038b8c 00049e6c 401fe000 42343344 9fe0: 423432dc 401b1a30 401989a0 6010 00038b8c 0217e1a0 029d0ff9 Backtrace: [] (IPS_unregister+0x0/0x318 [dsplinkk]) from [] (ZCPY
UART1 on DM6467
Hi all, We are trying to enable UART1 and UART2 in DM6467 EVM. We are using combined kernel tree which has DM355, Davinci and DavinciHD. What all changes do we need to do in kernel files for using UART1 and UART2? We found that this kernel already contains the support for all the UART'S. So we just enable the number of UART in make menuconfig from 1 to 2. We also changed the PINMUX 1 setting for uart. PINMUX 1 register (Base address 0x1c40004) originally read "0x2C" i.e Uart1 in GPIO mode, we changed it's value to "0x24" i.e. Uart1 in uart mode without flow control. Uart0 is in Uart mode with modem control and Uart2 in CIR mode. While performing loop back on Uart1 we are getting following error. "8250.c: Too much work for irq41." Commands we use to perform loopback operation of UART1 are: "cat /dev/tts/1" "echo a5 > /dev/tts/1" Also one surprising thing is that type detected for both UART's is different, detected chips are as follows: UART0: ST16654 UART1: ST16650v2 Is this detected chip proper? Regards, Deepika -- _ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. __ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
UART1 on DM6467
Hi All, We are trying to enable UART1 and UART2 in DM6467 EVM. We are using combined kernel tree which has DM355, Davinci and DavinciHD. What all changes do we need to do in kernel files for using UART1 and UART2? We found that this kernel already contains the support for all the UART'S. So we just enable the number of UART in make menuconfig from 1 to 2 and transmit data. While performing loop back of data we are getting following error. "8250.c: Too much work for irq41." Commands we use to perform loopback operation of UART1 are: "cat /dev/tts/1" "echo a5 > /dev/tts/1" Also one surprising thing is that type detected for both UART's is different, detected chips are as follows: UART0: ST16654 UART1: ST16650v2 Is this detected chip proper? Regards, Deepika -- _ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. __ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
