Apparatus and method for a transceiver for a serial bus system

Abstract

The invention relates to an apparatus for a transceiver for a serial bus system, wherein the apparatus comprises: a transceiver interface for connecting the apparatus to the transceiver, a plurality of controller interfaces for connecting the apparatus to a plurality of bus controllers for the serial bus system, wherein the apparatus is designed to at least temporarily enable data communication between at least one bus controller of the plurality of bus controllers and the transceiver.

Description

[0001] R.414641

[0002] Description

[0003] title

[0004] Device and method for a transceiver for a serial

[0005] State of the art

[0006] The disclosure relates to a method for a transceiver for a serial bus system.

[0007] The disclosure further relates to a device for a transceiver for a serial bus system.

[0008] Disclosure of the invention

[0009] Some examples relate to a device for a transceiver for a serial bus system, wherein the device comprises: a transceiver interface for connecting the device to the transceiver, a plurality of controller interfaces for connecting the device to a plurality of bus controllers for the serial bus system, wherein the device is configured to enable data communication, at least temporarily, between at least one bus controller of the plurality of bus controllers and the transceiver. In some examples, this allows for flexible use of the (one) transceiver with multiple bus controllers.

[0010] For example, the bus system is one of the following types, but is not limited to the examples listed below: a) Controller Area Network, CAN, for example Classical CAN, for example CAN CC, or b) CAN Flexible Data Rate, for example CAN FD, or c) CAN XL, or d) another type, for example based on at least one of CAN, for example CAN CC, or CAN FD or CAN XL. R.414641

[0011] - 2 -

[0012] For example, the transceiver is a CAN transceiver, such as a CAN CC transceiver, or a CAN FD transceiver, or a CAN XL transceiver, or a CAN Signal Improvement Capability, SIC, XL transceiver.

[0013] In some examples, the device is configured to receive and combine the respective transmit signals from the bus controllers (e.g., "CAN_Tx" in the case of CAN) and / or from at least one multiplexer via the controller interfaces, thereby obtaining, for example, a combined transmit signal, and output this combined transmit signal to the transceiver via the transceiver interface. For example, the combination can be achieved using a logical AND operation on the respective transmit signals. In some examples, this allows the respective transmit signals to be fed to the transceiver, for example, for transmission on the bus system.

[0014] Furthermore, for example, the device is designed to receive a received signal from the transceiver via the transceiver interface and to output it, at least temporarily, to at least one of the bus controllers and / or to a multiplexer device, for example to all bus controllers and / or multiplexer devices connected to the device, for example to forward it, in the case of CAN e.g. as a "CAN_Rx" signal.

[0015] In some examples, the device is configured to receive respective transmitter information signals from the bus controllers and / or from at least one multiplexer via the controller interfaces, wherein, for example, a transmitter information signal from a bus controller and / or from the at least one multiplexer indicates whether the bus controller and / or the at least one multiplexer (or a bus controller connected to the multiplexer) is currently the transmitter of a data frame, for example a CAN data frame, and to generate a first signal based on the received transmitter information signals, which indicates whether at least one of the bus controllers and / or the multiplexer (or a bus controller connected to the multiplexer) is currently the transmitter of a data frame, for example a CAN data frame.a bus controller connected to the multiplexer device) is currently the sender of a data frame, for example a CAN data frame, for example by means of an OR operation of the received sender information signals, R.414641.

[0016] - 3 - and output the first signal to the bus controllers and / or the at least one multiplexer. This makes it possible, for example, to inform the bus controllers and / or the at least one multiplexer whether at least one or another local component (bus controller and / or multiplexer) associated with the device is currently sending a data frame. Based on this information, the component in question can, in some examples, adjust its operation, for instance, suppress or omit a local acknowledgment ("ACK"), and / or suppress or omit optional PWM encoding of a CAN_Tx output, as is provided for in some conventional CAN systems, e.g., based on CAN XL in conjunction with SIC XL transceivers.

[0017] For example, the device is configured to enable at least temporary internal data communication between the bus controllers and / or at least one multiplexer, where, for example, the data communication does not involve any exchange of information with the transceiver interface or with the transceiver itself. In other words, the device can be configured, for example, to emulate a local bus system, such as an internal CAN bus, i.e., to replicate it. In some examples, this enables data communication between the bus controllers and / or at least one multiplexer, without, for example, a transceiver being connected to the device's transceiver interface.

[0018] In some examples, the device can be configured by means of configuration information and / or a configuration signal to enable internal data communication between the bus controllers and / or the at least one multiplexer device.

[0019] For example, at least temporary decoupling, e.g., separation, of signal paths to the transceiver interface, e.g., from the controller interfaces, may also be provided.

[0020] In some examples, the device is configured to output the first signal to the bus controllers and / or the at least one multiplexer unit during internal data communication with a signal value indicating that currently none of the bus controllers and / or the multiplexer unit R.414641

[0021] - 4 -

[0022] The sender of a data frame, for example a CAN data frame. This can prevent the potentially unwanted suppression of a transmitted signal, e.g. "CAN_Tx", in some examples, which may be desirable at least temporarily outside of internal data communication.

[0023] For example, the device can be configured to activate or deactivate at least one of its controller interfaces using configuration information and / or a configuration signal. This allows the relevant controller interface(s) to be selectively activated and / or deactivated, enabling flexible configuration and energy-efficient operation.

[0024] In some examples, the device can be provided in the form of a hardware circuit, for example a pure hardware circuit, e.g. as an application-specific integrated circuit, ASIC, or as a component or part for an ASIC.

[0025] Further examples relate to a bus controller for a device according to the disclosure, wherein the bus controller is configured to output a sender information signal to the device, the sender information signal indicating whether the bus controller is currently the sender of a data frame, for example, a CAN data frame. In some examples, this enables efficient operation of the device according to the disclosure with multiple bus controllers according to the disclosure.

[0026] In some examples, the bus controller is configured to receive a first signal from the device, where the first signal indicates whether at least one of several bus controllers connected to the device and / or a multiplexer connected to the device is currently transmitting a data frame, for example, a CAN data frame. This allows the bus controller, in some examples, to be informed, for instance, whether another bus controller connected to the device and / or the multiplexer connected to the device is currently transmitting a data frame. Based on this information, the operation of the bus controller can be influenced, for example, controlled, in some examples (R.414641).

[0027] - 5 - for example, for suppressing or omitting a local acknowledgment.

[0028] For example, the bus controller is configured to set a control signal when a) the first signal indicates that at least one of several bus controllers connected to the device and / or a multiplexer connected to the device is currently a sender of a data frame, for example a CAN data frame, and when b) the bus controller is not itself currently a sender of a data frame, for example a CAN data frame, wherein, for example, setting the control signal includes: setting a transmit signal of the bus controller to a signal value associated with a recessive level of the bus system, for example until the control signal is no longer set, for example, until it is reset.

[0029] In some examples, the bus controller is configured to reset the control signal if a) an error occurs in a received data frame, for example, if the bus controller detects the error in the received data frame, and / or if b) the data frame has ended.

[0030] In other examples, the bus controller can be provided in the form of a hardware circuit, for example a pure hardware circuit, e.g. as an application-specific integrated circuit, ASIC, or as a component or part for an ASIC.

[0031] Other examples relate to a multiplexer device for at least one serial bus system, wherein the multiplexer device comprises: a controller interface for connecting the multiplexer device to a bus controller for the at least one bus system, wherein, for example, the bus controller is configured according to the disclosure; a plurality of transceiver interfaces for connecting the multiplexer device to a plurality of transceivers for the at least one serial bus system and / or at least one device according to the disclosure, wherein the multiplexer device is configured to enable, at least temporarily, data communication between the bus controller and at least one, for example, exactly one, transceiver interface of the plurality of transceiver interfaces. R.414641

