Mistaken Sync interval timeout for calculation logMeanSyncInterval = -7
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Start in XilinxProcessorIPLib/drivers/axiethernet/examples/avb/xavb.c at line 392, then inspect how XAvb_ConvertLogMeanToDuration handles -7 for the 128-packets-per-second option. Confirm the timeout calculation no longer produces a zero multiplier or causes an immediate timeout for that sync rate.
Written by the indexing model from the issue text.
Description
Line 392 below subtracts 1 from the interval and multiplies by the timeout factor. However, for 128 packets-per-second, logMeanSyncInterval = -7 and XAvb_ConvertLogMeanToDuration converts -7 to 1. Then, when finally 1 is subtracted in line 392, a 0 multiplies the timeout factor. Ultimately, timeout always occur for this sync rate option.
- Dominant language
- HTML
- Stars
- 1.2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Xilinx/embeddedsw
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Xilinx/embeddedsw#388 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Xilinx/embeddedsw#385 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Xilinx/embeddedsw#374 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Xilinx/embeddedsw#287 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Xilinx/embeddedsw#235 ·
All issues in Xilinx/embeddedsw
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
espressif/esp-iot-solution#786 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100