Hi Can, The address that DSP accesses should be mapped to physical address by ARM. I am not sure what you are trying to do, but you can look at the below examples on how the Mapping works.
Reference: 1 ===== MPU side sample: http://gitorious.org/ti-dspbridge/userspace/blobs/master/source/samples/mpu/src/dmmcopy/dmmcopy.c DSP sample: http://gitorious.org/ti-dspbridge/userspace/trees/master/source/samples/dsp Reference: 2 ===== Felipe has good example on his tree. May be this is bit simpler. http://github.com/felipec/dsp-dummy/tree/master Thank you, Best regards, Hari > -----Original Message----- > From: Can Bal [mailto:can...@ee.bilkent.edu.tr] > Sent: Thursday, June 04, 2009 5:15 PM > To: Kanigeri, Hari > Cc: Can Bal; linux-omap@vger.kernel.org > Subject: RE: DSP MMU Fault > > Hi Hari, > > How can I map the address? At what part do I specify these mappings; > bridge installation, at DSP side program (with the tci file etc.)? By the > way just before that in the program I do a malloc(32) to another short > pointer but |it doesn't return any errors? > > Please forgive me if this is a trivial question but I'm just learning the > DSP programming. Thanks a lot. > > Best regards, > Can > > > > Hi Can, > > > >> Do you have any ideas why this might be happening and how to fix it? > >> Thanks a lot. > > > > Most probably you might not have mapped the address 0x230674a0. > > > > > > Thank you, > > Best regards, > > Hari > > > >> -----Original Message----- > >> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > >> ow...@vger.kernel.org] On Behalf Of Can Bal > >> Sent: Thursday, June 04, 2009 6:54 AM > >> To: linux-omap@vger.kernel.org > >> Subject: DSP MMU Fault > >> > >> Hi everyone, > >> > >> I'm implementing a code on DSP but at the time I do a memory allocation > >> at > >> the DSP side as: > >> > >> short *a; > >> a = malloc(192); // (short*)malloc(192) does not work either > >> > >> But at this line I get the following error and DSP fails afterwards. > >> Then > >> I need to reboot until I can run the application again. > >> > >> <6>***** DSPMMU FAULT ***** IRQStatus 0x2 > >> ***** DSPMMU FAULT ***** IRQStatus 0x2 > >> <6>***** DSPMMU FAULT ***** faultAddr 0x230674a0 > >> ***** DSPMMU FAULT ***** faultAddr 0x230674a0 > >> <6>WMD_DEH_Notify: ********** DEVICE EXCEPTION ********** > >> WMD_DEH_Notify: ********** DEVICE EXCEPTION ********** > >> <6>WMD_DEH_Notify: DSP_MMUFAULT,errInfo = 0x0 > >> WMD_DEH_Notify: DSP_MMUFAULT,errInfo = 0x0 > >> <6>WMD_DEH_Notify: DSP_MMUFAULT, High Address = 0x2306 > >> WMD_DEH_Notify: DSP_MMUFAULT, High Address = 0x2306 > >> <6>WMD_DEH_Notify: DSP_MMUFAULT, Low Address = 0x74a0 > >> WMD_DEH_Notify: DSP_MMUFAULT, Low Address = 0x74a0 > >> <6>WMD_DEH_Notify: DSP_MMUFAULT, fault address = 0x230674a0 > >> WMD_DEH_Notify: DSP_MMUFAULT, fault address = 0x230674a0 > >> > >> Do you have any ideas why this might be happening and how to fix it? > >> Thanks a lot. > >> > >> Can > >> > >> -- > >> To unsubscribe from this list: send the line "unsubscribe linux-omap" > in > >> the body of a message to majord...@vger.kernel.org > >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > > the body of a message to majord...@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