[0032] - 6 -

[0033] In some examples, the multiplexer setup is configurable to enable data communication between the bus controller and exactly one transceiver interface, at least temporarily. In other words, the multiplexer setup can be configured, or can configure itself, for example, based on relevant information and / or a configuration signal. The configuration specifies, for instance, which of the multiple transceiver interfaces should be enabled for data communication with the bus controller.

[0034] For example, the multiplexer device for at least one transceiver interface of the plurality of transceiver interfaces is configured to output a transmitter information signal, for example via the at least one transceiver interface, for example to the at least one device, wherein the transmitter information signal indicates whether the bus controller is currently the sender of a data frame, for example CAN data frame.

[0035] In some examples, the multiplexer device can be provided in the form of a hardware circuit, for example a pure hardware circuit, e.g. as an application-specific integrated circuit, ASIC, or as a component or part for an ASIC.

[0036] Some examples refer to a system comprising at least one of the following elements: a) a device according to the disclosure, or b) a bus controller according to the disclosure, or c) a multiplexer device according to the disclosure, wherein, for example, at least some components of the system are designed as an integrated circuit, for example, an application-specific integrated circuit, and / or are combined to form an integrated circuit.

[0037] Further examples relate to a method for a device for a transceiver for a serial bus system, wherein the device comprises: a transceiver interface for connecting the device to the transceiver, a plurality of controller interfaces for connecting the device to R.414641

[0038] - 7 - a plurality of bus controllers for the serial bus system, wherein the method comprises: at least temporarily enabling data communication between at least one bus controller of the plurality of bus controllers and the transceiver.

[0039] Further examples relate to a product, for example a vehicle or robot or cyber-physical system, comprising at least one of the following elements: a) a device according to the disclosure, or b) a bus controller according to the disclosure, or c) a multiplexer device according to the disclosure, or d) a system according to the disclosure.

[0040] Other examples relate to the use of the device according to the disclosure, and / or the bus controller according to the disclosure, and / or the multiplexer device according to the disclosure, and / or the system according to the disclosure, and / or the method according to the disclosure, and / or the product according to the disclosure for at least one of the following elements: a) enabling data communication between at least one bus controller and a transceiver, or b) extending existing bus controllers, for example CAN controllers, or c) increasing flexibility regarding connecting a bus controller to multiple transceivers, or d) providing a modular concept for the bus controller and / or the device and / or the multiplexer device and / or the system, or e) enabling individual verification of aspects of the bus controller and / or the device and / or the multiplexer device.

[0041] Further features, applications, and advantages will become apparent from the following description of examples illustrated in the figures of the drawing. All described or illustrated features, individually or in any combination, constitute the subject matter of the disclosure, irrespective of their aggregation in the claims or their cross-reference, and irrespective of their formulation or representation in the description or in the drawing.

[0042] The drawing shows:

[0043] Fig. 1 schematically shows a simplified block diagram, R.414641

[0044] - 8 -

[0045] Fig. 2 schematically shows a simplified flowchart,

[0046] Fig. 3 schematically shows a simplified flowchart,

[0047] Fig. 4 schematically shows a simplified flowchart,

[0048] Fig. 5 schematically shows a simplified flowchart,

[0049] Fig. 6 schematically shows a simplified flowchart,

[0050] Fig. 7 schematically shows a simplified flowchart,

[0051] Fig. 8 schematically shows a simplified flowchart,

[0052] Fig. 9 schematically shows a simplified block diagram,

[0053] Fig. 10 schematically shows a simplified flowchart,

[0054] Fig. 11 schematically shows a simplified block diagram,

[0055] Fig. 12 schematically shows a simplified block diagram,

[0056] Fig. 13 schematically shows a simplified block diagram,

[0057] Fig. 14 schematically shows a simplified block diagram,

[0058] Fig. 15 schematically shows examples of uses.

[0059] Some examples, Fig. 1, 2, relate to a device 100 for a transceiver 10 for a serial bus system 20, wherein the device 100 comprises: a transceiver interface 110 for connecting the device 100 to the transceiver 10, a plurality 120 of controller interfaces 120-1, 120-2, ..., 120-M for connecting the device 100 to a plurality 30 of bus controllers 30-1, 30-2, ... and / or multiplexer devices 200 for the serial bus system 20, wherein the device 100 is configured to R.414641

[0060] - 9 - to enable at least temporary data communication DK between at least one bus controller 30-1, 30-2, ... the plurality of bus controllers (and / or at least one of the multiplexer units 200) and the transceiver 10 300 (Fig. 2). In some examples, this allows flexible use of the (one) transceiver 10 with several bus controllers 30-1, 30-2, ... and / or with one or more multiplexer units 200.

[0061] The optional block 302 according to Fig. 2 symbolizes an optional data exchange DA between at least some of the components 30, 200 and the transceiver 10, as enabled by the device 100.

[0062] For example, Fig. 1, the bus system 20 has one of the following types, but is not limited to the examples mentioned below: a) Controller Area Network, CAN, for example Classical CAN, for example CAN CC, or b) CAN Flexible Data Rate, for example CAN FD, or c) CAN XL, or d) another type, for example based on at least one of CAN, for example CAN CC, or CAN FD or CAN XL.

[0063] For example, in Fig. 1, the transceiver 10 is a CAN transceiver, such as a CAN CC transceiver, or a CAN FD transceiver, or a CAN Signal Improvement Capability, SIC, transceiver, or a CAN SIC XL transceiver.

[0064] For the sake of clarity and without limiting generality, the following description and its examples refer primarily to a CAN bus system 20 and associated CAN transceivers. Nevertheless, the principle, as disclosed, may also be applicable to other serial bus systems.

[0065] In some examples, Fig. 1, the serial bus system 20, for example of CAN type, can be used for communication in a vehicle 40 (see Fig. 11) or another product such as a robot or a cyber-physical system. For example, several CAN buses can also be used for in-vehicle communication. R.414641

[0066] - 10 - To connect a device to a CAN bus 20, in some examples, see Fig. 1, the transceiver (e.g., "transmitter receiver") 10 can be used. In some examples, it represents an electronic component that is at least partially analog (e.g., specified according to ISO 11898-2) and can establish a physical connection to the bus system 20, for example, bus lines (not shown, e.g., twisted pair cable) of the bus system 20, and operates, for example, according to ISO / OSI layer 1.

[0067] For example, the transceiver 10 is designed to convert signals from the bus system, e.g. CAN bus, 20 (e.g. characterized by a differential voltage between two bus lines) into a digital output signal, e.g. designated as "RxD", and / or to convert a digital input signal (e.g. designated as "TxD") into a differential voltage and drive it onto the CAN bus, i.e. applying the differential voltage to the bus lines of the bus system 20.

[0068] In further examples, Fig. 1, the bus controller 30-1, for example CAN controller, represents, for example, a digital circuit that generates data frames, e.g. CAN data frames, for serial transmission of messages on the CAN bus 20 or decodes data frames received serially via the bus system 20, e.g. CAN data frames, and operates, e.g., according to ISO / OSI layer 2.

[0069] In some examples, at least one bus controller 30-1, 30-2, ... can be integrated into a target system (not shown) such as a microcontroller ("pC").

[0070] For example, a bus controller 30-1 , ... for a CAN bus system has at least the following two aspects: A) A protocol controller (e.g. "PRT") that provides the CAN bus's transmit and receive function, B) a message handler (e.g. "MH") that provides, for example, a target system-side, e.g., PC-side, message management function, for example with multiple intermediate storage locations.

[0071] In other examples, separately integrated CAN controllers can also be provided using the principle according to the disclosure. R.414641

[0072] - 11 -

