I am trying to access a CPLD from the HDVPSS M3. The CPLD has been mapped to a 16MB region starting at 0x08000000. After I a Linux startup script on the A8, I can use CCS to attach to the M3, download and run a modified version of the captureVip ezsdk/HDVPSS test program.
Running basically the same same software on the HDVPSS and the same startup script prior to starting OMX/syslink, causes a segmentation fault on the HDVPSS when the M3 attempts access the CPLD.
I am assuming that my problems are related to the DUCATI MMU. Attached is a word document with a dump of the DUCATI MMU region starting at 0x55080800 after OMX/syslink is run. The same region is essentially all 0's when the running just the captureVip test program. The DUCATI MMU region is not well documented and it was not obvious to me where the region is programmed in syslink or in the linux kernel source.
Here is a description of the attached files
DucatiMMU_after_OMXInit.docx - capture of 0x55080800 from the HDVPSS M3 after M3 is started with OMX
DucatiMME_withCaptureVips.docx - capture of 0x55080800 from HDVPSS M3 after running the captureVip software
go - linux startup script used with OMX
go.noOMX - linux startup script run prior to captureVip
initRmc_SlotA_ScIavm_Hdmi_V.txt - a linux script called by go and go.noOmx to initialize the GPIO, GPMC and other DM8168 peripherals prior to starting captureVip or OMX
Neil Walker