• State
  • Locked Locked
  • Replies 0 replies
  • Subscribers 97 subscribers
  • Views 239 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IVA2 Register Differences between the OMAP3530 and DM3730?

Akshay Panday
Expert 1640 points
Other Parts Discussed in Thread: DM3730

Hi,

I am working on getting a h264 encoder with a variety of OMAP Devices - 3530 (Beagle Board), 3630 (Zoom) and 3730 (Beagle Board - XM).

As it works presently, I have CCS hooked up to a Beagle Board and Android running on the Zoom and Beagle-XM. The codec library built in CCS has a socket node wrapper around it and is pushed into the Android filesystem.

 

The codec library which I was using on the Beagle Board refused to run on the Zoom and crashed with the following error:

 ***** DSPMMU FAULT ***** IRQStatus 0x2
***** DSPMMU FAULT ***** faultAddr 0x48306040
WMD_DEH_Notify: ********** DEVICE EXCEPTION **********
WMD_DEH_Notify: DSP_MMUFAULT,errInfo = 0x0
WMD_DEH_Notify: DSP_MMUFAULT, High Address = 0x4830
WMD_DEH_Notify: DSP_MMUFAULT, Low Address = 0x6040
WMD_DEH_Notify: DSP_MMUFAULT, fault address = 0x48306040

Tracing the fault led me to an IVA2 reset function which had the 'RM_RSTCTRL_IVA2' register set to 0x48306050 which had a switch for 3530 or 3430 operation. So, changing this address to 0x1181e050 made it work on the Zoom.

Now I am trying to get the same thing to work on the Beagle - XM, and using the library built for the Beagle, I get the same error as above. The DM3730 seems to share the 3530's architecture as far as this is concerned. 

Could there be anything that I have missed here? Will not a library meant for the Beagle work as-is on the Beagle -XM?

 

Thanks,

 

Akshay