SNIP_CLASSIC_CAN_SECTION_7_9_Notification_concept
Wortlaut
7.9 Notification concept
The Can module offers only an event triggered notification interface to the CanIf module. Each notification is represented by a callback function.
[SWS_Can_00099] ⌈The hardware events may be detected by an interrupt or by polling status flags of the hardware objects. The configuration possibilities regarding polling is hardware dependent (i.e. which events can be polled, which events need to be polled), and not restricted by this standard.⌋(SRS_Can_01132)
[SWS_Can_00007] ⌈It shall be possible to configure the driver such that no interrupts at all are used (complete polling).⌋(SRS_Can_01062) The configuration of what is and is not polled by the Can module is internal to the driver, and not visible outside the module. The polling is done inside the CAN main functions (Can_MainFunction_xxx). Also the polled events are notified by the appropriate callback function. Then the call context is not the ISR but the CAN main function. The implementation of all callback functions shall be done as if the call context was the ISR. For further details see also description of the CAN main functions Can_MainFunction_Read, Can_MainFunction_Write, Can_MainFunction_BusOff and Can_MainFunction_Wakeup.
Versionen & Provenienz · Zugeordnete Anforderungen
Diese Angaben zeigt der Versions-Explorer.
Begründung & Zuweisungs-Evidenz
Polling inside Can_MainFunction_Wakeup.
Dokumenten-Herkunft & Rückverfolgbarkeit
| Spezifikations-Dokument | SWS_CANDriver.pdf |
|---|---|
| Dokumentseite | Seite 41 |
| Ziel-Modul | can (classic) |
| Ziel-Anforderung | SWS_Can_00112 |
| Semantische Rolle | heuristic |
| Automatisierungs-Konfidenz | 0.75 |