Accurate delayMicroseconds for 14.7456 MHz, 11.0592 MHz, 7.3728 MHz, 3.6864 MHz and 1.8432 MHz about mcudude_corefiles HOT 7 CLOSED

I'm always happy when I can help. Just give me some days and I can provide solutions for them. I will probably start with the smallest ones first. :) 👍

from mcudude_corefiles.

Cool, thank you! I think it's smart to start with the lower frequencies first, yes. These "weird" frequencies all add up to each other:

3.6864 MHz = 1.8432 MHz * 2
7.3728 MHz = 3.6864 MHz * 2
11.0592 MHz = 7.3728 MHz + 3.6864 MHz
14.7456 MHz = 7.3728 MHz

from mcudude_corefiles.

I should probably tell you that tomorrow I'm heading to China for a week (business trip). This basically means I'm not able to respond to your messages while I'm there.

However, my wife at work this evening, so I got plenty of time tonight 😄

from mcudude_corefiles.

Any news @Jackjan4? 🙂

from mcudude_corefiles.

Hi,

i'm very sorry for this super late response, but University really kicked in I was unable to really do some other stuff beside from that. However, i'm back at it again and hope that my help is still needed. :)
I already prepared some code that can be tested out. So if this issue is still up-to-date I will create a PR!

from mcudude_corefiles.

No worries! I'm just happy you're willing to contribute. It is voluntary work after all 🙂.

It would be great if you prepared some code for the different clock frequencies. Then I can test them all and provide you the results. Just bear in mind that the "automatic code inspection" (Travis CI) doesn't accept tabs and trailing white spaces after a code line.

from mcudude_corefiles.

See commit e11435e

from mcudude_corefiles.