[0073] In some examples, Fig. 3, the device 100 (Fig. 1) is configured to receive respective transmit signals TX-1, TX-2, ... , TX-M from the bus controllers 30-1, 30-2, ... , (in the case of CAN e.g. "CAN_Tx") and / or from at least one multiplexer device 200 via the controller interfaces 120 310 (Fig. 3), to combine them 312, for example receiving a combined transmit signal TX, and to output them, for example in the form of the combined transmit signal TX, to the transceiver 10 via the transceiver interface 110 314.

[0074] For example, the combination 312 can be carried out by means of a logical AND operation of the respective transmitted signals, see the optional block 312a according to Fig. 3. In some examples, this allows the respective transmitted signals TX-1 , TX-2, ... , TX-M to be supplied to the transceiver 10, for example for transmission on the bus system 20.

[0075] Furthermore, for example, Fig. 1, 4, the device 100 is configured to receive a receive signal RX from the transceiver 10 via the transceiver interface 110 320 (Fig. 4) and to output it at least temporarily to at least one of the bus controllers 30-1, 30-2, ... , 30-M and / or to a multiplexer unit 200 322, for example to all bus controllers 30-1 , 30-2, ... and / or multiplexer units 200 connected to the device 100, for example to forward it 322a, in the case of CAN e.g. as "CAN_Rx" signal.

[0076] In some examples, Figs. 1, 5, the device 100 is configured to receive respective transmitter information signals IS-TX-1, IS-TX-2, ..., IS-TX-M from the bus controllers 30-1, 30-2, ... and / or from the at least one multiplexer 200 via the controller interfaces 120-1, 120-2, ..., 120-M, see block 330 according to Fig. 5, wherein, for example, a transmitter information signal IS-TX-1 from a bus controller 30-1 and / or from the at least one multiplexer indicates whether the bus controller 30-1 and / or the at least one multiplexer is currently the sender of a data frame, for example a CAN data frame, and thus is currently transmitting a data frame. R.414641

[0077] - 12 -

[0078] Furthermore, the device 100 is configured, for example, to generate a first signal S-1 based on the received transmitter information signals IS-TX-1, IS-TX-2, IS-TX-M (see block 332 according to Fig. 5), which indicates whether at least one of the bus controllers and / or the multiplexer is currently the sender of a data frame, for example a CAN data frame, for example by means of an OR operation of the received transmitter information signals (see optional block 332a), and to output the first signal S-1 to the bus controllers 30-1, 30-2, ... and / or the at least one multiplexer 200 (see block 334). This makes it possible, for example, to inform the bus controllers 30-1, 30-2, ... and / or the at least one multiplexer 200 whether at least one or another local component (bus controller and / or multiplexer) associated with the device 100 is currently the sender of a data frame, for example a CAN data frame. (Bus controller connected to the multiplexer device) is currently sending a data frame.Based on this information, the component in question can adjust its operation in some examples, for instance suppressing or omitting a local acknowledgment ("ACK"), and / or suppressing or omitting optional PWM encoding of a CAN_Tx output, as is provided for in some conventional CAN systems, e.g., based on CAN XL in conjunction with SIC XL transceivers.

[0079] For example, see Fig. 6, the device 100 is configured to enable, at least temporarily, internal data communication DK' between the bus controllers 30-1, 30-2, ... and / or the at least one multiplexer device 200, see Block 342, wherein, for example, the internal data communication DK' does not involve any information exchange with the transceiver interface 110 or with the transceiver 10. In other words, the device 100 can, for example, be configured to emulate, i.e., replicate, a local bus system, e.g., one internal to the device 100, such as an internal CAN bus. In some examples, this enables data communication DK' between the bus controllers 30-1, 30-2, ... and / or the at least one multiplexer device 200, e.g. without the transceiver 10 being connected to the transceiver interface 110 of the device 100 and / or being involved in the internal data communication DK'.The optional block 344 according to Fig. 6 symbolizes a corresponding data exchange DA' of components 30-1, 30-2, ... , 200 in the sense of internal data communication DK'. R.414641.

[0080] - 13 -

[0081] In some examples, Fig. 6, the device 100 can be configured, by means of configuration information CFG-1 and / or by means of a configuration signal S-CFG-1, see block 340, to enable internal data communication DK' between the bus controllers 30-1, 30-2, ... and / or the at least one multiplexer device 200. For example, at least temporary decoupling, e.g., isolation, of signal paths to the transceiver interface 110, e.g., from the controller interfaces 120, can also be provided.

[0082] In some examples, Fig. 6, the device 100 is configured to output the first signal S-1 to the bus controllers 30-1, 30-2, ... and / or the at least one multiplexer 200 with a signal value during internal data communication DK', see block 346, which indicates that currently none of the bus controllers 30-1, 30-2, ... and / or the multiplexer 200 is a sender of a data frame, for example, a CAN data frame. This prevents, in some examples, the potentially undesirable suppression of a transmit signal, e.g., "CAN_Tx", which may be desirable, at least temporarily, in some examples outside of internal data communication DK'. In other words, in some examples, the bus controllers and / or the multiplexer connected to the device 100 can prevent the suppression of a transmit signal, e.g., "CAN_Tx"."CAN_Tx" should be omitted if they receive the first signal S-1 with the signal value indicating that currently none of the bus controllers 30-1, 30-2, ... and / or the multiplexer unit 200 is a sender of a data frame, for example a CAN data frame.

[0083] For example, Fig. 7, the device 100 (Fig. 1) can be configured, by means of configuration information CFG-2 and / or by means of a configuration signal S-CFG-2 (see block 350), to activate or deactivate at least one of the controller interfaces 120-1, 120-2, ... 120-M (352a, 352b). This allows the controller interface(s) in question to be selectively activated and / or deactivated, enabling flexible configuration and energy-efficient operation. R.414641

[0084] - 14 -

[0085] In some examples, Fig. 1, the device 100 can be provided, for example, in the form of a hardware circuit, such as a pure hardware circuit, e.g., as an application-specific integrated circuit (ASIC), or as a component or part for an ASIC. In some examples, the device can also be integrated into a target system such as a microcontroller.

[0086] Further examples, e.g., Figs. 1, 8, relate to a bus controller 30-1, 30-2, ... for a device 100 according to the disclosure, wherein the bus controller is configured to output a transmitter information signal IS-TX-1 to the device 100, see block 370 according to Fig. 8, wherein the transmitter information signal IS-TX-1 indicates whether the bus controller 30-1 is currently the sender of a data frame, for example, a CAN data frame, i.e., whether it is currently sending a data frame. In some examples, this enables efficient operation of the device 100 according to the disclosure with several bus controllers 30-1, 30-2, ... (and at least one optional multiplexer device 200) according to the disclosure, for example, comprising the generation of the first signal S-1 described above.

[0087] In some examples, Fig. 8, the bus controller 30-1 is configured to receive a first signal S-1 from the device 100 (see block 372), where the first signal S-1 indicates whether at least one of several bus controllers 30-1, 30-2, ... connected to the device 100 and / or a multiplexer 200 connected to the device 100 is currently transmitting a data frame, for example, a CAN data frame. In some examples, this allows the bus controller 30-1 to be informed, for example, whether another bus controller 30-2, ... connected to the device 100 and / or the multiplexer 200, if any, connected to the device is currently transmitting a data frame. Based on this information, the operation of the bus controller 30-1 can be influenced, for example, controlled, for instance, by suppressing or omitting a local acknowledgment.

[0088] For example, Fig. 8, the bus controller 30-1 is configured to, when a) the first signal S-1 indicates that at least one of several bus controllers connected to the device 100 and / or a multiplexer connected to the device is currently a sender of a data frame, R.414641

