Honored ContributorHi all!
I would like to know how payload pad removal works in the aLtera TSE IP. How does the TSE know the payload length if ethernet header field "length/type" carries a type info (e.g. 0x0800 = IPv4 type)? Thx
Honored ContributorThe addition/removal is for 32bit alignment, so the core itself doesn't care what length or type the packet is.
Honored ContributorI'm sorry but I don't understand what you mean.
Can you develop please? Thx JulienHonored ContributorHello J_Renauld,
I know it's almost a year ago, but did you or somebody else find out how pad removal works? Because in my case it doesn't work (alltough I set the PAD_EN bit) and in assumption with the Leightweight IP-Stack and TCP I think it is not nice, that after every Connection establishment the Client sends back another ACK, because he thinks that there was some data in the ACK of the Client becaus of padding. Best Regards, EleganHonored ContributorHm, I see no problems with LwIP and TSE. 32bit alignment flag is set in TSE options as it is also set in LwIP driver options.
Honored ContributorSorry Socrates, but I think here you mean something different.
I think you mean the two byte which TSE puts in front of the Ethernet-Header to achive a 32-bit alignment. In this case are the missing bytes meant, which are put at the end of the frame to achieve the minimum ethernet frame length of 64 byte.Honored ContributorOh sorry, I misunderstood that... Did You check LwIP thread?
