Sr. No.	Title	Version
1	MDD Guidelines	Process 04.00.00
2	Software Naming Conventions	Process 04.00.00
3	Software Coding Standards	Process 04.00.00
4	AR400A_NxtrStrtUp_Design	See Synergy subproject version

Dependencies

SWCs

Module	Required Feature
None	N/A

Note : Referencing the external components should be avoided in most cases. Only in unavoidable circumstance external components should be referred. Developer should track the references.

Global Functions(Non RTE) to be provided to Integration Project

None

Configuration REQUIREMeNTS

Build Time Config

Modules	Notes
None

Configuration Files to be provided by Integration Project

None

DaVinci Parameter Configuration Changes

Parameter	Notes	SWC
N/A

DaVinci Interrupt Configuration Changes

ISR Name	Interrupt Category (FE/EI)	Interrupt Channel Number	Priority Dependency	Notes
N/A

Manual Configuration Changes

	Notes	SWC
N/A

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

None

Required Global Data Outputs

None

Specific Include Path present

Yes

Runnable Scheduling

This section specifies the required runnable scheduling.

Init	Scheduling Requirements	Trigger
N/A

Runnable	Scheduling Requirements	Trigger
N/A

Memory Map REQUIREMENTS

Mapping

Memory Section	Contents	Notes
.appstrtvect	Entry point to application	Must be placed at the location that the bootloader is expected to jump to via linker command file.

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

Usage

Feature	RAM	ROM
N/A

NvM Blocks

None

Compiler Settings

Preprocessor MACRO

None

Optimization Settings

The following option must be specified in the main .gpj project file:

-nostartfiles

This change prevents the use of the Green Hills startup library which this component replaces.

Appendix

The following symbols need to be defined in the linker command file for the project surrounding RAM sections that are to be cleared at init.

Symbol	Notes
clearedRamStart	To be placed near the top of RAM, before any bss or sbss section have been included by the application or OS.
clearedRamEnd	To be placed near the end of RAM but before the definition of any heap memory and after any and all bss or sbss sections.

These symbols are used by the library to denote the beginning and end of RAM that will be cleared during application init. The intent is to keep the range as small as possible to optimize startup timing while including all RAM that is guaranteed to be cleared at init. Due to the way Nexteer structures their memory map the cleared section may contain initialized sections (*data and *sdata) as well. This will not cause any functional issues but will hinder performance slightly.

Caution: if a variable is outside of the range between these two symbols its value at init cannot be assured. It is recommended that the .map file be analyzed once the changes have been integrated and the project compiles to ensure that there are no variables that fall outside of this range.

Last modified October 12, 2025: Initial commit (af72ad2)