unable to forward VLAN tagged ethernet packets via the PFE on demo_feature_L2_bridge_vlan

rares_o · ‎02-18-2025

Hello community,

I am trying to assess some of the PFE features on the Linux BSP while using the libfci, with no success. Hopefully someone can help.

Setup:
- board: S32G-VNP-RDB3 (S32G399A)
- software: LinuxBSP 43.0.0 + PFE Firmware 1.10.0
- PC0 connected to emac0 (P4)
- PC1 connected to emac1 (P5)

The problem:

I am trying to run the demo_feature_L2_bridge_vlan demo provided with the libfci which basically showcases the following:
1. untagged communication between 2 devices in the same network (PC0_NOVLAN and PC1_NOVLAN)
2. tagged communication between 2 devices in the same network (PC0_100 and PC1_100 - VLAN 100 or PC0_200 and PC1_200 - VLAN 200)

The first use-case I can successfully verify - sending a ping from the PC0 to PC1 (or vice-versa). Here is what happens:
- PC0 sends an ARP request asking for the MAC of PC2
- PC1 responds to the ARP giving with its MAC address
- PC0 sends the ICMP request
- PC1 responds with the ICMP reply

For the second use-case I can't see the packets being routed. PC1 does not respond to the ARP request sent by PC0. I have also tried sending hard coded packets (src and dst MAC/IP addresses of PC0 and PC1, basically doing the ARP job) with no success.

What have I done:

- Yocto build following the S32G3_LinuxBSP_43.0_User_Manual including the PFE SW and FW + flashing the SD card with the image (board is on SD card Boot mode)
- Configure the PC0 and PC1 ethernet interfaces to match the MAC/IP addresses of the demo configuration + VLAN when necessary (VLAN 100 or VLAN 200)
- Validated that the BSP default configuration of the SerDes/SJ switch configuration is correct
- Try to send packets between the PCs: pings or UDP packets (with hard-coded MAC/IP addresses)
- Verify that the ethernet packets sent to the S23G board are VLAN tagged

I need support in getting the second use-case running.

Thanks!

alejandro_e · ‎02-20-2025

Hello @rares_o,

Sorry for the late repose and thanks for the very detailed description of your problem. To have better context of your setup please provide the following information:

Which version of the Linux kernel are you using? BSP43 supports v6.6.52 and v5.15.167
Please share the output of the printenv command in the u-boot command line
Please share the changes you have done in the local.conf file for your Yocto setup.
If you are following a document to achieve this steps, please share the name of said documents.
Please share the Linux commands you are using to perform the test you listed.
Are you running a multicore setup?

Thanks in advance for the information.

rares_o · ‎02-21-2025

Hello @alejandro_e and thanks for the response.

- Which version of the Linux kernel are you using? BSP43 supports v6.6.52 and v5.15.167

v6.6.52

- Please share the output of the printenv command in the u-boot command line

