Honored Contributor
Honored ContributorHello,
--- Quote Start --- originally posted by dave@Nov 5 2006, 04:01 AM i too tried the web server example and had similar problems... --- Quote End --- I am investigating the problem. The web server driver manages to initialize itself with DHCP but we have this hang after less than a minute repetitive ping operation. Cstc1 very kindly sent me his driver that I tested thursday and friday. Unfortunately I didn't manage to make it initialize itself with DHCP, but it keeps capturing packets on the network for many minutes without hanging. I couldn't test the ping yet. I will try with 'hard wired' ip address today. The most important difference between the two codes is that cstc1 has made packet sending and receiving a critical section with a semaphore. Another difference is that Cstc1 interrupt handling code is simply queuing a request to process incomming data, where the web server driver read in the packet while in the interrupt code. These two difference may explain why cstc1 driver is more stable. Though I have some doubts on its performance since it adds 20usec after reading each data out of the driver. Is that required ? The reason why it can't initialize with DHCP is also still unclear now. cstc1 driver is also very terse in the feedback on the link up/down state or stats. But for now we look for a working solution.
