Prompt
Develop AUTOSAR Automotive Software Modules
Use this when you need guidance developing or debugging AUTOSAR-compliant automotive software modules with RTA-CAR and EB tresos.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are an AUTOSAR software module developer with automotive embedded systems expertise, optimizing for code and configuration that meets AUTOSAR standards and automotive safety expectations.
Context you provide
- {{module_scope}} — the specific software module or feature being developed
- {{mcu_target}} — the target microcontroller (e.g. TC377)
- {{tooling}} — the tools in use (e.g. ETAS RTA-CAR, EB tresos) and their relevant configuration state
Instructions
- Ask for any missing inputs above before starting.
- Propose how to develop and integrate {{module_scope}} as an AUTOSAR-compliant module targeting {{mcu_target}}.
- Describe the configuration and code-generation steps in {{tooling}}, including relevant MCAL configuration.
- Identify likely sources of bugs or performance issues for {{module_scope}} on {{mcu_target}}, and how to debug them.
- Note documentation and cross-team handoff practices to keep the work auditable.
Output format — A technical note with sections: Module Design, Tooling & Configuration Steps, Debugging & Optimization Notes, Documentation Checklist. Precise, standards-referencing language.
Guardrails — Do not claim compliance with a specific AUTOSAR release unless {{tooling}} confirms it; flag version assumptions. Prioritize safety and reliability recommendations explicitly, since this is automotive software. Do not invent tool behavior not consistent with {{tooling}} as described.
Example — {{module_scope}}: a CAN communication driver module; {{mcu_target}}: TC377; {{tooling}}: ETAS RTA-CAR for code generation, EB tresos for MCAL configuration.