⚠️ ETH and IPv4prot muxing fails when two access in the same cycle #13

New Issue

markus · 2022-10-31T16:51:36+01:00

markus commented

2022-10-31 16:51:36 +01:00

Two sources: HIGH-prio and LOW-prio. Current selection is LOW-prio.

Both request at the same time.

Data and tx_en from LOW-prio is latched -> first word is taken from there. Now, arbitration does its job and switches to high prio. All acks and data go here.

--> First byte is from LOW-prio source, rest is from HIGH-prio.

Two sources: HIGH-prio and LOW-prio. Current selection is LOW-prio. Both request at the same time. Data and tx_en from LOW-prio is latched -> first word is taken from there. Now, arbitration does its job and switches to high prio. All acks and data go here. --> First byte is from LOW-prio source, rest is from HIGH-prio.

markus added this to the TCP <-> Serial Bridge milestone 2022-10-31 16:51:36 +01:00

markus added the

bug

label 2022-10-31 16:51:36 +01:00

markus changed title from ~~ETH and IPv4prot muxing fails when two access in the same cycle~~ to ⚠️ ETH and IPv4prot muxing fails when two access in the same cycle

2022-10-31 16:52:01 +01:00

markus referenced this issue from a commit

2023-01-15 10:41:07 +01:00

eth+ipv4prot: Fix protocol arbitration

markus referenced a pull request that will close this issue

2023-01-15 10:42:24 +01:00

eth+ipv4prot: Fix protocol arbitration #18

markus modified the milestone from TCP <-> Serial Bridge to UDP <-> Serial Bridge

2023-01-21 20:27:47 +01:00

markus self-assigned this 2023-01-21 20:31:20 +01:00

Sign in to join this conversation.