Hit any key to stop autoboot: 0
=> printenv
baudrate=115200
board_rev=F
boot_mtd=booti
bootargs=root=/dev/ram rw earlycon loglevel=7
bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadimage; then run mmcboot; fi; fi
bootdelay=2
console=ttyLF0
eth1addr=00:04:9f:be:ef:00
eth2addr=00:04:9f:be:ef:01
eth3addr=00:04:9f:be:ef:02
ethaddr=f6:c8:38:ca:16:f1
fdt_addr=0x83000000
fdt_enable_hs400=fdt addr ${fdt_addr}; fdt rm /soc/mmc no-1-8-v; fdt resize;
fdt_file=s32g399a-rdb3.dtb
fdt_fixups=;
fdt_high=0xffffffffffffffff
fdt_override=;
fdtcontroladdr=ff891000
flashboot=echo Booting from flash...; run flashbootargs;mtd read Kernel ${loadaddr};mtd read DTB ${fdt_addr};mtd rea d Rootfs ${ramdisk_addr};${boot_mtd} ${loadaddr} ${ramdisk_addr} ${fdt_addr};
flashbootargs=setenv bootargs console=${console},${baudrate} root=/dev/ram rw earlycon;setenv flashsize 0x04000000;
hwconfig=serdes0:mode=pcie,clock=ext;pcie0:mode=rc;serdes1:mode=pcie&xpcs0,clock=ext,fmhz=100;pcie1:mode=rc;xpcs1_0: speed=1G,an=0
image=Image
initrd_high=0xffffffffffffffff
ipaddr=10.0.0.100
loadaddr=0x80000000
loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}; run fdt_override;
loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}
loadtftpfdt=tftp ${fdt_addr} ${fdt_file};
loadtftpimage=tftp ${loadaddr} ${image};
mmcargs=setenv bootargs console=${console},${baudrate} root=${mmcroot} earlycon
mmcboot=echo Booting from mmc ...; run mmcargs; if run loadfdt; then run fdt_fixups; ${boot_mtd} ${loadaddr} - ${fdt _addr}; fi;
mmcdev=0
mmcpart=2
mmcroot="/dev/mmcblk0p3" rootwait rw
netargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp e arlycon
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_c md tftp; fi; ${get_cmd} ${image}; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr } ${fdt_file}; then ${boot_mtd} ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then ${boot_mtd}; else ec ho WARN: Cannot load the DT; fi; fi; else ${boot_mtd}; fi;
netmask=255.255.255.0
nfsboot=echo Booting from net using tftp and nfs...; run nfsbootargs;run loadtftpimage; run loadtftpfdt;${boot_mtd} ${loadaddr} - ${fdt_addr};
nfsbootargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs rw ip=${ipaddr}:${serverip}::${netmask}::et h0:off nfsroot=${serverip}:/tftpboot/rfs,nolock,v3,tcp earlycon
pfe1_phy_addr=8
ramdisk_addr=0x90000000
script=boot.scr
serverip=10.0.0.1
stderr=serial@401c8000
stdin=serial@401c8000
stdout=serial@401c8000

- Please share the changes you have done in the local.conf file for your Yocto setup.

Those are the changes (specified in S32G3_LinuxBSP_43.0_User_Manual.pdf):
DISTRO_FEATURES:append = " pfe"
NXP_FIRMWARE_LOCAL_DIR = "/path/to/firmware/binaries/folder"

- If you are following a document to achieve this steps, please share the name of said documents.

I looked at most of the documents related to the PFE usage but information is spread around all of them, here are the main ones:

S32G3_LinuxBSP_43.0_User_Manual.pdf - build and flash

PFE_FCI_API_Reference.pdf - usage/internals

PFE_S32G_A53_LNX_UserManual.pdf - usage

- Please share the Linux commands you are using to perform the test you listed.

S32G board: nothing special, just running the libfci demos. For example: libfci_cli demo-feature-run --feature L2_bridge_vlan, then checking if the configuration is set via the libfci_cli <command>-print commands

PCs:
- ip: for changing the MAC and IP addresses of the network adapters
- vconfig: for configuring the VLAN of an interface
- for sending data:
- ping -I <my_interface> <destination_IP>
- python scripts using scapy (for the hard coded packets i previously mentioned)
- I also use wireshark to ensure the correct sending/receiving(when it works) of the packets

The list all the specific commands is pretty big, this is a summary of the main ones. Please let me know if you want more specific information about any of the steps in the configuration of interfaces, sending and checking of the packets or anything else.

- Are you running a multicore setup?

From what I know, no.

alejandro_e · ‎02-24-2025

Hello @rares_o,

Checking the release notes I can see there are several several issues with VLAN tagged ethernet packets [page 3 and 4, S32G PFE Firmware 1.10.0 Release Notes, Rev. 1.0.0 — 7 November 2024]:

Although they may not be directly related to the flow you are traying to use, what I would recommend is using an older version of PFE, in this case, for BSP43 the officially supported version of the PFE firmware is 1.8.0 [page 2, Linux BSP 43.0 Release Notes for S32G3]:

