This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

NDK not receiving frames with VLAN ID of 0

Hi,

We are observing a behaviour where a frame with VLAN ID =0 is not passed to higher layer by the NDK. It seems that NDK is dropping the frame with VLAN ID =0.

NDK version is: ndk_2_22_00_06.  Is there any setting which we need to do to receive this frame ?

Regards,

Robin

  • Hi Robin,

    Have you double checked your VLAN set up code?  Is VLANAddDevice returning success for ID 0?  Are you able to receive VLAN frames with other IDs?

    Also, just to check, are you using a VLAN enabled switch?

    Steve

  • Steven,

    this is still open for us. Now I was looking into other entries here on VLAN and the NDK docs.

    Now I can't find the 'client' example that supports the VLAN commands mentioned. Which package does contain that code?

    Also I understand that VLAN support needs to be supported by the NIMU driver. Where can I find an example NIMU driver for that? I do have the CPSW drivers but they do VLAN support in hardware so it is just a switch config option I think.

    In our case the NIMU driver does not care about VLAN tags. It just sends any received packets to the stack. With the current config VLAN tagged packets then just get dumped and do not reach any application. We do have certain packets here that have PRIO=0 and just need to reach the application...

     Would it be sufficient to do the prio mapping as mentioned here: http://e2e.ti.com/support/embedded/bios/f/355/p/230395/812045.aspx#812045

    Any comments welcome...

    Regards.

  • Steven,

    ok, I found the VLAN console stuff (just needs correct searching...).

    So I can include this in our code, it compiles and I can add a VLAN device manually. It does create the VLAN device although there is no special support in our driver. Now I need to test this...

    Regards,

     

  • added VLAN config to NDK setup and tested with VLAN tagged packets... working ok. we can close this now.

    Regards,