Can you turn on ARM-side trace and send the log? Namely, set the environment var "CE_TRACE" to "*=01234567" and re-run your app.
And in closing - and controversial - Memory_getPhysicalAddress() is not a supported Codec Engine API. :( Yeah, I know the DVSDK examples use them - and that's unfortunate - they shouldn't be. Instead, they (and others) should use the more powerful, and supported, Memory_getBufferPhysicalAddress(): https://www-a.ti.com/downloads/sds_support/targetcontent/CE/ce_1_10/code c_engine_1_10/docs/html/group__ti__sdo__ce__osal___memory.html#gd9e62f37 f2106a1cc46febe3385c5049 Memory_getPhysicalAddress() will be removed in a future Codec Engine release. Chris > -----Original Message----- > From: > [EMAIL PROTECTED] p.com [mailto:davinci-linux-open-source-> [EMAIL PROTECTED] On Behalf Of Cochrane, Euan > Sent: Wednesday, October 31, 2007 7:20 AM > To: '[email protected]' > Subject: Memory_getPhysicalAddress segmentation fault > > Hi, > I am getting a 'segmentation fault' when using > 'Memory_getPhysicalAddress' to get the physical address of > the display buffers to be used by the resizer. I have copied > the 'initDisplayDevice()' function from the TI demos as I > have done before in another app but for some reason this time > it is having a problem with this function. Does anyone know > what could be causing this? There were no errors or > associated warnings when compiling the code so I have no idea > what it could be. > Thanks, > Euan > _______________________________________________ > Davinci-linux-open-source mailing list > [email protected] > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
