module ti.sysbios.family.arm.a15.smp.Core
index URL

Core Identification Module

C synopsis target-domain sourced in ti/sysbios/family/arm/a15/smp/Core.xdc
#include <ti/sysbios/family/arm/a15/smp/Core.h>
Functions common to all ICore modules
UInt 
Core_getId// return the current core id();
macro UInt 
Core_hwiEnable// Locally enable interrupts();
Void 
Core_interruptCore// Cause an interrupt on a particular core(UInt coreId);
Functions common to all target modules
Core_Module_getMask// Returns the diagnostics mask for this module, Core_Module_hasMask// Test whether this module has a diagnostics mask, Core_Module_heap// The heap from which this module allocates memory, Core_Module_id// Get this module's unique id, Core_Module_setMask// Set the diagnostics mask for this module, Core_Module_startupDone// Test if this module has completed startup
Constants
extern const UInt 
Core_numCores// number of Cores in SMP environment;
extern const String 
Core_resetSection// Section to place the reset function;
extern const Bool 
Core_useSkernelCmd// Use sKernel command to wake-up cores on Keystone2 devices;
 
 
config Core_numCores  // module-wide
index URL

number of Cores in SMP environment

C synopsis target-domain
extern const UInt Core_numCores;
 
 
config Core_resetSection  // module-wide
index URL

Section to place the reset function

C synopsis target-domain
extern const String Core_resetSection;
 
DETAILS
This configuration parameter allows the app to specify a named output section that will contain the SYS/BIOS core reset function. The core reset function is different from _c_int00 and internally calls _c_int00.
If resetSection is null (or undefined) the reset function is placed in the target's default text section.
 
config Core_useSkernelCmd  // module-wide
index URL

Use sKernel command to wake-up cores on Keystone2 devices

C synopsis target-domain
extern const Bool Core_useSkernelCmd;
 
DETAILS
This config param only has an effect when building apps for Keystone2 devices. It is ignored for all other devices like OMAP5xxx, DRA7xx, etc.
If set to true, this config param will cause SYS/BIOS to use sKernel commands to wake-up cores. This param is true by default.
If debugging using CCS, a gel script can be used to wake-up all cores instead of using sKernel commands at runtime. This config param can be disabled in this case.
Note: If debugging using CCS and using a gel script to wake-up all cores, the application needs to be loaded on only one of the cores. Only the app symbols need to be loaded on all other cores.
 
Core_getId()  // module-wide
index URL

return the current core id

C synopsis target-domain
UInt Core_getId();
 
 
Core_hwiEnable()  // module-wide
index URL

Locally enable interrupts

C synopsis target-domain
macro UInt Core_hwiEnable();
 
RETURNS
opaque key for use by Hwi_restore() or Core_hwiRestore()
DETAILS
Core_hwiEnable locally enables hardware interrupts on the current Core and returns an opaque key indicating whether interrupts were enabled or disabled on entry to Core_hwiEnable().
The actual value of the key is target/device specific and is meant to be passed to Hwi_restore() or Core_hwiRestore().
 
Core_interruptCore()  // module-wide
index URL

Cause an interrupt on a particular core

C synopsis target-domain
Void Core_interruptCore(UInt coreId);
 
Module-Wide Built-Ins
index URL

C synopsis target-domain
Types_ModuleId Core_Module_id();
// Get this module's unique id
 
Bool Core_Module_startupDone();
// Test if this module has completed startup
 
IHeap_Handle Core_Module_heap();
// The heap from which this module allocates memory
 
Bool Core_Module_hasMask();
// Test whether this module has a diagnostics mask
 
Bits16 Core_Module_getMask();
// Returns the diagnostics mask for this module
 
Void Core_Module_setMask(Bits16 mask);
// Set the diagnostics mask for this module
 
Configuration settings sourced in ti/sysbios/family/arm/a15/smp/Core.xdc
var Core = xdc.useModule('ti.sysbios.family.arm.a15.smp.Core');
module-wide config parameters
    Core.numCores// number of Cores in SMP environment = UInt undefined;
    Core.resetSection// Section to place the reset function = String null;
    Core.useSkernelCmd// Use sKernel command to wake-up cores on Keystone2 devices = Bool true;
 
    Core.common$// Common module configuration parameters = Types.Common$ undefined;
 
 
config Core.numCores  // module-wide
index URL

number of Cores in SMP environment

Configuration settings
Core.numCores = UInt undefined;
 
C SYNOPSIS
Core_numCores
 
config Core.resetSection  // module-wide
index URL

Section to place the reset function

Configuration settings
Core.resetSection = String null;
 
DETAILS
This configuration parameter allows the app to specify a named output section that will contain the SYS/BIOS core reset function. The core reset function is different from _c_int00 and internally calls _c_int00.
If resetSection is null (or undefined) the reset function is placed in the target's default text section.
C SYNOPSIS
Core_resetSection
 
config Core.useSkernelCmd  // module-wide
index URL

Use sKernel command to wake-up cores on Keystone2 devices

Configuration settings
Core.useSkernelCmd = Bool true;
 
DETAILS
This config param only has an effect when building apps for Keystone2 devices. It is ignored for all other devices like OMAP5xxx, DRA7xx, etc.
If set to true, this config param will cause SYS/BIOS to use sKernel commands to wake-up cores. This param is true by default.
If debugging using CCS, a gel script can be used to wake-up all cores instead of using sKernel commands at runtime. This config param can be disabled in this case.
Note: If debugging using CCS and using a gel script to wake-up all cores, the application needs to be loaded on only one of the cores. Only the app symbols need to be loaded on all other cores.
C SYNOPSIS
Core_useSkernelCmd
 
metaonly config Core.common$  // module-wide
index URL

Common module configuration parameters

Configuration settings
Core.common$ = Types.Common$ undefined;
 
DETAILS
All modules have this configuration parameter. Its name contains the '$' character to ensure it does not conflict with configuration parameters declared by the module. This allows new configuration parameters to be added in the future without any chance of breaking existing modules.
generated on Tue, 09 Oct 2018 20:57:51 GMT