Can you try with this FW version and let me know if the problem persist?

Thanks in advance.

rares_o · ‎02-26-2025

I just double checked the compatibility of the BSP 43.0 with the PFE FW. Maybe you have an older version of the BSP 43.0 release notes but in the latest one, the PFE Firmware 1.10.0 is required:

Also the same "known issues" are present in the PFE Firmware 1.8.0 Release Notes as well:

I don't think this will solve the issue if this is the case. Do you still think it's worth flashing the older PFE FW?

alejandro_e · ‎02-27-2025

Hello @rares_o,

Thanks for the observation, there seems to be an update of the BSP43 release notes, just to confirm, which date is shown in the fist page of the file you have downloaded? In my local file I can see "11-Dec-2024" and in the online file I see "12-Dec-2024" (in which I see the same version you mentioned), considering this and the fact that you also pointed out that the same problems are present in version 1.8.0 I no longer recommend testing with an older version. Please allow me some more time to investigate possible know issues and I will come back to you once I have relevant information.

Can you share the revision of the PFE FCI API reference manual you as using to get the example?

Thanks

rares_o · ‎02-27-2025

For the Linux BSP 43.0 Release Notes the 12-Dec-2024 date is shown.
For the PFE FCI API i have the Rev. 2.6.0, but I mostly used it for the chapter where the features/demos are explained.

alejandro_e · ‎02-28-2025

Hello @rares_o,

Thanks a lot for the information. Yesterday I shared this issue with a colleague in the internal team to have a more in depth analysis , he has shared the following:

"

Could you ask the customer to use the following commands to configure a vlan-bridge to test first?

libfci_cli bd-add --vlan 200
libfci_cli bd-update --vlan 200 --ucast-hit FORWARD --ucast-miss FLOOD --mcast-hit FORWARD --mcast-miss FLOOD
libfci_cli bd-insif --vlan 200 --i emac0 --tag ON
libfci_cli bd-insif --vlan 200 --i emac1 --tag ON
libfci_cli bd-insif --vlan 200 --i emac2 --tag ON
libfci_cli phyif-update --i emac0 -E --promisc ON --mode VLAN_BRIDGE --bs NORMAL
libfci_cli phyif-update --i emac1 -E --promisc ON --mode VLAN_BRIDGE --bs NORMAL
libfci_cli phyif-update --i emac2 -E --promisc ON --mode VLAN_BRIDGE --bs NORMAL

Please ask the customer to use two PC to test ping communication. I have tested it in my setup with success.

"

Can you help me by testing those commands and sharing the result with me?

Thanks in advance.

rares_o · ‎03-05-2025

Ok so i made the VLAN bridge work, but not really as indented. Here is what I did:

1. Configured the SerDes as follows:

setenv hwconfig "serdes0:mode=pcie,clock=ext;pcie0:mode=rc;serdes1:mode=xpcs0&xpcs1,clock=ext,fmhz=125;xpcs1_0:speed=2G5;xpcs1_1:speed=2G5"

Based on the S32G3_LinuxBSP_43.0_User_Manual.pdf this configures the PFE0 on P4/P2 and PFE1 on P5:

2. Connected each PC to the following ports of the S32G3 board: P4 and P5

3. Configured the PFE with the configuration you send.

---

Now i am expecting the PFE0 and PFE1 VLAN bridge to be functional but it is still not working.
* If i configure the bridge to support non tagged messages between PFE0 and PFE1 it will work just fine.
But the good news are that the VLAN bridge between PFE1 and PFE2 (P3B) works fine.

This lead me to believe that the PFE0 is not correctly configured. I looked over the boot logs and indeed there are some warnings regarding PFE0. I attached below the logs of interest for PFE 0, 1 and 2:

