Is the OMAP3530evm missing from DVSDK dmai app_common.tci?

msj said:

I noticed there doesn't seem to be any configuration for the omap3530evm in the app_common.tci file included with the dmai module in the DVSDK. (/dvsdk_3_00_01_42/dmai_2_00_01_04/packages/ti/sdo/dmai/apps/app_common.tci)

 

Is this correct?

This is correct and normal, as you have probably noted DMAI still builds without any mention of OMAP in the app_common.tci file.

msj said:

For these demo apps how is the omap3530 dsp getting configured?

I believe it is using createFromServer to determine the memory mappings that would have been found in the tci file.

So for the dvsdk codecs the L1, L2 cache sizes will be set by the values in the server.tcf file:

dvsdk_3_00_01_42/cs1omap3530_1_00_01/packages/ti/sdo/server/cs/server.tcf

and in this case is:

    var device_regs = {
        l1PMode: "32k",
        l1DMode: "16k",
        l2Mode: "64k",
        l1DHeapSize: 0
    };

    var params = {
        clockRate: 360,
        catalogName: "ti.catalog.c6000",
        deviceName: "3530",
        regs: device_regs,
        mem: mem_ext
    };

and the will the clock rate be 360 Mhz when the Codecs are running, or is this set externally by the OPP utilities?

Thanks,

simon

msj said:

will the clock rate be 360 Mhz when the Codecs are running, or is this set externally by the OPP utilities?

The cpufreq driver on the ARM which sets the OPP states will end up controlling the actual DSP frequency, the clock rate shown in the TCF files is for informative purposes within BIOS so that if you have time dependendent objects, like PRD periodic functions, they operate at the appropriate rates. In other words the frequency in BIOS is not what BIOS is setting up the clock to be, but what BIOS expects the clock to be set up as through some other means, in a stand alone DSP this would typically be done through the boot loader, but in a ARM/DSP setup like this it can be controlled by the ARM.