[0089] - 15 - for example, CAN data frames, and if b) the bus controller 30-1 is not currently itself the sender of a data frame, for example, a CAN data frame, to set a control signal Rx_TSS, where, for example, setting 374 of the control signal has: Setting 374a of a transmit signal of the TX-1 (Fig. 1) bus controller 30-1 to a signal value that is associated with a recessive level of the bus system 20, for example, until the control signal Rx_TSS is no longer set, for example, is reset, see block 376. Setting 374a causes, for example, the suppression of a local acknowledgment ("local ACK") and / or an optional PWM encoding of a CAN_Tx output.

[0090] In some examples, Fig. 8, the bus controller 30-1 is configured to reset the control signal Rx_TSS 376 when a) an error occurs in a received data frame, for example, when the bus controller 30-1 detects the error in the received data frame, and / or when b) the data frame has ended.

[0091] In further examples, Fig. 1, the bus controller 30-1 can be provided, for example, in the form of a hardware circuit, for example, a pure hardware circuit, e.g., as an application-specific integrated circuit, ASIC, or as a component or part for an ASIC.

[0092] In further examples, the additional optional bus controllers 30-2, ... exhibit functionality comparable to or identical to that of the bus controller 30-1.

[0093] Other examples, Fig. 9, relate to a multiplexer device 200 for at least one serial bus system 20, 20', wherein the multiplexer device 200 comprises: a controller interface 210 for connecting the multiplexer device 200 to a bus controller 30-1 for the at least one bus system 20, 20', wherein, for example, the bus controller 30-1 is configured according to the disclosure, e.g., above to Fig. 1 ff., a plurality 220 of transceiver interfaces 220-1, 220-2, ... for connecting the multiplexer device 200 to a plurality of transceivers 10-1, 10-2, ... for the at least one serial bus system 20, 20' and / or at least one device 100 (Fig. 1) according to the disclosure, wherein the multiplexer device 200 is configured to at least temporarily

[0094] - 16 -

[0095] To enable data communication DK” between the bus controller 30-1 and at least one, for example exactly one, transceiver interface 220-1, 220-2, or the plurality 220 of transceiver interfaces, see block 392 according to Fig. 10. The optional block 394 according to Fig. 10 symbolizes an optional data exchange DA” between the bus controller 30-1 and the selected transceiver interface in the sense of the aforementioned data communication DK”.

[0096] In some examples, Figs. 9, 10, the multiplexer 200 is configurable (see Block 390) to enable data communication DK" between the bus controller 30-1 and exactly one transceiver interface 10-1 or 10-2, at least temporarily. In other words, the multiplexer 200 can be configured (see Block 390), for example, based on corresponding information and / or a configuration signal, where the configuration CFG' specifies, for example, which of the multiple transceiver interfaces (10-1, 10-2) data communication DK" with the bus controller 30-1 should be enabled.

[0097] For example, as shown in Figs. 9 and 10, the multiplexer 200 for at least one transceiver interface 10-1 of the plurality of transceiver interfaces is configured to output a transmitter information signal IS-TX-T 396, for example via the at least one transceiver interface 10-1, for example to the at least one device 100, wherein the transmitter information signal IS-TX-T indicates whether the bus controller 30-1 is currently the sender of a data frame, for example a CAN data frame. This can be useful, for example, for generating the first signal S-1 by the device 100.

[0098] In some examples, Fig. 9, the multiplexer device 200 can be provided, for example, in the form of a hardware circuit, such as a pure hardware circuit, e.g., as an application-specific integrated circuit, ASIC, or as a component or part for an ASIC.

[0099] Some examples, Fig. 1, relate to a system 1000 comprising at least one of the following elements: a) a device 100 according to the disclosure, or b) a bus controller 30-1 according to the disclosure, or c) R.414641

[0100] - 17 - a multiplexer device 200 according to the disclosure, wherein, for example, at least some components 30-1, 30-2, ... , 100, 200 of the system 1000 are designed as an integrated circuit, for example, an application-specific integrated circuit, and / or are combined to form an integrated circuit.

[0101] Further examples, Fig. 2, relate to a method for a device 100 for a transceiver 10 for a serial bus system 20, wherein the device 100 comprises: a transceiver interface 110 for connecting the device to the transceiver, a plurality 120 of controller interfaces for connecting the device to a plurality of bus controllers for the serial bus system, wherein the method comprises: at least temporarily enabling 300 a data communication DK between at least one bus controller 30-1 of the plurality of bus controllers and the transceiver 10.

[0102] Further examples, Fig. 11, relate to a product 40, for example a vehicle or robot or cyber-physical system, comprising at least one of the following elements: a) a device 100 (Fig. 1) according to the disclosure, or b) a bus controller 30-1 according to the disclosure, or c) a multiplexer device 200 according to the disclosure, or d) a system 1000 according to the disclosure.

[0103] Further aspects and examples are described below, which – in the case of further examples – can each be combined individually or in any combination with at least one of the aspects and / or examples described above.

[0104] CAN transceivers can send dominant or recessive signals to the CAN bus 20 (Fig. 1), e.g., drive a positive differential voltage "Vdiff" between the bus lines "CAN_H" and "CAN_L" as a dominant level on the bus. If none of several transceivers connected to the same bus drives a dominant level, termination resistors (not shown) of the bus system 20, for example, set a differential voltage Vdiff of 0 volts as a recessive level. Thus, in some examples, the recessive level is not driven by the transceivers. Therefore, for example, a transceiver that has an R.414641

[0105] - 18 - sends dominant level, overriding the undriven recessive level.

[0106] For the digital signals CAN_Tx and CAN_Rx of CAN-type bus controllers, e.g., '0' corresponds to the dominant level, and T to the recessive level on the CAN bus.

[0107] For example, a logical function on the CAN bus corresponds to a logical "AND". As soon as, for example, a bus participant sends a logical "0" (dominant), the bus state is "0" (dominant). Only when all bus participants send a logical "1" (recessive) is the bus state 1 (recessive).

[0108] In error-free operation, receivers of a CAN data frame send, for example, only a single dominant bit, the Acknowledge ("ACK") bit, in an ACK slot at the end of the CAN data frame, at the position where the sender transmits a sequence of recessive bits. In some cases, this confirms the correct reception of the CAN data frame. A receiver that detects an error in a CAN data frame can, for example, send a sequence of dominant bits onto the CAN bus, thereby invalidating the data frame and signaling this error to all other bus participants.

[0109] In devices with multiple CAN controllers, for example, all CAN controllers can be connected to different CAN buses. There are also cases where multiple CAN controllers are connected to the same CAN bus. This occurs, for example, when the device needs to send and receive more messages on a CAN bus than a single CAN controller can handle, or when, in multi-core PCs, specific cores are exclusively assigned their own CAN controller to avoid access conflicts between cores. This achieves "freedom of interference," meaning that CPUs and the software running on them can be isolated from each other because they do not share resources, such as CAN controllers. This increases the functional safety of a system.

[0110] The device 100 according to the disclosure and / or the bus controllers 30-1, 30-2, ... according to the disclosure and / or the multiplexer device 200 according to R.414641

[0111] - 19 -

[0112] Disclosures can be used in some examples for the operation of bus system 20 (Fig. 1) according to the aforementioned aspects of a CAN bus system.

[0113] The principle according to the disclosure allows, in some examples, any number of CAN controllers 30-1, 30-2, ... , (Fig. 1), even of different types, to share at least one transceiver 10. For example, each transceiver 10 can be provided with a device 100 according to the disclosure, which in some examples can also be referred to as a "transceiver sharing switch" ("TSS").

