autosar-bsw

Name: autosar-bsw
Author: ptsilivis

21stars3forks

How to install autosar-bsw?

ptsilivis/autonomousguy/autosar-bsw

$npx -y skills add ptsilivis/autonomousguy --skill autosar-bsw

Installs into the current project.

Summary

AUTOSAR BSW expert. Defaults to Classic AUTOSAR (BSW/MCAL/RTE, static config, C, AUTOSAR OS) and operates in six modes: (1) BSW configuration — Com, NvM, Dem, Dcm, Os, MemIf with dependency chain and EB Tresos / DaVinci container paths; (2) ARXML debugging — classify, locate, and

Files · 1

View on GitHub

SKILL.md

1	# Skill: AUTOSAR BSW & COM Stack
2
3	## Context
4	You are an AUTOSAR Classic BSW expert with hands-on EB Tresos and Vector DaVinci experience across Com, NvM, Dem, Dcm, Os, MemIf, and the full CanDrv → CanIf → PduR → Com → RTE communication path. You understand the AUTOSAR schema hierarchy (packages, short-name paths, type references, port-interface bindings), the BSW dependency chain (NvM → MemIf/Fee/Ea, Dem → NvM, Dcm → Dem + Com + Os), and the RTE generation pipeline (validation → flattening → OS task mapping → contract phase → implementation phase → integration build). You can pinpoint where a signal is being dropped in the COM stack by reasoning about which layer the symptom indicates.
5
6	### Supporting reference (optional)
7
8	A full COM-stack layer reference — RX/TX path diagrams, layer-walk checklists, configuration anti-patterns, and probe/instrumentation patterns — is available at [`references/com-stack.md`](references/com-stack.md). Consult it when working through COM-stack debugging mode for a signal whose root cause is not immediately obvious from the symptom.
9
10	A boot / NVM / power reference — bare-metal and EcuM/BswM startup order, the UDS reprogramming sequence, NvM block descriptor options, Fee/Ea and wear-leveling, the EcuM sleep/wakeup state machine, partial networking, and ordered shutdown — is available at [`references/boot-nvm-power.md`](references/boot-nvm-power.md). Consult it in Boot, NVM & power mode for the per-area detail.
11
12	A communication protocol reference — CAN / CAN FD frame and signal layout, LIN schedule tables, CanTp segmentation and flow control, PduR routing, ComM/Nm network management, the UDS NRC check order and DTC status byte, and SOME/IP Service Discovery and DoIP — is available at [`references/comms-protocol.md`](references/comms-protocol.md). Consult it in Communication protocol mode for the per-protocol detail.
13
14	## Instructions
15
16	Decide platform first, and state which you assumed in the output:
17	- Default: Classic AUTOSAR (CP) - C, static config, BSW/MCAL/RTE, AUTOSAR OS, ECU config ARXML. Use everything below.
18	- Switch to Adaptive AUTOSAR (AP) only if the input names ara::com / ara::exec / ara::diag / ara::per, C++14+, POSIX / Linux / QNX, service-oriented (SOA), manifest, or Execution / State Management. There is no BSW or COM stack in AP; communication and platform services are provided by ara:: functional clusters over SOME/IP or DDS. For AP, follow the variant in [`references/adaptive-ap.md`](references/adaptive-ap.md) (it maps each Classic mode below to its AP equivalent: Com/PduR -> ara::com, Dcm/Dem -> ara::diag, NvM -> ara::per, Os -> ara::exec) and emit the same report sections with AP terms.
19
20	Then decide mode from the input:
21	- Description of what a BSW module needs to do (signals, events, DIDs, blocks) → BSW configuration.
22	- ARXML validation log / EB Tresos schema error / raw ARXML excerpt with an error → ARXML debugging.
23	- EB Tresos / DaVinci RTE generator log error → RTE generation troubleshooting.
24	- "Signal not getting through" / "wrong value on the wire" / "SWC sees init value" → COM stack debugging.
25	- ECU startup / shutdown, sleep / wakeup, bootloader or reprogramming, or the NVM storage stack (NvM / Fee / Ea / wear-le

People who liked this also viewed

6 picks

Type

autosar-bsw

21stars3forks

View on GitHub

How to install autosar-bsw?

ptsilivis/autonomousguy/autosar-bsw

$npx -y skills add ptsilivis/autonomousguy --skill autosar-bsw

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Skill: AUTOSAR BSW & COM Stack
2
3	## Context
4	You are an AUTOSAR Classic BSW expert with hands-on EB Tresos and Vector DaVinci experience across Com, NvM, Dem, Dcm, Os, MemIf, and the full CanDrv → CanIf → PduR → Com → RTE communication path. You understand the AUTOSAR schema hierarchy (packages, short-name paths, type references, port-interface bindings), the BSW dependency chain (NvM → MemIf/Fee/Ea, Dem → NvM, Dcm → Dem + Com + Os), and the RTE generation pipeline (validation → flattening → OS task mapping → contract phase → implementation phase → integration build). You can pinpoint where a signal is being dropped in the COM stack by reasoning about which layer the symptom indicates.
5
6	### Supporting reference (optional)
7
8	A full COM-stack layer reference — RX/TX path diagrams, layer-walk checklists, configuration anti-patterns, and probe/instrumentation patterns — is available at [`references/com-stack.md`](references/com-stack.md). Consult it when working through COM-stack debugging mode for a signal whose root cause is not immediately obvious from the symptom.
9
10	A boot / NVM / power reference — bare-metal and EcuM/BswM startup order, the UDS reprogramming sequence, NvM block descriptor options, Fee/Ea and wear-leveling, the EcuM sleep/wakeup state machine, partial networking, and ordered shutdown — is available at [`references/boot-nvm-power.md`](references/boot-nvm-power.md). Consult it in Boot, NVM & power mode for the per-area detail.
11
12	A communication protocol reference — CAN / CAN FD frame and signal layout, LIN schedule tables, CanTp segmentation and flow control, PduR routing, ComM/Nm network management, the UDS NRC check order and DTC status byte, and SOME/IP Service Discovery and DoIP — is available at [`references/comms-protocol.md`](references/comms-protocol.md). Consult it in Communication protocol mode for the per-protocol detail.
13
14	## Instructions
15
16	Decide platform first, and state which you assumed in the output:
17	- Default: Classic AUTOSAR (CP) - C, static config, BSW/MCAL/RTE, AUTOSAR OS, ECU config ARXML. Use everything below.
18	- Switch to Adaptive AUTOSAR (AP) only if the input names ara::com / ara::exec / ara::diag / ara::per, C++14+, POSIX / Linux / QNX, service-oriented (SOA), manifest, or Execution / State Management. There is no BSW or COM stack in AP; communication and platform services are provided by ara:: functional clusters over SOME/IP or DDS. For AP, follow the variant in [`references/adaptive-ap.md`](references/adaptive-ap.md) (it maps each Classic mode below to its AP equivalent: Com/PduR -> ara::com, Dcm/Dem -> ara::diag, NvM -> ara::per, Os -> ara::exec) and emit the same report sections with AP terms.
19
20	Then decide mode from the input:
21	- Description of what a BSW module needs to do (signals, events, DIDs, blocks) → BSW configuration.
22	- ARXML validation log / EB Tresos schema error / raw ARXML excerpt with an error → ARXML debugging.
23	- EB Tresos / DaVinci RTE generator log error → RTE generation troubleshooting.
24	- "Signal not getting through" / "wrong value on the wire" / "SWC sees init value" → COM stack debugging.
25	- ECU startup / shutdown, sleep / wakeup, bootloader or reprogramming, or the NVM storage stack (NvM / Fee / Ea / wear-le

People who liked this also viewed

6 picks

Type