Welcome to the CAN-bus Wiki project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
controllers:bosch [2014/07/25 14:14] – [Stand alone CAN Controllers / IP Cores] heinzcontrollers:bosch [2025/02/06 13:22] (current) – [Stand alone CAN Controllers / IP Cores] M_CAN / X_CAN heinz
Line 1: Line 1:
-==== BOSCH ====+===== BOSCH =====
  
  
Line 18: Line 18:
  
 ===== Stand alone CAN Controllers / IP Cores ===== ===== Stand alone CAN Controllers / 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. 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 
 +  * C_CAN FD8: Support of CAN and CAN FD8 (up to 8 byte payload)
 +  * [[https://www.bosch-semiconductors.com/products/ip-modules/can-ip-modules/x-can/ | X_CAN]]: is a CAN IP module that can be implemented in a SoC (System on Chip). It supports CAN CC (Classical CAN), CAN FD (CAN with Flexible Data-rate), and CAN XL (CAN with Extended Length) communication according to ISO 11898-1:2024. For connection to the CAN physical layer, additional transceiver hardware is required. The X_CAN is being developed as Safety Element out of Context (SEooC) according to ISO 26262-11:2018 Clause 4. Safety Manual and FMEDA are available on request.
 +
 + --- **Attention** //[[Heinz@Oertel-Halle.de|Heinz-Jürgen Oertel]] 2015/08/09 12:45// Bosch has changed all document locations
  
  
Line 26: Line 34:
     * [[http://www.bosch-semiconductors.de/en/ubk_semiconductors/safe/ip_modules/d_can/d_can.html | D_CAN]] The [[http://www.bosch-semiconductors.de/media/en/pdf_1/ipmodules_1/can/d_can_users_manual_111.pdf|PDF User Manual]].     * [[http://www.bosch-semiconductors.de/en/ubk_semiconductors/safe/ip_modules/d_can/d_can.html | D_CAN]] The [[http://www.bosch-semiconductors.de/media/en/pdf_1/ipmodules_1/can/d_can_users_manual_111.pdf|PDF User Manual]].
  
- +  * [[http://www.bosch-semiconductors.de/media/automotive_electronics/pdf_2/ipmodules_3/m_can_m_ttcan_1/mcan_users_manual_v3211.pdf |M_CAN]] The [[http://www.bosch-semiconductors.de/media/pdf_1/ipmodules_1/m_can_m_ttcan/mcan_users_manual_v320.pdf | PDF User Manual V 3.2.1]]. Older [[http://www.bosch-semiconductors.de/media/pdf_1/ipmodules_1/m_can/mcan_users_manual_v302.pdf |PDF User Manual V 3.0.2]] \\ The first IP core integrating the new [[:can_fd|CAN FD]] protocol \\ Version 3 of the M_CAN module will be released in week 31/2014
-  * [[http://www.bosch-semiconductors.de/en/ubk_semiconductors/safe/ip_modules/m_can/m_can.html|M_CAN]] The [[http://www.bosch-semiconductors.de/media/en/pdf_1/ipmodules_1/m_can/mcan_users_manual.pdf|PDF User Manual]] \\ The first IP core integrating the new [[:can_fd|CAN FD]] protocol \\ Version 3 of the M_CAN module will be released in week 31/2014+
  
  

QR Code
QR Code controllers:bosch (generated for current page)