[0114] In some examples, multiple CAN controllers 30-1, 30-2, ... , for example any number, can be connected to the device or the TSS 100, e.g. via a uniform interface. In some examples, the TSS 100 can also be used without transceiver 10, in which case it represents, for example, a local CAN bus connection between the connected CAN controllers 30-1, 30-2, ... , or the multiplexer(s) 200 that may be present, which can be used, for example, for software testing.

[0115] In some examples, at least one multiplexer unit 200 (Fig. 1, 9) may also be provided, which can be referred to, for example, as a "Transceiver Bus Multiplexer" ("TBM"). For example, a CAN controller 30-1 (Fig. 9) can be connected to different transceivers 10-1, 10-2 or TSS 100 (see also Fig. 14) via the TBM 200.

[0116] For example, the principle according to the disclosure can be used in all CAN variants (e.g., CAN CC, CAN FD, and CAN XL). In CAN XL communication, for instance, a conflict is resolved where both the sending and receiving bus participants signal a change in transceiver modes differently using PWM symbols via a CAN_Tx pin. This change in transceiver modes using PWM symbols is taken into account in some examples according to the disclosure.

[0117] In total, using the principle according to the disclosure, for example, three different modules can be provided, which in further R.414641

[0118] - 20 -

[0119] Examples that can be flexibly combined are: A) CAN controller 30-1 , B) TSS 100, C) TBM 200.

[0120] Fig. 12 shows a block diagram according to further examples. Elements E1, E2, and E3 each symbolize a CAN controller according to the disclosure, for example, at least similar to the bus controller 30-1 according to Fig. 1 and / or Fig. 9. Element E4 symbolizes a device or a TSS 100 according to the disclosure, and element E5 symbolizes a CAN transceiver. Element E6 according to Fig. 12 symbolizes a digital domain, and element E7 symbolizes an at least partially analog domain.

[0121] The CAN controllers E1, E2, E3 each exhibit at least one functionality of conventional CAN controllers known per se, in that they each send a CAN_Tx signal and receive a CAN_Rx signal and can, for example, process CAN data frames.

[0122] In addition, in some examples, the CAN controllers E1, E2, and E3 can each be configured to receive an input signal Group_Tr, indicating whether a CAN controller from the group E1, E2, and E3 is currently sending a frame. The input signal Group_Tr can, for example, correspond to signal S-1 according to Fig. 1 and be generated, for example, by the TSS E4, e.g., on corresponding IS_Transmitter signals from the CAN controllers E1, E2, and E3. These signals are used by the CAN controllers E1, E2, and E3 to signal to the TSS 100 whether or not they are currently sending a CAN data frame (see also block 332 according to Fig. 5). For example, the CAN controllers E1, E2, and E3 (Fig. 12) send their respective IS_Transmitter signals to the TSS E4, which then generates the Group_Tr signal and outputs it to the CAN controllers E1, E2, and E3.

[0123] For example, if CAN controller E1 is currently receiving and another CAN controller E2 from the group E1, E2, E3 is transmitting, the receiving CAN controller E1 suppresses an ACK signal and, if applicable, a PWM signal based on the Group_Tr signal. The same applies to the other CAN controller E3. R.414641

[0124] - 21 -

[0125] As can be seen in Fig. 12, a controller interface E4a (e.g., at least similar to element 120-1 according to Fig. 1) for connecting the CAN controller E1 can thus have, for example, the following signals or signal connections: a) CAN_TxO, b) CAN_RxO, c) Group_TrO, d) IS_TransmitterO. As can also be seen in Fig. 12, a controller interface E4b (e.g., at least similar to element 120-2 according to Fig. 1) for connecting the CAN controller E2 can thus have, for example, the following signals or signal connections: a) CAN_Tx1, b) CAN_Rx1, c) Group_Tr1, d) IS_Transmitter1. The same applies, for example, to the further CAN controller E3 and the interface E4c.

[0126] Element E4d according to Fig. 12 symbolizes a transceiver interface, e.g. at least similar to element 110 according to Fig. 1, for connecting the transceiver E5. As can be seen from Fig. 12, the transceiver interface E4d can, e.g., have at least the following signals or signal connections: a) TxD, b) RxD.

[0127] Using the device or the TSS E4 according to Fig. 12, the multiple CAN controllers E1, E2, E3 can, for example, share the single transceiver E5, for example according to a time-division multiplexing principle or simultaneously or at least partially overlapping in time. In some examples, one TSS E4 can be provided per transceiver E5 (not shown in Fig. 12, see Fig. 14). The TSS E4 can offer one or more of the following features, for example: a) it provides the Group_Tr signal for the CAN controllers E1, E2, E3, or b) it emulates a CAN bus, at least temporarily, or c) optionally it enables communication between the groups E1, E2, E3, for example without a transceiver E5 connected to the TSS E4, or d) it enables data communication DK using the CAN_Tx, CAN_Rx or TxD, RxD signals between the components E1, E2, E3, E5 or the corresponding interfaces E4, E4b, E4c, E4d for the components E1, E2, E3, E5.

[0128] In this sense, Fig. 12 shows an example of how the three CAN controllers E1, E2, E3 share a CAN transceiver E5. The TSS E4, where the CAN signals are aggregated and evaluated, is located between the CAN controllers E1, E2, E3 and the CAN transceiver E5. R.414641

[0129] - 22 -

[0130] In some examples, the functionality of the TSS E4 according to Fig. 12 can at least approximately correspond to the functionality of the device 100 according to the disclosure.

[0131] The arrows a1, a2, a3 according to Fig. 12 symbolize control or

[0132] Configuration information or corresponding inputs of the TSS E4 for this purpose, by means of which a structure and / or operation of the TSS E4 can be influenced at least temporarily in some examples.

[0133] Arrow a1 symbolizes a generic VHDL parameter "Nodes_g", which specifies a number of controller interfaces, e.g., CAN controller connections, E4a, E4b, E4c. In some examples, Nodes_g can range from 0 to a predefined maximum value (here, 3 in this example). In VHDL, a "generic" is a constant whose value is only determined during circuit synthesis. For example, multiple instances of the E4 module with different values ​​for this generic parameter can be used simultaneously in an ASIC. In an implementation variant without a generic parameter, a number of devices, e.g., "TSSen", 100, with different numbers of connections, can be provided as an alternative or supplement. In some examples, the variant with the generic parameter Nodes_g has the advantage that only one circuit description needs to be managed, for example, maintained.

[0134] Arrow a2 symbolizes an optional connection activation input, e.g., labeled "Selected," where, for example, one bit per controller interface E4a, E4b, E4c can be set to determine whether that controller interface should be active or passive. If a controller interface is passive, it will have no effect on the outputs of the TSS E4 in some cases. The optional connection activation function can be used, for example, when the TSS E4 is used together with one or more TBM 200s (see Fig. 9).

[0135] In some examples, Fig. 12, the TSS E4 can optionally be switched to an "Internal" operating mode in which the connected CAN controllers E1, E2, E3 only communicate with each other, e.g. without using a transceiver E5, thus enabling, for example, bus emulation without a transceiver R.414641

[0136] - 23 - is feasible. In this optional "Internal" operating mode, for example, no transceiver E5 needs to be connected, and ACK signaling is not suppressed. The TSS E4 is switched to this operating mode, for example, by an input signal "Internal_Bus", see arrow a3. This operating mode can be used, for example, for software tests that can be performed independently of external devices. In this "Internal" operating mode, the TSS E4 always generates a "Group_Tr" signal with the value 0, so that the CAN controllers E1, E2, and E3 never suppress the CAN_Tx signal.

[0137] In further examples, Fig. 12, both the "Internal_Bus" and the "Selected" inputs, see arrows a2, a3, can either be controlled by a configuration register (then they can be set via software, for example), or they can be hardwired.

