Hi
We are developing using S32G, but we have found that CANFD with BRI bit seems to be unusable. How can I configure it to work properly
BSP Version is 35 and 38
Bring up can0 as blow:
CANoe setting(BRI is selected):
Candump can0 has no output and the number of TXs has not changed at all
and the number of interrupts has not changed
Once BRS is not selected, candump can receive data normally
Thank you
Hi,
We might not be understanding the behavior you are seeing. We understand that there is no problem with CAN-FD under BSP35.0. We see the following behavior from our side:
In which we previously enabled can0 and can1 with the following configurations:
We see the following information being sent under the CANBus:
In which it is shown that the BRS bit is equal to 1 and the data bitrate change is also seen.
We may be misunderstanding your setup. If so, we apologize.
Please, let us know.
Hi Daniel
Thanks for you replay.
As you said, from S32G to outside, the CAN FD communication with BRS bit is OK
# when we use cansend the 123##1112233 (means CAN FD frame, flags = CANFD_BRS, len = 3)
# the CANoe revice the data correctly as blow
But on the other hand, send the CAN FD with BRS bit from CANoe to S32G,
it seems that an error occured.
(at this moment, the CAN data has been send to S32G was confimed by oscilloscope and
just as the before thread, interrupt was not increase)
Could you pls confirm the case that S32G receive CAN FD data with BRS bit set?
Thank you
Hi,
We may be misunderstanding the request, but we have confirmed that we can send and receive CAN FD frames with BRS bit enabled.
The situations you may be seeing is the can bit timing itself. Since we are using S32G as our transmitter and receiver, the can bit timing remains the same. Since you are using an outside tool, you should either reconfigure the tool to have the same can bit timing as S32G or viceversa.
Please, let us know.
Hi Daniel
Thanks for your support
After setting the simple-point of S32G and CANoe to the same value, both parties can communicate with each other.
But when using FlexCAN and LLCECAN, I found the following content displayed on the driver layer (not affect functionality yet). Can you tell me why this phenomenon occurs
Hi,
For the LLCE messages, it is related to the FW being used under LLCE which is a Standard LLCE-FW version. The Standard version does not provide the features are shown under your console.
As for the FlexCAN, which configurations did you apply to them? The ones that start providing those messages. It seems that the channel was configured incorrectly, hence the error.
Please, let us know.