| Both sides previous revisionPrevious revision | |
| controllers:bosch [2025/02/06 13:20] – [Stand alone CAN Controllers / IP Cores] heinz | controllers:bosch [2025/02/06 13:22] (current) – [Stand alone CAN Controllers / IP Cores] M_CAN / X_CAN heinz |
|---|
| |
| [[http://www.bosch-semiconductors.de/media/pdf_1/ipmodules_1/can_protocol_license_/Bosch_CAN_Protocol_License_Conditions.pdf | Bosch CAN IP license conditions]] as of 05/2014. It lists currently only the following IP cores: | [[http://www.bosch-semiconductors.de/media/pdf_1/ipmodules_1/can_protocol_license_/Bosch_CAN_Protocol_License_Conditions.pdf | Bosch CAN IP license conditions]] as of 05/2014. It lists currently only the following IP cores: |
| * [[https://www.bosch-semiconductors.com/products/ip-modules/can-ip-modules/m-can/ | M_CAN]]: Supports CAN, full CAN FD (up to 64 byte payload) and TTCAN | * [[https://www.bosch-semiconductors.com/products/ip-modules/can-ip-modules/m-can/ | M_CAN]]: Supports CAN, full CAN FD (up to 64 byte payload) and TTCAN. The M_CAN is a CAN IP module that can be realized as stand-alone device, as part of an ASIC, or on an FPGA. It supports CAN CC (Classical CAN) and CAN FD (CAN with Flexible Data-rate) communication according to ISO11898-1:2024. For a connection to the CAN physical layer, additional transceiver hardware is required. The M_CAN is also available as M_TTCAN, to additionally support Time-Triggered CAN according to ISO11898-4. The M_CAN has been developed as Safety Element out of Context (SEooC) according to ISO 26262-11:2018, Clause 4. Safety Manual and FMEDA are available on request. |
| * D_CAN: Support of CAN | * D_CAN: Support of CAN |
| * C_CAN FD8: Support of CAN and CAN FD8 (up to 8 byte payload) | * C_CAN FD8: Support of CAN and CAN FD8 (up to 8 byte payload) |