[0138] In some examples, Fig. 12, the CAN_Tx outputs of the CAN controllers E1, E2, E3, or the corresponding signals CAN_TxO, CAN_Tx1, CAN_Tx2 received by the TSS E4, are combined in the TSS E4 using an AND gate (not shown). The output of the AND gate then drives, for example, the TxD input of the transceiver E5 via the TxD output of the TSS E4, the transceiver interface E4d, and the TxD input of the transceiver E5. The TSS E4 forwards, for example, the RxD output of the transceiver E5 via the RxD input of the TSS E4 and its CAN_Rx[n] outputs to all CAN_Rx inputs of the CAN controllers E1, E2, E3. For the CAN_Rx[n] and CAN_Tx[n] pins or signals, the index "[n]" stands, for example, for the number of the CAN controller connection of the TSS E4, in this case 0 or 1 or 2.

[0139] In some examples, see Fig. 9, at least one TBM 200 may be provided, by means of which a CAN controller 30-1 can be connected to several transceivers 10-1, 10-2. In some examples, one TBM 200 may be provided per CAN controller 30-1, e.g., if the CAN controller 30-1 is to be connected to more than one transceiver 10-1, 10-2. In some examples, the TBM 200 may provide one or more of the following functions, for example: a) it connects a selected transceiver 10-1 or TSS 100 to the CAN controller 30-1, e.g., based on a configuration of the TBM 200, or b) forwards a signal IS_Transmitter R.414641.

[0140] - 24 - from the connected CAN controller 30-1, e.g. to a TSS 100 (details see Fig.13).

[0141] Fig. 13 shows an extension of the example from Fig. 12, namely how the three CAN controllers E1, E2, E3 share a first CAN transceiver E5a. Additionally, CAN controller E3 is connected to another CAN transceiver E5b via a TBM E8. During operation, CAN controller E3 can, for example, use either of the two CAN transceivers E5a or E5b.

[0142] The arrows a4, a5, a6 according to Fig. 13 symbolize control or configuration information by means of which a structure and / or operation of the TBM E8 can be influenced, at least temporarily, in some examples.

[0143] Arrow a4 symbolizes, for example, a generic VHDL parameter, e.g., "Buses_g", which specifies the number of transceiver interfaces E8a, E8b, i.e., how many (physical) bus interfaces the TBM E8 should have.

[0144] Arrow a5 symbolizes, for example, a generic VHDL parameter, such as "M_range_g", which defines the width of an "M_Select" input a6. For instance, M_range_g=3 for the parameter "Buses_g" (arrow a4) allows for a range of up to eight bus interfaces. Other encodings of M_Select (arrow a6) are possible in other examples. In some examples, the "M_Select" input a6 can be controlled by a configuration register and thus set via software. Alternatively, if M_Select is hard-wired in other examples, the TBM E8 can be omitted in some cases, and a CAN controller interface can be connected directly to the selected bus interface.

[0145] In some examples, Fig. 13, a CAN controller E3 can thus be connected via a TBM E8 to two or more transceivers E5a, E5b, ... or at least one TSS E4. As with the TSS E4, in some examples there are also two implementation variants for the TBM E8: either different TBMs can be used depending on the number of connections E8a, E8b, or, for example, only one TBM E8, where, for example, with a generic parameter a4, R.414641

[0146] - 25 - the number of connections can only be set during circuit synthesis, for example.

[0147] As can be seen in Fig. 13, the TBM E8 has an interface, i.e., a controller interface, E8c to a CAN controller E3 (where interface E8c is at least similar to, for example, identical to, interfaces E4a, E4b, E4c, see Fig. 12) and several transceiver interfaces, e.g., bus interfaces, E8a, E8b. In some examples, the bus interfaces E8a, E8b can be connected to a TSS E4 or a transceiver E5a, E5b. In other examples (not shown), it is also possible to connect several TBMs E8 in series, i.e., to cascade them.

[0148] When a bus interface E8b (Fig. 13) is directly connected to a transceiver E5b, in some examples the "ls_Transmitter" output remains open (not connected) and the "Group_Tr" input is wired to the logical 'O' level, e.g., ground potential. In other examples, the M_Select input a6 of the TBM E8 determines which bus interface E8a or E8b is active. For example, only one bus interface E8a or E8b may be active at any given time. In the example shown in Fig. 13, if the bus interface E8b to the transceiver E5b is active, the Select input a2 of the TSS E4, which is assigned to the TBM E4 (e.g., "Selected[2]"), can be switched to passive mode, since the TBM E8 cannot currently use its bus interface E8a to the TSS E4.

[0149] When a bus interface E8a (Fig. 13) of the TMB E8 is connected to a TSS E4, the signals "ls_Transmitter" and "Group_Tr" are looped through, for example, to / from the controller interface E8c (i.e., between the interfaces E8a, E8c), for example, to enable an exchange of the signals "ls_Transmitter" and "Group_Tr", in addition to the signals CAN_Rx, CAN_Tx, between the connected components E3, E4.

[0150] The following are further aspects and advantages of the principle according to the disclosure, which are at least temporarily present or may occur in some examples: a) a conventional, e.g. already existing, CAN controller can be extended to include the functionality of the bus controller 30-1 according to the disclosure, whereby, for example, comparatively minor adjustments need to be made; the adjustment can thus be easily R.414641

[0151] - 26 - can be inserted into any existing CAN controller, or b) Depending on the needs of an application, several TSS 100 units of different sizes (e.g., having a different number of controller interfaces 120-1, 120-2, ...) can be implemented, e.g., without changing an existing bus controller, e.g., a CAN controller, or e) Depending on the needs of an application, e.g., each CAN controller E1, E2, E3 (Fig. 13) can be connected via a TBM 200 to any number of TSS 100 units, ... or transceivers 10-1, 10-2, ..., e.g., without changing the CAN controller or the TSS 100 unit(s), or d) The method can also be used with SIC XL transceivers, e.g., or e) The modular concept provided by the principle according to the disclosure allows CAN controllers, TBMs, and TSS units to be individually verified, e.g., before they are interconnected as library cells in an ASIC, or f) An integrator of the ASIC can, for example, independently build arbitrarily complex structures from these modules, depending on the application.

[0152] The principle according to the disclosure can also be used to save costs, for example, by having two or more CAN controllers 30-1, 30-2, ... (Fig. 1) share a CAN transceiver 10, for example, if the CAN controllers 30-1, 30-2, ... are to be connected to the same CAN bus 20. On the one hand, this saves transceivers 10 in some examples, and on the other hand, it may also save pins of a microcontroller that, for example, has the CAN controllers 30-1, 30-2, ..., where these pins represent a bottleneck in some conventional approaches.

[0153] In some examples, it is provided that several CAN controllers connected to device 100 (Fig. 1) cannot signal an ACK to each other, at least temporarily ("local ACK"), e.g., by suppressing it temporarily as described above (e.g., block 374 according to Fig. 8). This allows a sender, for example, to determine whether a connection between transceiver 10 and the rest of the CAN network is still functioning, because an external ACK (e.g., from an external node or bus participant) is still receivable, even while the local ACK is suppressed. In particular, this ensures in some examples that no ambiguities arise from a local ACK potentially generated by a local CAN controller connected to device 100 (Fig. 1). R.414641

[0154] - 27 -

[0155] Furthermore, this ensures that in some examples a fault confinement function of the CAN protocol is fully functional. In addition, the sequence according to block 374 of Fig. 8 enables the use, and in particular correct switching, of SIC XL transceivers in some examples.

