Hi Sergio
Thank you for your input!
You were right, there was another task using pbufs.
We re-initialized it every time a new network setting got applied (i.e. also
when a DHCP request was completed).
Sadly it every time took a new pbuf but didn't release the old one.
After fixing this the DHCP
Hello,
I changed my PHY from DP83848 in MII to LAN8720 in RMII. Initialisation in
code seems correct, and signals also (REFCLOCK...)
But I got a strange ping answer starts at 500ms, decrease to 1ms and roll
again.
I test my webserver and it is also very slow.
Hi folks,
I wrote a driver for the DM9000 Ethernet chip, and nowadays it is
missing the link state part. I feel reluctant to add it because I don't
really see a need for the stack/application to know the link state,
since all the devices I can imagine I'll be developing will be
permanently
Hi, this is the kind of problem I love to figure out and not have it
myself... ;^)
1) I would put a wireshark or equivalent to really see what is going on,
those text reports can be lots of non-related stuff. I guess packets
have an id number and so lost packets are detected, but I don't see that
Good to know!
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Hi pcu
I am also using the LAN8720 in RMII, together with an STM32F4 and FreeRTOS.
I also had an issue with lost packages. That was solved by a patch provided in
this list.
Have a look at the thread at
http://lists.gnu.org/archive/html/lwip-users/2013-09/msg00025.html
With this fix lwIP works
Hi,
First of all DP83484 has a few versions. I worked with the DP83484M and
DP83484C. I also worked with Marvel
Switch 88E6071
I found that all standard IEEE compliant PHY's have 32 registers and the
general purpose code supplied by ST
should work with all of them. However when I triad
Hi,
I found a different patch for ethernetif_input function
void ethernetif_input( void * pvParameters )
{
struct pbuf *p;
for( ;; )
{
if(xSemaphoreTake(Ethernet_xSemaphore,
emacBLOCK_TIME_WAITING_FOR_INPUT) == pdTRUE)
{
TRY_GET_NEXT_FRAGMENT:
p = low_level_input(
Hello Sergio,
On Thu, Jun 12, 2014 at 12:50:54PM -0300, Sergio R. Caprile wrote:
My question to the lwIP users: does anyone have the need to know the
link state ? Can you share why ?
This is obviously a great feature for DHCP, without link state you can
end up forever with the previous
Hi Sylvain, thanks for your input.
I don't see why that is a problem, as long as you don't change networks
you can keep your address for as long as your server assigned it and
there is no need to change it, even if your cable goes in and out
several times.
That would only be necessary when moving
pcu wrote
I changed my PHY from DP83848 in MII to LAN8720 in RMII.
Hi
Just to clear things out here, you are saying you didn't change anything in
the ethernetif layer and interrupt/DMA handling when you changed PHY? Just
based on the strange pattern on those wraparound delays it looks to me
My question to the lwIP users: does anyone have the need to know the link
state ? Can you share why ?
I do, for 2 reasons.
One: We have a panel LED for link/no link/connected to PC state. Often the
user can't see the jack or switch. Gets the 2 basic connectivity questions
answered quickly.
It may be very important for mantainance and during the instalation.
I usualy have one Led with different blinks for different link and
connection status and it helps a lot with support
Alain
Em 12-06-2014 12:50, Sergio R. Caprile escreveu:
Hi folks,
I wrote a driver for the DM9000 Ethernet
13 matches
Mail list logo
