Wiznet812MJ UDP problem

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When I connected my Wiznet812MJ to atmega64p, everything is fine using tcp protocol. However, when I use UDP protocol, it seems not working.

I used Wireshark to see what happens.

It always display
who has 192.168.1.2? Tell 192.168.1.6
192.168.1.2 is at a4:ba:db:95:3a:e8
who has 192.168.1.2? Tell 192.168.1.6
192.168.1.2 is at a4:ba:db:95:3a:e8
who has 192.168.1.2? Tell 192.168.1.6
192.168.1.2 is at a4:ba:db:95:3a:e8
who has 192.168.1.2? Tell 192.168.1.6
192.168.1.2 is at a4:ba:db:95:3a:e8

and so on....So the data cant send out.

Note: 192.168.1.2 is the destination (my laptop IP)
192.168.1.6 is the IP of the Wiznet/Atmega.

when I'm using TCP, no problem at all. I can ping all the times.

what's seems wrong?

cs

I'm happy ytd, today, and tmr :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Is this doing ARP? Is the laptop running servers for ARP and DHCP?

It's more usual to connect both module and laptop to the same router and either by static IP allocation or DHCP for them to get different IP addresses at which point they can then communicate between the two.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes, it is on the same router. Yes, it was doing ARP.

I really don't understand, when the laptop replies with the mac address, why the Wiznet still keep on asking?

cs

I'm happy ytd, today, and tmr :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Someone has a similar problem like mine
(2010-6-23, Wiznet cant solve that problem yet?)
http://www.wiznettechnology.com/...

cs

I'm happy ytd, today, and tmr :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks clawson, problem solved! :)

It was due to timing issue...

cs

I'm happy ytd, today, and tmr :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Though I don't use WizNet's C code, I do use the SPI interface and both UDP and TCP. I don't know of a way for the host microprocessor to discover that the PHY link is down (no link light) via the 5100's registers. There would have to be a new I/O bit tied to a link LED output of the '5100, but that pulses, etc.

If anyone knows a good way, I'd like to know.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

A simple way is to use ping. Ping to a few known good servers, if ALL no reply, it means the PHY link is down.

cs

I'm happy ytd, today, and tmr :)