FlsTst_Integration_Manual

Contents

1 Dependencies 1

1.1 SWCs 2

1.2 Functions to be provided to Integration Project 2

2 Configuration 2

2.1 Build Time Config 2

2.2 Configuration Files to be provided by Integration Project 2

2.2.1 Da Vinci Parameter Configuration Changes 3

2.2.2 DaVinci Interrupt Configuration Changes 3

2.2.3 Manual Configuration Changes 3

3 Integration 3

3.1 Required Global Data Inputs 3

3.2 Optional Global Data Inputs 4

3.3 Specific Include Path present 4

4 Runnable Scheduling 4

5 Memory Mapping 4

5.1 Mapping 4

5.2 Usage 4

5.3 NvM Blocks 5

6 Compiler Settings 5

6.1 Preprocessor MACRO 5

6.2 Optimization Settings 5

7 Revision Control Log 5

Dependencies

NOTE – the TMS570_uDiag component includes both uDiag and FlsTst functionality. For complete integration information on the TMS570_uDiag component, also see the Cd_uDiag integration manual (in the TMS570_uDiag\doc folder).

SWCs

ModuleRequired Feature
NxtrLib

DtrmnElapsedTime_uS_u32()

GetSystemTime_uS_u32()

TMS570 CRC peripheralExclusive access to the CRC peripheral registers.
TMS570 DMA peripheralExclusive access to the DMA peripheral registers.
TMS570 ESM peripheralExclusive access to the ESM configuration bits that control the DMA MPU interrupt enable, nError pin action, and Interrupt level mapping.
DiagMgr (Nexteer DEM)NxtrDiagMgr_ReportNTCStatus() API
uDiagESMDMAMPUErr() Callback notification on DMA MPU violation
Basic System ServicesEnableCRCInterrupt()

Functions to be provided to Integration Project

< Global function (except the ones that are defined in RTE modules) that is defined in this component but used by other function>

void FlsTst_MainFunction( void );

void FlsTst_Init( const FlsTst_ConfigType* ConfigPtr );

void FlsTst_Suspend( void );

void FlsTst_Resume( void );

Configuration

Build Time Config

ModulesNotes
None

Configuration Files to be provided by Integration Project

FlsTst_Cfg.c generated by FlsTst_Cfg.c.tt

FlsTst_Cfg.h generated by FlsTst_Cfg.h.tt

NOTES: The FlsTst module parameter description file and generator templates are located in the “generate” folder. The generation scheme at this time relies on the ARTT generation framework developed by BMW. Following are the recommended steps to integrate the provided generation templates and parameter description with Davinci Configurator:

  1. Copy the “Artt/artt” framework folder into the “Generators” directory (if not already present)

  2. Execute the “Integrate.bat” script from the Tools directory of this component to perform the necessary integration steps:

    1. The script creates the required directories in the integration project, “Generators/Artt/FlsTst” and “Generators/Components/_Schemes/FlsTst/bswmd”

    2. The script then copies the required files from the CBD generate directory into the new directories.

  3. If this is the first time integration, then perform the Davinci Configurator 3rd party component integration procedure.

Da Vinci Parameter Configuration Changes

ParameterNotesSWC
FlsTstConfigSetAt least one block configuration set must be defined. See FlsTst technical reference for details.FlsTst
FlsTstConfigurationOfOptApiServicesConfiguration of optional API services. All optional services are disabled by default.FlsTst
FlsTstDemEventParameterRefsConfiguration of NTC enumeration symbol name for diagnostic tests performed in this module.FlsTst
FlsTstGeneralGeneral module configuration. See FlsTst technical reference for details.FlsTst
FlsTst\Runtime\FlsTstBlockBgndConfigSet\App\FlsTstBlockSizeNumber of bytes in flash test block – NOTE that this number has a max value of 8388600 in the current version of the uDiag component, and a max value of 524280 in version FDD32B_TMS570_uDiag_000.21 and previous. Numbers greater than the max value will not give an error indication but will cause the flash CRC check to not operate correctly.FlsTst (contained in TMS570_uDiag component)

DaVinci Interrupt Configuration Changes

ISR NameVIM #Priority DependencyNotes
FlsTst_CrcIRQ19Must be IRQ and Category 2

Manual Configuration Changes

ConstantNotesSWC
None

Integration

Required Global Data Inputs

<Mention any global variable that this component requires for other components>

Optional Global Data Inputs

<Mention any global variable that this component requires for other components>

Specific Include Path present

<Yes>

Runnable Scheduling

This section specifies the required runnable scheduling.

RunnableScheduling RequirementsPrivileged ModeTrigger
FlsTst_Init()Must be executed prior to using FlsTst_MainFunction()RequiredInit*
FlsTst_MainFunction()Scheduling cycle can influence the time to complete the background test interval. A new test block is started only during the invocation of the MainFunction, so an excessively large period between MainFunction calls will extend the time for a test interval to complete.Cyclic
FlsTst_CrcIrq()Scheduled via hardware IRQ. The integrator must enable the interrupt source configured in the Os before this runnable can be triggered by the hardware.IRQ on signature failure

* Can be called during run time to change block test configuration if required.

Memory Mapping

Mapping

ConstantNotes
FLSTST_START_SEC_VAR_CLEARED_8
FLSTST_START_SEC_VAR_16
FLSTST_START_SEC_VAR_CLEARED_UNSPECIFIED
FLSTST_START_SEC_VAR_UNSPECIFIED
FLSTST_START_SEC_CODE
FLSTST_START_SEC_CONST_UNSPECIFIED

* Each …START_SEC… constant is terminated by a …STOP_SEC… constant as specified in the AUTOSAR Memory Mapping requirements.

Usage

Table 1: ARM Cortex R4 Memory Usage

FeatureRAMROM
Full driver

NvM Blocks

Block Name
<NvM Block Info>

Note : Size of the NVM block if configured in developer

Compiler Settings

Preprocessor MACRO

<Define all the preprocessor Macros needed and conditions when needed>.

Optimization Settings

Revision Control Log

Rev #Change DescriptionDateAuthor Initials
1Initial versionJJW
2Updated integration process description to reference use of Integrate.bat09/18/12JJW
3Updated to latest template, other misc cleanup.06-Jan-14KMC
Last modified October 12, 2025: Initial commit (0347a62)