--- Quote Start ---
Hi ted!
what about the packet format which I have at this point? I have not sent "UDP packet" but just Ethernet packet without IP and UDP Encapsulation.
As far I understood in "UDP port to channel mapper" component, It also doing some operation concerning IP and UDP packet.
--- Quote End ---
If you care about the NIOS getting some traffic (i.e. so that the NIOS can continue to operate it's own IP stack), then you will need to craft your own "channel mapper". Basically you need to have some component figure out if a given packet is going to be routed to your custom component, or ignore it and send it through to the NIOS SGDMA for processing.
If you have reached the point where you don't care about the NIOS any more, then now would be a good time to remove the channel mapper, DEMUX, NIOS SGDMA etc. in order to avoid creating your own "channel mapper" which is probably not part of your long term final solution.
I wanted to mention that another way to accomplish this is to structure your own component with Avalon-ST sink and source ports, and connect the output of the TSE in series through your component to the SGDMA. i.e. have your component figure out if the packet gets consumed by your component, or if it is passed along to the SGDMA. Depending on the purpose and structure of your component, you could also simply have it pass-through all of the packets and "tap" the signals as they come through for your analysis and processing.
The UDP offload example is structured in a modular and extensible way, but yes, it is specific to UDP protocol processing.
Honored Contributor
