RE: Problems mounting the DM644 DVEVM hda1 partition
-Original Message- From: Kevin Hilman [mailto:khil...@deeprootsystems.com] Sent: Thursday, April 30, 2009 8:41 PM To: David Brownell Cc: davinci-linux-open-source@linux.davincidsp.com; Young, Joseph Subject: Re: Problems mounting the DM644 DVEVM hda1 partition David Brownell davi...@pacbell.net writes: On Thursday 30 April 2009, Kevin Hilman wrote: As one can see by the logs below, linux sees the IDE device (ide0), but not the partitions, and will not let me connect to them. Has anyone had this problem, or knows what I am doing wrong? I have seen this problem as well, but have not tracked it down. Is the relevant pcf GPIO expander driver included? Um.., er.., well, as a module which wasn't loaded :/ Indeed after loading pcf857x the disk itself is detected: Hey, it worked for me as well! Thank you very much! Joe ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Compiling EDMA, ASP, and I2C as modules
How to compile the above drivers as modules. I am using MVL 2.6.10. Can any one where are the options to do so ini menuconfig? -- Amr. _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Compiling EDMA, ASP, and I2C as modules
Well, I am trying to do this because I have a problem in playing back audio. Playback stalls and does not work again unless I restart my board. I found a document describing the driver heirarchy. I am trying to load and unload each module involved with sound playback. I am done with soundcore, davinci_audio, davinci_audio_aic33, davinci_audio_dma_intfc, tlvaic33. Remaining ones are the ASP, EDMA, and I2C itself. -- BR, Amr Ali. Date: Mon, 4 May 2009 12:24:19 +0200 From: opindr...@softhard.sk To: amra...@hotmail.com CC: davinci-linux-open-source@linux.davincidsp.com Subject: Re: Compiling EDMA, ASP, and I2C as modules Hi I2c is in Device drivers - I2C support - ASP is in Device drivers - Sound - ... You should examine what can you check as module and would work About EDMA i suppose that it should be part of kernel and each driver is using library with EDMA functions. For example Davinci_VPFE. Ondrej Pindroch SoftHard Technology ltd. -Original Message- From: amr ali amra...@hotmail.com To: davinci forum davinci-linux-open-source@linux.davincidsp.com Date: Mon, 4 May 2009 13:05:55 +0300 Subject: Compiling EDMA, ASP, and I2C as modules How to compile the above drivers as modules. I am using MVL 2.6.10. Can any one where are the options to do so ini menuconfig? -- Amr. Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
about audio driver stalls.
All, I found there was a serious stalls bug from DAVINCI OSS/ALSA audio driver EDMA driver. I have asked many times but I have no gotten any news from forum as well as TI support team. Any help is appreciated. BR, Jeff ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: about audio driver stalls.
On Mon, 2009-05-04 at 18:34 +0800, Jeff wrote: All, I found there was a serious stalls bug from DAVINCI OSS/ALSA audio driver EDMA driver. I have asked many times but I have no gotten any news from forum as well as TI support team. Any help is appreciated. Don't know much about DaVinci OSS, but I tested DaVinci ALSA (dm6446/6467/355 and da830) quite extensively and I have not noticed any kernel issues. The only issues I noticed is periodic frame/audio pulse using GStreamer with MV 2.6.18 kernel. The problem was traced back to the application. I used aplay/record, wavplay/rec, sox, and TI's decode (which plays audio and video). All seems to work for me. Regards, Steve BR, Jeff ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Compiling EDMA, ASP, and I2C as modules
On Mon, 2009-05-04 at 13:58 +0300, amr ali wrote: Hi Steve, I guess you are right about EDMA and I2C. But where is the source code of the EDMA in the kernel source tree? I found the I2C. Regarding ASP, how can I compile EDMA is in arch/arm/mach-davinci/dma.c 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: Compiling EDMA, ASP, and I2C as modules
Hi Steve, I guess you are right about EDMA and I2C. But where is the source code of the EDMA in the kernel source tree? I found the I2C. Regarding ASP, how can I compile it as a module?? -- Amr Ali. Subject: RE: Compiling EDMA, ASP, and I2C as modules From: sc...@mvista.com To: amra...@hotmail.com CC: opindr...@softhard.sk; davinci-linux-open-source@linux.davincidsp.com Date: Mon, 4 May 2009 05:55:33 -0500 On Mon, 2009-05-04 at 13:29 +0300, amr ali wrote: Well, I am trying to do this because I have a problem in playing back audio. Playback stalls and does not work again unless I restart my board. I found a document describing the driver heirarchy. I am trying to load and unload each module involved with sound playback. I am done with soundcore, davinci_audio, davinci_audio_aic33, davinci_audio_dma_intfc, tlvaic33. Remaining ones are the ASP, EDMA, and I2C itself. You probably don't want to build i2c and EDMA as modules since these are used by quite a number of other drivers. Your kernel may not boot when you have either one as modules. Regards, Steve -- BR, Amr Ali. __ Date: Mon, 4 May 2009 12:24:19 +0200 From: opindr...@softhard.sk To: amra...@hotmail.com CC: davinci-linux-open-source@linux.davincidsp.com Subject: Re: Compiling EDMA, ASP, and I2C as modules Hi I2c is in Device drivers - I2C support - ASP is in Device drivers - Sound - ... You should examine what can you check as module and would work About EDMA i suppose that it should be part of kernel and each driver is using library with EDMA functions. For example Davinci_VPFE. Ondrej Pindroch SoftHard Technology ltd. -Original Message- From: amr ali amra...@hotmail.com To: davinci forum davinci-linux-open-source@linux.davincidsp.com Date: Mon, 4 May 2009 13:05:55 +0300 Subject: Compiling EDMA, ASP, and I2C as modules How to compile the above drivers as modules. I am using MVL 2.6.10. Can any one where are the options to do so ini menuconfig? -- Amr. __ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! __ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source _ Windows Live™: Keep your life in sync. Check it out! http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_012009___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: about audio driver stalls.
On Mon, 2009-05-04 at 06:01 -0500, Steve Chen wrote: On Mon, 2009-05-04 at 18:34 +0800, Jeff wrote: All, I found there was a serious stalls bug from DAVINCI OSS/ALSA audio driver EDMA driver. I have asked many times but I have no gotten any news from forum as well as TI support team. Any help is appreciated. Don't know much about DaVinci OSS, but I tested DaVinci ALSA (dm6446/6467/355 and da830) quite extensively and I have not noticed any kernel issues. The only issues I noticed is periodic frame/audio pulse using GStreamer with MV 2.6.18 kernel. The problem was traced back to the application. I used aplay/record, wavplay/rec, sox, and TI's decode (which plays audio and video). All seems to work for me. Actually, I need to correct myself. GStreamer and TI's decode demo has some performance issuess on the dm355 EVM. Regards, Steve BR, Jeff ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Compiling EDMA, ASP, and I2C as modules
Hi I2c is in Device drivers - I2C support - ASP is in Device drivers - Sound - ... You should examine what can you check as module and would work About EDMA i suppose that it should be part of kernel and each driver is using library with EDMA functions. For example Davinci_VPFE. Ondrej Pindroch SoftHard Technology ltd. -Original Message- From: amr ali amra...@hotmail.com To: davinci forum davinci-linux-open-source@linux.davincidsp.com Date: Mon, 4 May 2009 13:05:55 +0300 Subject: Compiling EDMA, ASP, and I2C as modules How to compile the above drivers as modules. I am using MVL 2.6.10. Can any one where are the options to do so ini menuconfig? -- Amr. Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! [http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us] ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Codec engine hangs when during TraceUtil_start function
Hi,
I am developing an application based on the codec_engine. For the
same I want to see the DSP side traces for the various codecs used. So
I have added TraceUtil_start(EngineName) function after Engine_open
api.
But the application hangs because of TraceUtil_start.
Following are the logs:
# ./vs_appd -f ../test_vectors/ws_uyvy.yuv
# TraceUtil Warning: Failed to open local log file
trace/cearmlog.txt, using stdout
TraceUtil Warning: Failed to open dsp CE log file
trace/cedsp0log.txt, using stdout
TraceUtil Warning: Failed to open dsp/bios log file
trace/bioslog.dat, disabling log
@0x0002c12e:[T:0x4002] OP - daemon thread created.
@0x000447be:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x40556000)
@0x000448ee:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x40556000, size=1)
@0x000449e4:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x00044aad:[T:0x8003] OM - Memory_getPhysicalAddress return (0x8280)
@0x0004ae67:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x40655000)
@0x0004af56:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x40655000, size=1)
@0x0004b01c:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x0004b0db:[T:0x8003] OM - Memory_getPhysicalAddress return (0x828ff000)
@0x000514b1:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x40754000)
@0x0005159c:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x40754000, size=1)
@0x00051662:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x0005173e:[T:0x8003] OM - Memory_getPhysicalAddress return (0x829fe000)
7792:junk2009
NT:No passwd file available, taking factory passwd
REQCFG
REQCFG
7792:junk2009
NT:No passwd file available, taking factory passwd
SETCFG
SETCFG
Rszcopy Debug: Configuring resizer job to copy image of resolution 320x240
@0x00595d34:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x408ed000)
@0x00595e64:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x408ed000, size=1)
@0x00595f56:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x00596023:[T:0x8003] OM - Memory_getPhysicalAddress return (0x8280)
@0x0059c413:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x409ec000)
@0x0059c4fd:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x409ec000, size=1)
@0x0059c5bd:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x0059c677:[T:0x8003] OM - Memory_getPhysicalAddress return (0x828ff000)
@0x005a2a2a:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x40aeb000)
@0x005a2b14:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x40aeb000, size=1)
@0x005a2bd7:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x005a2caa:[T:0x8003] OM - Memory_getPhysicalAddress return (0x829fe000)
@0x005a4d85:[T:0x00010005] CE - Engine_open('scale', 0x0, 0xbe1ffa3c)
@0x005a4eb6:[T:0x00010005] CE - rserverOpen('./all.x64P'), count = 0
@0x005a4f7f:[T:0x00010005] OP - Process_create
Enter(imageName='./all.x64P', attrs=0xbe1ffa40)
Project Name : INCCM and Version : inccm 0.1
@0x005f5364:[T:0x4002] OP - Process_create_d Enter(proc=0x4fb38)
@0x005f54ef:[T:0x4002] OP - Process_create_d Initializing DSP PROC...
@0x005f5a52:[T:0x4002] OP - Process_create_d Attaching to DSP PROC...
@0x005f759c:[T:0x4002] OP - Process_create_d Opening MSGQ pool...
@0x005f7821:[T:0x4002] OP - Process_create_d Loading ./all.x64P
on DSP (2 args)...
@0x00609b1d:[T:0x4002] OP - Process_create_d Starting DSP PROC...
@0x0060aa35:[T:0x4002] OP - Process_create_d Opening remote transport...
@0x0060ac31:[T:0x4002] OP - Process_create_d return (1)
@0x0060ae06:[T:0x00010005] OP - Process_create return (0x4fb38)
@0x0060aee3:[T:0x00010005] CE - rserverOpen('./all.x64P'): 0x45218 done.
@0x0060af9a:[T:0x00010005] OC - Comm_create Enter(queueName='scale',
queue=0x4fa10, attrs=0x0)
@0x0060b171:[T:0x00010005] OC - Comm_create return (0x53178)
@0x0060b25e:[T:0x00010005] OC - Comm_alloc Enter(poolId=0x0,
msg=0x4fa1c, size=576)
@0x0060b379:[T:0x00010005] OC - Comm_alloc msg=0x40c84900, returning (0)
@0x0060b43a:[T:0x00010005] OC - Comm_locate Enter(queueName='rmsq',
queue=0x4fa0c)
@0x0060d1b8:[T:0x00010005] OC - Comm_locate return (0)
@0x0060d2a2:[T:0x00010005] CE - checkServer(0x4fa00)
@0x0060d365:[T:0x00010005] OC - Comm_put Enter(queue=0x0, msg=0x40c84900)
@0x0060d44c:[T:0x00010005] OC - Comm_put return (0)
@0x0060d56a:[T:0x00010005] OC - Comm_get Enter(queue=0x1,
msg=0xbe1ffa38, timeout=-1)
@0x0060d6b2:[T:0x00010005] OC - Comm_get return (0)
If any one has any suggestions for the solution to above problem
please send me the same.
Thanks in advance
--
Bhushan
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
RE: about audio driver stalls.
I have noticed that the problem is while closing files. Is it the same with you? -- Amr. check out the rest of the Windows Live™. More than mail–Windows Live™ goes way beyond your inbox. More than messages _ Windows Live™: Keep your life in sync. Check it out! http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_012009___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Compiling EDMA, ASP, and I2C as modules
On Mon, 2009-05-04 at 13:29 +0300, amr ali wrote: Well, I am trying to do this because I have a problem in playing back audio. Playback stalls and does not work again unless I restart my board. I found a document describing the driver heirarchy. I am trying to load and unload each module involved with sound playback. I am done with soundcore, davinci_audio, davinci_audio_aic33, davinci_audio_dma_intfc, tlvaic33. Remaining ones are the ASP, EDMA, and I2C itself. You probably don't want to build i2c and EDMA as modules since these are used by quite a number of other drivers. Your kernel may not boot when you have either one as modules. Regards, Steve -- BR, Amr Ali. __ Date: Mon, 4 May 2009 12:24:19 +0200 From: opindr...@softhard.sk To: amra...@hotmail.com CC: davinci-linux-open-source@linux.davincidsp.com Subject: Re: Compiling EDMA, ASP, and I2C as modules Hi I2c is in Device drivers - I2C support - ASP is in Device drivers - Sound - ... You should examine what can you check as module and would work About EDMA i suppose that it should be part of kernel and each driver is using library with EDMA functions. For example Davinci_VPFE. Ondrej Pindroch SoftHard Technology ltd. -Original Message- From: amr ali amra...@hotmail.com To: davinci forum davinci-linux-open-source@linux.davincidsp.com Date: Mon, 4 May 2009 13:05:55 +0300 Subject: Compiling EDMA, ASP, and I2C as modules How to compile the above drivers as modules. I am using MVL 2.6.10. Can any one where are the options to do so ini menuconfig? -- Amr. __ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! __ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: about audio driver stalls.
I am facing same problem with OSS driver from MVL. -- Amr. _ More than messages–check out the rest of the Windows Live™. http://www.microsoft.com/windows/windowslive/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: 答复: about audio driver stalls.
Well, I commented closing the audio driver from my application and is working fine now for hours. Hope, It keep working. -- Amr Ali From: jy...@ailips.com To: amra...@hotmail.com CC: davinci-linux-open-source@linux.davincidsp.com Subject: 答复: about audio driver stalls. Date: Mon, 4 May 2009 20:14:38 +0800 It is not only closing file, when I played clips with audio video for 2 hours, it got stuck during playing. Now I am upset by this serious bug too. BR Jeff 发件人: amr ali [mailto:amra...@hotmail.com] 发送时间: 2009年5月4日 19:46 收件人: davinci forum; jy...@ailips.com 主题: RE: about audio driver stalls. I have noticed that the problem is while closing files. Is it the same with you? -- Amr. check out the rest of the Windows Live™. More than mail–Windows Live™ goes way beyond your inbox. More than messages Windows Live™: Keep your life in sync. Check it out! _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Compiling EDMA, ASP, and I2C as modules
Hi, Were there any reports that closing the audio driver stalls playback??? -- Amr Ali. Subject: RE: Compiling EDMA, ASP, and I2C as modules From: sc...@mvista.com To: amra...@hotmail.com CC: opindr...@softhard.sk; davinci-linux-open-source@linux.davincidsp.com Date: Mon, 4 May 2009 06:03:37 -0500 On Mon, 2009-05-04 at 13:58 +0300, amr ali wrote: Hi Steve, I guess you are right about EDMA and I2C. But where is the source code of the EDMA in the kernel source tree? I found the I2C. Regarding ASP, how can I compile EDMA is in arch/arm/mach-davinci/dma.c Regards, Steve _ Show them the way! Add maps and directions to your party invites. http://www.microsoft.com/windows/windowslive/products/events.aspx___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: 答复: about audio driver stalls.
On Mon, 2009-05-04 at 20:17 +0800, Jeff wrote: Did you no see stalls while playing clip with audio video using ALSA on MVL 2.6.18? When I switched to MVL 2.6.18, I found this bug is not fixed. There is a priority inversion issue with pre-releases version of GStreamer/DSPLink TI gave me. Once I worked around the issue, GStreamer worked fine on DM6446 EVM. On DM355, GStreamer never worked very well for me. For one thing, I play video/audio from NFS. The dm9000 on the DM355 EVM has really bad Ethernet performance (something like 25-28 Mbps with netperf). Not to mention the driver is copying Ethernet data with CPU in the ISR which does not help interrupt latency. Did you change the source code of MVL 2.6.18? I suspected that it was caused by EDMA setting. But I am not sure it. There has been some EDMA updates from MVL 2.6.10 to MVL 2.6.18. Audio driver is of course completely redone. However, the dm9000 and video drivers are largely unchanged. Regards, Steve BR Jeff -邮件原件- 发件人: Steve Chen [mailto:sc...@mvista.com] 发送时间: 2009年5月4日 19:14 收件人: Jeff 抄送: Davinci-Linux-Source 主题: Re: about audio driver stalls. On Mon, 2009-05-04 at 06:01 -0500, Steve Chen wrote: On Mon, 2009-05-04 at 18:34 +0800, Jeff wrote: All, I found there was a serious stalls bug from DAVINCI OSS/ALSA audio driver EDMA driver. I have asked many times but I have no gotten any news from forum as well as TI support team. Any help is appreciated. Don't know much about DaVinci OSS, but I tested DaVinci ALSA (dm6446/6467/355 and da830) quite extensively and I have not noticed any kernel issues. The only issues I noticed is periodic frame/audio pulse using GStreamer with MV 2.6.18 kernel. The problem was traced back to the application. I used aplay/record, wavplay/rec, sox, and TI's decode (which plays audio and video). All seems to work for me. Actually, I need to correct myself. GStreamer and TI's decode demo has some performance issuess on the dm355 EVM. Regards, Steve BR, Jeff ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
difficulty in VDEC2 interface in dm6467
I used VDEC2 interface for our own decoder. But somehow i am not able to open the VDEC2 interface But the decode demo that comes along with TI works with VDEC2 interface, here with i am sending the debug message which i get when i use the vdec2 interface. Suggest me what is the problem with VDEC2 interface with our decoder implementation Decode demo started. @0,734,311us: [+4 T:0x40018528] OG - Global_init This program was built with the following packages: @0,734,667us: [+4 T:0x40018528] OG - package gnu.targets.rts470MV (/home/Vina/dvsdk_1_40_00_28/xdc_3_00_06/packages/gnu/targets/rts470MV/) [1,0,0,0,1203621000516] @0,734,823us: [+4 T:0x40018528] OG - package ti.xdais.dm(/home/Vina/dvsdk_1_40_00_28/xdais_6_10_01/packages/ti/xdais/dm/) [1,0,4,1210262746529] @0,734,902us: [+4 T:0x40018528] OG - package ti.xdais (/home/Vina/dvsdk_1_40_00_28/xdais_6_10_01/packages/ti/xdais/) [1,2,1,1210262742149] @0,734,971us: [+4 T:0x40018528] OG - package ti.sdo.utils.trace (/home/Vina/dvsdk_1_40_00_28/framework_components_2_10_01/packages/ti/sdo/utils/trace/) [1,0,0,1210378728605] @0,735,041us: [+4 T:0x40018528] OG - package ti.sdo.ce.utils.xdm (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/utils/xdm/) [1,0,1,1210912978675] @0,735,167us: [+4 T:0x40018528] OG - package ti.sdo.fc.dman3 (/home/Vina/dvsdk_1_40_00_28/framework_components_2_10_01/packages/ti/sdo/fc/dman3/) [1,0,3,1210378548029] @0,735,238us: [+4 T:0x40018528] OG - package ti.sdo.fc.acpy3 (/home/Vina/dvsdk_1_40_00_28/framework_components_2_10_01/packages/ti/sdo/fc/acpy3/) [1,0,2,1210378523580] @0,735,308us: [+4 T:0x40018528] OG - package dsplink.gpp (/home/Vina/dvsdk_1_40_00_28/dsplink-davinci-v1.50-prebuilt/packages/dsplink/gpp/) [3,0,0] @0,735,520us: [+4 T:0x40018528] OG - package ti.sdo.linuxutils.cmem (/home/Vina/dvsdk_1_40_00_28/cmem_2_10/packages/ti/sdo/linuxutils/cmem/) [2,0,1,1204929560755] @0,735,598us: [+4 T:0x40018528] OG - package ti.catalog.c470 (/home/Vina/dvsdk_1_40_00_28/xdc_3_00_06/packages/ti/catalog/c470/) [1,0,1,0,1203561761475] @0,735,670us: [+4 T:0x40018528] OG - package ti.catalog.c6000 (/home/Vina/dvsdk_1_40_00_28/xdc_3_00_06/packages/ti/catalog/c6000/) [1,0,0,0,1203561781695] @0,735,738us: [+4 T:0x40018528] OG - package ti.platforms.evmDM6467 (/home/Vina/dvsdk_1_40_00_28/xdc_3_00_06/packages/ti/platforms/evmDM6467/) [1,0,0,0,1203562062227] @0,735,806us: [+4 T:0x40018528] OG - package ti.sdo.ce.osal (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/osal/) [2,0,2,1210912758604] @0,735,874us: [+4 T:0x40018528] OG - package ti.sdo.ce.ipc (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/ipc/) [2,0,1,1210912707081] @0,735,940us: [+4 T:0x40018528] OG - package ti.sdo.ce.osal.linux (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/osal/linux/) [2,0,1,1210912772730] @0,736,008us: [+4 T:0x40018528] OG - package ti.sdo.ce.ipc.dsplink (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/ipc/dsplink/) [2,0,1,1210912721394] @0,736,077us: [+4 T:0x40018528] OG - package ti.sdo.ce.alg (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/alg/) [1,0,1,1210912389491] @0,736,146us: [+4 T:0x40018528] OG - package ti.sdo.ce (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/) [1,0,6,1210912375058] @0,736,212us: [+4 T:0x40018528] OG - package ti.sdo.ce.speech (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/speech/) [1,0,2,1210912797352] @0,736,279us: [+4 T:0x40018528] OG - package ti.sdo.ce.speech1 (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/speech1/) [1,0,1,1210912803800] @0,736,345us: [+4 T:0x40018528] OG - package ti.sdo.ce.audio (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/audio/) [1,0,2,1210912396869] @0,736,412us: [+4 T:0x40018528] OG - package ti.sdo.ce.video (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/video/) [1,0,3,1210912990552] @0,736,477us: [+4 T:0x40018528] OG - package ti.sdo.ce.video1 (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/video1/) [1,0,2,1210912997315] @0,736,543us: [+4 T:0x40018528] OG - package ti.sdo.ce.video2 (/home/Vina/dvsdk_1_40_00_28/codec_engine_2_10_01/packages/ti/sdo/ce/video2/) [1,0,2,1210913003946] @0,736,611us: [+4 T:0x40018528] OG - package ti.sdo.dmai (/home/Vina/dvsdk_1_40_00_28/dmai_1_10_00_05/packages/ti/sdo/dmai/) [1,0,0,1241325687000] @0,737,485us: [+4 T:0x40018528] OG - package ti.sdo.simplewidget (/home/Vina/NVR/multimedia/packages/ti/sdo/simplewidget/) [] @0,737,584us: [+4 T:0x40018528] OG - package nvr_mp4_dec0 (/home/Vina/NVR/multimedia/nvr_mp4_dec0/) [] @0,737,655us: [+4 T:0x40018528] OG - package nvr_mp4_dec1 (/home/Vina/NVR/multimedia/nvr_mp4_dec1/) [] @0,737,722us: [+4 T:0x40018528] OG - package nvr_mp4_dec2
Re: 答复: 答复: about audio driver stalls.
On Mon, 2009-05-04 at 20:49 +0800, Jeff wrote: How to work around the priority inversion issue? Your much help is appreciated. Thanks. Below was my e-mail describing the issue and the work around. Please note that this is only a work around. The freeze problem is caused by priority between the I/O thread and DSPLINK_DPC_2. The DSPLINK_DPC_2 is blocked when the GStreamer I/O thread runs. The audio/video thread (both has higher priority then I/O thread) depends on the DSPLINK_DPC_2. As a result, both audio and video display thread are blocked while I/O thread runs. We can avoid the issue by lowering the I/O thread priority using nice. Replace gstreamer_demo/shared/run_pipe.sh, $CMD with nice -n 15 $CMD Regards, Steve Jeff -邮件原件- 发件人: Steve Chen [mailto:sc...@mvista.com] 发送时间: 2009年5月4日 20:50 收件人: Jeff 抄送: Davinci-Linux-Source 主题: Re: 答复: about audio driver stalls. On Mon, 2009-05-04 at 20:17 +0800, Jeff wrote: Did you no see stalls while playing clip with audio video using ALSA on MVL 2.6.18? When I switched to MVL 2.6.18, I found this bug is not fixed. There is a priority inversion issue with pre-releases version of GStreamer/DSPLink TI gave me. Once I worked around the issue, GStreamer worked fine on DM6446 EVM. On DM355, GStreamer never worked very well for me. For one thing, I play video/audio from NFS. The dm9000 on the DM355 EVM has really bad Ethernet performance (something like 25-28 Mbps with netperf). Not to mention the driver is copying Ethernet data with CPU in the ISR which does not help interrupt latency. Did you change the source code of MVL 2.6.18? I suspected that it was caused by EDMA setting. But I am not sure it. There has been some EDMA updates from MVL 2.6.10 to MVL 2.6.18. Audio driver is of course completely redone. However, the dm9000 and video drivers are largely unchanged. Regards, Steve BR Jeff -邮件原件- 发件人: Steve Chen [mailto:sc...@mvista.com] 发送时间: 2009年5月4日 19:14 收件人: Jeff 抄送: Davinci-Linux-Source 主题: Re: about audio driver stalls. On Mon, 2009-05-04 at 06:01 -0500, Steve Chen wrote: On Mon, 2009-05-04 at 18:34 +0800, Jeff wrote: All, I found there was a serious stalls bug from DAVINCI OSS/ALSA audio driver EDMA driver. I have asked many times but I have no gotten any news from forum as well as TI support team. Any help is appreciated. Don't know much about DaVinci OSS, but I tested DaVinci ALSA (dm6446/6467/355 and da830) quite extensively and I have not noticed any kernel issues. The only issues I noticed is periodic frame/audio pulse using GStreamer with MV 2.6.18 kernel. The problem was traced back to the application. I used aplay/record, wavplay/rec, sox, and TI's decode (which plays audio and video). All seems to work for me. Actually, I need to correct myself. GStreamer and TI's decode demo has some performance issuess on the dm355 EVM. Regards, Steve BR, Jeff ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: about audio driver stalls.
On Monday 04 May 2009, Steve Chen wrote: Actually, I need to correct myself. GStreamer and TI's decode demo has some performance issuess on the dm355 EVM. Ditto basic playback on the GIT kernels. Chip errata say that DMA to/from SRAM is required. The ASoC drivers don't use SRAM yet. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: about audio driver stalls.
On Mon, 2009-05-04 at 07:49 -0700, David Brownell wrote: On Monday 04 May 2009, Steve Chen wrote: Actually, I need to correct myself. GStreamer and TI's decode demo has some performance issuess on the dm355 EVM. Ditto basic playback on the GIT kernels. Chip errata say that DMA to/from SRAM is required. The ASoC drivers don't use SRAM yet. I seem to recall someone posted a patch to use SRAM for audio drivers. That was a few months back. Anyone know what happened to that patch? ___ 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 v2] ARM: DaVinci: Cleaning of DaVinci MMC driver
On Thursday 30 April 2009, Kevin Hilman wrote: Pierre has had some more questions/comments on LKML. Are you planning to address those and re-submit upstream? I'd like to see this driver get re-submitted upstream before pulling into DaVinci git. I see that mainline has now pulled the dm6446 updates, including EDMA ... Which says to me that if these issues get resolved, there might still be time to get the MMC driver into mainline before 2.6.30 finalizes! - Dave ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: about audio driver stalls.
I had changed the original OSS drivers to originate the buffers from TCRAM, but had no luck in terms of a performance improvement. The testing involved heavy video decoding alongside audio playback, and the audio still suffered from drop-outs. A look at the EDMA queue management did show that audio TX was properly placed in the higher priority queue. David, have you had a chance to test the IRAM functionality with Alsa in the git? Also in my experience, the stalls (as I have mentioned in previous emails) came from: == There was a faulty line in the OSS driver which was scheduling a tasklet even if nothing was pending == Not properly clearing the EDMA missed event register == Bug in the shutdown of the rx (which was also shutting off tx) when there were no more dma queue items Most of these you have to pin point using printk statements - there is no other option than to curl up your sleeves and just dive into the audio driver code. I had to for at least a few weeks before I could get some headway into this. Thanks, Jerry Johns Design Engineer Nuvation Research Corp - Canada Tel: (519) 746-2304 ext. 221 www.nuvation.com http://www.nuvation.com ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: about audio driver stalls.
On Monday 04 May 2009, Jerry Johns wrote: David, have you had a chance to test the IRAM functionality with Alsa in the git? No ASoC support for it ... and the iram.c stuff is dm6446-specific anyway. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: about audio driver stalls.
Steve Chen wrote: On Mon, 2009-05-04 at 07:49 -0700, David Brownell wrote: On Monday 04 May 2009, Steve Chen wrote: Actually, I need to correct myself. GStreamer and TI's decode demo has some performance issuess on the dm355 EVM. Ditto basic playback on the GIT kernels. Chip errata say that DMA to/from SRAM is required. The ASoC drivers don't use SRAM yet. I seem to recall someone posted a patch to use SRAM for audio drivers. That was a few months back. Anyone know what happened to that patch? ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source I'll post a new RFC for the git kernel as soon as I integrate David's SRAM allocation changes. Troy ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
[patch 2.6.30-rc2-davinci] gpio irq enable tweaks
From: David Brownell dbrown...@users.sourceforge.net
Fix two IRQ triggering bugs affecting GPIO IRQs:
- Make sure enabling with IRQ_TYPE_NONE (default, unspecified)
isn't a NOP ... default to both edges, at least one must work.
- As noted by Kevin Hilman, setting the irq trigger type for a
banked gpio interrupt shouldn't enable irqs that are disabled.
Since GPIO IRQs haven't been used much yet, it's not clear these
bugs could have affected anything. The few current users don't
seem to have been obviously suffering from these issues.
Signed-off-by: David Brownell dbrown...@users.sourceforge.net
---
Applies also to mainline, with minor offsets. So if I get some
acks, I can submit to the ARM patch queue...
arch/arm/mach-davinci/gpio.c | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
--- a/arch/arm/mach-davinci/gpio.c
+++ b/arch/arm/mach-davinci/gpio.c
@@ -179,10 +179,15 @@ static void gpio_irq_enable(unsigned irq
{
struct gpio_controller *__iomem g = get_irq_chip_data(irq);
u32 mask = __gpio_mask(irq_to_gpio(irq));
+ unsigned status = irq_desc[irq].status;
- if (irq_desc[irq].status IRQ_TYPE_EDGE_FALLING)
+ status = IRQ_TYPE_EDGE_FALLING | IRQ_TYPE_EDGE_RISING;
+ if (!status)
+ status = IRQ_TYPE_EDGE_FALLING | IRQ_TYPE_EDGE_RISING;
+
+ if (status IRQ_TYPE_EDGE_FALLING)
__raw_writel(mask, g-set_falling);
- if (irq_desc[irq].status IRQ_TYPE_EDGE_RISING)
+ if (status IRQ_TYPE_EDGE_RISING)
__raw_writel(mask, g-set_rising);
}
@@ -197,10 +202,13 @@ static int gpio_irq_type(unsigned irq, u
irq_desc[irq].status = ~IRQ_TYPE_SENSE_MASK;
irq_desc[irq].status |= trigger;
- __raw_writel(mask, (trigger IRQ_TYPE_EDGE_FALLING)
-? g-set_falling : g-clr_falling);
- __raw_writel(mask, (trigger IRQ_TYPE_EDGE_RISING)
-? g-set_rising : g-clr_rising);
+ /* don't enable the IRQ if it's currently disabled */
+ if (irq_desc[irq].depth == 0) {
+ __raw_writel(mask, (trigger IRQ_TYPE_EDGE_FALLING)
+? g-set_falling : g-clr_falling);
+ __raw_writel(mask, (trigger IRQ_TYPE_EDGE_RISING)
+? g-set_rising : g-clr_rising);
+ }
return 0;
}
___
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/rfc davinci-git 3/3] add sram allocator
David Brownell wrote: From: David Brownell dbrown...@users.sourceforge.net Provide a generic SRAM allocator using genalloc, and vaguely modeled after what AVR32 uses. This builds on top of the static CPU mapping set up in the previous patch, and returns DMA mappings as requested (if possible). Compared to its OMAP cousin, there's no current support for (currently non-existent) DaVinci power management code running in SRAM; and this has ways to deallocate, instead of being allocate-only. The initial user of this should probably be the audio code, because EDMA from DDR is subject to various dropouts on at least DM355 and DM6446 chips. This works for me after +obj-$(CONFIG_GENERIC_ALLOCATOR)+= sram.o and adding ;'s to sram.h extern void *sram_alloc(size_t len, dma_addr_t *dma); extern void sram_free(void *addr, size_t len); Troy ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
DM6446- NAND_ECC_HW3_512 - Data CRC failed
Hi All, I am getting this error when I use NAND_ECC_HW3_512. Where I can get a patch file?. mtd-read(0x44 bytes from 0x2a8a7b8) returned ECC error mtd-read(0x6a bytes from 0x2a8a7fc) returned ECC error mtd-read(0x44 bytes from 0x2a8a744) returned ECC error mtd-read(0x44 bytes from 0x2a8a868) returned ECC error mtd-read(0x44 bytes from 0x2a8a7b8) returned ECC error mtd-read(0x6a bytes from 0x2a8a7fc) returned ECC error jffs2_get_inode_nodes(): Data CRC failed on node at 0x02a8aa00: Read 0x8dc69d5e, calculated 0xdefd1884 jffs2_do_read_inode(): No data nodes found for ino #1042 Returned error for crccheck of ino #1042. Expect badness... Thanks, John ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Codec engine hangs when during TraceUtil_start function
What are the attributes configured for TraceUtil in the XDC cfg file? By
default, the CE traces will be redirected to /tmp/cearmlog.txt. It looks like
you have set the environment variables CE_TRACEFILE so it gets redirected to
trace/cearmlog.txt. If the directory trace doesn't exist, there would be
errors.
If you don't *need* TraceUtil specifically - if you just want to observe the
DSP side traces for debugging, a better (and easier) option would be to use
CE_DEBUG:
http://tiexpressdsp.com/index.php?title=CE_DEBUG
When using CE_DEBUG, the traces will automatically come to the console. There
is no need to change the ARM application code.
Best Regards,
Anand Balagopalakrishnan
Texas Instruments
India
-Original Message-
From: davinci-linux-open-source-boun...@linux.davincidsp.com
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of
bhushan
Sent: Monday, May 04, 2009 5:07 PM
To: davinci-linux-open-source@linux.davincidsp.com
Subject: Codec engine hangs when during TraceUtil_start function
Hi,
I am developing an application based on the codec_engine. For the
same I want to see the DSP side traces for the various codecs used. So
I have added TraceUtil_start(EngineName) function after Engine_open
api.
But the application hangs because of TraceUtil_start.
Following are the logs:
# ./vs_appd -f ../test_vectors/ws_uyvy.yuv
# TraceUtil Warning: Failed to open local log file
trace/cearmlog.txt, using stdout
TraceUtil Warning: Failed to open dsp CE log file
trace/cedsp0log.txt, using stdout
TraceUtil Warning: Failed to open dsp/bios log file
trace/bioslog.dat, disabling log
@0x0002c12e:[T:0x4002] OP - daemon thread created.
@0x000447be:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x40556000)
@0x000448ee:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x40556000, size=1)
@0x000449e4:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x00044aad:[T:0x8003] OM - Memory_getPhysicalAddress return (0x8280)
@0x0004ae67:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x40655000)
@0x0004af56:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x40655000, size=1)
@0x0004b01c:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x0004b0db:[T:0x8003] OM - Memory_getPhysicalAddress return (0x828ff000)
@0x000514b1:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x40754000)
@0x0005159c:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x40754000, size=1)
@0x00051662:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x0005173e:[T:0x8003] OM - Memory_getPhysicalAddress return (0x829fe000)
7792:junk2009
NT:No passwd file available, taking factory passwd
REQCFG
REQCFG
7792:junk2009
NT:No passwd file available, taking factory passwd
SETCFG
SETCFG
Rszcopy Debug: Configuring resizer job to copy image of resolution 320x240
@0x00595d34:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x408ed000)
@0x00595e64:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x408ed000, size=1)
@0x00595f56:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x00596023:[T:0x8003] OM - Memory_getPhysicalAddress return (0x8280)
@0x0059c413:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x409ec000)
@0x0059c4fd:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x409ec000, size=1)
@0x0059c5bd:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x0059c677:[T:0x8003] OM - Memory_getPhysicalAddress return (0x828ff000)
@0x005a2a2a:[T:0x8003] OM - Memory_getPhysicalAddress
Enter(virtAddr=0x40aeb000)
@0x005a2b14:[T:0x8003] OM - Memory__getPhysicalAddress
Enter(virtAddr=0x40aeb000, size=1)
@0x005a2bd7:[T:0x8003] OM - Memory__getPhysicalAddress returning
physAddr=0x0
@0x005a2caa:[T:0x8003] OM - Memory_getPhysicalAddress return (0x829fe000)
@0x005a4d85:[T:0x00010005] CE - Engine_open('scale', 0x0, 0xbe1ffa3c)
@0x005a4eb6:[T:0x00010005] CE - rserverOpen('./all.x64P'), count = 0
@0x005a4f7f:[T:0x00010005] OP - Process_create
Enter(imageName='./all.x64P', attrs=0xbe1ffa40)
Project Name : INCCM and Version : inccm 0.1
@0x005f5364:[T:0x4002] OP - Process_create_d Enter(proc=0x4fb38)
@0x005f54ef:[T:0x4002] OP - Process_create_d Initializing DSP PROC...
@0x005f5a52:[T:0x4002] OP - Process_create_d Attaching to DSP PROC...
@0x005f759c:[T:0x4002] OP - Process_create_d Opening MSGQ pool...
@0x005f7821:[T:0x4002] OP - Process_create_d Loading ./all.x64P
on DSP (2 args)...
@0x00609b1d:[T:0x4002] OP - Process_create_d Starting DSP PROC...
@0x0060aa35:[T:0x4002] OP - Process_create_d Opening remote transport...
@0x0060ac31:[T:0x4002] OP - Process_create_d return (1)
@0x0060ae06:[T:0x00010005] OP - Process_create return (0x4fb38)
@0x0060aee3:[T:0x00010005] CE - rserverOpen('./all.x64P'): 0x45218 done.
