MFR4310 commnication issue

[Makabaka]

Dear:

We have a project that uses MFR4310 and TJA1082 to communicate with  FlexRay nodes.When sending data, the receiving node will detect the phenomenon that a frame of data is sent repeatedly occasionally, and the repeated data frames are not fixed.

Example of data transmission mode: in one time interval, two frames of data with serial numbers 1 and 2 are first sent, then the serial numbers are added 1, and the data with serial numbers 3 and 4 are sent, and repeated successively.

So Data frames with serial numbers 1,2,3,4,5,6,7,8 are sent on the FlexRay bus.However, the receiving data will have sequence numbers of 1,2,3,3,5,6,7,8 or 1,2,3,4,5,5,7,8.

At present, only one board appears this problem, do not understand the cause of this issue. Please help to analyze it.

[lukaszadrapa]

Hi,

to recognize if it is related to receiver or transmitter: do you mean that MFR4310 is the node which receives wrong data? What can you see directly on the bus when it happens?

Thanks,

Lukas

[Makabaka]

Hi  Lukas:

I  think, there should be no problem with data transmitting and receiving.

I'm going to send four frames  in each time interval. And I will define the corresponding serial number in each frame of data, such as 400xxxxxx, 401xxxxxx,402xxxxxx, 403xxxxxx.

Grabs the bus data with device:

Normal data log:

....

400xxxxxx,401xxxxxx,402xxxxxx,403xxxxxx

400xxxxxx,401xxxxxx,402xxxxxx,403xxxxxx

400xxxxxx,401xxxxxx,402xxxxxx,403xxxxxx

.....

Abnormal data log are as follows:

400xxxxxx,401xxxxxx,402xxxxxx,403xxxxxx

400xxxxxx,401xxxxxx,402xxxxxx,402xxxxxx

400xxxxxx,401xxxxxx,402xxxxxx,403xxxxxx

after a period of communication,  402xxxxxx will be sent twice, and 403xxxxxx is lost.

Now I wonder if the message buff of MFR4310 was not updated to 403xxxxxx in time, so sent 402xxxxxx twice.

What do you think might cause this phenomenon? and which registers should I check?

Thanks

[lukaszadrapa]

Hi,

It really looks like the data 403xxxxxx come soon or late. Is there anything running on the MCU which can interrupt/delay loading the new data into the transmit MB?

What trigger the uploading new MB data (based on which you will update the content of the MB)?

Can you share the configuration of the transmit MB which cause this behavioral?

You mentioned that you are sending the MB data: 400xxxxxx, 401xxxxxx,402xxxxxx, 403xxxxxx. But on the bus is sometimes 400xxxxxx, 401xxxxxx,402xxxxxx, 402xxxxxx. So it means that you are sending this 4 MB data still around for testing purpose (so on the bus is following: 400xxxxxx, 401xxxxxx,402xxxxxx, 403xxxxxx, 400xxxxxx, 401xxxxxx,402xxxxxx, 403xxxxxx….)?

You are sending these different MB in different cycle (during 4 cycles) or slot (during one cycle)?

When you configure the MBCCFR[MTM] = 0x0 what is happening (this se the MB into the event transmission mode so it means that it will be sent only once)?

Thank you.

Regards,

Lukas

[lukaszadrapa]

Hi,

I'm trying to find someone who could help with this. But it's obsolete part which is already end-of-life, so I can't promise...

Regards,

Lukas