megaTinyCore in combination with ATtiny_PWM library on a 1614 issue

[pzw001]

Hello all,

Not sure where to ask this question, since I am not sure if it is bad / old / deprecated code in the library.

What I am trying to do is to use the ATtiny_PWM library on the 1614 . When compiling any example I get the error
/var/folders/xc/1l09vczs0wb18rv9qc39gpvm0000gn/T//cc9YbewD.ltrans0.ltrans.o: In function ATtiny_PWM::ATtiny_PWM(unsigned char const&, float const&, float const&)':
:(.text+0xc22): undefined reference to __PeripheralControl'

I searched all over the place, but cannot find anything referring to this error. Maybe I am just very bad at searching! ;-)

Since the author of the library has archived all his repositories, I have no good way to contact him. So I am hoping that someone here can help out..

The whole reason why I was looking at that library is because I need to generate a frequency in the range of 500-800kHz on a pin. Maybe there is another way to accomplish this. I do not need PWM, just a frequency control with a duty cycle of 50%.

Thanks for your time!

[hmeijdam]

Is it this library?
https://github.com/khoih-prog/ATtiny_PWM
That seems to be archived and not recently maintained.

I quickly tried I am using a portable version of V1.8.19 of the Arduino IDE and the examples compile fine for the 1614.
They fail for the 1604 and the 1624 because the library wants to use TimerD, which only the 1614 has.

[hmeijdam]

And you may want to have a look at the TCA0Demo sketches that are in the examples section of Megatinycore. Especially TCA0Demo2.ino

And the associated readme

[pzw001]

Thanks for checking. I just tried it in a clean 1.8.19, and indeed it compiles.
So it looks like something changed. I tried it previously in 2.3.4, but no luck.

I will checkout the suggested sketch. :-) Maybe it solves all my issues in a very easy way!

Thanks again.

[pzw001]

I decided to abandon the usage of the ATtiny_PWM library and just use some of the code out of the example.
Also, since it compiles in 1.8.19 but not in 2.3.4, I assume it is a Arduino core change which is causing this, nothing to do with any of the libraries / board definitions I am using.

Thanks for your time..!

[hmeijdam]

I think that is the better choice, as then you also will also learn about using the hardware more directly. At the cost of a steeper learning curve, you will gain more flexibility to tweak and tune your solution.