xCheckLoopback
Market leading real time kernel for 40+ microcontroller architectures
Brought to you by:
gaurav-aws,
rtel
Hi Marty, the official drivers for FreeRTOS+TCP can be found at github/aws.
I have occasionally posted newer versions of the drivers, either because they were better optimised, or they contained new features. Also in these drivers, I introduced a generic handler of the PHY, call common/phyHandling.c
xCheckLoopback
was one such features: it adds a simple loop-back device. It makes self-testing very easy:I hope that one day the drivers will be merged.
I'm attaching FreeRTOS_loopback.zip which contains the adapted FreeRTOS_ARP.[ch]
Allso attached a simple self-test with 2 UDP sockets.
Thanks. I had a copy of the xCheckLoopback code from a forum post that is working for me. My primary goal with this request was to see if the FreeRTOS_ARP.[ch] code in this repo could be udpated (or the dependency could be removed from the Zynq port in this repo).
I am managing my project with SVN, and was hoping to be able to use an SVN external to pull in all of the FreeRTOS-Plus code without modificaition, but that requires the Zynq port code and the FreeRTOS-Plus-TCP code in Source Forge to be compatible with eachother.
All I can ( and will ) do is propose my changes to the AWS/FreeRTOS team, and hope that it gets approved to be included into the official release.
Understood. Hopefully everthing goes smoothly. Thanks.
Quick update, it looks like the latest FreeRTOS+TCP Network Interface code in 10.3.0 removed the xCheckLoopback function. I can't speak to the need to put it back, but this at least resolves this issue since it no longer depends on an undefined function.
For those who get here, looking for the latest
xCheckLoopback()
, please find it attached. It has two modifications, one forFreeRTOS_ARP.c
and one forFreeRTOS_ARP.h
.It must be called from the
xNetworkInterfaceOutput()
function:All packets that have the local MAC-address as their destination, will be answered by the own IP-task.