@h2loop/autosar 1.0.1 → 1.1.0

package/skills/autosar/references/runnable-code.md

@@ -0,0 +1,50 @@
+# Runnable code: allowed RTE API, verify, context
+
+## Three tiers of an RTE API name (AUTOSAR CP R25-11 SWS_RTE 5.6)
+- **allowed** for runnable R: R has the access point the API's *Existence* requirement names. Only these may be
+  called from R and the functions it calls (SWS_Rte_CONSTR_09017/09083/...: "may only be used by the runnable that
+  contains the corresponding ..."). Shown in `autosar_build_context` section 3.
+- **generated**: some runnable of the SW-C is allowed it, so it is in `Rte_<Swc>.h`. Calling it from another runnable
+  compiles but is wrong (NOT-ALLOWED).
+- **derivable**: the port/element/IRV exists, but no runnable has the access point, so the API is not generated yet.
+
+| API | Access point (role) | Existence | Signature |
+|---|---|---|---|
+| `Rte_Write_<p>_<o>` / `Rte_Send_<p>_<o>` | dataSendPoint, data / queued element | SWS_Rte_01280 / 01281 | SWS_Rte_01071 / 01072 |
+| `Rte_Read_<p>_<o>` / `Rte_Receive_<p>_<o>` | dataReceivePointByArgument | SWS_Rte_01289 / 01288 | SWS_Rte_01091 / 01092 |
+| `Rte_DRead_<p>_<o>` | dataReceivePointByValue (primitive) | SWS_Rte_07395 | SWS_Rte_07394 |
+| `Rte_IRead[Ref]_<re>_<p>_<o>`, `Rte_IStatus_...` | dataReadAccess | SWS_Rte_01301 / 04578 / 02600 | SWS_Rte_03741 / 04577 / 02599 |
+| `Rte_IWrite[Ref]_<re>_<p>_<o>`, `Rte_IInvalidate_...` | dataWriteAccess | SWS_Rte_01302 / 05510 / 03801 | SWS_Rte_03744 / 05509 / 03800 |
+| `Rte_Call_<p>_<o>` / `Rte_Result_<p>_<o>` | (a)synchronousServerCallPoint / ...ResultPoint | SWS_Rte_01293/01294 / 01296 | SWS_Rte_01102 / 01111 |
+| `Rte_Mode_<p>_<o>` / `Rte_Switch_<p>_<o>` | modeAccessPoint / modeSwitchPoint | SWS_Rte_02629 / 02632 | SWS_Rte_02628 / 02631 |
+| `Rte_Prm_<p>_<o>` / `Rte_CData_<name>` | parameterAccess (port / local) | SWS_Rte_03929 / 01300 | SWS_Rte_03928 / 01252 |
+| `Rte_IrvRead/IrvWrite_<re>_<o>` | read/writtenLocalVariable, explicit IRV | SWS_Rte_01305 / 01306 | SWS_Rte_03560 / 03565 |
+| `Rte_IrvIRead/IrvIWrite[Ref]_<re>_<o>` | read/writtenLocalVariable, implicit IRV | SWS_Rte_01303 / 01304 | SWS_Rte_03550 / 03553 |
+| `Rte_Pim_<name>` | any runnable | SWS_Rte_01299 | SWS_Rte_01118 |
+| `Rte_Enter/Exit_<ea>` | canEnterExclusiveArea | SWS_Rte_01307 / 01308 | SWS_Rte_01120 / 01123 |
+
+Parameter passing: IN primitive by value (SWS_Rte_01017), IN struct/union by `const T*` (01018, 07086), IN array as
+pointer to the base type (05107); OUT always by pointer (01019, 07082, 05108); a struct/array return is a const
+pointer (07071, 07072). Multiple instantiation adds `Rte_Instance self` first. `Rte_IsUpdated`, `Rte_Invalidate`,
+`Rte_Feedback`, `Rte_IStatus` exist only with their ComSpec / InvalidationPolicy settings.
+
+## autosar_verify_rte
+Each `Rte_*` call is mapped to its enclosing function and to every runnable whose SYMBOL reaches it through the call
+graph (a static helper called from two runnables is checked for both). Statuses:
+- **OK**.
+- **NOT-ALLOWED**: rewrite with an allowed API, or add the access point to the runnable (ops given). For
+  `Rte_I*`/`Rte_Irv*` the runnable name is part of the API name: use the caller's.
+- **INVENTED**: no such port/element/runnable, or the wrong API kind for the port's direction or the element's
+  data/event semantics (the hint names the right one). When new data is truly needed the ops add the data
+  element (to the port's interface — note other users of that interface) or a new port + interface, then the access
+  point. New element types default to the type of a same-named element elsewhere, else `uint8` (flagged).
+After applying ops: `autosar_generate`, then verify again; then `autosar_build`. RTE lifecycle calls (`Rte_Start`, ...)
+in integration code are listed as not checked.
+
+## autosar_build_context
+Sections, in fixed order: 1 task, 2 SW-C definition, 3 allowed RTE API (exact header text), 4 runnable code,
+5 callees, 6 Com signals / NvM blocks behind its ports and calls, 7 FUZZY similar functions in other SW-Cs, 8 FUZZY
+similar past git changes (ARXML semantic delta + C hunks, ranked by overlap with the task's ports/elements/words and
+recency). Over budget (~4 chars/token): drop 8, drop 7, callees → prototypes, truncate code, truncate config,
+callees → names, code → head, compact 2. Sections 1 and 3 are never reduced. Output is byte-identical for the same
+inputs; the MANIFEST lists every source (file:line, sha1, included mode). Treat 7–8 as hints, never as truth.