Interrupt-Problem

1
2
Page 2 of 2

Merlin

Administrator

Gender:
Age: 24
Posts: 1409
Registered: 03 / 2005

Subject:

Re: Interrupt-Problem

· Posted: 13.04.2021 - 16:53 · #9

Quote

The real point is actually to use the WizNet sockets (WIZNET memory), so that the CPU does not have to worry about the LAN traffic so quickly and wastes computing time waiting.

Exactly so, Thorsten, which is why I wrote it.

Harry

Moderator

Gender:
Location: zwischen Augsburg und Ulm
Age: 59
Posts: 2134
Registered: 03 / 2003

Subject:

Re: Interrupt-Problem

· Posted: 13.04.2021 - 16:55 · #10

Hello Merlin,

I have a great idea: Please write a ping for your driver.

Unfortunately, I don't know what the protocol for that looks like. I just know it's ICMP.

@Thorsten: Ich frag grad den Interruptpin so ab und dann reagiert das Programm nach Ablauf des Ping-Timeout. Wenn alles im Netz erreichbar ist (1..3ms Response-Time), wird auch der Touch schneller bedient und auch der richtige Interrupt funktioniert deutlich besser. Also ja, der Treiber wartet, bis der Client anwortet oder der TimeOut zuschlägt.

Harry

pvs-deck

PowerUser

Gender:
Age: 53
Homepage: pvs-deck.de
Posts: 1341
Registered: 02 / 2009

Subject:

Re: Interrupt-Problem

· Posted: 13.04.2021 - 17:15 · #11

Hello Harry,

the WizNet ICMP Source-Code and AppNote can find here

Ich konnte mich mit dem Thema noch nicht so richtig beschäftigen, zu viele andere Baustellen

Aber der nötige Source Code in C ist vorhanden.

Thorsten

Merlin

Administrator

Gender:
Age: 24
Posts: 1409
Registered: 03 / 2005

Subject:

Re: Interrupt-Problem

· Posted: 13.04.2021 - 17:49 · #12

Quote

I have a great idea: Please write a ping for your driver.

Unfortunately, I don't know what the protocol for that looks like. I just know it's ICMP.

It is actually fairly straightforward, but unfortunately I do not have the hardware to test is on these days. I did start to do it but had no need of it in the end and so did not complete it. I don't mind finishing the source if someone else can test...

miparo

Administrator

Gender:
Location: Germany
Age: 58
Posts: 959
Registered: 09 / 2007

Subject:

Re: Interrupt-Problem

· Posted: 13.04.2021 - 19:46 · #13

Quote by pvs-deck"]
[quote="Harry

...

@miparo:
Aber gibt es überhaupt einen Grund beim Wiznet auf Interrupts so schnell zu reagieren? Die haben intern doch den Speicher, ich denke da machen ein paar ms mehr oder weniger nichts aus.

Thorsten

Der dümmpelt auch nur im Hintergrund rum, bei TinaPrioLow.
Ich hatte das selbst so am laufen als Inet Radio mit Display und Touch.

Ob das Interrupt System so sein muss ist ne andere Sache , das war aber als der heilige Gral so erwünscht.Ich hätte es anders gemacht.

Zumal der wzTina eh alles alleine macht.

Harry

Moderator

Gender:
Location: zwischen Augsburg und Ulm
Age: 59
Posts: 2134
Registered: 03 / 2003

Subject:

Re: Interrupt-Problem

· Posted: 14.04.2021 - 10:19 · #14

Hello Merlin,

when you finish programming that, i will be happy to test it

.
If the ping does not wait for an answer or timeout, can I send several pings at the same time?

Do you have an example of how to use your driver?

Harry

Merlin

Administrator

Gender:
Age: 24
Posts: 1409
Registered: 03 / 2005

Subject:

Re: Interrupt-Problem

· Posted: 14.04.2021 - 10:29 · #15

Quote

when you finish programming that, I will be happy to test it

.
If the ping does not wait for an answer or timeout, can I send several pings at the same time?

Do you have an example of how to use your driver?

Yes, as many pings as you have sockets spare - one ping per socket. And yes I do have examples.

Harry

Moderator

Gender:
Location: zwischen Augsburg und Ulm
Age: 59
Posts: 2134
Registered: 03 / 2003

Subject:

Re: Interrupt-Problem

· Posted: 14.04.2021 - 13:47 · #16

That sounds very interesting and promising. Then I just have to think about how to manage multiple sockets on the input side.

Harry

1
2
Page 2 of 2

Interrupt-Problem

Registered users in this topic