How can I use the LLCE-CAN under the linux

[StanleyShen]

Hi Dear

I want to use the LLCE-CAN in BSP35 ,  and since  read the S32G2_LinuxBSP_33.0_User_Manual.pdf, I ses blow steps must be executed:

1. Download LLCE firmware
2. Unpack the package to a folder of your choice and locate the following files in subdirectory
   firmware/llce_bin/s32g2/bin/ghs/enablement, which are required by Yocto:
   • dte.bin
   • frpe.bin
   • ppe_tx.bin
   • ppe_rx.bin
3. Enable LLCE CAN feature and specify the location where firmware binaries can be found. You can copy the .bin files
   to a common firmware location (e.g. /path/to/firmware/binaries/folder) or use unpack subdirectory
   above directly. This step requires to add the following lines in <builddirectory>/conf/local.conf file.

DISTRO_FEATURES_append = " llce-can "
NXP_FIRMWARE_LOCAL_DIR = "/path/to/firmware/binaries/folder"​

Here are my questions:

1. How to obtain the LLCE firmware, I haver downloaded the the LLCE 1.0.4 via https://www.nxp.com/app-autopackagemgr/software-package-manager:AUTO-SW-PACKAGE-MANAGER is it correct?
2. After set the firm information to <builddirectory>/conf/local.conf, just compiling the kernel,or is it compiling the yocto project fully?
3. Do I need to set LLCE_CAN  config to enable in the kernel?
4. Who will run those bin files? M core or A core or LLCE-self?
5. Is it necessary for A and M cores to communicate during the use of LLCE-CAN

Thank you very much!

[StanleyShen]

Pls allow me to answer my own question:

1. How to obtain the LLCE firmware, I haver downloaded the the LLCE 1.0.4 via https://www.nxp.com/app-autopackagemgr/software-package-manager:AUTO-SW-PACKAGE-MANAGER is it correct?

Yes, with those files, the LLCE-CAN function can run normally.

After set the firm information to <builddirectory>/conf/local.conf, just compiling the kernel,or is it compiling the yocto project fully?

Only rebuild kernel is not OK, beacuse those bin files will install to {rootfs}/lib/firmware directory.

Do I need to set LLCE_CAN  config to enable in the kernel?

Yes, by default, those firmware are loaded by driver/mfd/llce_core.c, but device driver is missing.

Is it necessary for A and M cores to communicate during the use of LLCE-CAN

I am still a bit confused about this point, it seems that it isn't necessary for A and M cores to communicate during the use of LLCE-CAN and both A core and M core can setup the LLCE-CAN, but if I want to use LLCE-CAN with A core and M core  simultaneously, How?

Also, I have other question:

When I tried to confirm the LLCE function as blow:

the function was confirmed correctly, but the dmesg information was a bit strange

[    6.191030] llce_core 43ff8000.llce: Successfully loaded LLCE firmware
[    6.408370] llce_mb 43a00000.llce_mb: LLCE firmware version: GGEE_2A
[    6.408393] llce_mb 43a00000.llce_mb: LLCE firmware: logging support disabled
[    6.516508] random: systemd: uninitialized urandom read (16 bytes read)
[    6.540726] random: systemd: uninitialized urandom read (16 bytes read)
[    6.553088] random: systemd-journal: uninitialized urandom read (16 bytes read)
[    7.028696] random: crng init done
[    7.028714] random: 162 urandom warning(s) missed due to ratelimiting
[    7.467133] s32cc-dwmac 4033c000.ethernet eth0: PHY [stmmac-0:01] driver [Micrel KSZ9031 Gigabit PHY] (irq=POLL)
[    7.480378] s32cc-dwmac 4033c000.ethernet eth0: Enabling Safety Features
[    7.480520] s32cc-dwmac 4033c000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
[    7.480858] s32cc-dwmac 4033c000.ethernet eth0: registered PTP clock
[    7.481301] s32cc-dwmac 4033c000.ethernet eth0: configuring for phy/rgmii-id link mode
[    7.484358] 8021q: adding VLAN 0 to HW filter on device eth0
[   65.368085] llce_can 43ff8000.llce:llce_can0: LLCE FW error 53
[   65.368113] llce_can 43ff8000.llce:llce_can0 llcecan0: Advanced RX filter not added. Logging feature not available.
[   65.370492] IPv6: ADDRCONF(NETDEV_CHANGE): llcecan0: link becomes ready
[ 1384.057054] llce_can 43ff8000.llce:llce_can14: LLCE FW error 53
[ 1384.057084] llce_can 43ff8000.llce:llce_can14 llcecan14: Advanced RX filter not added. Logging feature not available.
[ 1384.062005] IPv6: ADDRCONF(NETDEV_CHANGE): llcecan14: link becomes ready

Why is the following information output and how can I modify it

[ 6.272311] llce_mb 43a00000.llce_mb: LLCE firmware: logging support disabled

[ 72.719488] llce_can 43ff8000.llce:llce_can0: LLCE FW error 53
[ 72.719515] llce_can 43ff8000.llce:llce_can0 llcecan0: Advanced RX filter not added. Logging feature not available.

[nxf92355]

Hi @StanleyShen 

Hope you are doing well

Q. if I want to use LLCE-CAN with A core and M core simultaneously, How?

A. Right now does not offer this possibility. The multi-host awareness is also planned for BSP37.

Q. Why is the following information output and how can I modify it

A. I think ghennadi_procopciuc answered of this. The advanced version of the firmware should be used to avoid it.

let us know if any query

Regards ,

Tushar

[StanleyShen]

Hi @ghennadi_procopciuc @nxf92355 

Thank you very much for you answer.

A. I think ghennadi_procopciuc answered of this. The advanced version of the firmware should be used to avoid it.

Does this mean we need to develop firmware ourselves, and does NXP have plans to upgrade this version?

[nxf92355 · Accepted solution]

Hi @StanleyShen 

No need to develop firmware yourself. LLCE FW is developed by NXP. There are two different LLCE FW, one is "enablement", and another is "advanced". CAN Logging feature needs advanced FW, So, the message will appear if the you are using enablement FW. but it didn't influence the function,you can just ignore it.

if you want advanced FW, you need to buy the FDK.

Regards ,

Tushar

[StanleyShen]

@nxf92355 

I see, thank you very much.

[ghennadi_procopciuc]

Hi @StanleyShen ,

This message lets you know that the firmware you are using does not include support for LLCE CAN logging:

Advanced RX filter not added. Logging feature not available.

Regards,

Ghennadi