You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the stack for a TP/IP coupler using an RP2040 and a W5500. I have managed to get the coupler to work, however in order for the ethernet frame to be sent, I've had to modify the check for frame length in cemi_frame.cpp.
Previous code on line 371 if (_length != 0 && _length != (addInfoLen + apduLen + NPDU_LPDU_DIFF + 2))
New code if (_length != 0 && _length != (addInfoLen + apduLen + NPDU_LPDU_DIFF + 3))
On my system the frame is never valid with the original code. Is this being used elsewhere that in a TP/IP couple scenario ? And why would the check for frame length be different in another scenario ?
The text was updated successfully, but these errors were encountered:
I am using the stack for a TP/IP coupler using an RP2040 and a W5500. I have managed to get the coupler to work, however in order for the ethernet frame to be sent, I've had to modify the check for frame length in
cemi_frame.cpp
.Previous code on line 371
if (_length != 0 && _length != (addInfoLen + apduLen + NPDU_LPDU_DIFF + 2))
New code
if (_length != 0 && _length != (addInfoLen + apduLen + NPDU_LPDU_DIFF + 3))
On my system the frame is never valid with the original code. Is this being used elsewhere that in a TP/IP couple scenario ? And why would the check for frame length be different in another scenario ?
The text was updated successfully, but these errors were encountered: