Lines Matching refs:frame
205 may be delayed by the reception of a high prio CAN frame. To
233 creates an appropriate error message frame. Error messages frames can
237 by default. The format of the CAN error message frame is briefly
265 The basic CAN frame structure and the sockaddr structure are defined
270 __u8 can_dlc; /* frame payload length in byte (0 .. 8) */
323 struct can_frame frame;
325 nbytes = read(s, &frame, sizeof(struct can_frame));
334 fprintf(stderr, "read: incomplete CAN frame\n");
338 /* do something with the received CAN frame */
342 nbytes = write(s, &frame, sizeof(struct can_frame));
351 struct can_frame frame;
353 nbytes = recvfrom(s, &frame, sizeof(struct can_frame),
356 /* get interface name of the received CAN frame */
359 printf("Received a CAN frame from interface %s", ifr.ifr_name);
369 nbytes = sendto(s, &frame, sizeof(struct can_frame),
376 bitrates for the arbitration phase and the payload phase of the CAN FD frame
378 kernel interfaces (ABI) which heavily rely on the CAN frame with fixed eight
388 __u8 len; /* frame payload length in byte (0 .. 64) */
410 The length of the two CAN(FD) frame structures define the maximum transfer
414 #define CAN_MTU (sizeof(struct can_frame)) == 16 => 'legacy' CAN frame
415 #define CANFD_MTU (sizeof(struct canfd_frame)) == 72 => CAN FD frame
475 The CAN filters are processed in per-device filter lists at CAN frame
540 sending the CAN frame is assumed to be unwanted and therefore
571 printf("got CAN FD frame with length %d\n", cfd.len);
574 printf("got legacy CAN frame with length %d\n", cfd.len);
577 fprintf(stderr, "read: invalid CAN(FD) frame\n");
588 been received from the socket a legacy CAN frame has been read into the
624 MSG_DONTROUTE: set when the received frame was created on the local host.
626 MSG_CONFIRM: set when the frame was sent via the socket it is received on.
662 The aligned payload 'frames' uses the same basic CAN frame structure defined
709 TX_SEND: Send one CAN frame.
732 RX_CHANGED: BCM message with updated CAN frame (detected content change).
743 and count. Starting the timer leads simultaneously to emit a CAN frame.
750 subsequent frame in frames. This is intended as usage simplification. For
763 TX_RESET_MULTI_IDX: Reset the index for the multiple frame transmission.
786 struct can_frame frame[4];
805 is activated directly - even without a former CAN frame reception.
809 CAN frame is stateless as state changes within the ival2 periode may get
816 data bytes of the first CAN frame contain the mask of relevant bits that
817 have to match in the subsequent CAN frames with the received CAN frame.
818 If one of the subsequent CAN frames is matching the bits in that frame data
820 Up to 257 CAN frames (multiplex filter bit mask CAN frame plus 256 CAN
823 /* usually used to clear CAN frame data[] - beware of endian problems! */
828 struct can_frame frame[5];
835 U64_DATA(&msg.frame[0]) = 0xFF00000000000000ULL; /* MUX mask */
836 U64_DATA(&msg.frame[1]) = 0x01000000000000FFULL; /* data mask (MUX 0x01) */
837 U64_DATA(&msg.frame[2]) = 0x0200FFFF000000FFULL; /* data mask (MUX 0x02) */
838 U64_DATA(&msg.frame[3]) = 0x330000FFFFFF0003ULL; /* data mask (MUX 0x33) */
839 U64_DATA(&msg.frame[4]) = 0x4F07FC0FF0000000ULL; /* data mask (MUX 0x4F) */
885 rcvlist_eff - list for single extended frame (EFF) entries
889 rcvlist_sff - list for single standard frame (SFF) entries
909 can_send - transmit a CAN frame (optional with local loopback)
921 - TX: Put the CAN frame from the socket buffer to the CAN controller.
922 - RX: Put the CAN frame from the CAN controller to the socket buffer.
1151 Note that a restart will also create a CAN error message frame (see
1157 arbitration phase and the payload phase of the CAN FD frame. Therefore a