This setting should be “Yes” because the driver is QM software, which means in the EPS system that it must be run in a user mode application. In order for the Os to appropriately configure the MPU and switch to user mode a category 2 interrupt is required.

This setting is “grayed out” and set to “No”. The current software implementation configures a Cat2 interrupt function which then simply calls the interrupt function as a workaround.

Desired configuration is to provide interrupt processing only on Tx messages. The “Type Specific” setting provides a polling configuration granularity that allows this configuration.

“Individual” would also work, but has a finer configuration granularity that is more complex and is not necessary for this use case.

Nexteer has no design in place to log the fatal failures in the event an assertion is triggered during development. Perhaps the assertions should be mapped to the Autosar Det. Until a design use case is determined, this feature is being disabled.

The production intended setting is “None” to reduce the driver operating overhead (i.e. runtime and program space) by eliminating unnecessary error checking in the final tested configuration.

• Synch Mechanism

“Default” handling is NOT selected because the VStdLib default interrupt handling requires a privileged CPU mode of execution. The Nexteer use case is placing the Can drivers in a user mode application because they are QM rated drivers. Therefore the “Default” interrupt handling will not function properly and cannot be used.

“OSEK” Handling selected for compatibility with the Nexteer use case.