Running HDVPSS on VPSS-M3 and ex02_messageq example on VIDEO-M3 concurrently

Hello There,

Here is the generated memory map for the two applications:

VPSS-M3 (Color Bar Application)

VIDEO-M3 (ex02_messageq example)

Thanks and Regards,

Vivek

Vivek,

Thanks for writing a detailed post for your question. It gave us some good details to study.

One possible issue is the management of the Ducati dual-core gate. There is a gate used by SYS/BIOS for protecting access to resources shared by both Ducti processors. By default, SYS/BIOS assumes that the VIDEO-M3 (coreId = 0) core will initialize this gate, but this also assumes that the VIDEO-M3 core is loaded and running before the VPSS-M3 (coreId = 1) core. You need to decide which core will initialize this gate, configure both executables accordingly, and then always load and run that core first. Looking at you post, it seems that you are changing your load/start order from run to run. This is not supported.

I suggest that you decide which core will always be loaded/run first, then add the following to the config script of that executable.

var GateDualCore = xdc.useModule('ti.sysbios.family.arm.ducati.GateDualCore');
GateDualCore.initGates = true;

In the config script for the other core, add the same as above but set initGates = false.

I'm curious if you are using slaveloader to load/run both cores or are you using firmwareloader for the vpss core and slaveloader for the video core?

~Ramsey

Ramsey,

Thanks for the reply. I understand that I cannot change the running order run by run. Our use-case is to run VPSS-M3 first and then VIDEO-M3. I added the GateDualCore script you mentioned in the mail above. GateDualCore.initGates = true in the VPSS-M3 CFG file and GateDualCore.initGates = false in the VIDEO-M3 CFG file. But I did not see a change in behavior. This is what I am running now

Sequence1:

1. Load VPSS-M3 image
2. Load VIDEO-M3 image
3. insmod vpss.ko sbufaddr=8e200000: It Hangs here

Sequence2:

1. Load VPSS-M3 image
2. Run Color Bar Application on VPSS-M3. SUCCESS
3. Load VIDEO-M3 image. Color Bar Application Stopped.
4. Run MeesageQ application on VIDEO-M3. Doesn’t work.

Is it possible that DualCore setting is being done from some global place (SYSBIOS?) and changing the local CFG file doesn't have any effect? I am also attaching the CFG files I am using for the VPSS-M3 and VIDEO-M3 applications

VPSS-M3 CFG File:6735.proxyServerHost_ti811x.cfg

VIDEO-M3 CFG File:4555.Video.cfg

Regards,

Vivek

Vivek,

I see conflicting configuration in your two cfg files. The AMMU configuration is not compatible. Remember that there is only one AMMU which is shared by both VPSS and VIDEO processors. Since you load the VPSS first, it will enable the cache and configure the AMMU. When you load the VIDEO core, it will change the AMMU configuration which will crash the VPSS. You have to make sure the two configurations are compatible. For example, the largePages[1] configuration is incompatible.

proxyServerHost_ti811x.cfg

AMMU.largePages[1].logicalAddress = 0x8C000000;

Video.cfg

var entry = AMMU.largePages[1];
entry.logicalAddress = configBld.ammu.prgmBaseAddr; /* 0x80000000, from config.bld */

Furthermore, only the first processor to run (VPSS) should configure L2_BOOT and L2_RAM. I see smallPages[1] being configured in both.

You have the original ex02_messageq example. Compare the Video.cfg and Vpss.cfg files to see the differences.

I would not have the following in both files, keep it in the proxyServerHost_ti811x.cfg file and remove it from the Video.cfg file.

var Cache = xdc.useModule('ti.sysbios.hal.unicache.Cache');
Cache.enableCache = true;

~Ramsey