s32cc_serdes_phy serdes@44180000: Using mode 4 for SerDes subsystem
s32cc_serdes_phy serdes@44180000: Stable RX detected on XPCS0 after 2 µs
, eth1: pfe0s32cc_serdes_phy serdes@44180000: Unstable RX detected on XPCS1
, eth2: pfe1, eth3: pfe2
Hit any key to stop autoboot:  0
=> printenv hwconfig
hwconfig=serdes0:mode=pcie,clock=ext;pcie0:mode=rc;serdes1:mode=xpcs0&xpcs1,clock=ext,fmhz=125;xpcs1_0:speed=2G5;xpcs1_1:speed=2G5
=> boot
switch to partitions #0, OK
mmc0 is current device
15482888 bytes read in 648 ms (22.8 MiB/s)
Booting from mmc ...
61499 bytes read in 7 ms (8.4 MiB/s)
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Using Device Tree in place at 0000000083000000, end 000000008301203a
   fixup: pfe1: update phy addr to 0x8
Failed to configure XPCS1_1
Failed to update XPCS1 for SerDes1

...

[    8.490864] pfeng 46000000.pfe pfe0 (uninitialized): fixed link full duplex 2500Mbps not recognised
[    8.507918] pfeng 46000000.pfe pfe0 (uninitialized): Subscribe to HIF0
[    8.514502] pfeng 46000000.pfe pfe0 (uninitialized): Host LLTX disabled
pfeng 46000000.pfe pfe0 (uninitialized): Enable HIF0
[    8.527438] pfeng 46000000.pfe pfe0 (uninitialized): setting MAC addr: 00:04:9f:be:ef:00
[    8.535626] pfeng 46000000.pfe pfe0 (uninitialized): PTP HW addend 0x80000000, max_adj configured to 46566128 ppb
[    8.545924] pfeng 46000000.pfe: IEEE1588: Input Clock: 200000000Hz, Output: 100000000Hz, Accuracy: 10.0ns
[    8.556072] pfeng 46000000.pfe pfe0 (uninitialized): Registered PTP HW clock successfully on EMAC0
[    8.565887] pfeng 46000000.pfe pfe0: registered
[    8.578490] pfeng 46000000.pfe pfe1 (uninitialized): Subscribe to HIF1
[    8.585071] pfeng 46000000.pfe pfe1 (uninitialized): Host LLTX disabled
[    8.591913] pfeng 46000000.pfe pfe1 (uninitialized): Enable HIF1
[    8.598004] pfeng 46000000.pfe pfe1 (uninitialized): setting MAC addr: 00:04:9f:be:ef:01
[    8.606180] pfeng 46000000.pfe pfe1 (uninitialized): PTP HW addend 0x80000000, max_adj configured to 46566128 ppb
[    8.616492] pfeng 46000000.pfe: IEEE1588: Input Clock: 200000000Hz, Output: 100000000Hz, Accuracy: 10.0ns
[    8.626585] pfeng 46000000.pfe pfe1 (uninitialized): Registered PTP HW clock successfully on EMAC1
[    8.636253] pfeng 46000000.pfe pfe1: registered
[    8.640910] pfeng 46000000.pfe pfe2 (uninitialized): Subscribe to HIF2
[    8.647480] pfeng 46000000.pfe pfe2 (uninitialized): Host LLTX disabled
[    8.654319] pfeng 46000000.pfe pfe2 (uninitialized): Enable HIF2
[    8.660419] pfeng 46000000.pfe pfe2 (uninitialized): setting MAC addr: 00:04:9f:be:ef:02
[    8.668588] pfeng 46000000.pfe pfe2 (uninitialized): PTP HW addend 0x80000000, max_adj configured to 46566128 ppb
[    8.678903] pfeng 46000000.pfe: IEEE1588: Input Clock: 200000000Hz, Output: 100000000Hz, Accuracy: 10.0ns
[    8.688997] pfeng 46000000.pfe pfe2 (uninitialized): Registered PTP HW clock successfully on EMAC2
[    8.698558] pfeng 46000000.pfe pfe2: registered
[    8.768636] pfeng 46000000.pfe: HIF0 started
[    8.773216] pfeng 46000000.pfe pfe0: configuring for fixed/sgmii link mode
[    8.780358] pfeng 46000000.pfe pfe0: Link is Up - 2.5Gbps/Full - flow control off
[    8.787987] pfeng 46000000.pfe: HIF1 started
[    8.795451] pfeng 46000000.pfe pfe1: PHY [stmmac-0:08] driver [Aquantia AQR113C] (irq=POLL)
[    8.803931] pfeng 46000000.pfe pfe1: configuring for phy/sgmii link mode
pfeng 46000000.pfe: HIF2 started
[    8.907320] pfeng 46000000.pfe pfe2: PHY [pfeng-emac-2:04] driver [Micrel KSZ9031 Gigabit PHY] (irq=POLL)
[    8.916998] pfeng 46000000.pfe pfe2: configuring for phy/rgmii-id link mode
[   13.023767] pfeng 46000000.pfe pfe2: Set TX clock to 125000000Hz
[   13.029391] pfeng 46000000.pfe pfe2: Link is Up - 1Gbps/Full - flow control rx/tx
[   13.916451] pfeng 46000000.pfe pfe1: Link is Up - 1Gbps/Full - flow control rx/tx