[0156] Further examples of suppressing (local) ACK signals and / or PWM signaling at a receiver's CAN_Tx output, as described in some examples, are provided below. To prevent a fault confinement function of the CAN protocol from being overridden by local ACK signaling, the dominant ACK bit sent by the receiver of a valid CAN data frame can be suppressed in some examples. Additionally, when using SIC XL transceivers, PWM encoding of the receiver's CAN_Tx output can be suppressed. Both (local ACK, PWM encoding of the CAN_Tx output) are suppressed in some examples only if the sender of the data frame is one of the CAN controllers 30-1, 30-2, ... (Fig. 1) with which the receivers share a transceiver 10. If the transmitter is an external CAN controller (not shown), or if it is connected to another transceiver 10-2 (Fig. 9), the (e.g.Local ACK signaling is not suppressed in some examples. The receiver should, for example, still be able to send an active error flag (consisting of dominant bits), e.g., if it detects an error in a received data frame.

[0157] To know when to suppress the local ACK and / or PWM encoding of the CAN_Tx output, each connected CAN controller E1, E2, E3 (Fig. 12) can provide an output signal, e.g., labeled "ls_Transmitter" (see also block 370 according to Fig. 8 and block 330 according to Fig. 5), indicating that this CAN controller is currently the sender of a CAN frame. In the TSS E4, an output signal, e.g., labeled "Group_Tr" (e.g., signal S-1 according to block 332 of Fig. 5), can be generated from the "ls_Transmitter" outputs or signals of the connected CAN controllers E1, E2, E3. This output signal is then active (e.g., logic 1) when at least one of the connected CAN controllers E1, E2, E3 is the sender of a CAN data frame. For example, multiple transmitters can be active at the beginning of a data frame R.414641

[0158] - 28 - e.g., until a CAN arbitration is resolved. For example, the TSS E4 sends the signal Group_Tr to all CAN controllers belonging to the group of CAN controllers E1, E2, E3 locally connected to the TSS E4. In some examples, if the CAN controllers E1, E2, E3 are active with their Group_Tr input and are not themselves the sender of a CAN data frame (e.g., because they did not start a data frame or because they lost the arbitration), they set the aforementioned control signal, e.g., designated "Rx_TSS", see also Fig. 1. It remains set, for example, until the CAN controller E1, E2, E3 detects an error in the received data frame or until the data frame ends. As long as Rx_TSS is set, the CAN_Tx output of the CAN controller E1, E2, E3 is held at logic "1", which corresponds to the recessive level on the CAN bus 20. This suppresses the local ACK and the optional PWM encoding of the CAN_Tx output in some examples.Optionally, this function of the control signal Rx_TSS can be enabled or disabled, for example, by a configuration bit of the CAN controller E1, E2, E3. Optionally, this function of the control signal Rx_TSS can be removed by a generic parameter of the CAN controller, for example, during circuit synthesis, e.g., if this function is not needed in a current ASIC. In some examples, the CAN controller E1, E2, E3 resets the control signal Rx_TSS upon detecting an error. Thus, in some examples, the CAN controller E1, E2, E3 can send an active error flag as a receiver.

[0159] Fig. 14 schematically shows a simplified block diagram according to further examples. Four bus controllers E10, E11, E12, E13, e.g., CAN controllers, are depicted, each connected to a multiplexer device, e.g., "TBM", E14, E15, E16, E17. Also depicted are four devices 100 according to the disclosure, e.g., "TSS", E18, E19, E20, E21, and four transceivers, e.g., CAN transceivers E22, E23, E24, E25. The configuration shown as an example allows a fully flexible, optional connection between each CAN controller E10, E11, E12, E13 and each CAN transceiver E22, E23, E24, E25, whereby the corresponding communication paths can be established by controlling the multiplexers E14, E15, E16, E17 and by controlling the TSS E18, E19, E20, E21. In some examples, with the configuration according to Fig. 14, several, for example all, CAN controllers E10, E11, E12, E13 can share the same transceiver (e.g., E22), or R.414641

[0160] - 29 - Two pairs of CAN controllers each share two different transceivers. The control of components E14, E15, E16, E17, E18, E19, E20, E21 can, in some examples, be carried out by software, e.g., arrows a2, a6 according to Figs. 12, 13.

[0161] In some examples, for instance, two configuration bits may be provided for each TBM E14, E15, E16 E17, e.g. for encoding four different multiplexer states, e.g. corresponding to the four outputs or transceiver or TSS connections of the TBM.

[0162] In some examples, five configuration bits may be provided for each TSS E18, E19, E20 E21, e.g. for the optional activation / deactivation of four different controller interfaces (in this case to the TBM) and the operating mode “Internal”.

[0163] The principle according to the disclosure allows, in some examples, the provision of a modular concept that enables, for example, ASIC integrators to assemble arbitrarily complex systems or configurations, such as applications, using multiple CAN controller modules 30-1, 30-2, ... as well as TBM 200 and TSS 100. Existing CAN controllers or CAN controller IP modules can be advantageously adapted with little effort to provide the corresponding functionality, e.g., element 30-1 (Fig. 1).

[0164] Further examples, Fig. 15, relate to a use 400 of the device 100 according to the disclosure, and / or the bus controller 30-1, 30-2, ... according to the disclosure, and / or the multiplexer device 200 according to the disclosure, and / or the system 1000 according to the disclosure, and / or the method according to the disclosure, and / or the product 40 according to the disclosure for at least one of the following elements: a) enabling 401 data communication between at least one bus controller and a transceiver, or b) extending 402 existing bus controllers, for example CAN controllers, or c) increasing 403 flexibility regarding connecting a bus controller to multiple transceivers, or d) providing 404 a modular concept for the bus controller and / or the device and / or the multiplexer device and / or the system, or e) R.414641

[0165] - 30 -

[0166] 405 enables individual verification of aspects of the bus controller and / or the device and / or the multiplexer device.

Claims

R.414641 - 31 - Claims 1. Device (100) for a transceiver (10) for a serial bus system (20), wherein the device (100) comprises: a transceiver interface (110) for connecting the device (100) to the transceiver (10), a plurality (120) of controller interfaces (120-1 , 120-2, ...) for connecting the device (100) to a plurality (30) of bus controllers (30-1, 30-2, ...) for the serial bus system (20), wherein the device (100) is configured to enable at least temporary data communication (DK) between at least one bus controller (30-1) of the plurality (30) of bus controllers (30-1, 30-2, ...) and the transceiver (10) (300).

2. Device (100) according to claim 1, wherein the bus system comprises one of the following types: a) Controller Area Network, CAN, for example Classical CAN, for example CAN CC, or b) CAN Flexible Data Rate, for example CAN FD, or c) CAN XL, or d) another type, for example based on at least one of CAN, for example CAN CC, or CAN FD or CAN XL, wherein for example the transceiver (10) is a CAN transceiver, for example CAN CC transceiver, or a CAN FD transceiver or a CAN Signal Improvement Capability, SIC, XL transceiver.

3. Device (100) according to at least one of the preceding claims, wherein the device (100) is configured to receive (310) and combine (312) respective transmit signals (TX-1, TX-2, ..., TX-M) from the bus controllers (30-1, 30-2, ...) and / or from at least one multiplexer device (200) via the controller interfaces (120-1, 120-2, ...), for example, a combined transmit signal (TX) is obtained, and output (314) via the transceiver interface (110) to the transceiver (10), for example, in the form of the combined transmit signal (TX). R.414641 - 32 - 4. Device (100) according to at least one of the preceding claims, wherein the device (100) is configured to receive a received signal (RX) from the transceiver (10) via the transceiver interface (110) (320) and to output (322) at least temporarily to at least one of the bus controllers (30-1 , 30-2, ...) and / or to a multiplexer device (200), for example to forward (322a).

