delay() is inaccurate, averaging 500us too short.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- embedded-iot
Research direction
Start at the SAM/SAMD implementation of delay(n) and compare its millisecond-counter behavior with the linked AVR issue and commit. Done means elapsed time in the current millisecond is accounted for so delay(n) no longer averages about 500us too short.
Written by the indexing model from the issue text.
Description
Since delay(n) waits for n ticks of the millisecond counter, any time already elapsed in the "current" millisecond isn't taken into account.
This was fixed a long time ago for the AVR, but it didn't make it into SAMD/SAM
- Dominant language
- HTML
- Stars
- 91
- Forks
- 112
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 arduino/ArduinoCore-sam
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
arduino/ArduinoCore-sam#129 ·
-
Type: Bug USB: CDC serial
Difficulty 4/5 3-5 days Newbie friendliness 52/100
arduino/ArduinoCore-sam#153 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
arduino/ArduinoCore-sam#151 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
arduino/ArduinoCore-sam#147 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
arduino/ArduinoCore-sam#146 ·
All issues in arduino/ArduinoCore-sam
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zephyrproject-rtos/zephyr#121795 ·
Maintainers usually reply within 2 days
-
minstret adds an extra 0x4000 at every low-byte carry (regression from the XLEN parameter change)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
chipsalliance/Cores-VeeR-EH2#56 · 2 comments ·
-
2P IPC yaw feedback is never updated (axisYawF_2P)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NatLabRockies/ROSCO#510 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
new device support
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Koenkk/zigbee2mqtt#33344 · 1 comment ·
Maintainers usually reply within 1 day