It seems that there is an issue with XPCS1. I don't know yet what does this mean, but I'll look into it. I would appreciate if you also have a look and provide a response.

alejandro_e · ‎03-05-2025

Hello @rares_o,

I was able to use P4 and P5, I had to change the jumper configuration of the SJA1110 (J189) to the following:

SW17: All ON

SW8: ON

Just as reference, this is the routing of the ports in the RDB3:

I focused on the network functionality, I did not configure the VLAN tags.

Linux logs with IP in both PFE1 and PFE0:

Auto Linux BSP 43.0 s32g399ardb3 ttyLF0

s32g399ardb3 login: root
root@s32g399ardb3:~# udhcpc -i pfe0
udhcpc: started, v1.35.0
udhcpc: broadcasting discover
udhcpc: broadcasting discover
udhcpc: broadcasting discover
udhcpc: broadcasting select for 10.112.102.145, server 10.114.0.140
udhcpc: lease of 10.112.102.145 obtained from 10.114.0.140, lease time 7200
/etc/udhcpc.d/50default: Adding DNS 10.13.2.34
/etc/udhcpc.d/50default: Adding DNS 134.27.69.4
root@s32g399ardb3:~# udhcpc -i pfe1
udhcpc: started, v1.35.0
udhcpc: broadcasting discover
udhcpc: broadcasting discover
udhcpc: broadcasting discover
udhcpc: broadcasting select for 10.112.102.37, server 10.114.0.140
udhcpc: lease of 10.112.102.37 obtained from 10.114.0.140, lease time 7200
Error: ipv4: Address already assigned.
RTNETLINK answers: File exists
/etc/udhcpc.d/50default: Adding DNS 10.13.2.34
/etc/udhcpc.d/50default: Adding DNS 134.27.69.4
root@s32g399ardb3:~# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether ea:40:4f:33:0b:88  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 55  base 0xe000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 82  bytes 6220 (6.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 82  bytes 6220 (6.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pfe0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.112.102.145  netmask 255.255.255.0  broadcast 10.112.102.255
        inet6 fe80::204:9fff:febe:ef00  prefixlen 64  scopeid 0x20<link>
        ether 00:04:9f:be:ef:00  txqueuelen 1000  (Ethernet)
        RX packets 11  bytes 2214 (2.1 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 42  bytes 6579 (6.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x46000000-46ffffff

pfe1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.112.102.37  netmask 255.255.255.0  broadcast 10.112.102.255
        inet6 fe80::204:9fff:febe:ef01  prefixlen 64  scopeid 0x20<link>
        ether 00:04:9f:be:ef:01  txqueuelen 1000  (Ethernet)
        RX packets 279  bytes 25237 (24.6 KiB)
        RX errors 0  dropped 5  overruns 0  frame 0
        TX packets 87  bytes 7661 (7.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x46000000-46ffffff

pfe2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:04:9f:be:ef:02  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x46000000-46ffffff

root@s32g399ardb3:~#

Please not that the u-boot error are still present:

NOTICE:  Reset status: Power-On Reset
NOTICE:  BL2: v2.10.7(release):bsp43.0_rc5-2.10.7
NOTICE:  BL2: Built : 08:17:37, Nov 26 2024
NOTICE:  BL2: Booting BL31


U-Boot 2022.04+gc01b3bf7b1+p0 (Nov 21 2024 - 14:00:36 +0000)

SoC:   NXP S32G399A rev. 1.1
CPU:   ARM Cortex-A53 r0p4 @ max 1300 MHz
Model: NXP S32G399A-RDB3
DRAM:  3.5 GiB
Core:  315 devices, 25 uclasses, devicetree: board
MMC:   FSL_SDHC: 0
Loading Environment from MMC... OK
s32cc_serdes_phy serdes@40480000: Using mode 0 for SerDes subsystem
pci_s32cc pcie@40400000: Configuring as RootComplex
pci_s32cc pcie@40400000: Failed to get link up
In:    serial@401c8000
Out:   serial@401c8000
Err:   serial@401c8000
Board revision: RDB3 Revision F
PCIe:   BusDevFun       VendorId   DeviceId   Device Class       Sub-Class
__________________________________________________________________________
pcie@40400000 RootComplex
|   `-- 01:00.00        0x1957     0x4300     Bridge device           0x04
Net:   eth0: ethernet@4033c000
Found PFE version 0x0101 (S32G3)
pfeng pfeng-base: Uploading CLASS firmware
pfeng pfeng-base: EMAC0 block was initialized
pfeng pfeng-base: EMAC1 block was initialized
pfeng pfeng-base: EMAC2 block was initialized
pfeng pfeng-base: Enabling the CLASS block
pfeng pfeng-base: PFE Platform started successfully (mask: 7)
s32cc_serdes_phy serdes@44180000: Using mode 4 for SerDes subsystem
s32cc_serdes_phy serdes@44180000: Stable RX detected on XPCS0 after 2 µs
, eth1: pfe0s32cc_serdes_phy serdes@44180000: Unstable RX detected on XPCS1
, eth2: pfe1, eth3: pfe2
Hit any key to stop autoboot:  0
=>
=> printenv hwconfig
hwconfig=serdes0:mode=pcie,clock=ext;pcie0:mode=rc;serdes1:mode=xpcs0&xpcs1,clock=ext,fmhz=125;xpcs1_0:speed=2G5;xpcs1_1:speed=2G5

Therefore in my setup (using the same hwconfig as you) the only blocker for P4 was the jumer/switch config:

Let me know if with this configuration you can solve your problem.

rares_o · ‎03-06-2025

Unfortunately this configuration does not work on my side. Changing the jumper position does nothing for me.
Just to make things clear, the non-tagged communication works fine on my side as well on pfe0 (with or without changing the jumper position).

alejandro_e · ‎03-06-2025

Hello @rares_o,

Sorry for not understanding correctly. I will share this information with the internal team again for them to analyze, I will get back to you once they have an update.

Thanks for your patience.

alejandro_e · ‎03-10-2025

Hello @rares_o,

My colleague suggested to try using Vlan 101.

Another method could be to configure the SJA1110 Firmware to allow Vlan tagged messages to go through, you can get the firmware customization environment from the GoldVIP SW package, in the AUTO-SW-PACKAGE-MANAGER:

If you don't have access to this package, please contact your FAE/NXP representative so he/she may be able to help you.

Once you get the SJA1110 Customization environment you can create a post in the Other-NXP-Products/ community so one of my colleagues with expertise in the topic may help you configuring the SJA1110 for VLAN messages.

Please let me know if you have any other question about this topic.

rares_o · ‎03-11-2025

That would be all for now then. I will try what you suggested and open a different discussion if needed. Thanks for your support!

alejandro_e · ‎03-11-2025

Hello @rares_o,

Thanks for letting me know the topic is over!

If you have any other problem or question you can always post a new topic.

Best regards.