Question about S32G3 LLCE CAN2Eth function.

[SongShizhe]

Hi:

    I have completed the CAN2eth function by EB Studio.  On the A-core side, data can be dumped from pfe2. But timestamp in acf-can message is always 0x0.   How to get runtime data of avtp_timestamp  in acf-can message?

[S9527Y]

您好

我现在也在使用EB Tresos做CAN2ETH的内容，将CAN数据发送给A核，我阅读了您上传的A核日志，我看里面A核是作为PFE的Slave，请问是由M核来作为PFE的Master吗，这种实现方式有什么可以参考的示例吗，M核只将CAN数据发送给A核，M核的PFE需要怎么进行配置呢

[SongShizhe]

Hi,

Thank you for your reply. According to your suggestion, the code is being modified.

I also have another issue.

In my development, RX/TX frames of about five CAN channels including  be routing to ethenet using CAN2Eth feature.

Only  one routing table with large buffer size and number referenced by CanAdvancedFeature for all CAN frames routing to ethernet.

In test, four CAN channel is connected by VN1640A device.  On one channel, only one frame(0x572)is as input, the busload is low.

Dump pfe2 interface,   data loss is found.   What's the reason?  Any suggestion?

[Daniel-Aguirre]

Hi,

Thanks for your feedback. We understand that the original request was fulfilled, is this correct?

As for the last inquiry, since this does not relate to NXP example codes we might be unable to reproduce the outcome you are seeing. Can you also confirm if this is a custom board?

FoWe can recommend opening a ticket under the NXP online services, since again we don't seem to be able to reproduce the respective outcome, nor we have the required setup. We do apologize.

Please, let us know.

[Daniel-Aguirre]

Hi,

Can you let us know which LLCE version are you using? Also, we understand that the available example for CAN2ETH uses only the M7 core, for which we understand that this is a custom application, is this correct?

Under the A core, which BSP are you running? Can you help us sharing the respective log from the A core?

Please, let us know.

[SongShizhe]

Q:Can you let us know which LLCE version are you using? Also, we understand that the available example for CAN2ETH uses only the M7 core, for which we understand that this is a custom application, is this correct?

A: LLCE version is S32G_LLCE_1.0.7.  My development is a custom application.

Q:Under the A core, which BSP are you running? Can you help us sharing the respective log from the A core?

A:  The respective log is attached.

The touting rules table  is  configured by EB tools which is no timestamps option.  I wondered which module or firmware fills the timestamps information of ACF-CAN messages? 

[Daniel-Aguirre]

Hi,

Thanks for your feedback. The following information is provided under the LLCE Firmware User Guide:

"

For formats that use timestamp, the timestamp is taken from the Timestamp Module as described in the S32G reference manuals. For CAN frames, the timestamp is generated by hardware and has high accuracy

"

Also, it seems that the following steps are provided on this regard:

"

Please check the steps:

1. choice the clock source， suggest customer to choose PFE. We do not provide API to modify it. so please enable CAN_TS_CNT_SEL and TS_ENABLE bits of TIMESTAMP_CONTROL_REGISTER

2. Enable PFE EthGlobalTimeSupport

"

Please, let us know.

[SongShizhe]

Hi,

Following your suggestion.

1.  Choose PFE as the clock source, enable CAN_TS_CNT_SEL and TS_ENABLE bits of TIMESTAMP_CONTROL_REGISTER;

2.  PFE EthGlobalTimeSupport had been enabled before.

Found that still no timestamps value in AVTP data.

Any other suggestions? 

Thank you.

[Daniel-Aguirre]

Hi,

Thanks for your feedback. Can you confirm that the timer was started? We see the following information under the LLCE-FW User Guide:

"Thus, the user has to select the timestamp source, enable the timestamp module in Timestamp Control Register and start the timer."

Also, the information provided before was not from the user guide itself, but from internal recommendations. We see that the recommended timer under the LLCE-FW User Guide is STM7:

"(recommended STM7 - clock driven XBAR_DIV2_CLK)"

Please, let us know.

[SongShizhe · Accepted solution]

Hi:

It works as CAN timestamp is enabled.