digitalPinToInterrupt on ATTiny841
3sigma opened this issue · 3 comments
3sigma commented
Hello,
On the following line you associate INT0 with PB2:
But on the ATTiny841, INT0 is on PB1. Did I miss something ?
Thanks,
Nicolas
SpenceKonde commented
And just a few days agpo someone asked why this version wasn't in board manager. It's stuff like this!!! Was wrong on both directions of pin mapping for the the x41, because the files had been based on the 84, and because Atmel's designers had been sniffing glue or something, the INT0 pin which was PB2 on the 84, was moved to the strictly worse PB1 for the follow-on product.
Thanks for reporting. We need a ton more people doing that.
3sigma commented
Thank you. Yes, strange to use one of the crystal pin for this interrupt...
SpenceKonde commented
Especially when the chip is a followon tp a chip that had it 9n a different
pin. M9re than anything I think what doomed Atmel to being bought out was a
lack of managers who were willing to walk the engineering floor wielding
whips to keep the engineers in line, and keep that darned dartboard that
they taped product package diagrams to in order to choose pinouts locked
up.
…____________
Spence Konde
Azzy’S Electronics
New products! Check them out at tindie.com/stores/DrAzzy
GitHub: github.com/SpenceKonde
ATTinyCore: Arduino support for almost every ATTiny microcontroller
Contact: ***@***.***
On Thu, Jul 13, 2023, 03:43 Nicolas Gachadoit ***@***.***> wrote:
Thank you. Yes, strange to use one of the crystal pin for this interrupt...
—
Reply to this email directly, view it on GitHub
<#791 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTXEW63RKWSA7LTQES7TB3XP6RJFANCNFSM6AAAAAA2IOPN4E>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>