|Subject:||Re: [lwip-users] lwip stall|
|Date:||Wed, 8 Oct 2014 10:09:19 +0000|
Sometimes RBUS is set, sometimes not. I think this just depends whether i have broken into the code it when its in the middle of receiving some data. However, I *am* still receiving frames so I don't think there is any problem the receiving, even after the stall, the Rx Interrupt is firing,
I am beginning to think the problems I am having are with either something subtle about the driver, or the PHY itself (seems less likely) . I have traced the outbound tcp packets with print statements, the whole way through the ip later to inside HAL_ETH_TransmitFrame() and it looks as though the packet is dispatched - or at least up to this point, the HAL does not present any errors.
I am suspecting there is an error somewhere in the ETH_DMA that is not accounted for by stm's HAL, and the outbound packet is silently failing to send (I don't see it on wireshark).
One thing to note is that if I pause execution of the mcu as soon as the 'stall' happens, and wait a few seconds, then resume, things will partially recover, although it will stall again with retransmits from the python side 3-5 seconds later, but more packets do get through the stack.
Do you see similar behavior, and is your RBUS bit latched up when you get a stall?
Date: Wed, 8 Oct 2014 00:23:37 +0200
Subject: Re: [lwip-users] lwip stall
It seems you have similar problem as me (Re: [lwip-users] lwIP hangs after some data transferred). When the stack stalls, what value do you have in the DMASR register (EthHandle.Instance->DMASR)? Is the RBUS bit set?
_______________________________________________ lwip-users mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/lwip-users
|[Prev in Thread]||Current Thread||[Next in Thread]|