compile help
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. No Output 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. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
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 Kernel directory 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. No Output 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
How to improve image quality on DM355?
Hi all! We want to use DM3555 to develop a digital camera, the sensor is MT9P031.Now the system can run properly and we can get 5M pixels picture. But the Image quality is rather bad,I think this is beacause the IPIPE parameter in the processing path is not optimized for MT9P031, and some ipipe blocks(edge enhancement,gamma correction and some others) is disabled entirely.so I want to konw how can we improve the image quality on our DC? Is there some addtional document to help us do this job more quickly? btw:Can you provide some addtional information or links to help us improve imge quality? Any help or tips is appreciated! Thank you! 2009-08-19 windlazio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: da830/omapl137 boot problem caused by clocks
On 15-08-09 22:03, Koen Kooi wrote: Hi, 2kernel BUG at arch/arm/mach-davinci/time.c:375! 1Unable to handle kernel NULL pointer dereference at virtual address 1pgd = c0004000 it's this bit: timer_clk = clk_get(NULL, timer0); I've seen some talk about not using clocknames and all, but I haven't wrapped my head around it yet, so does someone have an idea to quickly work around this? I'm currently using revision 34b63d949e973eb72a833b4d618431869563399d with DEBUG_LL and the printascii hack. ping ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
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 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 help. Regard's Rohan Tabish --- 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 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 Kernel directory 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. No Output 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.
[PATCH] TI DaVinci EMAC: delay DaVinci EMAC initialization
On TI's DA850/OMAP-L138 EVM, MAC address is stored in SPI
flash which is accessed using MTD interface.
This patch delays the initialization of DaVinci EMAC driver
by changing module_init to late_initcall. This helps SPI and
MTD drivers to get initialized before EMAC thereby enabling
EMAC driver to read the MAC address while booting and use it.
Tested with NFS on DM644x, DM6467, DA830/OMAP-L137 and
DA850/OMAP-L138 EVMs.
Signed-off-by: Sudhakar Rajashekhara sudhakar@ti.com
Reviewed-by: Chaithrika U S chaithr...@ti.com
---
drivers/net/davinci_emac.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/davinci_emac.c b/drivers/net/davinci_emac.c
index 12fd446..5e6652b 100644
--- a/drivers/net/davinci_emac.c
+++ b/drivers/net/davinci_emac.c
@@ -2817,7 +2817,7 @@ static int __init davinci_emac_init(void)
{
return platform_driver_register(davinci_emac_driver);
}
-module_init(davinci_emac_init);
+late_initcall(davinci_emac_init);
/**
* davinci_emac_exit: EMAC driver module exit
--
1.5.6
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: da830/omapl137 boot problem caused by clocks
On Wed, 2009-08-19 at 11:43 +0200, Koen Kooi wrote: On 15-08-09 22:03, Koen Kooi wrote: Hi, 2kernel BUG at arch/arm/mach-davinci/time.c:375! 1Unable to handle kernel NULL pointer dereference at virtual address 1pgd = c0004000 it's this bit: timer_clk = clk_get(NULL, timer0); I've seen some talk about not using clocknames and all, but I haven't wrapped my head around it yet, so does someone have an idea to quickly work around this? I'm currently using revision 34b63d949e973eb72a833b4d618431869563399d with DEBUG_LL and the printascii hack. ping The latest (as of 8/18/09) git kernel (using da830_omapl137_defconfig) boots for me on my DA830 EVM. The line numbers in time.c of my kernel matches yours. I'm not sure what is the difference that caused clk_get to return NULL. Regards, Steve ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: uImage not booting kernel
rohan tabish wrote: hi everyone i am trying to embedded linux in DM6446. i am using open source code to build the kernel, using cross compiler. when i load the kernel using tftp and run it the kernel gets halted.can anyone help me.here is whaT I AM GETTING. i have not loaded the file system for the kernel. What do you mean by this? You didn't install a file system yet? You should have a file system on /dev/hda1 (according to you params) You also need the following nodes: /dev/tty /dev/ttyX (depending on your config) /dev/console And you need a link to the program you want to boot. /init or /linuxrc (depending on your config) Starting kernel ... Uncompressing Linux. ... done, booting the kernel. My guess: you're kernel is booting fine, but you're missing the required nodes on your file system. :) Theo PS. Sorry about the disclaimer, it's out of my control. DISCLAIMER: Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: da830/omapl137 boot problem caused by clocks
On 19-08-09 13:48, Steve Chen wrote: On Wed, 2009-08-19 at 11:43 +0200, Koen Kooi wrote: On 15-08-09 22:03, Koen Kooi wrote: Hi, 2kernel BUG at arch/arm/mach-davinci/time.c:375! 1Unable to handle kernel NULL pointer dereference at virtual address 1pgd = c0004000 it's this bit: timer_clk = clk_get(NULL, timer0); I've seen some talk about not using clocknames and all, but I haven't wrapped my head around it yet, so does someone have an idea to quickly work around this? I'm currently using revision 34b63d949e973eb72a833b4d618431869563399d with DEBUG_LL and the printascii hack. ping The latest (as of 8/18/09) git kernel (using da830_omapl137_defconfig) boots for me on my DA830 EVM. The line numbers in time.c of my kernel matches yours. I'm not sure what is the difference that caused clk_get to return NULL. That defconfig spirals into an endless kernel-fault loop. Let's see if turning of unwind support helps. If it does, it means someone broke vanilla gcc and people would be forced to use those harry potter toolchains :( regards, Koen ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: How to improve image quality on DM355?
Hi, Which LSP release are you using? Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 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 windlazio Sent: Wednesday, August 19, 2009 4:14 AM To: davinci-linux-open-source Subject: How to improve image quality on DM355? Hi all! We want to use DM3555 to develop a digital camera, the sensor is MT9P031.Now the system can run properly and we can get 5M pixels picture. But the Image quality is rather bad,I think this is beacause the IPIPE parameter in the processing path is not optimized for MT9P031, and some ipipe blocks(edge enhancement,gamma correction and some others) is disabled entirely.so I want to konw how can we improve the image quality on our DC? Is there some addtional document to help us do this job more quickly? btw:Can you provide some addtional information or links to help us improve imge quality? Any help or tips is appreciated! Thank you! 2009-08-19 windlazio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
Mauro, Kevin has approved the architecture part of this patch. When can I expect these to be merged to linux-next? Thanks. Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 email: m-kariche...@ti.com -Original Message- From: Karicheri, Muralidharan Sent: Tuesday, August 18, 2009 5:51 PM To: 'Mauro Carvalho Chehab' Cc: Mauro Carvalho Chehab; linux-me...@vger.kernel.org; davinci-linux-open- sou...@linux.davincidsp.com; khil...@deeprootsystems.com; Hans Verkuil Subject: RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver Mauro, Here are the patches from Chaithrika that I am referring to. http://www.mail-archive.com/linux-me...@vger.kernel.org/msg08254.html http://www.mail-archive.com/linux-me...@vger.kernel.org/msg07676.html Let me know once they are merged... Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 new phone: 301-407-9583 Old Phone : 301-515-3736 (will be deprecated) email: m-kariche...@ti.com -Original Message- From: Mauro Carvalho Chehab [mailto:mche...@infradead.org] Sent: Tuesday, August 18, 2009 1:28 PM To: Karicheri, Muralidharan Cc: Mauro Carvalho Chehab; linux-me...@vger.kernel.org; davinci-linux- open- sou...@linux.davincidsp.com; khil...@deeprootsystems.com; Hans Verkuil Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver Em Tue, 18 Aug 2009 11:06:54 -0500 Karicheri, Muralidharan m-kariche...@ti.com escreveu: Mauro, I need to send a set of patches for adding vpif capture driver. Currently the linux-next doesn't have the last patch from Chaithrika applied for vpif display. Is it possible to apply this asap so that I can create the vpif capture patch today? Sure. Could you please point me what's the patchwork ID(s)[1] of the patch you need me to apply at our development tree and at linux-next? [1] http://patchwork.kernel.org/project/linux-media/list/ Cheers, Mauro ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
TI JPEGENC 2.00.00.2 unable to call IMGENC1_create
Dear group, I'm still searching why the TI JPEG encoder fails in IMGENC1_create. The general problem is: Calling // setup imgenc_params.size = sizeof(IIMGENC1_Params); imgenc_params.maxHeight = 480; imgenc_params.maxWidth = 720; imgenc_params.maxScans = 3; imgenc_params.dataEndianness = XDM_BYTE; imgenc_params.forceChromaFormat = XDM_YUV_422ILE; // call iencHandle = IMGENC1_create(codecengine, encoderName, imgenc_params ); always fails (returns NULL), if I use iencHandle = IMGENC1_create(codecengine, encoderName, NULL ); a non null ptr is returned but I can't do any IMGENC1_control/process calls (all fail). I have attached a trace log of a sample run (CE_DEBUG=2, DSKT2 trace enabled)). So some basic questions/comments: 1. Has anyone ever managed to successfully integrate the JPEGENC 2.00.00.2 encoder on an DM6446 (DVEVM)board using DVSDK 1.30 into a CE application? 2. I've also tried the DVSDK 2.00 but it still fails to create the encoder instance. 3. Is there a way to get some more trace/debugging information out of the encoder (algorithm) instance? My current trace mask is: export CE_TRACE=*=01234567 export TRACEUTIL_DSP0TRACEMASK=*+01;*=01234567 There is no output from the encoder itself. The last trace message is from DSKT2_createAlg3: [DSP] @2,402,771tk: [+7 T:0x8fa0348c] ti.sdo.fc.dskt2 - DSKT2_createAlg3 algInit call failed -1 4. I have compiled the JPEG encode example with CCS and tested it as a DSP only app. Everything works as expected. So the encoder library seems to be healthy 5. I have double checked the dsplink memory segments with the TCF memory segments and they do match. 6. If I use the (very simple) imgenc1_copy encoder (replace the algorithm in the server cfg file) everything is working. 7. A self built video_copy server/app runs w/o problems, so the build environment seems to be healthy. Any hint/comment is appreciated. Regards Frank App- Application started. Calling CERuntime_init @0,479,428us: [+4 T:0x400176e8] OG - Global_init This program was built with the following packages: @0,480,110us: [+4 T:0x400176e8] OG - package gnu.targets.rts470MV (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/xdc_3_00_02/packages/gnu/targets/rts470MV/) [1,0,0,0,1193542866293] @0,480,296us: [+4 T:0x400176e8] OG - package ti.sdo.codecs.jpegenc (/ns0/Davinci/DVSDK_v1.30.01/workdir/dvsdk_examples/codec_engine_examples/ti/sdo/codecs/jpegenc/) [1,0,0,1228489791665] @0,480,441us: [+4 T:0x400176e8] OG - package ti.xdais.dm (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/xdais_6_00_01/packages/ti/xdais/dm/) [1,0,4,0] @0,480,570us: [+4 T:0x400176e8] OG - package ti.xdais (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/xdais_6_00_01/packages/ti/xdais/) [1,2,1,0] @0,480,696us: [+4 T:0x400176e8] OG - package ti.sdo.utils.trace (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/framework_components_2_00_01/packages/ti/sdo/utils/trace/) [1,0,0,0] @0,480,825us: [+4 T:0x400176e8] OG - package ti.sdo.ce.utils.xdm (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/codec_engine_2_00_01/packages/ti/sdo/ce/utils/xdm/) [1,0,1,1200333457442] @0,480,948us: [+4 T:0x400176e8] OG - package dsplink.gpp (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/dsplink_140-05p1/packages/dsplink/gpp/) [1,1,0,0,1249926646000] @0,481,068us: [+4 T:0x400176e8] OG - package ti.sdo.linuxutils.cmem (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/cmem_2_00_01/packages/ti/sdo/linuxutils/cmem/) [2,0,0,0] @0,481,197us: [+4 T:0x400176e8] OG - package ti.sdo.fc.acpy3 (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/framework_components_2_00_01/packages/ti/sdo/fc/acpy3/) [1,0,2,0] @0,481,322us: [+4 T:0x400176e8] OG - package ti.sdo.fc.dman3 (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/framework_components_2_00_01/packages/ti/sdo/fc/dman3/) [1,0,3,0] @0,481,442us: [+4 T:0x400176e8] OG - package ti.sdo.ce.osal (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/codec_engine_2_00_01/packages/ti/sdo/ce/osal/) [2,0,1,120029943] @0,481,567us: [+4 T:0x400176e8] OG - package ti.sdo.ce.alg (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/codec_engine_2_00_01/packages/ti/sdo/ce/alg/) [1,0,0,1200332939285] @0,481,692us: [+4 T:0x400176e8] OG - package ti.catalog.c470 (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/xdc_3_00_02/packages/ti/catalog/c470/) [1,0,1,0,1192229332845] @0,481,811us: [+4 T:0x400176e8] OG - package ti.catalog.c6000 (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/xdc_3_00_02/packages/ti/catalog/c6000/) [1,0,0,0,1192229349164] @0,481,933us: [+4 T:0x400176e8] OG - package ti.platforms.evmDM6446 (/ns0/Davinci/DVSDK_v1.30.01/dvsdk_1_30_01_41/bios_5_31_08/packages/ti/platforms/evmDM6446/) [1,0,0,0] @0,482,054us: [+4 T:0x400176e8] OG - package
Re: uImage not booting kernel
Oops! I guess my answer won't fix your current issue. :-/ Anyway, what toolchain are you using? And what's the size of your kernel? Theo Theo Debrouwere wrote: rohan tabish wrote: hi everyone i am trying to embedded linux in DM6446. i am using open source code to build the kernel, using cross compiler. when i load the kernel using tftp and run it the kernel gets halted.can anyone help me.here is whaT I AM GETTING. i have not loaded the file system for the kernel. What do you mean by this? You didn't install a file system yet? You should have a file system on /dev/hda1 (according to you params) You also need the following nodes: /dev/tty /dev/ttyX (depending on your config) /dev/console And you need a link to the program you want to boot. /init or /linuxrc (depending on your config) DISCLAIMER: Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: TI JPEGENC 2.00.00.2 unable to call IMGENC1_create
FWIW, I dug into the trace logs a little from a framework POV and nothing jumped out at me. The framework is providing the memory which the codec is asking for, but ultimately, as you point out in #3, the codec is just returning error when the framework says hey, codec, time to create yourself... and here's the memory you asked for. Typically this happens b/c the specific create params aren't supported(?). Regarding #4, that's a great data point - does the codec example app use the same create params you're using? If not, can you change the create params to what you want and successfully create the codec? Chris From: davinci-linux-open-source-bounces+cring=ti@linux.davincidsp.com [mailto:davinci-linux-open-source-bounces+cring=ti@linux.davincidsp.com] On Behalf Of Frank Bhattacharyya Sent: Wednesday, August 19, 2009 8:32 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: TI JPEGENC 2.00.00.2 unable to call IMGENC1_create Dear group, I'm still searching why the TI JPEG encoder fails in IMGENC1_create. The general problem is: Calling // setup imgenc_params.size = sizeof(IIMGENC1_Params); imgenc_params.maxHeight = 480; imgenc_params.maxWidth = 720; imgenc_params.maxScans = 3; imgenc_params.dataEndianness = XDM_BYTE; imgenc_params.forceChromaFormat = XDM_YUV_422ILE; // call iencHandle = IMGENC1_create(codecengine, encoderName, imgenc_params ); always fails (returns NULL), if I use iencHandle = IMGENC1_create(codecengine, encoderName, NULL ); a non null ptr is returned but I can't do any IMGENC1_control/process calls (all fail). I have attached a trace log of a sample run (CE_DEBUG=2, DSKT2 trace enabled)). So some basic questions/comments: 1. Has anyone ever managed to successfully integrate the JPEGENC 2.00.00.2 encoder on an DM6446 (DVEVM)board using DVSDK 1.30 into a CE application? 2. I've also tried the DVSDK 2.00 but it still fails to create the encoder instance. 3. Is there a way to get some more trace/debugging information out of the encoder (algorithm) instance? My current trace mask is: export CE_TRACE=*=01234567 export TRACEUTIL_DSP0TRACEMASK=*+01;*=01234567 There is no output from the encoder itself. The last trace message is from DSKT2_createAlg3: [DSP] @2,402,771tk: [+7 T:0x8fa0348c] ti.sdo.fc.dskt2 - DSKT2_createAlg3 algInit call failed -1 4. I have compiled the JPEG encode example with CCS and tested it as a DSP only app. Everything works as expected. So the encoder library seems to be healthy 5. I have double checked the dsplink memory segments with the TCF memory segments and they do match. 6. If I use the (very simple) imgenc1_copy encoder (replace the algorithm in the server cfg file) everything is working. 7. A self built video_copy server/app runs w/o problems, so the build environment seems to be healthy. Any hint/comment is appreciated. Regards Frank ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: unsubscribe
Can I unsubscribe the mail list of davinci-linux-open-source thanks ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
what these Register for?
Hi all, I want to use the edge enhancement in DM355, but i don't know what these register for,such as: Edge Enhancer Enable Register (YEE_EN), MedianNR Enable Register (YEE_EMF), HPF Shift Length Register (YEE_SHF), HPF Coefficient 00 Register (YEE_MUL_00，01，02，10，11，12，20，21，22),I see the illustration in TMS320DM35x Digital Media System-on-Chip (DMSoC)Video Processing Front End (VPFE), but it is simple, can anyone know these register and tell me, thank you! Zhou sheng ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH 3/5 - v3] DaVinci: platform changes to support vpfe camera capture
On Monday 17 August 2009, m-kariche...@ti.com wrote:
static struct i2c_board_info dm355evm_i2c_info[] = {
{ I2C_BOARD_INFO(dm355evm_msp, 0x25),
.platform_data = dm355evm_mmcsd_gpios,
},
+ {
+ I2C_BOARD_INFO(PCA9543A, 0x73),
+ },
/* { plus irq }, */
/* { I2C_BOARD_INFO(tlv320aic3x, 0x1b), }, */
};
The DM355 EVM board has no PCA9543A I2C multiplexor
chip, so this is not a good approach to use. (*)
If I understand correctly you are configuring some
particular add-on board, which uses a chip like that.
There are at least two such boards today, yes? And
potentially more. Don't preclude (or complicate)
use of different boards...
The scalable approach is to have a file for each
daughtercard, and Kconfig options to enable the
support for those cards. The EVM board init code
might call a dm355evm_card_init() routine, and
provide a weak binding for it which would be
overridden by the
- Dave
(*) Separate issue: there's ongoing work to get the
I2C stack to support such chips in generic ways;
you should plan to use that work, which ISTR wasn't
too far from being mergeable.
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: RE: How to improve image quality on DM355?
My SDK version is dvsdk_1_30_00_40,Thank you for your kindly reply! 2009-08-20 windlazio 发件人： Karicheri, Muralidharan 发送时间： 2009-08-19 23:29:19 收件人： windlazio; davinci-linux-open-source 抄送： 主题： RE: How to improve image quality on DM355? Hi, Which LSP release are you using? Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 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 windlazio Sent: Wednesday, August 19, 2009 4:14 AM To: davinci-linux-open-source Subject: How to improve image quality on DM355? Hi all! We want to use DM3555 to develop a digital camera, the sensor is MT9P031.Now the system can run properly and we can get 5M pixels picture. But the Image quality is rather bad,I think this is beacause the IPIPE parameter in the processing path is not optimized for MT9P031, and some ipipe blocks(edge enhancement,gamma correction and some others) is disabled entirely.so I want to konw how can we improve the image quality on our DC? Is there some addtional document to help us do this job more quickly? btw:Can you provide some addtional information or links to help us improve imge quality? Any help or tips is appreciated! Thank you! 2009-08-19 windlazio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
toolchain
Hi,I want to build git kernel 2.6.31-rc4,which version of the toolchain should I use？ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