5. Device (100) according to at least one of the preceding claims, wherein the device (100) is configured to receive respective transmitter information signals (IS-TX-1, IS-TX-2, ..., IS-TX-M) from the bus controllers (30-1, 30-2, ...) and / or from at least one multiplexer (200) via the controller interfaces (120-1, 120-2, ...) (330), wherein, for example, a transmitter information signal (IS-TX-1; IS-TX-M) from a bus controller (30-1) and / or from the at least one multiplexer (200) indicates whether the bus controller (30-1) and / or the at least one multiplexer (200) is currently a transmitter of a data frame, for example a CAN data frame, based on the received transmitter information signals (IS-TX-1; IS-TX-M) a first signal (S-1) to form (332), which indicates whether at least one of the bus controllers (30-1 , 30-2, ...) and / or the multiplexer unit (200) is currently a sender of a data frame, for example a CAN data frame, for example by means of an OR operation (332a) of the received sender information signals (IS-TX-1 ; IS-TX-M), and output the first signal (S-1) to the bus controllers (30-1) and / or the at least one multiplexer unit (200) (334).

6. Device (100) according to at least one of the preceding claims, wherein the device (100) is configured to at least temporarily perform internal data communication (DK) 1 ) between the bus controllers (30-1 , 30-2, ...) and / or at least one multiplexer device (200) or the at least one multiplexer device (200) to enable (342), wherein, for example, data communication (DK 1 ) does not have any information exchange with the transceiver interface (110) or with the transceiver (10). R.414641 - 33 - 7. Device (100) according to claim 6, wherein the device (100) is configurable (340) by means of a configuration information (CFG-1) and / or by means of a configuration signal (S-CFG-1) to enable internal data communication (DK). 1 ) between the bus controllers (30-1, 30-2, ...) and / or the at least one multiplexer device (200) to enable (342).

8. Device (100) according to at least one of claims 6 to 7, referring back to claim 5, wherein the device (100) is configured to perform, during internal data communication (DK 1 ) to output the first signal (S-1) to the bus controllers (30-1) and / or the at least one multiplexer unit (200) with a signal value (346) indicating that currently none of the bus controllers (30-1, 30-2, ...) and / or the multiplexer unit (200) is a sender of a data frame, for example a CAN data frame.

9. Device (100) according to at least one of the preceding claims, wherein the device (100) is configurable (350) by means of a configuration information (CFG-2) and / or by means of a configuration signal (S-CFG-2) to activate (352a) or deactivate (352b) at least one of the controller interfaces (120-1 , 120-2, ... , 120- M).

10. Bus controller (30-1) for a device (100) according to at least one of the preceding claims, wherein the bus controller (30-1) is configured to output a sender information signal (IS-TX-1) to the device (100) (370), wherein the sender information signal (IS-TX-1) indicates whether the bus controller (30-1) is currently a sender of a data frame, for example a CAN data frame.

11. Bus controller (30-1) according to claim 10, wherein the bus controller (30-1) is configured to receive a first signal (S-1) from the device (100) (372), wherein the first signal (S-1) indicates whether at least one of several bus controllers (30-1, 30-2, ...) connected to the device (100) and / or a multiplexer device (200) connected to the device (100) is currently a sender of a data frame, for example a CAN data frame. R.414641 - 34 - 12. Bus controller (30-1) according to claim 11, wherein the bus controller (30-1) is configured to set a control signal (Rx-TSS) (374) when a) the first signal (S-1) indicates that at least one of several bus controllers (30-1, 30-2, ...) connected to the device (100) and / or a multiplexer device (200) connected to the device (100) is currently a sender of a data frame, for example a CAN data frame, and when b) the bus controller (30-1) is not itself currently a sender of a data frame, for example a CAN data frame, and wherein, for example, setting (374) the control signal (Rx-TSS) comprises: setting (374a) a transmit signal (TX-1) of the bus controller (30-1) to a signal value associated with a recessive level of the bus system (20), for example until the control signal (Rx-TSS) is no longer set, for example reset (376).

13. Bus controller (30-1) according to claim 12, wherein the bus controller (30-1) is configured to reset the control signal (Rx-TSS) (376) when a) an error occurs in a received data frame, for example, when the bus controller (30-1) detects the error in the received data frame, and / or when b) the data frame has ended.

14. Multiplexer device (200) for at least one serial bus system (20, 20'), wherein the multiplexer device (200) comprises: a controller interface (210) for connecting the multiplexer device (200) to a bus controller (30-1) for the at least one bus system (20, 20'), wherein, for example, the bus controller (30-1) is configured according to at least one of claims 10 to 13; a plurality (220) of transceiver interfaces (220-1, 220-2, ...) for connecting the multiplexer device (200) to a plurality of transceivers (10-1, 10-2, ... ) for the at least one serial bus system (20, 20') and / or at least one device (100) according to at least one of claims 1 to 9, wherein the multiplexer device (200) is configured to at least temporarily establish data communication (DK) between the bus controller (30-1) and at least one, for example exactly one, transceiver interface (220-1 , 220-2, ...) the majority (220) of transceiver interfaces (220-1 , 220-2, ...) to enable (392). R.414641 - 35 - 15. Multiplexer device (200) according to claim 14, wherein the multiplexer device (200) is configurable (390) to enable at least temporary data communication (DK") between the bus controller (30-1) and the exactly one transceiver interface (220-1 , 220-2, ...) (392).

16. Multiplexer device (200) according to claim 14 or 15, wherein the multiplexer device (200) is configured for at least one transceiver interface (220-1) of the plurality (220) of transceiver interfaces (220-1 , 220-2, ...) to output a transmitter information signal (IS-TX-T) (396), for example to the at least one device (100), wherein the transmitter information signal (IS-TX-T) indicates whether the bus controller (30-1) is currently the sender of a data frame, for example a CAN data frame.

17. System (1000) comprising at least one of the following elements: a) a device (100) according to at least one of claims 1 to 9, or b) a bus controller (30-1) according to at least one of claims 10 to 13, or c) a multiplexer device (200) according to at least one of claims 14 to 16, wherein, for example, at least some components (100, 30-1, 200) of the system (1000) are designed as an integrated circuit, for example, an application-specific integrated circuit.

18. Method for a device (100) for a transceiver (10) for a serial bus system (20), wherein the device (100) comprises: a transceiver interface (110) for connecting the device (100) to the transceiver (10), a plurality (120) of controller interfaces (120-1, 120-2, ...) for connecting the device (100) to a plurality (30) of bus controllers (30-1, 30-2, ...) for the serial bus system (20), wherein the method comprises: at least temporarily enabling (300) data communication (DK) between at least one bus controller (30-1) of the plurality (30) of bus controllers (30-1, 30-2, ...) and the transceiver (10).

19. Product, for example vehicle (40) or robot or cyber-physical system, comprising at least one of the following elements: a) a R.414641 - 36 - Device (100) according to at least one of claims 1 to 9, or b) a bus controller (30-1) according to at least one of claims 10 to 13, or c) a multiplexer device (200) according to at least one of claims 14 to 16, or d) a system (1000) according to claim 17.

20. Use (400) of the device (100) according to at least one of claims 1 to 9, and / or of the bus controller (30-1) according to at least one of claims 10 to 13, and / or of the multiplexer device (200) according to at least one of claims 14 to 16, and / or of the system (1000) according to claim 17, and / or of the method according to claim 18, and / or of the product (40) according to claim 19 for at least one of the following elements: a) enabling (401) data communication (DK) between at least one bus controller (30-1) and a transceiver (10), or b) extending (402) existing bus controllers, for example CAN controllers, or c) increasing (403) flexibility with regard to connecting a bus controller (30-1) to multiple transceivers (10-1, 10-2), or d) providing (404) a modular Concept for the bus controller (30-1) and / or the device (100) and / or the multiplexer device (200) and / or the system (1000),or e) enabling (405) individual verification of aspects of the bus controller (30-1) and / or the device (100) and / or the multiplexer device (200).

Images